“Temporary” isn’t an abstract promise. Here’s what temporary inboxes and forwarding aliases handle at each stage: creation, receipt, extension, and expiration.
The address receives mail; the access credential proves that the current browser can read it. It isn’t an account password and won’t bring an expired address back. Don’t treat a browser session as cross-device sync.
The system processes the sender, subject, body, and delivery details so they can appear in your inbox. Temporary email is suitable for text verification codes and confirmation links—not as a file repository or channel for sensitive communication.
Each extension adds 3 hours. It only moves the upcoming expiration time; it doesn’t turn the old address into a permanent one or guarantee that the sender will accept it.
Once 24 hours have passed since creation, you can’t extend the address further. There is no recovery path for the address, access, or mail, so complete verification or move your account email before then.
A forwarding alias can keep the entry point active long term, but mail in the dashboard still has a defined retention period.
Enter a real receiving email address and sign in with the 6-digit verification code. This is the final delivery destination; the service you register with sees only the alias.
Incoming mail is forwarded according to the alias settings, with optional spam detection, allowlists, and blocklists. The system must briefly process message content to perform these actions.
The dashboard archive is for short-term tracking and shouldn’t be relied on after 30 days. Save mail that you truly need long term in your receiving inbox.
The message is delivered normally to your receiving inbox, while a short-term copy remains in the dashboard to help troubleshoot delivery and spam classification.
To limit storage pressure, large messages continue to your receiving inbox, but the dashboard keeps no searchable copy.
Ask the sender to use a trusted file link, reduce the attachment size, or split the message into multiple sends. Email encoding may increase the final size.
Temporary inboxes are designed for short-lived text communication. When you need attachment continuity, choose forwarding mode instead.
A privacy promise is only verifiable when it names specific data items — not a vague "we value your privacy".
Recipient address, sender address, timestamps, delivery status. Without these we can't forward mail — or tell you where a message stalled when things break.
The anti-spam engine scores content mechanically. No human reads it; the outcome surfaces only as one of three states — forwarded, blocked, or flagged.
The disposable inbox requires no signup, and its access credential lives only in your browser session. We cannot map an inbox to a person.
When an inbox expires, an archive turns 30 days old, or an alias is deleted, the data is purged. There is no shadow backup — and no paid "recovery service".
Stating what we can't do protects you better than overclaiming.
Email isolation shrinks your address exposure; it is not legal anonymity. Your network environment, browser fingerprint, and the other site's logs are all outside our reach.
Senders may reject temporary domains. We don't rotate domains to fight blocks — that's spam-tool behaviour, and it would poison deliverability for every legitimate user.
Every piece of data has an explicit expiry. Using TmpOne as a filing cabinet is misuse; forward anything important to a long-term mailbox you control.
