Scope

This page covers two different things, because they are genuinely different: this website (cindermail.xyz, informational only), and the Cindermail software as run by anyone who deploys their own copy. This is not legal advice. If you operate a deployment other people rely on, especially anywhere GDPR or similar regulation applies, have someone qualified review your own notice before relying on this one.

This website

cindermail.xyz is a static, informational site. It sets no cookies, runs no analytics or tracking scripts, and has no forms, accounts, or logins. The homepage's star count does make one client-side request to GitHub's public API (api.github.com) to show a live number, which exposes your IP address to GitHub the same way visiting any github.com page would; nothing else on the site talks to a third party. Cloudflare, as the hosting provider, processes standard connection metadata (IP address, request timing) to serve the page and for its own network security, the same as any site behind its network. That data is not collected or stored by this project itself.

What a deployment of the software stores

Anyone running Cindermail deploys their own copy on their own Cloudflare account. Unless stated otherwise below, that operator, not this project, is the one storing and controlling the data below. A deployment stores, in its own Cloudflare D1 database:

• The disposable address itself, and the Discord, Telegram, or Slack user ID that owns it
• An optional note the owner labelled it with
• Creation, expiry, and revocation timestamps
• For mail.tm-backed addresses only: the mail.tm mailbox's own credentials, used solely to poll and later delete that specific mailbox
• Rate-limit bookkeeping: which owner ID ran which command and when, kept only long enough to enforce the per-command limits, cleared automatically after 30 days of inactivity

Emails are never stored, anywhere. A deployment never stores or requests:

• Email content, subject lines, senders, or attachments. Each message is parsed in memory and delivered the moment it arrives, then it's gone; nothing about its content is ever written to the database
• Payment information
• Anything beyond what is listed above

A deployment's public status page (if reachable) shows running totals only, addresses created, emails received, addresses torched, and how many people currently hold an active address. No addresses, notes, owner IDs, or content, ever, on that page.

The private hosted instance

This project's maintainer also runs one deployment themselves, for personal and invite-only use, not a public sign-up service. It is a deployment like any other: the data it stores and the data it never touches are exactly what's listed above, nothing more. Its live status page, counts only, is at status.cindermail.xyz. Because the maintainer operates this one directly, requests about it (unlike a third-party deployment) go to the contacts below, not to some other operator.

Access and deletion

For a third-party deployment, requests to access or delete stored data should go to whoever runs that specific deployment, not to this project; for the private hosted instance above, they go to this project directly, via the contacts below. /torch marks an address revoked immediately, mail sent to it afterward is dropped, not delivered, and it stops showing up in /list. The row itself (and the mail.tm mailbox behind any mail.tm-backed address) is physically deleted by the daily cleanup once it's 24 hours past revocation or expiry, not instantly.

Terms

Cindermail is open-source software, provided as-is, without warranty of any kind. Using it does not create any relationship between an end user and this project. Each third-party deployment is independently operated; this project is not responsible for how any specific one is configured or run. The private hosted instance above is likewise offered as-is, invite-only, with no uptime guarantee, and may be changed or discontinued at any time.

Contact

Questions about this project: github.com/psalm2517 or Bluesky. Questions about data held by a specific deployment: contact that deployment's operator directly.