Privacy

Last updated: 17 November 2026

This page covers this website and the unmodified, self-hosted Tide software. Each installation is operated by its owner in their own Cloudflare account. The project does not operate a hosted mail service and receives no mail, calendar data, credentials or usage telemetry from installations. An operator who changes the software or its data practices must disclose those changes to their users.

Tide is in development and is not yet publicly available. The software sections below describe its self-hosted data practices.

This website

This website has no analytics, advertising, tracking scripts, forms or sign-in. It does not collect mail or calendar data. It saves your chosen light or dark theme in your browser’s local storage. Clear this website’s browser data to remove that preference.

Cloudflare hosts and delivers the website and processes connection information, such as your IP address and request details, to serve and secure it. Its handling of that information is covered by Cloudflare’s Privacy Policy. Links to other sites take you to services with their own policies.

Mail and calendar data in your installation

When you connect an account, Tide accesses the account identity, mail and calendar information you authorize. This can include your name and email address; message headers, bodies, attachments, folders and flags; and calendar names, events, attendees and invitations. It uses this information only to provide your own mail and calendar functions: displaying, searching, syncing, composing and sending mail; saving drafts; organizing or deleting mail; and displaying, creating, updating and responding to calendar events as you choose.

Google and Microsoft sign-in use the operator’s own OAuth application. Mail access and optional calendar connections require consent for their respective permissions. There is no shared project-operated Google or Microsoft application receiving your data.

Storage and security

Your installation stores metadata, the mail and search indexes, drafts, contacts, settings and calendar records in Cloudflare D1; fetched message bodies, attachments within messages, and own-domain mail in R2; and transient sync state in Durable Objects. These resources belong to the operator’s Cloudflare account. Lists and messages you have viewed are also cached in your browser; signing out clears that cache.

Saved passwords, OAuth refresh tokens, relay keys and private calendar links are encrypted with keys derived from a secret held by the Worker. Sign-in uses passkeys, with recovery codes as a fallback. Mail itself is not end-to-end encrypted. Your Worker processes it in plain text, and Cloudflare and anyone controlling the Cloudflare account can access what the installation holds. Protect that account and its secrets.

Sharing and optional services

Tide does not sell your data, serve ads, include trackers or use your mail or calendar data to train AI models. The project’s maintainers have no access to your installation. Processing and transfers needed to provide the features you choose include:

  • Mail and calendar providers: your installation communicates with the accounts you connect. Sending mail or invitations delivers information to the recipients and their providers; connected calendar apps and private subscription links receive the calendar data you choose to expose. Anyone holding a private subscription link can read that feed.
  • Cloudflare and account discovery: Cloudflare processes your installation’s data as its infrastructure provider. When you add a mailbox, Cloudflare DNS-over-HTTPS and Mozilla’s Thunderbird autoconfig service receive the address’s domain to find server settings, not your full address or password.
  • Services you configure: a sending relay processes outgoing mail; your browser’s push service delivers encrypted notifications; and an optional Cloudflare API token allows domain setup in your account.
  • MCP assistants: only an assistant you explicitly authorize with a token can read and search mail or, with a read-and-drafts token, save drafts. Mail returned to an assistant is processed by that assistant and any provider you configure for it, under their policies. MCP has no send, forward, delete or rule-making tools. Revoke tokens in Settings → AI access. This access is separate from Workers AI.
  • Suggested replies: off by default. If you enable Workers AI, your Worker sends the cleaned text of the message you are replying to (up to 4,000 characters), your account’s sender name and fixed instructions to Workers AI in your Cloudflare account. It does not send attachments or other messages. Tide does not store suggestions or log their email content. Suggestions only enter the composer when you select one; sending remains your action. Cloudflare states that Workers AI does not use customer content to train models and does not retain inputs or outputs after they are no longer needed to process the request, subject to its documented exceptions. See Workers AI privacy.

Google API data: Limited Use

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

See the Google API Services User Data Policy and the Google Workspace user data and developer policy. Google data is used only for the disclosed, user-facing mail and calendar features, including optional features you explicitly enable. Transfers are limited to those permitted by those policies, including those needed to provide these features with your consent. Google data is not sold, used for advertising or used to train generalized AI models. The project does not allow its maintainers to read your Google data. Each operator is responsible for ensuring that their installation and any connected assistant comply with these requirements.

Disconnecting and deleting data

Remove a mail account in Settings to delete its records and stored message copies from your installation. This does not delete the original mailbox at your provider. You can also revoke OAuth access in your Google or Microsoft account and revoke app passwords at your mail provider.

To remove an installation completely, delete its Worker, D1 database, R2 bucket and Durable Object data in Cloudflare, plus any backups or copies you made. Signing out clears the browser mail cache; clearing site data removes remaining browser preferences. Revoke MCP tokens, calendar device passwords and private calendar links when no longer needed. Copies already delivered to recipients, downloaded by calendar apps, processed by authorized assistants or retained in backups must be managed separately. The project cannot delete resources it does not control.

Contact

For an installation’s data practices or deletion requests, contact its operator.