Privacy Policy

Last updated: July 31, 2026

commissure is built local-first on purpose: your personal data stays on your device. This explains the little that does leave it, and why.

What stays on your device, and what leaves

The corpus commissure builds from your messages, email, browser history, notes, files, and other sources lives on your own device. We never upload it wholesale, and we cannot see it.

What the cloud sees

Using commissure.ai (accounts, the website, metered "ask") involves our cloud, which handles only:

• Account metadata: your email, plan tier, and usage counts, to run your account and meter usage.
• Cloud message content, only when you use a cloud model: when you send a message through our metered cloud, that message and the corpus snippets needed to answer it go to the model provider to generate the reply. We don't store your corpus or your message; the request transits, and the billing record keeps token counts and model identities, never your text. Run a fully local model instead and nothing leaves your device at all.
• The commissure.ai chat: the chat on the site answers questions about commissure. It sees your account info and nothing else, and we don't store the content of your messages to it.
• The sync channels you turn on: the data you choose to sync from your device (your rules, items, and the coordination reading), the encrypted backup, quick captures, and the (currently disabled) ask relay. The Security page is the canonical channel-by-channel list: what each carries, what the server can and cannot read, and what is off by default.

Google Gmail & Calendar access

If you connect Gmail or Google Calendar, commissure uses Google OAuth in the local Mac app to request read-only access. The OAuth tokens are saved on your device, and Gmail messages plus Calendar events are ingested into your local corpus so you can search, summarize, and reason over your own context.

Google data is not uploaded wholesale to commissure.ai. It leaves your device only when you explicitly use a cloud AI feature that sends the question and the selected snippets needed to answer it. We do not sell Google user data, use it for advertising, or use it to train models.

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

Who we share with

Only the providers needed to operate: Anthropic / OpenAI / Google (model inference on the request you submit, for the model route you picked), Stripe (payments), Cloudflare (hosting), Resend (sign-in and invite emails), and Twilio (invite texts, when you ask us to send one). We do not sell your data, ever, and it is not used to train models.

Cookies

The website uses only the essential cookies needed to keep you signed in. No advertising or third-party tracking cookies.

Where data is processed

Our cloud runs on Cloudflare and may be processed in the United States and other countries where our providers operate. The model provider you choose processes your request in its own regions.

Your rights

You can access, correct, export, or delete your account data, and object to or restrict how it is used. Where the law grants these rights (including the EU's GDPR and California's CCPA/CPRA), we honor them for everyone. We do not sell or "share" your data for advertising. To exercise any right, email nik@commissure.ai.

Retention & deletion

Your local data is yours to delete on your device anytime. We keep your cloud account data until you delete it or close your account; email nik@commissure.ai and we'll remove it, and backup copies age out shortly after.

Children

commissure is not for anyone under 18, and we do not knowingly collect data from them.

Security

Accounts use passkeys (no passwords to leak), and cloud data is limited to the metadata above. No system is perfectly secure, but the local-first design means the sensitive part, your corpus, isn't ours to lose. The full practices (encryption, signing, what each subsystem can and cannot read) are on the Security page.

Changes & contact

We may update this policy; material changes are posted here with a new date. Questions or requests: nik@commissure.ai.