Security

Privacy needs more than a random address.

A trustworthy service must protect message content, control abuse, minimize retention, and explain its limitations honestly.

Production security checklist

  • Sanitize HTML email content and block remote trackers by default.
  • Scan attachments and restrict executable file types.
  • Rate-limit inbox generation and access.
  • Use TLS, secure headers, monitoring, and strict operational access controls.
  • Publish retention periods and deletion behavior clearly.
  • Prevent outbound sending to reduce spam and impersonation.

User safety

Do not put passwords, identity documents, payment details, or confidential records into a temporary inbox. Anyone with access to an inbox identifier may be able to read its contents depending on the implementation.

The HTML package does not claim real encryption, anonymous delivery, or mail-server security because those features require backend infrastructure.