Murmur Privacy Policy
Last updated: 2026-07-20
Murmur is a personal voice-capture app. This policy describes what data it handles and where it goes.
What Murmur collects
- Audio recordings you make when you tap record.
- Transcripts generated from those recordings, entirely on-device using Apple's on-device speech recognition. Audio is never sent to Apple, Murmur's developer, or any third party for transcription.
Both are stored locally on your device (and your Apple Watch, if you use watch capture) so an idea is never lost, even before it's transcribed or synced anywhere.
What Murmur does not do
- No analytics, crash reporting, or advertising SDKs are included in the app.
- Murmur has no backend server of its own and does not operate a database of user data. There is no Murmur account to create or sign in to.
- Your audio and transcripts are never used for tracking, and are never sold or shared with third parties for advertising.
Optional: syncing to a destination you own
In Settings you can choose one sync destination: Notion or Obsidian. Both are places you already own. Murmur never keeps a copy of your ideas on a server of its own, because it does not operate one.
If you don't choose a destination, capture still works fully — recordings and transcripts stay on your device and appear in the app's list.
Notion
Murmur uses Notion's OAuth flow to get permission to write to a database in your own Notion workspace. This is equivalent to connecting a Notion integration, not creating an account with Murmur — during authorization you choose which pages and databases the connection covers, and Murmur can reach nothing outside that grant.
- To let you pick a destination, Murmur asks Notion for the list of databases your grant covers and shows their names. Once you pick one, it reads that database's property schema (adding one property it needs) and looks up pages it previously created there, so an interrupted sync doesn't create a duplicate. It does not read the contents of your other pages.
- Syncing an idea uploads its audio file and transcript to your Notion workspace, where they become a page with the recording attached. This goes directly from your device to Notion's API; once there, the data is held by Notion under Notion's own privacy policy.
- OAuth token exchanges are brokered by a small, stateless server component that never stores your data or credentials — it only relays the initial authorization-code exchange and, periodically afterward, the refresh-token exchanges needed to keep your connection alive, with Notion.
Obsidian
You pick a folder inside your own vault, and Murmur writes each idea there as a Markdown note with the audio file saved alongside it.
- This is an ordinary file write on your device. Nothing is sent over the network, and no third party — including Notion and Murmur's developer — is involved.
- Murmur's access is limited to the folder you picked, and lasts only as long as you keep that folder selected in Settings.
- If your vault is stored in iCloud Drive or another file-sync service, that service will sync these files exactly as it syncs the rest of your vault, under its own privacy policy.
Your control over your data
- Delete any idea (audio + transcript) directly in the app at any time. In-app deletion removes the local copy only — if the idea has already synced, the Notion page or the Obsidian note stays where it is until you delete it there.
- Uninstalling the app removes all locally stored audio and transcripts.
- To revoke Murmur's access to your Notion workspace, remove the Murmur integration from your Notion workspace's connection settings at any time — independent of the app.
- To revoke Murmur's access to your Obsidian vault, deselect the folder in Settings, or choose a different destination. Notes Murmur already wrote are ordinary files in your vault and remain yours to keep or delete.
Contact
Questions about this policy can be sent via the support channel listed on Murmur's App Store listing.