Privacy Policy

Last updated: October 16, 2026

This policy explains what Munin Labs, Inc. ("Munin", "we") collects when you use the Munin Mac app and website, why, and who else handles it. Meetings are private by nature, so we collect as little as we can.

1. What we collect

• Account details: your email address, used to sign you in with a one time code
• Meeting audio: recorded by the Mac app from your microphone and your computer's sound output, or by the website from your microphone, while you record
• Transcripts and notes: the text, summaries, decisions and open questions created from your recordings
• Your vocabulary lists: names and terms you add so transcription spells them correctly
• People and voiceprints: the names you give the speakers in your meetings and, for each person, voiceprints: numbers that describe how their voice sounds, so Munin can recognise them in your next meeting. Section 4 explains them
• Questions you ask: what you type when you ask about your meetings, and the answers
• Billing details: handled by Stripe. We see your plan and payment status, never your full card number
• Basic technical logs: IP address, browser type and request times, kept by our hosting provider for security and debugging

2. How we use it

Only to run Munin for you: to sign you in, transcribe and organize your meetings, answer your questions about them, bill you, keep the Service secure and reply when you contact us. We do not sell your data, show you ads or use your meetings to train AI models.

3. Who handles your meetings

Meetings are private, so here is everyone who touches yours: where they are stored, which services see them while they are processed, what our own team can see, and how long each copy stays.

Where your meetings are stored

• Supabase stores your account in its Northeast Asia (Tokyo) region, on Amazon Web Services ap-northeast-1, and, for meetings on the website, the recording in a private storage space, the transcript, the notes, your own notes and your dictionary. Supabase states that it encrypts this data at rest and in transit
• Your browser keeps your conversations with Ask Munin, the last 30 messages of each. They are not saved on our servers

Services that see your meetings while processing them

• ElevenLabs turns audio into text. It receives your audio twice: streamed while you record, for the live captions, and as a full file after you stop, for the full transcript. Right after each full transcript comes back, Munin asks ElevenLabs to delete its stored copy of it. ElevenLabs does not say whether this also deletes the audio it received. Live captions come back without an id we could use to delete them, so ElevenLabs keeps them in its request history, which is its default. After any deletion, ElevenLabs keeps backups for up to 30 days. ElevenLabs' terms let it use customer content to improve its models unless the customer opts out in its account settings
• OpenRouter passes your transcript to the AI model that writes your notes, and the parts of your meetings that matter to the model that answers your questions in Ask Munin. OpenRouter does not store this text or use it for training. The model is Google Gemini, with Anthropic Claude as a backup when Gemini is unavailable, and each provider applies its own rules. We have set OpenRouter to send these requests only to services that keep nothing once they answer (zero data retention): Google Vertex AI for Gemini, and Amazon Bedrock or Google Vertex AI for Claude. OpenRouter lists none of them as training on it
• Cloudflare hosts the website and runs Munin's server. Your recordings, transcripts and questions pass through that server on their way to the services above. The full version of your notes is usually written in Cloudflare Workflows, which keeps the result of each step, including parts of your notes, the meeting title and your dictionary, for up to 30 days after the job ends. Sign in and invitation emails are sent by Supabase, either directly or through Cloudflare's email service

AI assistants you connect

You can connect an AI assistant such as ChatGPT, Claude or Codex to your Munin account, from the assistant's own connector page or with a key from the Connect AI page. Nothing is shared with an assistant until you press Allow on its sign in page or create a key for it. Once connected, it can read what your account holds: your meeting list, titles and times, notes, transcripts with speaker names, the people named in them and your own notes. When you ask it to, it can also rename a speaker in one of your meetings. It never receives your recordings, and it cannot delete anything. Munin receives only the requests the assistant sends, such as the words to search for, never your conversation with it, and does not store those requests. What the assistant receives is then handled under that provider's own terms and privacy policy, not ours. Each connection is listed on the Connect AI page, where you can revoke it; access stops at once.

What the Munin team can see

Our admin page shows only numbers for each account: meetings, minutes recorded, credits, plan and payments. Email addresses are hidden there, and one is shown only when an admin clicks to reveal it. By internal rule, nobody at Munin opens your meetings, transcripts or notes. To understand a problem we use those numbers or ask you. Munin does not offer end to end encryption: as the owner of the database, we are technically able to read what is stored in it, and only the rule above keeps us out.

Analytics

Analytics never include your meetings, meeting titles or email address. They run only with your consent, and in the web app our own server passes them on. Details are in section 6.

When you delete

