Privacy Policy

Last updated: October 12, 2026

The short version

You do not need an account to use the inbox. Your inbox session is kept in your browser. Our blog uses separate server storage. Optional first-party traffic analytics starts only when you choose “Allow analytics”; declining does not affect the inbox.

What we store

How mail is handled

Messages are provided live by the Mail.tm service. When you load your inbox, your browser sends authorized requests through our server proxy to Mail.tm using the token stored in your browser. We do not copy, cache, or log the contents of your messages.

Cookies and tracking

We do not set advertising cookies or add third-party analytics trackers. If you opt in, a random first-party cookie lasts up to 30 days to estimate browser uniqueness. Analytics records canonical public page paths, timestamps, broad referral categories and estimated country, not inbox addresses, messages, credentials, tokens or URL parameters. Country is resolved locally from the connecting IP; the IP is not stored in analytics or sent to a geolocation service. A daily keyed IP hash supports short-lived rate limiting. Event records are retained for about 90 days and rate hashes for up to 25 hours, with hourly private cleanup. Standard hosting logs are separate from analytics. Use “Analytics privacy” in the footer to withdraw consent; this stops new collection and does not erase prior anonymous records. DNT and Global Privacy Control are respected. See our Cookie Policy for details.

Third parties

Mail delivery and storage of received messages are handled by Mail.tm. Please review their privacy policy for how they process messages. Temporary mail should not be used for sensitive information. See our Transparency page for exactly how mail flows and what we can and cannot see.

Responsible use

tempail.co is a privacy and testing tool. Using it to spam, defraud, harass, or attack others is prohibited. Read our Responsible Use Policy before using the service.

Security

Analytics storage is private, separate from the blog and restricted to the site administrator. Inbox API requests necessarily pass through our server proxy; analytics never reads their payloads. For the technical details, including transport security and our HTTP security headers, see our Security page.

Changes to this policy

We may update this page from time to time. Any changes will be reflected here with a new “Last updated” date.

Contact

Questions about privacy? Reach us at .