Security and privacy
Privacy statement
When you run eMailPlane on your own server, your mail lives there, and we never host those mailboxes or keep copies of their messages. So you never have to fight your hosting company over email settings, our delivery network carries your mail on its way in and out. Like every email delivery service, it handles each message briefly while passing it along, and never saves, logs or shares the contents. If your server is offline, the sender simply retries later, so nothing waits with us. Your server keeps an eye on the settings we manage for your domain and alerts you if anything changes that it didn't make. We keep delivery counts, not your contacts, and we'd only ever disclose anything if legally required. Want us fully out of the path? Switch to direct mode any time.
To let you try eMailPlane the minute you sign up, we also host two Starter mailboxes for you, hello@ and concierge@. Those are on our server, so we do hold their mail: the next section says exactly how.
Your hosted Starter mailboxes
Every new account gets two mailboxes on our own server, hello@ (your first address) and concierge@ (an inbox for an AI agent), so mail works before you set anything up.
- Where: on our server in a data centre in Atlanta, Georgia, USA, and in our encrypted backups with Cloudflare R2.
- How long: each message you receive is deleted automatically 90 days after it arrives. A copy of each message you send stays in our sending queue for 7 days, even after it has gone out, and up to 37 days if it has to wait its turn.
- Encryption: the full text of every message you receive is encrypted when it is stored. The index that lists your inbox (sender, recipient, subject line, attachment names) sits in our database, which is not yet encrypted at rest. Backups are encrypted before they leave our server.
- Who can reach it: you and the keys you create, each limited to your own Starter mailboxes; our software, which receives, virus-scans and files each message; among people, only the operator with administrator access to our server; the AI coding tools we use to build and run eMailPlane, which work on that server with administrator rights; and Cloudflare's network, only if you switch on reading mail in your dashboard, while it carries that mail to your browser.
- How to leave: download any message exactly as it arrived with your Starter key, then move to your own server and your own domain whenever you like.
The full answer, with every retention period, is in our privacy policy and data processing agreement.
How it's built
- Mail stays on your server. On a server you run, mailboxes, stored messages and signing keys live on that server.
- Stored messages are encrypted at rest on your server.
- Inbound mail is virus-scanned on your server before anything reads it.
- The API runs on your server, behind keys. Your apps call it at your server's own address, and every call needs a scoped key, except the few that must work before anyone has one, such as the error catalog, unsubscribe links and dashboard sign-in. The database, the queue and the mail server's admin are never published. What your server exposes, and which calls need a key
- Tokens are scoped and stored as hashes. Each token carries only the scopes it needs, and we never store the secret itself.
- Errors never repeat an email address, so they are safe to paste into a bug report or an agent transcript.
- Sending fails closed. If the suppression list or sending budget can't be checked, the send is refused, not attempted.
For AI agents reading mail
Email content is untrusted input for an AI agent. eMailPlane does not claim to be injection-proof. Planned protections Coming soon:
- every sender labelled by authentication (DKIM and DMARC) before an agent reads the message;
- untrusted content wrapped and hidden text removed, with HTML off for agents by default;
- reply-only sending by default: an agent's message to someone new waits for a person's approval, and the text of an email can't widen who an agent writes to;
- loop protection, and a check for secrets in outgoing mail;
- AI-sent mail disclosed and signed by default, so your recipients know.
Laws such as the EU AI Act place disclosure duties on the businesses that deploy AI. Disclosure will be on by default; meeting those duties remains the deployer's responsibility.
Who else touches what
| Service | What for | Your mail? |
|---|---|---|
| SSDNodes, with HIVELOCITY, Inc. | Hosting our server, in Atlanta, Georgia, USA | Delivery network: only in memory, while it passes your mail along, never stored. Starter mailboxes: stored there, with the message text encrypted. |
| Cloudflare | DNS, serving this website and your dashboard, and storing our encrypted backups | Inside our encrypted backups, which include your Starter mailboxes, and, only if you switch on reading mail in your dashboard, while it carries that mail to your browser. Mail travelling between mail servers never goes through Cloudflare. |
| Stripe | Billing | Never. Only billing details. |
The full list, with what each company can touch and where it is, is on our sub-processors page.
Report a vulnerability
Email the address in our security.txt. Please include steps to reproduce, and give us a reasonable time to fix the issue before you share it.