Data used to provide the service
The service processes inbox addresses, sender and recipient information, message bodies, recognized verification codes, attachments and delivery metadata. It also processes session identifiers and request IP information for access control and rate limits. Administrator operations are audited.
Raw email and attachment files use private object storage. Parsed message content, codes and attachment records are stored in the database. Authorized administrators can view retained message content.
Browser storage and connection passwords
A session identifier is sent in an HttpOnly cookie. The interface saves your language code in localStorage. The application does not persist your mailbox password or message bodies in localStorage.
Connection passwords are stored on the server as salted scrypt hashes. A generated password is shown after creation; closing the credentials dialog clears that displayed copy. If you explicitly download a credentials file, it contains the address and password in plain text and remains on your device. Protect that file.
What deletion changes
Cleanup is asynchronous and can be delayed by storage failures. Historical database messages have no automatic deletion deadline in the current cleanup policy; permanent deletion is managed centrally by the backend cleanup rules. This page does not promise immediate erasure of every copy.
| Action | User access | Retained data |
|---|---|---|
| Delete a message | The user cannot open the deleted message or its attachments. | The database deletion flag, body, verification code and attachment records are temporarily retained and managed centrally by the backend cleanup rules. |
| Inbox expires or is destroyed | The user cannot recover access, even with the old password. | Maintenance schedules raw email, attachment file and address-registration cleanup. Database message bodies, codes, attachment records and user-deletion flags remain available to administrators. |
External images and attachments
External images are blocked by default in message previews. Choosing to load external resources lets your browser contact the remote image server. That server may observe your IP address and request timing or use a tracking image. Closing and reopening the message resets this choice.
Email HTML is sanitized and displayed in a sandbox. Attachments that have not passed the configured scan remain quarantined. These controls do not make every message or downloaded file trustworthy.
Your choices
- Do not send sensitive personal information or permanent account-recovery email to a temporary inbox.
- Keep connection credentials private and remove downloaded credential files when no longer needed.
- Read the retention rules before using user deletion or destroying an inbox.