How long do temporary emails last?

Retention is the single most consequential property of a disposable inbox, and the hardest to verify from outside.

Three different lifetimes people confuse

1. The inbox lifetime. How long the address itself resolves and can be opened.
2. The message lifetime. How long an individual message stays readable.
3. The storage lifetime. How long bytes physically remain in a database or object store.

A well-behaved service makes these align or explicitly states the difference. A message expiring before its inbox means you can open the inbox and find nothing.

What expiry should do

At expiry, three things should stop:

• The address should no longer resolve to an inbox.
• New mail to that address should be rejected at SMTP time, not silently accepted and discarded.
• Existing messages should be gone.

That third one is where services differ. “No longer accessible” via the API while rows remain in storage is a common and not entirely honest implementation. Deleting the rows is the stronger position.

Why a countdown beats a policy page

A written retention policy is a claim. A live countdown is evidence about the current inbox. When the interface tells you exactly how many minutes remain, you can make a decision — extend it, or finish what you are doing — instead of guessing.

The practical failure mode

The failure people actually experience is not a service keeping data too long. It is the inbox expiring while they are still waiting for a code, or the address expiring before they come back to a signup they started.

Two habits avoid almost all of it:

1. Finish the verification in one sitting. Do not create an inbox, start a signup, and return the next day.
2. Extend before you wait. If the sender batches mail or greylists new domains, delays of several minutes are normal. Extending early costs nothing.

Why shorter is not automatically safer

A ten-minute inbox is not more secure than a one-hour inbox. Both use the same access control. The only thing a shorter window changes is how quickly you lose access — and how quickly anyone who obtained your token loses it too.

Choose the window that matches the task. Do not choose the shortest one as a security gesture.

What to assume

Assume messages disappear exactly when the countdown says, and that nothing is recoverable. Design your workflow around that assumption rather than testing it.