Privacy policy
We host your mail. That is a position of trust, so here is exactly what we hold and what we do with it.
This describes how the service actually works rather than restating a template. It is not legal advice, and it has not been reviewed by a lawyer.
Your mail
Messages in your mailboxes are stored on our mail server so you can read them. They are not scanned for advertising, not profiled, and not used to train any model. There is no assistant here to feed them to.
We do not read your mail. An operator can technically reach the server that stores it, which is true of every mail host that is not end-to-end encrypted, and we will not pretend otherwise. Access happens only where it is needed to run or repair the service, or where the law compels it.
Mail is stored until you delete it. Deleting a mailbox deletes the messages in it, and deleting a domain deletes every mailbox on it. That is immediate and cannot be undone, so export first if you want a copy.
What we store about you
Account: your name, email address and profile picture, as supplied by Google when you sign in. We never receive your Google password.
Sessions: a session token, the IP address and the browser user agent for each sign-in, so you stay signed in and so we can spot abuse.
Service records: the domains, mailboxes and aliases you create, and the plan you are on.
Newsletters: the lists you create, the campaigns you send, and for each subscriber their address, their name if given, when and how they consented, and whether each email reached them.
Billing: invoices and the payments recorded against them. You pay by bank transfer, so card details never exist here at all. What we see is the line your bank reports — the amount, the date, the description you typed, and the sender's name and account number as the bank prints them.
Who else is involved
Google, because sign-in uses your Google account. Google learns that you signed in to this service.
Let's Encrypt, which issues the certificates that encrypt your connections. Certificate issuance publishes your domain name to a public transparency log — that is how the system works everywhere, not something specific to us.
Your bank and ours. Paying by transfer means your bank tells ours who sent the money and what you wrote in the description. That is how a transfer works everywhere, not something specific to us.
Our hosting provider, which runs the machines. We do not sell, rent or share your data with anyone else, and we do not use advertising or analytics trackers on this site.
If you subscribed to a customer's newsletter
The organization that runs the list is responsible for it; we deliver the mail on their behalf. We hold your address, your name if you gave one, the language you signed up in, when and how you consented, and whether each email reached you. We do not record your IP address, and we do not track whether you open anything or what you click.
Unsubscribing takes you off that list immediately. The record is kept, marked as unsubscribed, so that a later import cannot add you back. To have it removed entirely, ask the sender, or get in touch through the community group.
Delivery is not private by nature
Mail travels between servers, and we encrypt those connections wherever the other side supports it. But once you send a message it is in someone else's hands, and email as a protocol offers no guarantee about what happens next. If you need certainty, encrypt the message itself.
Your domain's DNS records, including DKIM, are public by design. Anyone can look them up.
Your control
Export everything, any time, from the dashboard. The Maildir export is lossless and another mail server will accept it, so leaving is a download rather than a request.
Delete a mailbox, a domain, or your whole account whenever you want. Deleting the account removes your service records and the mail stored under it.
To ask what we hold about you, or to have it removed, get in touch through the community group.
Changes
If this policy changes in a way that affects what happens to your mail, we will say so rather than quietly editing the page.
Last updated 16 September 2026