Trust: where your data actually goes
Audiee.ai 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.
This page last changed on 2026-10-26. 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 in English, Mandarin, Cantonese, Vietnamese, Thai, Indonesian, Malay or Filipino; dictation audio in Mandarin, Cantonese, Mixed, Thai, Indonesian, Malay or Filipino | Alibaba Cloud Model Studio (Singapore region) through Audiee.ai's gateway, with BytePlus (Singapore) as the fallback when it is unavailable | Returned as text; Audiee.ai's servers keep no copy of audio or transcript |
| Meeting audio in any other language (Japanese, Korean, Spanish, French, German, Portuguese, Italian, Russian, Dutch, Hindi); dictation audio in English, Vietnamese or any other language not listed above | Deepgram (United States), streamed from your Mac directly with a short-lived token that Audiee.ai's gateway mints; relayed through the gateway only if that direct connection fails; every request carries Deepgram's opt-out from model improvement | Returned as text; Audiee.ai's servers keep no copy of audio or transcript |
| Transcript text (for the summary); anything you type or say to the assistant | DeepSeek's API platform (China), through Audiee.ai's gateway; may change, and this page changes first | Processed to produce the answer; Audiee.ai's servers keep no copy |
| Text read off the shared screen during a meeting (when "Read screen" is on — it is by default; switch it off in the live window or Settings) | Read on your Mac (Apple Vision, on-device); the recognised text joins the transcript sent to the language-model provider for the summary | The screenshot itself is never saved or uploaded; the text stays in the meeting's notes and Knowledge page on your Mac |
| A screenshot you ask a question about or save to Knowledge with Ctrl+S | The language-model provider's vision endpoint, as a downscaled image | Read to produce the answer or the Knowledge page; Audiee.ai's servers keep no copy. The full-resolution capture stays on your Mac |
| 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 |
| What the iPhone app sends to your Mac (in testing): meetings and voice notes recorded on the phone — notes, transcript, optionally the recording — and articles, photos or files you share to Audiee.ai | A mailbox in Cloudflare R2 through Audiee.ai's gateway, held only until your Mac collects it (deleted then, or after 30 days) | Encrypted on the phone before upload with a key that belongs to your account, issued by our gateway to each device you sign in on (no pairing). Not end-to-end: we hold that key, so we could read the mailbox; we do not, and the copy is deleted once your Mac collects it. Our servers see the account, file names, sizes and times |
| Google Workspace mail, calendar, Drive | From your Mac — Calendar, Drive, Docs and Sheets with Audiee.ai's own OAuth client | Tokens stay encrypted on your Mac; Audiee.ai's servers never receive Google data |
| Access tokens for the other tools you connect — GitHub, Notion and Slack (OAuth), and API keys you paste in Settings such as a Telegram bot token or your own speech-provider key | Audiee.ai's credential vault: a Supabase edge function that encrypts each token with AES-256-GCM under a key derived per account, and stores the ciphertext in our database | Kept so the daemon can fetch them when you sign in and re-sync them about once a minute while it runs; the daemon then holds a decrypted copy in its own encrypted store on your Mac and hands it to the skill at run time. In the database they can be read only through that function, called with your sign-in token. There is no disconnect switch for these tools in the app yet: a token stays in the vault until your account is deleted (the rows go with it) or you email hello@audiee.ai to have it removed; revoking Audiee.ai's access at GitHub, Notion or Slack makes the stored token useless immediately |
| Connected-tool health: after each run of a skill that uses one of those tokens, the provider's name and — on an auth failure — a short reason such as token_expired | Our database, as an RPC call with your sign-in token | Meant to stamp last-used / last-failure on that provider's row in your account, for support diagnostics; nothing else is written. Sent only if AUDIEE_TELEMETRY=1 is set in the daemon's environment (off by default since daemon 0.1.9, September 2026); otherwise nothing is sent. The database function it calls may be absent — if so, the call is rejected and nothing is recorded |
| Last seen from the app: that an authenticated request arrived, plus app version, daemon version and OS | Audiee.ai's gateway, which writes one row per account in our database — about once every 10 minutes (the throttle is in-memory per gateway instance, so occasionally more often) | Kept as first-seen, last-seen, days active, a throttled request count and the last versions, so we can tell an account that opens Audiee.ai daily from one that signed in once. Deleted with the account |
| Error reports from the Mac app (since 0.1.100, October 2026): when a recording won't start or stops on its own, a summary, dictation, connecting Google or sending the notes fails — what failed (a short code and the sentence shown), the app and macOS versions, your interface language, and the last few minutes of the app's and the daemon's own logs | Audiee.ai's gateway, sent with your sign-in token, into our database | Kept 30 days, then deleted; deleted with the account. Never audio, transcripts, notes or chat — the logs do not hold them. Before anything leaves the Mac the app removes meeting titles, window titles, people's names, email addresses, tokens and your Mac user name; the gateway removes addresses and tokens again. At most five reports a day per account, one per kind of failure. On by default; Settings → Your data → "Send error reports" turns it off |
| A usage log of MCP tool calls (tool name, timing, status, client, first 200 characters of search queries) | Nowhere, as of daemon 0.1.7 | Forwarding is off by default since September 2026; older daemons sent it to our gateway, which discarded it unread |
| MCP session pings: one 'started' event when an AI client connects to Audiee.ai's MCP server (client name and version, Audiee.ai version, OS and chip, a random session id) and one 'ended' event when it disconnects (that id and a reason such as idle) | Audiee.ai's gateway, sent with your sign-in token | Accepted and discarded unread as of September 2026. No tool names, queries or content. Off by default since daemon 0.1.9 (September 2026): sent only if AUDIEE_TELEMETRY=1 is set, the same switch as the tool-call log — see the note below |
What stays on your Mac
- Transcripts and notes once written — Markdown under ~/.audiee, readable without Audiee.ai.
- 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.ai keeps about you, as files you can open and delete.
- Dictation history, to-dos, and the screenshots saved to Knowledge — the capture is read by a vision model on the way in (see the table above); the file and the page it becomes live here.
- Speaker names: read from Zoom's own window on your Mac when you grant Accessibility; no audio fingerprinting anywhere.
The usage log, in full
Tool-call log — off by default since daemon 0.1.7 (September 2026). Until then, when an AI client (Claude Code, Cursor, Claude Desktop) called one of Audiee.ai's MCP tools, the daemon wrote one event to a local SQLite buffer and forwarded batches to Audiee.ai's gateway. The event was metadata about the call, not the call's content: tool name, timing, status, error bucket, client name and version, Audiee.ai version, macOS and chip. For search-class tools (wiki__search, slack__search_messages, notion__search_pages, github__search_code…) the first 200 characters of the query were included; for send, read and create tools only the shape of the arguments — which fields were present and how long they were — never their values. The gateway returned 202 and discarded every batch unread; nothing was ever stored. Today this log is written and sent only if AUDIEE_TELEMETRY=1 is set in the daemon's environment; otherwise the daemon deletes the buffer an older version left behind, so no query text lingers on disk.
MCP session pings — off by default since daemon 0.1.9 (September 2026). The same AUDIEE_TELEMETRY switch gates them: with it unset, no 'started' or 'ended' event is sent when an AI client connects to or leaves Audiee.ai's MCP server, and no session id is minted. Daemons 0.1.7–0.1.8 did send them regardless — one 'started' event (client name and version, Audiee.ai version, OS and chip, a random session id, and that it came over the stdio bridge) and one 'ended' event (the same id and a reason such as idle or client closed), with your sign-in token, never tool names, queries, transcripts or content. As of September 2026 the gateway accepts any that arrive with a 202 and discards them unread.
Since October 2026 the Mac app does send one kind of failure data: the error reports in the table above, each a single failure with the app's own logs around it — not usage, not tool calls, not queries. They were added to this page and given their Settings switch (Your data → Send error reports, on by default) in the same release.
Where things run
- Gateway: Cloudflare Workers at ai-gateway.audiee.ai. It holds the provider keys, meters your allowance, relays Chinese-language audio and language-model text, and mints the short-lived tokens the direct speech path uses; it does not store audio or text.
- Accounts, shares, connected-tool tokens and the last-seen row: Supabase (Postgres, auth, the credential-vault edge function) and Cloudflare R2 (share bodies and images).
- Speech-to-text: Alibaba Cloud Model Studio (Singapore; BytePlus, Singapore, as the fallback) for English, Mandarin and Cantonese meetings and for Chinese dictation; Deepgram (United States) for meetings in the other ten languages and for non-Chinese dictation, connected directly from your Mac.
- Language model: DeepSeek's API platform (China), reached through our gateway; it can change between releases, and this page changes first. 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.ai'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.
- Connected-tool tokens (GitHub, Notion, Slack, pasted API keys): encrypted in the vault until your account is deleted or you email us to remove one — there is no disconnect switch for them in the app yet. The last-seen row and tool-health stamps go with the account.
- 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 or on the phone-to-Mac mailbox (encrypted, but with a key we hold). 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.ai records, and the law where you and your participants sit decides what you must tell them. Audiee.ai 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.ai
Is Audiee.ai 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.ai 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. Meetings in English, Mandarin, Cantonese, Vietnamese, Thai, Indonesian, Malay or Filipino, and Mandarin, Cantonese, Mixed, Thai, Indonesian, Malay or Filipino dictation, go to Alibaba Cloud Model Studio in Singapore (BytePlus, also Singapore, as the fallback) through Audiee.ai's gateway, which holds the key and does not store audio. Meetings in any other language, and English or other non-Chinese dictation, go to Deepgram in the United States, streamed from your Mac directly with a short-lived token our gateway mints; the gateway relays that audio only if the direct connection fails. No long-lived provider key sits on your Mac either way. We name the providers to evaluators on request rather than on this page, so that a provider change never outruns the page; none of them trains on your audio.
Does anyone use my data to train models?
Audiee.ai does not. We do not train anything on your audio, transcripts or notes, and we have no copy to train on. Nor do the speech providers: two rule it out in their terms, and for the third, every request from our gateway and from current app versions carries its opt-out from model improvement. The language model (DeepSeek's API platform) receives transcript text, not audio, and only what a request needs; its terms make no commitment about training on API inputs, so we make none for it here, and we will say so when the routing changes.
What does the usage log contain?
Two different things. The tool-call log — 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.ai version, macOS and chip, and for search tools only the first 200 characters of the query; never message bodies, file contents, email text or tokens — is off by default since daemon 0.1.7 (September 2026). It is sent only if AUDIEE_TELEMETRY=1 is set in the daemon's environment, and the local buffer an older daemon left is deleted on upgrade. The same switch gates the connection pings: since daemon 0.1.9 (September 2026), with AUDIEE_TELEMETRY unset — the default — no 'started' or 'ended' event is sent when an AI client connects to Audiee.ai's MCP server. With it set, each carries client name and version, Audiee.ai version, OS and chip, a random session id and an end reason, with your sign-in token; no tool names, queries or content; the gateway accepts and discards them unread. Before we store either 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.ai for their organisation, along with the provider routing. Email hello@audiee.ai.
Does it work on a corporate network, behind a proxy or TLS inspection?
Yes, with four hosts allowed — see the network guide for IT teams. Since version 0.1.101 the app trusts the certificates in the Mac's keychain, so an inspection certificate your IT installed is accepted; the live transcription stream (a WebSocket to ai-gateway.audiee.ai) must not be buffered or content-scanned. Speech providers are reached through our gateway when a direct connection is blocked, so nothing else needs allowing.
Do you have SOC 2 or ISO 27001?
No. Audiee.ai 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 your Markdown notes, memory, to-dos and saved screenshots). Account: delete it in the app (Mac: Settings → Your data → Delete my account; iPhone: Account → Delete account) or email hello@audiee.ai, and account data — including any connected-tool tokens in the vault and the last-seen row — is deleted within 30 days. Shares: stop sharing from the app and the read-only page goes dark immediately.