FIRST,
THERE IS
ONLY MAIL.
Your message begins as information intended for one person. The rest of the system will now build around it.
Crypted.li is being built around a stronger idea than “trust us”. For protected Crypted ↔ Crypted mail, the architecture is intended to remove the server's long-term ability to reopen message content after the required cryptographic operation is complete.
BUILD THE VAULT ↓Your message begins as information intended for one person. The rest of the system will now build around it.
The payload is encapsulated. What follows is not decoration: each visual layer represents a boundary the protected message must cross.
A temporary message-specific key appears for the cryptographic operation. It is not meant to become a permanent skeleton key for every mailbox.
Protective segments lock around the message one after another. The structure only becomes complete when every expected layer is present.
When sender and recipient both use Crypted.li, the protected route does not need another mailbox provider in the middle of the conversation.
The protected payload reaches the authorized recipient side. The server should not need to retain permanent decoding capability just because delivery occurred.
Temporary service-side decoding material is destroyed once it has completed its role. Nothing meaningful should remain server-side that can later be reused to reopen protected content.
The product goal is simple: Crypted.li should not retain a usable key capable of reopening protected Crypted-to-Crypted message content later.
The strongest Crypted privacy model is intended for conversations where both endpoints use Crypted.li and no external mailbox provider is introduced into the delivery path.
Standard email remains possible, but another provider's infrastructure, policies and legal environment become part of the trust chain once the message leaves Crypted.
Crypted.li is intentionally narrow. It is being designed as private mail, not as another cloud platform that happens to contain an inbox.
Private correspondence is not meant to become material for routine advertising, behavioural profiling or indiscriminate content inspection.
The service deliberately refuses unnecessary media storage. Less accumulated content means less data available to expose.
150, 250 or 350 MB. The product encourages communication rather than endless accumulation.
The “Crypted cannot reopen it” promise must be backed by the final client key exchange, storage, backup, indexing and notification architecture — not by marketing text alone.
Every tier gets the same Crypted experience. Upgrades remain flexible; downgrades become available once usage fits inside the target quota.
150 MB mailbox
No image/video attachments
Web + native apps
250 MB mailbox
No image/video attachments
Web + native apps
350 MB mailbox
No image/video attachments
Web + native apps
Keep both correspondents inside Crypted.li whenever possible. Minimise third parties. Minimise retained data. And build the cryptography so the service itself does not retain the key needed to reopen protected mail.
CREATE PRIVATE MAILBOX ↗