Disposable email with a narrower promise
Susmail is a small receive-only inbox for short verification flows. The product exists for the moments when a site needs to send a code or confirmation link, but you do not want that one-time exchange to become a permanent relationship with your personal mailbox. It is intentionally not a replacement for regular email, account recovery, or private long-term correspondence.
What the product is trying to do
Most temporary-email tools solve the same basic job: provide an address quickly and show the incoming message. Susmail focuses on making that narrow loop easier to inspect. The reader pulls likely verification codes and primary action links into separate controls, keeps a text fallback available, and blocks remote images by default so opening a message does not automatically fetch sender-controlled tracking pixels.
The design goal is not to hide the tradeoffs. Temporary addresses are useful precisely because they are disposable, but that also means they are poor fits for anything you might need to recover later. If a signup can affect money, health, work access, legal identity, or a lasting account, use a durable mailbox you control instead.
How a typical session works
Opening the inbox creates or restores a short-lived address in the browser session. You copy the address into a form, wait for a message, then use the extracted code or confirmation link if one is detected. The countdown shown in the interface is part of the product contract: when the inbox expires, the service treats the address and its message history as gone. The burn control lets you delete the current inbox earlier when you are finished.
Susmail is receive-only. It does not send mail, relay replies, or provide mailbox hosting. That keeps the service focused on one-time inbound verification flows and reduces the abuse surface that comes with outbound email features.
What Susmail measures
The service uses aggregate first-party rollups to understand whether the product is functioning: page views, inbox creation, messages received, message opens, OTP-copy actions, and similar product-flow counts. Those rollups are deliberately coarse. Susmail does not send email bodies, subjects, full sender addresses, inbox local parts, raw MIME keys, or message contents to product analytics.
Public pages may also use conservative advertising and consent signals where allowed, but the inbox, message reader, abuse flows, and operator surfaces stay ad-free. In explicit-consent regions, Google CMP behavior is preferred for Google advertising consent so users are not shown overlapping prompts for the same decision.