--- title: "Contact Mumr — support, privacy and security" description: "Contact Mumr at hello@mumr.app for support, bug reports, privacy requests, security disclosure and press. Independent developer, United Kingdom." canonical: "https://mumr.app/contact" language: "en-GB" last-updated: "2026-08-23T13:21:26+01:00" source: "https://mumr.app — Markdown rendition of the HTML page at `canonical`" --- Contact · One inbox · Answered by the developer # Contact One address for everything: [hello@mumr.app](mailto:hello@mumr.app). It reaches the person who writes the app, not a ticket queue. There is no contact form on this page for the same reason there is no Mumr account — nothing here stores what you send, so email is the honest channel. Last updated: 23 August 2026 · Mumr · London, United Kingdom The short version - Email **[hello@mumr.app](mailto:hello@mumr.app)** — support, bugs, privacy, security, press, all of it. - Replies usually land within **two to three working days** — one person, UK hours. - **Never send a recording, transcript or API key.** They are not needed, and we would rather not receive them. - Mumr is made by an independent developer in the **United Kingdom**; the Terms are governed by the laws of England & Wales. ## What to include The difference between a two-email exchange and a two-week one is usually four lines at the top of the first message. Whatever you are writing about, start with these: - **Mumr version and build** — Settings, then the version at the bottom of the General tab. - **macOS version** and whether the Mac is Apple Silicon or Intel. - **What you expected, and what happened instead.** - **Whether it reproduces** — every time, sometimes, or exactly once. | If you are writing about | Add this | | --- | --- | | A bug or a crash | The steps that reproduce it, and the audio devices in use (built-in mic, AirPods, an interface). Audio routing is behind most recording bugs. | | Missing or silent audio | Whether the mic track, the system-audio track, or both are affected, and which app the meeting was in. | | A summary that went wrong | Which backend produced it — Apple Intelligence, Anthropic, OpenAI, or a local CLI. Do not paste the summary itself. | | A privacy or data request | Nothing extra. Say what you want and read the note below first — the answer is usually shorter than you expect. | | A security issue | A description of the issue and how to reproduce it. Please give us a reasonable window before disclosing publicly. | | Press or a review | Your outlet and deadline. Screenshots and the icon are available on request. | ## Privacy and data requests Under the UK GDPR you can ask what personal data we hold about you, and ask for it to be deleted. The honest answer for almost every user is that we hold none: Mumr stores your recordings, transcripts and summaries only on your own Mac, and your API keys only in your macOS Keychain. There is no Mumr account and no Mumr database that could contain them. The one thing we do receive is anonymous, content-free analytics, which carries no name, email or device identifier that could be tied back to you — which also means we cannot look up "your" events to delete them. If you would rather send nothing at all, turn analytics off in Settings; the switch is local and takes effect immediately. Full detail is in the [Privacy Policy](https://mumr.app/privacy). ## Please do not send - **Recordings, transcripts or summaries.** Diagnosing a bug does not need them, and email is the wrong place for the most sensitive hour of your week. - **API keys.** No support question requires one. If you have already sent one, revoke it with your provider. - **Screenshots with meeting content visible.** Crop or blur first — the UI around the content is the part we need. ## Support that is faster than email Some questions already have written answers. The [FAQ](https://mumr.app/#faq) covers where recordings live, offline behaviour, supported macOS versions and the transcription engines. The [guides](https://mumr.app/blog) cover recording Zoom, Teams, Google Meet and webinars, and [Developers & AI agents](https://mumr.app/developers) documents the on-disk format and the `mumr://` URL scheme. ## Not using Mumr yet? Free on the Mac App Store. Records your calls locally, transcribes on-device, and writes the recap with the AI you choose. [Download for Mac](https://mumr.app/download) Free on the Mac App Store · macOS 15 or later ## FAQ ### How quickly will I get a reply? Usually within two to three working days. Mumr is one person in the UK, so replies land in UK hours and a bank holiday will stretch that. If a week passes with no answer, send the message again — occasionally one gets filtered. ### Is there a phone number or live chat? No. Email is the only support channel, and it is genuinely read by the developer. A single-person project with a phone line would be a phone line nobody answers. ### Where do I report a security vulnerability? Email [hello@mumr.app](mailto:hello@mumr.app) with a description and reproduction steps. Please allow a reasonable window to ship a fix through App Store review before disclosing publicly. In scope: the sandboxed macOS app and the files it writes, plus this website and the small service that serves it. Out of scope by construction: there is no account system and no backend holding user content, so there is nothing there to attack. ### Can you recover a recording I lost? No, and this is the sharp edge of a local-only design. Your recordings exist only in the folder you chose on your Mac — nothing is backed up to us because nothing is sent to us. If the folder is on a drive covered by Time Machine or iCloud Drive, your own backup is the place to look.