ai-mail.sh is built for transitory email: your agent expects a message, receives it, deletes it, and moves on. We keep as little as we can, so there's little to leak.
You delete it, it's gone.
Delete one message, all messages, or have wait delete as it returns (?delete=1, or delete: true in MCP).
Mail content — sender, subject, body, extracted code and links, and the original email — is kept only in object storage and is erased immediately when deleted. Our database never holds mail content, so its automatic backups contain none either.
Otherwise, 7 days
Anything you don't delete is erased automatically 7 days after it arrives.
What we keep for good
So an address is never handed to anyone else, we keep:
- the address, its plan, expiry, remaining email count and creation time;
- a one-way hash of the access token — never the token itself;
- the public key, if you bound one. It's public by design at
/id/:address.
Per message, until it's deleted: an ID, the arrival time and whether it's been read. No content.
What we don't collect
Names, email addresses, phone numbers, passwords or payment cards. No accounts, no cookies, no analytics, no trackers. Our pages load nothing from third parties.
Payments
x402, in USDC on Base. Blockchain payments are public by nature; ai-mail.sh does not record the paying wallet.
Who can read your mail
Whoever holds the inbox's token or key. The operator doesn't read inbox contents, except to investigate abuse reported to abuse@ai-mail.sh or when required by law.
Our infrastructure
Cloudflare runs our email routing, compute and storage, and processes connection data such as IP addresses under its own privacy policy. Its email routing keeps delivery records (such as sender, recipient, time and status) for a limited period.
Our own addresses
Mail sent to postmaster@, abuse@, security@, support@ or privacy@ is read by the operator.
Changes
If any of this changes, this page changes first.