• A meeting: its transcript, notes and your own notes are deleted from the database right away. Its recording is deleted from storage by our server once the Undo button has gone, about 8 seconds later. If you close Munin within those seconds, a daily job on our server deletes the recording within a day
• Your dictionary: stays until you remove the words, even when the meeting a word came from is deleted
• Your account: open Settings, Account, Delete account and type the word asked for. Your recordings, meetings, transcripts, notes, dictionary, people and their voiceprints, credits and connection keys are deleted right away, then the account itself. Nothing is kept for a grace period and there is no undo. Billing records (what you paid, when, and the Stripe ids) are kept for accounting, with your account id removed from them. The record that your invite code was used is kept so the code cannot be reused. You can also email support@muninlabs.ai and we will do it for you
• Backups: deleted data can stay in Supabase's daily database backups until they expire, which on Supabase's paid plans is after 7 to 30 days. These backups do not include recordings

The Mac app

Recordings, transcripts and notes made in the Mac app are saved on your Mac. To make them, the audio is sent to ElevenLabs as described above and the notes are written by Anthropic Claude. The Mac app does not yet ask ElevenLabs to delete its copy of the transcript. A meeting goes to your Munin account only when you choose Upload, and the question you answer says so: the notes, transcript and recording go to your private space, and if you keep it on this Mac, it stays only on this Mac.

Other providers

• Stripe: processes payments
• Google and PostHog: analytics, only if you choose Accept in the cookie bar (section 6)
• GitHub: only if you turn on sync, your notes are saved to a private repository in your own GitHub account

These providers may process data in the United States and other countries.

Every service at a glance

Voiceprints are made in your browser and stored only in Supabase. They are not sent to ElevenLabs, OpenRouter, any AI model or any other service in this table.

4. Voiceprints and speaker identification

Munin can recognise who is speaking across your meetings. To do this it keeps voiceprints of the people you name. This section says what a voiceprint is and everything that happens to it.

