Privacy Policy

Last updated: October 17, 2026

Murmur is an iPhone app for live transcription. It is developed and published by an independent developer, shown as the seller on the App Store ("we", "us"). This policy explains what data Murmur handles, where it goes and how long it is kept. Contact us at support@murmur-record.app.

1. Data stored on your iPhone

• Recordings and transcripts are saved in Murmur's storage on your device, protected by iOS file encryption. Depending on your iOS settings, they may be included in your iCloud or computer backups.
• Your OpenAI API key and the keys used for the live mirror are kept in the iOS Keychain, on this device only. They are not synced to other devices.
• Settings, such as languages, prompts and keywords, are stored on your device.
• Diagnostics (error codes, timings, device model, iOS and app versions) are stored on your device. They are never sent automatically. They leave your phone only if you choose to share a diagnostics file.

Exports (text, audio or backups) leave your phone only through the iOS share sheet, to a destination you choose.

2. Transcription with OpenAI

Murmur uses OpenAI's API with an API key you provide. Nothing is sent to OpenAI until you allow Murmur to send audio for transcription. After that:

• During a recording, audio is streamed directly from your iPhone to OpenAI for live transcription, together with the language, prompt and keywords you set.
• When you refine a recording, or if you turn on automatic refinement, the saved audio file is uploaded directly to OpenAI with the same settings and a short excerpt of the previous transcript for context.
• The connection test in Settings sends only your API key to OpenAI to check that it works.

These requests go from your phone to OpenAI and do not pass through our servers. OpenAI processes them as your API provider under your own agreement with OpenAI, and bills your OpenAI account. See OpenAI's privacy policy.

3. Live mirror (Pro)

The live mirror shows your transcript in web browsers that you pair with your phone. Only text is shared, never audio. Before any text leaves your phone, it is encrypted with keys that only your phone and your paired browsers hold (AES-256-GCM, with keys agreed using ECDH). Our relay passes the encrypted text along and cannot decrypt it.

To deliver the mirror, the relay processes:

• random identifiers for your share and recording, and hashed access tokens;
• timestamps, sharing status, and the number and size of encrypted messages;
• how many browsers are connected, and a label for each paired browser (by default the browser's name, which you can change).

Your IP address is used briefly to limit abusive traffic. Our relay does not store it.

How long it is kept:

• Encrypted transcript text is deleted about one hour after sharing ends, or after 90 minutes without activity plus one hour, and is never kept longer than 24 hours. Starting a new share deletes the previous one.
• Unused pairing requests expire within 10 minutes.
• A paired browser's access is removed after 30 days without use, or after 24 hours if you didn't choose to remember that browser.
• Removing the connection in Murmur revokes access and deletes the shared text.
• A pseudonymous identifier for your phone's sharing identity is kept so that your paired browsers keep working. Email us to have it deleted.
• Our hosting provider keeps short-term recovery copies of stored data as part of its service.

The relay keeps limited operational logs, such as request type, result and duration, for a sample of requests and for errors. These logs don't include transcript text, share identifiers or IP addresses.

Readers don't need an account. The reading page uses no cookies and no analytics. It stores display preferences in the browser and, only if the reader chooses to remember the browser, the credential needed to reconnect. Transcript text is not saved in the browser. A reader can still copy or save what they see, and revoking access cannot take back text already copied.

The relay runs on Cloudflare. See Cloudflare's privacy policy.

4. Subscription

Purchases are handled by Apple. We don't receive your name, Apple Account or payment details. To check that your Pro subscription is active, Murmur sends Apple's signed transaction information to our server, which confirms it with Apple. We keep the original transaction ID, product, subscription status and expiry date, and how many hours of sharing you used each month. We use this only to provide Pro, enforce the monthly limit, handle refunds and prevent abuse, and we delete it when it is no longer needed for those purposes.

5. Permissions

• Microphone: to record and transcribe.
• Camera: only to scan a QR code when pairing a browser. No photos or video are saved.

6. This website and email

murmur-record.app uses no cookies, analytics or tracking. Cloudflare, our host, processes basic request data such as IP addresses to deliver and protect the site. If you email us, we use your email address and message only to reply, and keep them only as long as needed.

7. Who receives data

We don't sell personal data. Data is processed only by these providers, for the purposes above:

• OpenAI: transcription, under your own API account.
• Cloudflare: hosting for the live mirror relay and this website.
• Apple: App Store distribution and payments.

These providers may process data in the United States and other countries. We may disclose information if required by law.

8. Your choices

• In Murmur you can delete a recording, delete only its audio, or delete all local data. Your API key is removed separately in Settings.
• You can stop sending audio to OpenAI at any time by turning off permission in Murmur.
• Deleting the app removes its data from your phone. iOS may keep Keychain items such as your API key, so remove the key in Settings first.
• To access or delete data held on our servers, email support@murmur-record.app. We will respond within 30 days.

9. Children

Murmur is not directed to children under 13, and we do not knowingly collect personal information from them.

10. Changes

If we change this policy, we will update this page and the date above. If a change significantly affects how your data is handled, we will also tell you in the app.