Tests can be repeated,
but inbox responsibilities still matter

01 / Service scope

For test emails, not everyday email

Use temporary email to receive one-time verification codes, test registration emails, password reset messages, and other transactional notifications, or to preview email template layouts in our reader. You can get a temporary address without registering, but it has a defined validity period and shouldn’t be used for long-term account recovery, ongoing notifications, or critical business communications.

Long-term aliases are a separate service. After verifying your real email address with a code, you can create an alias that forwards incoming messages to that verified inbox. An alias isn’t an automatic upgrade to a temporary address and won’t transfer messages from a temporary inbox. For long-term email, sign in separately to manage your aliases.

Neither temporary addresses nor long-term aliases can send email, reply using the address, or resend third-party verification codes. Our HTML reader is for previewing and may not display messages exactly as every email client does. For layout checking methods and limitations, see the Email Template Preview Workbench.

02 / Validity and recovery limits

When a test case ends, so does its inbox

Temporary inboxes are valid for 3 hours by default. Each extension request made during that period adds 3 hours, up to a maximum total validity of 24 hours per inbox. Check the inbox display and the server’s recorded time for the remaining validity. An extension doesn’t extend a third-party verification code’s validity or reactivate an expired sign-in link.

Selecting “Get a new address” creates a new inbox and destroys the old one; it doesn’t add a backup address to the old inbox. Once an address expires or is destroyed, neither the address nor its emails can be recovered by refreshing, signing in again, or contacting support. Save any test results you need before switching addresses or ending your test.

Don’t link a disposable address to financial, production, authentication, or other important accounts that require long-term recovery. Receiving a verification code during a test doesn’t mean you’ll be able to recover the account using that address later. For ongoing use, choose an inbox you can keep access to, or use a long-term forwarding alias if appropriate.

03 / Allowed and prohibited uses

Testing requires authorization

Make sure the systems, accounts, and email content you test are within your authorized scope, and control your testing frequency and data sensitivity. Being able to create new addresses doesn’t mean you can create unlimited third-party accounts or that a third party agrees to accept disposable email.

This list covers common examples but isn’t exhaustive. If you’re unsure whether you have permission, get clear approval from the system owner first. If a third party prohibits temporary email or limits registrations, follow its rules instead of repeatedly changing addresses to get around them.

We may restrict access, suspend related inbox or forwarding features, or disable affected addresses or accounts in response to unusual traffic or suspected abuse. Don’t use this service as a target for load testing. Use a dedicated environment with explicit authorization for load tests.

04 / Email delivery limits

Automatic refresh doesn’t guarantee delivery

The inbox automatically checks for new messages, but those checks only reflect the messages Tempcase has received at that point. We can’t guarantee that every email will arrive or appear within a set time. Sender queues, rate limits, bounce handling, domain policies, and filtering or rejection by the forwarding destination can all affect delivery.

“Not received yet” alone doesn’t prove the sender’s system failed. Likewise, “the comparison email arrived” doesn’t rule out differences in sender routes, content, or policies. When troubleshooting, consider the sending time, destination address, sender logs, message identifiers, and bounce details instead of assigning responsibility based only on the inbox results here.

Keep evidence before drawing conclusions. Record the address used and the sending time, then check whether the sender’s system accepted the message. If you need a comparison, use another sending route you’re authorized to operate.

We can’t resend third-party verification codes, remove another service’s domain restrictions, or guarantee recovery of undelivered emails. For troubleshooting steps, see Verification Code Delivery Troubleshooter. If an email arrived but its code has expired, request a new one from the original service according to its rules.

05 / Your responsibilities

Keep your credentials and test results safe

Treat temporary inbox access tokens, account sign-in credentials, email verification codes, and authenticator keys as sensitive information. Don’t include them in public support tickets, shared screenshots, code repositories, or demo recordings. Don’t give sign-in codes to anyone or send valid codes or keys to our support email.

After using a shared device, sign out of your long-term forwarding account and clear the site data in your browser if needed. Clearing data may remove your temporary inbox access credentials, so save anything you need first. Keeping browser data doesn’t extend an address’s validity.

The Netflix and Uber emails shown on the homepage are demos illustrating verification and transactional email layouts. They aren’t affiliated with these brands and don’t represent real sign-ins, orders, trips, charges, or account security events. When assessing actual test results, check the sender, subject, and time; don’t treat a demo email as proof of successful delivery.

If you need to submit a test report, save redacted results separately and promptly, and follow your team’s data management requirements. Don’t send production keys, real payment information, or unnecessary personal data to a disposable inbox. For details about how we handle data, read our Privacy Policy.

06 / Service changes and support

We’ll communicate changes, but can’t make promises we can’t keep

We may adjust features, limit requests, or temporarily interrupt service when necessary for maintenance, security risks, unusual use, or changes to dependent services. We don’t guarantee a specific uptime, delivery time, or permanent availability of any inbox. Don’t rely on the service as your only channel for critical business communications or disaster recovery.

When these terms change, we’ll update the content and date on this page. We may also notify you on the site about changes to important usage limits, depending on the circumstances. Review updates before continuing to use the service. If you don’t accept the changes, stop using the service and save any results you need while they’re still accessible.

If you have questions about receiving email, forwarding, or these terms, contact support@tempcase.com. Please include when the issue occurred and the time zone, which feature you used, steps to reproduce it, and redacted error details. Don’t send verification codes, access tokens, authenticator keys, or complete sensitive emails.

These terms don’t exclude any rights or responsibilities that applicable law prohibits us from excluding or limiting. If you still have questions about the service or data handling, read our Privacy Policy before deciding whether to run this test on Tempcase.