3 hours by default
Receive email without signing in. You can extend the period manually, up to 24 hours per inbox. Expired messages can’t be recovered.
Retention limitsPrivacy policy
A one-time sign-up may only need a temporary inbox, while ongoing notifications may call for a forwarding alias. Here’s what information each service uses, how long it is retained, and what you can delete yourself.
Last updated: · Applies to tmprelay.com
Receive email without signing in. You can extend the period manually, up to 24 hours per inbox. Expired messages can’t be recovered.
Retention limitsLogin codes go to your email, and messages sent to your aliases are forwarded there too. Give senders your alias, not your primary address.
Forwarding and historyAnyone with the complete inbox link or access credentials may be able to read your messages. Closing the tab doesn’t destroy the inbox.
Protect links and devicesThis policy covers how information is handled when you use Tmprelay’s sign-in-free temporary inboxes, email-code login, forwarding aliases and forwarding history. Temporary inboxes are accessed with a credential and don’t require you to provide a personal email address. Forwarding requires you to verify an email address, which identifies your account and receives forwarded messages.
Temporary inbox messages and the forwarding history available after sign-in are separate sets of data. Deleting data from one doesn’t delete data from the other, and signing out of a forwarding account doesn’t destroy a sign-in-free temporary inbox.
This page explains how our service handles information. It doesn’t replace the privacy policies of registration sites, survey platforms or email providers. Before submitting a form to those services, check how they use the information you provide. For account recovery, sensitive identity documents or ongoing correspondence, use an email address you can control long term.
Receiving email requires an address, the delivered message and access credentials. Login and forwarding also require an email address where you can receive verification codes. The table below explains each separately, so “no registration” isn’t mistaken for “no data is handled.”
This policy doesn’t list unverified device fingerprints, advertising profiles or specific log-retention periods. If you have questions about information or retention practices not covered here, contact us using the email address at the end of this page. Don’t assume such information is kept for the same period as email messages.
| Information | Purpose | Important limits |
|---|---|---|
| Temporary address and access credentials | Assign an inbox address, identify the same inbox and restore access after a page refresh or when using the complete link. | Your browser stores the information needed to restore access. The inbox remains accessible until expiry, but anyone who obtains the link or credentials may be able to read its messages. |
| Message content and delivery details | Display the subject, sender, received time and message body, and provide options to read, delete or forward messages. | Temporary email follows its expiry time. The period for which forwarding history can be searched isn’t necessarily the same as the underlying data deletion period. |
| Login email and account credentials | Send login codes, identify your account, manage aliases and forward messages sent to your aliases to your email address. | Login session credentials keep you signed in. If two-step verification is enabled, we also process authenticator settings and information needed to verify one-time codes. |
| Alias settings and forwarding status | Identify the account an address belongs to, whether forwarding can continue, and any available delivery or forwarding history. | Disabling or deleting an alias is different from deleting existing history. Neither action recalls copies already delivered to an external email account. |
| Information needed to handle requests | Handle webpage and API access, authentication, request rate limits and troubleshooting, such as limiting access based on request origin. | This page doesn’t promise that request information is deleted at the same time as temporary email, or make specific guarantees about unverified log fields or retention periods. |
If you only need a one-time code, you can use the sign-in-free temporary inbox. You only need to sign in to your email and manage aliases.
Temporary email addresses are valid for 3 hours by default. Each time you use “Extend by 3 hours” in the inbox, you add 3 hours, up to 24 hours per inbox. Check the countdown below the address and the extension confirmation; an open browser tab doesn’t mean the inbox is still active.
Refreshing the page, reopening a link or automatically checking for new mail doesn’t extend the expiry time. Only a successful extension changes it.
When the validity period ends, the temporary address and its messages are deleted automatically, and expired messages can’t be recovered. Destroying an inbox also ends access to its address and messages. A saved link can’t restore an inbox that has expired or been destroyed.
If a confirmation email may take several hours to arrive, extend the inbox before it expires. For notifications expected to arrive on another day, use long-term forwarding or your regular email address instead. Check expiry planning to match your inbox to when you expect the message, rather than trying to recover it after expiry.
Your email address receives login codes and serves as the destination for messages sent to your forwarding aliases. When you give a registration service an alias, we process incoming messages and forward them to your email address. Message delivery also involves the sender and your email provider.
After signing in, you can view forwarding history from the past 30 days in the console, including available subject lines, senders, statuses and message details. “Past 30 days” describes the history available to search in the interface. It doesn’t promise that all underlying copies, system logs or backups are deleted after 30 days.
Disabling an alias stops new messages from being forwarded. Deleting it removes its configuration. Neither action automatically deletes copies already delivered to your email account; delete those there if needed.
Likewise, deleting a forwarding history entry doesn’t delete the corresponding message from the sender’s or recipient’s email account. Go to alias management to manage aliases and existing history separately. For questions about what can be deleted at the account level, contact support.
Temporary inboxes don’t verify who you are through an email login. Access depends on the corresponding link or credentials. Anyone with the complete link or credentials may be able to read the messages, so don’t post inbox links in public chats, screenshots, on social media or in shared documents.
Being able to open the same link on another device is convenient, but it also means you should protect the link like private information. Temporary email isn’t suitable for long-term account recovery, financial information or anything else that requires lasting, exclusive control. See the inbox recovery guide.
On a shared device, delete messages or destroy the temporary inbox when you’re done, then close the page. If you used a forwarding account, sign out as well. Clearing local browser data may remove your way to regain access, but it doesn’t itself delete data from the server.
Different actions affect different things. First check whether you want to handle one message, a temporary inbox or a long-term forwarding alias. If you need to keep a registration number or event date, note it down before deleting anything. Temporary messages that are deleted or expire can’t be restored by reopening the page.
To ask what information we hold about you, request a correction or deletion, or ask about data handling not covered by this policy, email support@tmprelay.com. Tell us whether your question concerns a temporary inbox or forwarding account, roughly when the issue occurred and what you’d like us to do. We may need to verify that you control the relevant account or information.
Don’t include login codes, authenticator keys or complete inbox access credentials in your email. For specific data requests, we’ll explain what we can verify and any applicable limits. We can’t promise to restore temporary messages that have expired or been deleted. Any future policy updates will show a new date at the top of this page.
Just describe the issue in writing. If you include a screenshot, hide any verification codes and private links first. If you’re waiting for a confirmation email, you can also check the pre-registration checklist.