• What a voiceprint is: a list of 512 numbers that describes how one person's voice sounds. It contains no audio and no words
• How it is made: when you open a meeting in the web app (the Mac app's main window shows the same page), your browser fetches that meeting's recording from your private storage and runs an open speaker model on your own device to compute voiceprints for each unnamed speaker, from pieces of their speech about 8 seconds long. The model today is 3D-Speaker ERes2Net (see Open source licenses). Nothing is sent to ElevenLabs, OpenRouter or any AI service to do this; only the voiceprints you keep are saved to your account, as described below
• When it is saved: only while Recognise speakers is on, and only when a speaker is given a name: when you rename a speaker, answer Yes to a suggestion such as "Is this Alex?", or name a speaker through an AI agent you connected to Munin (it is then saved the next time you open that meeting). Voiceprints of speakers nobody names are not saved
• What is saved and where: in the people list of your own account in Supabase, each person's name, other spellings of it, whether the person is you, and up to their 12 newest voiceprints, each with the meeting it came from and when it was saved. Each meeting also keeps which speaker was matched to which person, and how close the match was
• Who can see them: only your account. The database lets each account read and change only its own people list. Voiceprints are never shared with other accounts or compared with theirs. Nobody at Munin opens them, under the same internal rule as your meetings (section 3)
• What they are used for: only to put the right names on the speakers in your own meetings. We do not use voiceprints to train any AI model, we do not sell them, and we do not use them to identify anyone outside your account
• They are about other people: most voiceprints in an account belong to the people its owner meets, not to the owner. That is why recording people and naming them carries the duties in section 3 of our Terms of Service
• How long they are kept: for the period you choose in Settings, People and voiceprints, Keep voiceprints: 1 year, 2 years, or until you delete them. The default is 2 years. Each voiceprint counts from the day it was saved, and once its period ends it is deleted automatically, within a day. You can also delete them yourself at any time (below), and they are always deleted with your account. Deleting a meeting does not delete the voiceprints learned from it
• How to delete them: on the People page, Delete voiceprints removes every voiceprint of that person at once; the name stays, and Munin has to learn the voice again. Deleting your account deletes all your people and their voiceprints (section 3, When you delete)
• Turning it off: speaker identification is on by default. To turn it off, open Settings, People and voiceprints, and switch off Recognise speakers. While it is off, Munin does not download the speaker model, does not compute voiceprints and does not save new ones, and meetings show no speaker suggestions. Voiceprints already saved stay until you delete them on the People page or their period ends

Biometric data laws

Some laws treat voiceprints as biometric data and set extra rules for them. The Illinois Biometric Information Privacy Act lists voiceprints as biometric identifiers. Under the EU General Data Protection Regulation (Article 9), biometric data used to uniquely identify a person is a special category of personal data. Laws like these can require that each person is told, and gives consent, before a voiceprint of them is made, and can limit how long it is kept. Munin's speaker identification is not offered for use where you cannot get that consent: in those places, do not name speakers, and delete any voiceprints already saved.

5. Cookies and browser storage

The website uses your browser's storage to keep you signed in and to remember your cookie choice. We do not use advertising cookies. Analytics cookies are set only if you accept them (section 6).

6. Analytics

Only if you choose Accept in the cookie bar, we use two analytics tools to understand how people use Munin and where it needs work. If you choose Essential only, or make no choice, neither tool loads and nothing is sent to them.

• Who: Google Analytics 4, run by Google LLC, on the website and in the web app, and PostHog, run by PostHog, Inc., in the web app only
• How it reaches them: on the website, Google's script loads in your browser. In the web app, no analytics script loads at all: the app sends each event to our own server, which passes on only the event name, its numbers and the ids below. Our server does not pass on your IP address, your browser details or the page you came from
• What we collect: the pages you visit on the website, and a few events in the web app, such as starting a recording, saving one with its length in minutes, asking Munin a question, opening the credits page and clicking a top up or plan button, with numbers only. In the web app, events carry a random id kept in your browser, the time your visit started and, when you are signed in, a random account id. Google Analytics does not log or store IP addresses
• What we never collect: your email address, meeting titles, transcripts, notes, speaker names or anything you type. Session recording, automatic click tracking, Google signals and ad personalization are turned off
• Why: to see which features help and where people get stuck. Never for advertising
• How long: Google Analytics keeps this data for 14 months. PostHog keeps it for the retention period set in our PostHog account
• Cookies and storage: on the website, Google Analytics sets cookies named _ga and _ga_ followed by an id, which last 2 years. The web app sets no analytics cookies; it keeps the random id as mn.cid in your browser's storage, and the start of your visit as mn.sid until you close the tab. None of them is set before you choose Accept
• How to refuse or change your mind: choose Essential only in the cookie bar, or open Cookie settings at the bottom of the website or in the app's Settings at any time. Essential only stops both tools and deletes their cookies and the random id from your browser

Separately, Cloudflare Web Analytics, run by Cloudflare, Inc., counts page views and measures how fast our pages load. Cloudflare states that it uses no client-side state, such as cookies or browser storage, and does not fingerprint visitors by IP address, browser or any other data. That is why it runs for every visitor, without the cookie bar. More: Cloudflare Web Analytics

Questions about analytics: support@muninlabs.ai

7. How long we keep it

We keep your transcripts and notes until you delete them or close your account. When you close your account, we delete your data from our systems within 30 days, except where the law requires us to keep billing records. How long each service keeps its copy, and what happens when you delete a meeting, is in section 3. Voiceprints are kept for the period you choose, 2 years by default, then deleted automatically; you can delete them sooner on the People page, and they are deleted with your account (section 4).

8. Your choices and rights

You can view, export and delete your meetings in the app at any time, and delete the voiceprints of any person on the People page. You can also ask us to access, correct or delete your personal data by emailing us. Depending on where you live, laws such as the GDPR or the California Consumer Privacy Act may give you additional rights, and we will honor them.

If you were in a meeting someone else recorded with Munin, your voiceprint, if one was saved, is in that person's account, not in one of yours. The quickest way to have it deleted is to ask them: it takes one click on their People page. You can also write to support@muninlabs.ai. Because nobody at Munin opens users' meetings or people lists, tell us whose account it is, and we will handle your request as the law requires.

9. International transfers

Munin Labs, Inc. is a company in the United States. The services in section 3 may store and process your data in the United States and other countries, whose data protection laws may differ from those where you live. When you use Munin from outside the United States, your data is transferred there. Where the law requires a safeguard for this transfer, we rely on the European Commission's Standard Contractual Clauses in our service providers' data processing terms, where those providers offer them. To get a copy of the safeguard that applies to a given service, write to support@muninlabs.ai.

10. Security

Data is encrypted in transit. Access to each account's meetings is restricted at the database level so that other users cannot read them. Who else is technically able to, and why we do not, is in section 3. No system is perfectly secure, and we will tell you promptly if a breach affects your data.

11. Children

Munin is not intended for anyone under 18, and we do not knowingly collect data from children.

12. Changes

If we change this policy in a material way, we will tell you by email or in the app before the change takes effect.

13. Contact

Munin Labs, Inc., a Delaware corporation. We operate online only and answer every privacy question or request by email within 30 days.

Privacy questions or requests: support@muninlabs.ai