Privacy

Who we are

Daimon is operated by The Private Intelligence Company, 2261 Market Street, San Francisco, CA 94114. This policy covers the Daimon apps, daimon.work, and the Daimon Pro plan. For privacy questions or a data request, contact [email protected].

Google accounts, mail, and calendar

Google sign-in provides your account identifier, name, email address, and profile image. With your authorization, Daimon accesses message bodies, headers, attachments, labels, drafts, and mailbox history to display and search mail, sync changes, and carry out actions such as sending, archiving, and moving mail to trash.

Calendar access reads your calendar list and event details, including attendees, and supports event changes you request. Mail and calendar data are also cached on your device so the app can display and search them locally.

In the browser, authorized Gmail and Calendar requests pass through Daimon’s server. That server can process their contents in transit. Browser account records and Google access and refresh tokens are stored in the service database. In the desktop app, Google requests run from the app, credentials are protected using the operating system’s credential encryption, and mail is stored in a local SQLite database and attachment files.

Local mail databases and browser caches are not application-encrypted vaults. Access also depends on your device, browser profile, and operating system protections.

AI processing

AI features use your instructions and the relevant draft, thread, mailbox, or calendar context. In Local mode, the desktop app processes that context on your Mac using models it downloads from Hugging Face, and the context does not leave your device.

Private Cloud, part of Daimon Pro, sends that context to models run by NEAR inside confidential computing environments. Your device verifies the environment and encrypts the request for it before sending; Daimon’s servers relay and meter the request but cannot read its content. The AI request gateway briefly keeps the encrypted reply, for up to 10 minutes, so an interrupted request can resume. If verification fails, Private Cloud stops instead of using a less private mode. Daimon does not offer a non-confidential cloud AI mode.

Private Cloud protects AI request content only. It does not hide your mail traffic in the browser, your account data, or billing metadata such as request timing and cost from Daimon. Google-derived content is not used for advertising or to train general-purpose AI models.

Service, billing, and operational data

The service handles sign-in sessions, IP addresses, user-agent information, account identifiers, subscription status, promotion code redemption, and usage records needed to authenticate you, enforce allowances, prevent abuse, and reconcile charges. Usage records can include request identifiers, timing, model, token counts, cost, and processing status. They do not require storing prompts or generated replies.

Payments are handled by Stripe, the merchant of record for Daimon Pro. Stripe receives your payment details, billing address, and email address for the purchase; Daimon does not store card numbers. A subscription does not give Stripe access to your mailbox.

We use these service providers: Vercel (hosting), Neon (service database), Upstash (Gmail and Calendar rate limits), Cloudflare (desktop app downloads, the AI request gateway, and email forwarding), NEAR (Private Cloud AI), Stripe (payments), and Hugging Face (local model downloads).

Google API Limited Use

Daimon’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Google-derived data is used to provide the user-facing mail, calendar, and Compose features you choose. It is not sold or used for personalized advertising. People at Daimon read it only in the cases that policy permits, such as with your specific consent for support, for security investigations, or when the law requires it.

Control, retention, and deletion

You can revoke Google access in your Google Account connections. Revocation stops future authorized access; it does not itself erase copies already stored on your device or service records. Removing a connected mailbox, signing out, cancelling a subscription, and deleting a Daimon account are distinct actions.

Local data may remain until removed through the app or by clearing its application or browser storage. Email [email protected] to request access to, correction of, or deletion of server-side personal data. Requests may require identity verification. Required payment, tax, fraud-prevention, or legal records may need to be retained separately.

We keep account, subscription, and usage records while your Daimon account exists. Usage records do not include prompts or generated replies. When you ask us to delete your account, we delete its server-side records within 30 days, except payment, tax, and fraud-prevention records we must keep by law. Deleted data can remain in database backups until they expire. We respond to access, correction, and deletion requests within 30 days.

Changes and rights

We will tell you about material changes to how we use data before they take effect, and ask for your consent again where required. Applicable privacy rights depend on your location. Email [email protected] to exercise them or raise a concern; this policy does not limit rights provided by law.