The basic flow
Why in-memory storage matters for privacy
Most email systems write messages to disk (SSD or HDD storage). This means data persists even after "deletion" until the storage sectors are overwritten. Redis is an in-memory database — data only ever exists in RAM. When the key is deleted, the data is gone immediately and completely, with no disk footprint to recover.
MX records — how email finds you
When someone sends an email to swift.eagle291@houdininbox.com, their email client looks up the MX (Mail Exchange) DNS record for houdininbox.com. This record points to Cloudflare's email routing infrastructure, which accepts the email and forwards it to our backend via a webhook.
This is the same fundamental mechanism used by Gmail, Outlook, and every other email service — the difference is what happens to the message once it arrives.
Why there's no signup
Traditional email services need an account because they need to store your messages persistently and authenticate you on return visits. Houdininbox doesn't store anything persistently — your browser is the only "account" that exists. The address is generated locally, and your browser session is the only thing that can read your inbox.
What happens to emails after 10 minutes
The backend runs a timer for each active inbox. When it expires, a single Redis DEL command removes the key and all associated message data. There is no archive, no backup, no recovery. The data is gone in the same way RAM is cleared when you power off a computer.
For developers: Houdininbox uses Cloudflare Email Workers for inbound email routing, Redis for in-memory inbox storage, and a lightweight Node.js backend on Railway. The entire stack is serverless-compatible and designed for minimal latency.