Trust: where your data actually goes
Audiee is local-first, not fully offline. This page lists every service that can receive something from your Mac, what it receives, and for how long. It is the long version of the privacy page, written for the person who has to approve the tool.
Last reviewed against the code on 2026-09-13. If a row here is out of date, email hello@audiee.ai and we fix it the same week.
What leaves your Mac, and where it goes
| What | Goes to | Then |
|---|---|---|
| Meeting audio (every meeting); dictation audio in Mandarin, Cantonese or Mixed | BytePlus Seed ASR (ByteDance's international cloud), Singapore region, through Audiee's gateway | Returned as text; Audiee's servers keep no copy of audio or transcript |
| Dictation audio in other languages | Deepgram (Nova models), streamed with a short-lived token | Returned as text; not retained by Audiee |
| Transcript text (for the summary); anything you type or say to the assistant | Our language-model provider, through Audiee's gateway (named to evaluators on request; may change) | Processed to produce the answer; Audiee's servers keep no copy |
| A screenshot you ask a question about | The language-model provider's vision endpoint, as an image | Screenshots you save to Knowledge are different: OCR runs on your Mac with Apple Vision and the pixels stay |
| Email address, subscription tier, sign-in tokens | Supabase (accounts) and Stripe (payments) | Kept while you have an account; deleted within 30 days of account deletion |
| Pages and meeting recaps you share by email | Metadata in Supabase, bodies and images in Cloudflare R2, the email itself via Resend | Encrypted at rest, not end-to-end; revocable any time; bodies of expired shares are deleted 7 days after expiry |
| Google Workspace mail, calendar, Drive | Your own Google Cloud project, from your Mac | Tokens stay encrypted on your Mac; Audiee's servers never receive Google data |
| A usage log of MCP tool calls (see below) | Audiee's gateway on Cloudflare Workers | Accepted and discarded as of September 2026; see the note before we change that |
What never leaves
- Transcripts and notes once written — Markdown under ~/.audiee, readable without Audiee.
- The knowledge base: pages, links, properties, the graph.
- Search. Keyword and semantic search run on your Mac; the embedding model is downloaded once to ~/.audiee/models.
- Memory: the small facts Audiee keeps about you, as files you can open and delete.
- Dictation history, to-dos, screenshots saved to Knowledge (OCR on device).
- Speaker names: read from Zoom's own window on your Mac when you grant Accessibility; no audio fingerprinting anywhere.
The usage log, in full
When an AI client (Claude Code, Cursor, Claude Desktop) calls one of Audiee's MCP tools, the daemon writes one event to a local SQLite buffer and forwards batches to Audiee's gateway. The event is metadata about the call, not the call's content: tool name, timing, status, error bucket, client name and version, Audiee version, macOS and chip. For search-class tools (wiki__search, gmail__search_emails, slack__search_messages, notion__search_pages, github__search_code…) the first 200 characters of the query are kept because the query is the signal we need to improve search. For send, read and create tools only the shape of the arguments is kept — which fields were present and how long they were — never their values.
As of September 2026 the gateway returns 202 and discards these events; there is no warehouse behind it yet. We are telling you now because the app already sends them. Before we store them we will: update this page, add a Settings switch, and say what the stored data is for (crash and failure rates per tool and per client).
Where things run
- Gateway: Cloudflare Workers at ai-gateway.audiee.ai. It holds the provider keys, meters your allowance and forwards audio and text; it does not store either.
- Accounts and shares: Supabase (Postgres, auth) and Cloudflare R2 (share bodies and images).
- Speech-to-text: BytePlus in Singapore (ap-southeast-1); Deepgram for non-Chinese dictation.
- Language model: a hosted provider reached over its API through our gateway. We do not name it here because it can change between releases; we tell evaluators which one on request. What reaches it is transcript text and your questions — never audio, never your knowledge base.
- Payments: Stripe. We never see card numbers.
Retention
- Audio: not stored anywhere after transcription.
- Transcript and summary text sent for summarisation: not stored by Audiee's gateway.
- Shares: until you stop sharing or the expiry you set (7, 30 or 90 days); bodies deleted 7 days after expiry.
- Account data: deleted within 30 days of your request.
- Everything on your Mac: yours; delete the folder and it is gone.
What we do not have
No certifications (no SOC 2, no ISO 27001). No enterprise SSO. No on-premise gateway. No end-to-end encryption on shared pages. We would rather list these than let you find out later; if one of them is the blocker, tell us which and we will tell you honestly whether it is coming.
Recording other people
You decide what Audiee records, and the law where you and your participants sit decides what you must tell them. Audiee never joins a call as a participant, so nothing announces the recording for you; the terms put that responsibility where it belongs — with the person pressing record.
Questions people ask before approving Audiee
Is Audiee fully offline?
No, and we don't say it is. Notes, transcripts, the knowledge base, search and memory live and run on your Mac. Audio must leave your Mac to be transcribed, and transcript text leaves to be summarised. Tools that run their own speech model on the Mac can be fully offline; Audiee trades that for better mixed Chinese-English accuracy and Intel support.
Which company hears my meetings?
The speech-to-text provider for the language you chose: BytePlus (Singapore region) for every meeting and for Mandarin, Cantonese and Mixed dictation; Deepgram for dictation in other languages. Audio goes through Audiee's gateway so the provider keys never sit on your Mac, and the gateway does not store audio.
Does anyone use my data to train models?
Audiee does not. We do not train anything on your audio, transcripts or notes, and we have no copy to train on. Provider terms are theirs, not ours to restate; the trust page names every provider so you can read them, and we will say so here if one changes.
What does the usage log contain?
For each MCP tool call: the tool's name, when it ran, how long it took, whether it succeeded and a normalised error bucket, the client's name and version (Claude Code, Cursor…), the Audiee version, macOS and chip. For search tools only, the first 200 characters of the query. Never message bodies, file contents, email text or tokens. Today the gateway accepts these events and discards them; before we start storing them we will update this page and add a switch in Settings.
Where can I see exactly what is sent?
Ask. The audit payload is one struct and the redaction rules are one file; we will send both to anyone evaluating Audiee for their organisation, along with the provider routing. Email hello@audiee.ai.
Do you have SOC 2 or ISO 27001?
No. Audiee is a small team in Singapore operating under the PDPA; we have not been audited by a third party and will not claim otherwise. What we can offer is a short list of services, plain files on your Mac, and this page kept current.
How do I delete everything?
Local data: delete ~/.audiee (or use Export first — one click, a zip of Markdown). Account: email hello@audiee.ai and account data is deleted within 30 days. Shares: stop sharing from the app and the read-only page goes dark immediately.