Privacy policy
If we can't enforce it in code, we don't promise it here either.
This page says where your data lives, what little of it touches our servers, and what we will never do with it. It is written to be read.
Last updated · 16 July 2026
The short version
Your communications never live on our servers. Messages, contacts, the knowledge graph MYNC builds from them, and the keys that encrypt them all live on your Mac, in an encrypted store (SQLCipher, AES-256) whose key sits in your macOS Keychain. There is no cloud copy of your corpus to breach, subpoena, or delete.
What our servers do see
- Account identity — your email and login, managed through Auth0, so your subscription works.
- Billing — handled by Stripe. We never see or store card numbers.
- Connection tokens — when you connect a source (Gmail, Outlook), OAuth runs through our token layer. Long-lived refresh tokens stay inside that layer; short-lived access tokens are cached encrypted (AES-256-GCM) and replaced on every refresh. We cannot read your mailbox with what we store.
- Enrichment relay (hosted plans only) — if you opt into a hosted plan, per-query slices pass through our relay to the model in memory, are delivered back to your Mac once, and are purged. Undelivered results are deleted within 25 minutes. Nothing is written to durable storage.
- Usage counts — how many enrichment requests your plan used. Counts, never content.
What we never do
- We never sell your data, to anyone, for anything.
- We never train models on your data — and our processors are contractually barred from doing so.
- We never show ads, and there is no analytics or tracking on this website. None.
When you connect Gmail, MYNC requests read-only access (gmail.readonly) and uses it for exactly one thing: syncing your messages into the encrypted store on your Mac, where they become part of your private knowledge graph. Google message content is not stored on MYNC servers, not used for advertising, not sold, and not used to train models.
MYNC's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
No human at MYNC reads your Google data. The narrow exceptions the policy permits — with your explicit consent, for security investigation, or to comply with law — are the only ones we recognize, and we will tell you if one is ever exercised. Disconnecting Gmail stops the sync immediately; you can purge the already-synced source data from the app at any time, and it deletes locally because that is the only place it exists.
Data flows follow your plan, and only your plan
On the Local plan, nothing leaves your Mac. On hosted plans, the slice of data a query needs routes to a named processor (our hosted open models, or Anthropic's Claude under commercial API terms: no training, short retention) — we publish the processor list and every routing choice in the app carries a badge saying where data goes. On BYOK, your Mac calls the providers you chose with your own keys, under your accounts and their terms; the keys live in your Keychain and never reach our backend. Queries made through Claude Desktop travel through your own Claude account, not ours.
Your rights
Access and portability are trivially satisfied: the corpus is on your machine. Deletion likewise — forget people, purge sources, or delete the store; there is no server copy. To delete your account (identity, billing record, usage counts), email support@mync.ai and we will complete it within 30 days. We operate from Toronto under PIPEDA and honour the spirit of GDPR and CCPA regardless of where you live: your data is not our asset.
Security, children, changes
Encryption at rest (SQLCipher AES-256, key in your Keychain), TLS in transit, signed updates (EdDSA), and a CI gate that keeps personal content out of our logs. MYNC is not directed at children under 16. If this policy changes materially, we will say so in the app and date the change here — the current version is always this page.