PRIVATE MAIL SYSTEM / 2026 NO MASS SCANNING · NO AD PROFILING · MINIMAL DATA

DON'T
TRUST.
REMOVE
ACCESS.

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
00 / EMPTY SPACE

FIRST,
THERE IS
ONLY MAIL.

Your message begins as information intended for one person. The rest of the system will now build around it.

SCROLL TO ASSEMBLE / SYSTEM STATUS: UNPROTECTED
01 / MESSAGE CAPSULE

THE MESSAGE
IS SEALED.

The payload is encapsulated. What follows is not decoration: each visual layer represents a boundary the protected message must cross.

PAYLOAD / SEALED · MESSAGE ID / RANDOMIZED
02 / EPHEMERAL MATERIAL

A KEY IS
BORN TO DIE.

A temporary message-specific key appears for the cryptographic operation. It is not meant to become a permanent skeleton key for every mailbox.

KEY SCOPE / MESSAGE · RETENTION / TEMPORARY
03 / CRYPTOGRAPHIC SHELL

THE VAULT
BUILDS ITSELF.

Protective segments lock around the message one after another. The structure only becomes complete when every expected layer is present.

SHELL / ASSEMBLING · INTEGRITY / VERIFYING
04 / PRIVATE CORRIDOR

KEEP BOTH
ENDS INSIDE.

When sender and recipient both use Crypted.li, the protected route does not need another mailbox provider in the middle of the conversation.

ROUTE / CRYPTED → CRYPTED · THIRD-PARTY MAILBOX / NONE
05 / DELIVERY

ONLY THE
DESTINATION
MATTERS.

The protected payload reaches the authorized recipient side. The server should not need to retain permanent decoding capability just because delivery occurred.

DESTINATION / AUTHORIZED CLIENT · DELIVERY / COMPLETE
06 / DESTRUCTION

NOW DESTROY
THE KEY.

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.

KEY / DESTROYING · SERVER REOPEN CAPABILITY / REMOVING
07 / FINAL STATE

NO KEY.
NO BACKDOOR
BY DEFAULT.

The product goal is simple: Crypted.li should not retain a usable key capable of reopening protected Crypted-to-Crypted message content later.

FINAL STATE / PROTECTED · RETAINED SERVICE KEY / NONE
CRYPTED VAULT ASSEMBLY
CRYPTED / VAULT COREPHASE 00
STATUS / WAITING
THE POINT OF THE WHOLE SYSTEM

WE CAN'T HAND OVER
A KEY WE DON'T HAVE.

CRYPTED ↔ CRYPTED

Keep the trust chain short.

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.

CRYPTED ↔ EXTERNAL

The boundary changes.

Standard email remains possible, but another provider's infrastructure, policies and legal environment become part of the trust chain once the message leaves Crypted.

PRIVACY IS A SYSTEM PROPERTY

LESS TO SCAN.
LESS TO STEAL.

Crypted.li is intentionally narrow. It is being designed as private mail, not as another cloud platform that happens to contain an inbox.

001

No mass-scanning business model.

Private correspondence is not meant to become material for routine advertising, behavioural profiling or indiscriminate content inspection.

002

No image or video attachments.

The service deliberately refuses unnecessary media storage. Less accumulated content means less data available to expose.

003

Small mailboxes on purpose.

150, 250 or 350 MB. The product encourages communication rather than endless accumulation.

004

No magical security claims.

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.

SAME SECURITY MODEL

CHOOSE ONLY
THE CAPACITY.

Every tier gets the same Crypted experience. Upgrades remain flexible; downgrades become available once usage fits inside the target quota.

CRYPTED / 150
$15 / MONTH

150 MB mailbox
No image/video attachments
Web + native apps

SELECT 150 MB
CRYPTED / 350
$35 / MONTH

350 MB mailbox
No image/video attachments
Web + native apps

SELECT 350 MB
CRYPTED.LI

PRIVACY
WITHOUT
PERMISSION.

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 ↗