Privacy Policy

Last updated: 6 August 2026.

This page follows the data, not the promises. It walks an address from the click that generates it to the moment it stops existing, and says at each step what is written down, where, and who else can see it.

The moment you generate an address

Before the click, nothing about you exists here. After it, exactly two records do.

The first is the mailbox itself: an address, the domain it was issued on, and the timestamp at which it dies. The second is a random string placed in your browser so this page can show you the same mailbox when you come back. That string is generated here, is not derived from anything about you, and is meaningless to every other website in the world.

What is not created is worth more attention than what is. No IP address is recorded, because there is no field for one anywhere in the schema: not on mailboxes, not on messages, not on accounts, not on sessions. Your address exists in memory while a request is answered and vanishes when the answer is sent.

No access log exists either. The web server in front of the application was configured without logging, so nothing on disk says which page was fetched from where at what second. Keeping those files for months is what most sites do without thinking; here the files were never created.

The rate limiter forgets too. The counter that stops one visitor generating a thousand addresses a minute lives in process memory and is erased by a restart.

The seconds after, when the counter is told

Generating an address sends one event to Google Analytics. It says that a mailbox was created, whether a name was typed in by hand, and whether the domain was changed from the default. Three facts, no identifiers.

Over the life of the address the counter may also hear that the address was copied, that a message arrived, that somebody registered, that somebody signed in. Every one of those is a count.

The address itself is never sent. No part of any message is ever sent: not the sender, not the subject, not a line of the body, not the name of an attachment. A mail service that leaked those to an analytics platform would be handing over the only thing it exists to protect, so the boundary is drawn in the code rather than in this paragraph.

While the address receives mail

Each message that lands is stored so it can be shown to you: sender, subject, headers, body, attachments. That content is not scanned to select advertising, not sold, and not passed to anyone.

If you registered, the account adds an email address and a password hash. The password itself is never written down and cannot be recovered from the hash; your address exists to sign you in and to receive a reset link, and is used for nothing else.

Anyone holding a guest address can read what is in it. There is no password on a guest mailbox and there cannot be one without turning it into an account: with no identity to check, there is nothing to check against. Generated addresses are unguessable in practice, but the rule to work by is that guest mail is readable by anyone who learns the address. Anything you would mind a stranger seeing belongs in a mailbox behind an account.

Meanwhile, in other companies' systems

Cloudflare accepts every connection before it reaches this server, filters attacks and serves cached files, so it sees the address of every visitor and keeps aggregate traffic figures. That happens under Cloudflare's privacy terms rather than ours.

Cloudflare Turnstile watches the registration and password forms for signs of automation. No puzzles, and the verdict never joins an advertising profile.

Amazon SES carries password reset mail, and only that, from a separate sending domain.

Google runs the advertising and the visitor counter, and sets cookies for both. Those cookies may be used by Google and its partners to select ads from where you have been before. Personalised advertising can be switched off at Google Ads Settings or blocked in your browser; the generator works the same either way, and no page here waits for your consent before it will show you anything.

The moment the address ends

For a generated address with no account behind it, the ending comes twenty four hours after you last opened it. Pressing generate again brings that ending forward to the same second, taking the mail with it.

Registering moves the numbers rather than the principle. The mailbox then counts a week from your last sign in, any individual message inside it gets a month at the outside, and a file attached to a message shares the message's ending exactly.

Deletion is the removal of the row, not a flag on it. Nothing is archived, no backup carries a second copy, no extract is kept for analysis. After the cleanup job runs, that message cannot be produced for you, for an advertiser or for anyone who arrives with a demand, because there is no longer anywhere it could be read from.

After that, if you want it gone sooner

Delete the account in your settings and the email address, the password hash and every mailbox and message attached to it go in one operation. For a guest there is nothing to delete: generating a new address destroys the old one immediately, and doing nothing destroys it within a day.

Visitors in the EU and the UK have four rights under the GDPR: to see what is held, to correct it, to erase it and to complain to a supervisory authority. They apply here, and the first one is unusually easy to answer, because the walkthrough above is the complete inventory. The third is faster still: pressing generate erases the previous mailbox before any request could be written.

Children

This is not a service for children, it is not advertised to them, and no information about anybody under 13 is held knowingly. Tell us that an account belongs to a child and it is deleted, without documents or an argument.

When this page changes

The date at the top moves with it. A change in what is collected will be described here in sentences, not slipped into a list.

Questions: hello@tempmailgenerator.net or the contact page.