Most people use email that lives on someone else’s computer, run by a company whose revenue often depends on knowing things about you. That arrangement is convenient and mostly works — but it’s worth being clear-eyed about what it means, and about what genuinely changes when the mailbox is yours.
What your provider can see
When a company hosts your mailbox, it has technical access to a lot:
- The content of your mail. Unless a message is end-to-end encrypted (most aren’t), it sits on the provider’s servers in a form they can read.
- Who you talk to, and when. The metadata — sender, recipients, subject lines, timestamps, frequency — is often more revealing than any single message. It maps your relationships, routines and interests.
- Everything you’ve ever kept. Mailboxes are archives. Years of receipts, logins, medical and financial correspondence, and password resets accumulate in one place.
Whether a provider uses that access — for ad profiling, “features,” training data, or simply handing it to a third party on request — is a matter of their policy and the law where they operate. The point is that the capability exists, and you’re trusting a policy not to change.
What self-hosting actually changes
Running your own server doesn’t make email magically private — mail you send still travels to other people’s servers, and metadata is inherent to how email is delivered. What changes is who holds the mailbox:
- No provider is reading or profiling your content. There’s no ad business, no scanning pipeline, and no product built on top of your correspondence.
- You control retention. You decide what’s kept and for how long, rather than inheriting a retention policy designed around someone else’s interests.
- Access requests come to you. A demand for your data has to reach you — the data owner — rather than being served quietly on a third party who may never tell you.
- You can leave with everything. Your mail is standard files on a server you control. There’s no lock-in and no export queue.
What it doesn’t change
Honesty matters here, so the limits:
- Metadata still exists. Delivering mail means revealing sender, recipient and timing to the servers in between. Self-hosting doesn’t hide that.
- The other end is still the other end. If you email a Gmail user, a copy of that message lives in Gmail. You control your side, not theirs.
- Encryption in transit is not encryption at rest for both parties. TLS protects mail as it moves; it doesn’t stop the recipient’s provider from reading what lands in their mailbox.
For content that must stay private end to end regardless of provider, you still want a tool like PGP or an encrypted-by-design channel.
Ownership as the honest default
The privacy argument for self-hosting isn’t that it makes you invisible. It’s narrower and more durable: your mailbox stops being a product. The server is yours, the retention rules are yours, and no one whose incentives differ from yours is sitting in the middle of your correspondence.
cripta.to exists to make that ownership practical — the server runs on infrastructure you control, and you can take your data and go at any time. That is the part a free inbox can never offer, no matter how good the spam filter is.