Privacy
The architecture is deliberately simple: your browser talks directly to the mail provider, and MailFizz does not maintain its own user database.
Data used by the service
MailFizz creates a random temporary address, a technical inbox ID, an access token, and a session expiry time. These values are stored in your browser so the inbox survives a page refresh.
Where messages are stored
Temporary addresses and incoming messages are handled by Mail.tm. MailFizz calls its API directly and does not copy message content into a separate server database.
What stays in your browser
- the active temporary email address;
- the token required to read that inbox;
- the session start and expiry time;
- your notification preference.
Selecting “New address” replaces the local session and asks the provider to delete the previous inbox. You can also clear local data through your browser settings.
Installed app
The service worker caches only interface assets and an offline page. It does not add incoming message content to the persistent app cache.
Safer message viewing
Email HTML is intentionally not executed. MailFizz displays the text version, opens verification links only after your action, and never runs attachments automatically.
Important limitation
Temporary email is not suitable for confidential documents, banking, healthcare, government services, or important account recovery. Do not send anything whose loss could cause harm.