Privacy Policy

Effective: June 2026

tl;dr

Your audio recordings and the resulting transcripts are never stored by us, on any engine. Period.

The only data we keep at all is what's necessary to bill the no-key engine — your account email and per-request metadata (timestamp, audio duration, charge amount). No analytics, no telemetry, no tracking pixels.

Your privacy posture depends on which engine you pick in the app. Each one is described separately below so the trade-offs are explicit.

On-device engine

Audio is transcribed locally on your Mac by whisper.cpp. Audio never leaves the machine. There is no network call associated with the transcription itself.

The transcription model (~75 MB) is downloaded once from Hugging Face the first time you enable this engine. After that, no further network calls are made for dictation in this mode.

Bring-your-own-key (BYOK) engine

Audio is sent directly from your Mac to api.groq.com using an API key you provide, over an encrypted (HTTPS) connection. Nothing passes through any server we operate, because we don't operate one in this path.

Your Groq API key is stored locally in the macOS Keychain and never leaves the Mac it was entered on. We have no way to access it.

Groq's own privacy policy governs what Groq does with the audio and transcripts on their side. Refer to groq.com/privacy-policy for that.

No-key engine

Audio is sent from your Mac to our hosted service over an encrypted (HTTPS) connection. The service streams the audio through to Groq for transcription, returns the resulting text to your Mac, and discards the audio. We do not write the audio bytes to disk anywhere, and we do not write the transcribed text to disk anywhere.

What we DO store, and why

Where it's stored

All of the above lives in our Supabase project (managed PostgreSQL). Access is restricted to the unmute hosted services and the account owner.

How long

Billing records (top-ups, usage metadata) are retained for as long as your account exists, plus a reasonable period afterwards for accounting and tax purposes. You can request account deletion at any time — see "Deleting your data" below.

Payment data

Payments are processed by Dodo Payments, acting as Merchant of Record. They store your payment method details on our behalf — we never see your card number or full payment details. Their privacy policy applies to that data; see dodopayments.com/privacy.

Cookies, analytics, telemetry

The unmute app contains no analytics SDK, no telemetry SDK, and no crash-reporting SDK. The only outbound network requests the app makes are to whichever engine you've explicitly chosen — your own Groq endpoint, our no-key service, or the model download URL for the on-device engine.

This website (the one you're reading) is hosted on GitHub Pages and uses Google Fonts. Both of those are HTTP-served by their respective companies and may log standard server-side info (IP address, user agent). We don't set any cookies on this site.

Today's dictations cache (in-app)

The History tab in the app shows your recent dictations so you can copy them again or re-run them. These transcripts are stored locally on your Mac and are automatically cleared the next day. They never leave the device.

Deleting your data

To delete your no-key account and all associated billing records, email arpitpatel20121999@gmail.com from the email address on the account. We'll remove the records within a reasonable timeframe.

For the local cache (today's dictations, your Groq key in the Keychain), uninstalling the app removes everything stored on this Mac.

Children's privacy

unmute is not directed at children under 13. If you believe a child has created an account, please email us and we'll delete it.

Changes to this policy

We'll update this page when the product changes in ways that affect what data is processed. The "Effective" date at the top always reflects the latest version.

Contact

Email arpitpatel20121999@gmail.com with anything privacy-related.