murmur

Security at murmur.

The murmur apps have no server and no accounts, so there is no database of people to breach. This page answers what a security review usually asks, including what murmur does not have.

What leaves the device, and where does it go?

The audio of a take goes to the transcription provider the person chose, and its words go to the cleanup provider they chose, under their own key. Connections are encrypted, unless someone types an unencrypted http address and confirms it after a warning. Nothing reaches Eze Media LLC on its own. The update check and the provider list come from GitHub. The full list is on the privacy page.

Who processes the data?

Only the provider the person picks, under the terms they accepted when they made their key. Groq is the default, and any OpenAI-compatible service works, including a server on their own computer, where the audio never leaves it. Choosing a provider.

What is stored, and where?

History, settings, notes, and recordings waiting for a retry stay on the device. On Mac and Windows, the words in history are encrypted on disk by default, under a key held by the system's secure storage, and a switch beside Keep history turns that off. On iPhone, history stays in murmur's own storage, protected by the device. Notes stay plain files, and recordings and settings are protected by the device itself. Keep history sets how long they stay, down to not saving any words at all. Purchase records are kept by Eze Media LLC and Stripe, or by Apple on iPhone.

Is the microphone always on?

By default it stays ready while murmur runs on Mac and Windows, holding the last 300 milliseconds in memory so a first word is not cut off. Nothing is saved or sent until the hotkey is pressed. A setting closes the mic completely between takes, at the cost of a short wait on each press.

How are API keys stored?

Encrypted by the system: Electron's secure storage on Mac and Windows, and the Keychain on iPhone. Keys are never written to logs, and they go only to the address saved with them, or to wherever a provider redirects that address. murmur refuses a redirect to unencrypted http.

How are updates and licenses checked?

On Mac and Windows, updates come from murmur's GitHub releases, and Settings can make them automatic, ask first, or turn them off. Each download is checked against the checksum published with the release, and on Mac against the app's signature too. Pro license keys are ed25519 signatures checked offline, with no licensing server. On a Mac, an update already downloaded still installs if updates are turned off afterward.

What is signed on each platform?

The Mac and iPhone apps are. The Windows installer is not:

What certifications does murmur have?

None. murmur has no SOC 2 report, no ISO 27001 certificate, and has had no independent penetration test. With no server, most of what those cover does not apply, but they are not a claim murmur can make. What you can do instead is read the code: it is public under GPL-3.0 on GitHub.

What about HIPAA and similar rules?

They depend on the provider a person picks, since that is who handles the audio and text. The apps send nothing to Eze Media LLC, so it does not sign a business associate agreement. A team with those duties should use a provider that signs one, or a server of its own.

How is this website protected?

It is static apart from the download links, which count each click (the day, Mac or Windows, and which link sent it, never who) and forward to the file on GitHub. Visitors get no cookies, and there is no analytics service and no script but its own, under a strict content security policy. Checked 2026-11-05: A+ from Mozilla Observatory, Qualys SSL Labs, and securityheaders.com. A weekly check watches the live site.

How do I report a security problem?

Email security@murmurapp.app. You get a reply within 3 business days. The address is also in security.txt, and the security policy says what is in scope.

Last changed 2026-11-15.