Privacy, storage, and email retention
temp-mail.dev is an interface to email providers. Your inbox credentials, provider-held messages, and optional shared access have different storage and retention rules.
What stays in your browser
Mailbox addresses and passwords are saved in local browser storage for restoration. The current tab also caches authentication tokens and up to 100 message previews per inbox in session storage. Full message bodies are not saved by that preview cache.
Clearing this site's browser data removes saved sessions. Account exports contain credentials and must be kept private. Anyone who can access this browser profile may be able to open its saved inboxes.
Where messages are processed
The email provider receives and stores incoming email. Requests to Mail.tm pass through the application's restricted transport proxy. The app retrieves messages and attachments for display; saving credentials locally does not extend the provider's retention policy.
Remote images are blocked by default because loading them can contact sender-controlled servers. If you enable images, those servers may observe the request.
Optional inbox sharing
Shared access requires a six-digit PIN and expires after the selected duration. Mailbox credentials are encrypted in edge storage for the share. The viewing browser receives read-only access without the mailbox password or provider token.
Share only with people you intend to give access to your mail. Shared pages and email API endpoints are excluded from search indexing.
Site analytics and contact
The site uses Vercel Web Analytics for aggregate site usage. Inbox passwords, authentication tokens, subjects, and message bodies are not intentionally sent as analytics events. Browser requests still reach the hosting and email infrastructure needed to operate the service.
Use the Contact on Telegram link in the app for support. Download any messages you need to retain before the email provider removes them.