Privacy Policy

Effective: October 2026

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

• Your sign-in email — required to associate prepaid credits with the right account.
• Per-request usage metadata — for each no-key transcription we record: a timestamp, the audio duration in seconds, the model used, and the resulting charge in cents. This is the minimum needed for accurate billing and for showing you a usage history inside the app. We do not record the audio or the transcribed text.
• Top-up records — every credit purchase generates a row with the amount, currency, payment provider event ID, and status. This is synced from Dodo Payments via signed webhook.

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.

Google Calendar and meeting notes

Connecting Google Calendar is optional and separate from signing in to Unmute. With your permission, the app reads your Google account email, subscribed calendar list, and upcoming events in the calendars you enable. Event data includes meeting titles, times, invitee names and email addresses, and meeting join links. This supports upcoming meeting lists, reminders, joining meetings, and naming your notes. The app does not create, edit, or delete Google Calendar events.

Calendar synchronization runs on your Mac. Connected account details, calendar selections, and reminder settings are stored locally. Upcoming events are held in memory and fetched again when the app starts. Refresh tokens are encrypted using macOS-backed storage when available; otherwise they are kept only in memory.

When you choose to record a meeting, its calendar metadata is saved with the meeting locally. To generate notes, the meeting title and invitee names (or email addresses when a name is unavailable) are sent with the transcript to your notes agent. That agent may use an external AI service under your account. Its processing and retention are governed by that service's policies and your account settings. Local transcription does not make this notes-generation step local.

You can disable individual calendars or disconnect an account in Notetaker settings. Disconnecting removes the account's local credentials and attempts to revoke Google access; you can also revoke access through your Google Account settings. Disconnecting does not delete notes you have already recorded. You can delete those meetings in Unmute.

Unmute's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

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/legal/privacy-policy.

Cookies, analytics, telemetry

The unmute app contains no analytics SDK, no telemetry SDK, and no crash-reporting SDK. Dictation requests go to your selected transcription engine or its model download service. Optional connected features also make network requests, including Google Calendar synchronization and the notes-agent processing described above.

This website (the one you're reading) is hosted on GitHub Pages which 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.

Local application data may remain on your Mac after uninstalling the app. Use the in-app deletion controls for history and meetings, and remove remaining local application data separately if needed.

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.