Messages only you two can read.
Enchant is a private messenger built like a lockbox. Every word is sealed on your phone before it leaves. The server that carries it holds no key, and under Veil it never learns who wrote it.
- 0
- messages we can read
- 100%
- device side encryption
- 0
- sender details under Veil
Maya
end to end encrypted
How a message travels
The journey of a message
Watch what happens the moment you hit send. Sealed at one end, sealed in the middle, and opened only at the other.
Ava writes
Her phone seals the message in a fresh Envelope, with keys that have never existed before. The outside carries only Ben's destination, and a secret reply token rides inside, so her name never needs to appear.
Sealed on deviceEnchant's server
The server reads the destination on the outside, nothing more. It never sees the message inside, and it never learns who wrote it. Timing and destination stay visible by design; that is the honest limit, and Veil was built within it.
Destination only · Veil onBen reads
The envelope opens for Ben alone, because only his device holds the matching keys. His reply rides back on the secret token, no names attached, and the keys retire the moment they are used.
Unsealed by keysEnvelope · new keys every message
Destination · the only thing on the outside
Veil · the writer's name never appears
Rotation · break one key, the rest stay sealed
The front page
Sealed twice, and that is the point
Two layers of protection, working together. Not even our own servers ever see your words in the clear.
Voice & video calls
Voice and video ride the same Envelope that protects your messages.
Groups & channels
One message, sealed once, for the many. Each member opens only their own copy, and the server never learns who else was in the room.
Polls & location
Interactive messages obey the same seal as text. Nothing leaves the thread in the clear.
Status & stickers
Expressive, brief, and sealed by the same Envelope as everything else.
From the build log
Privacy isn't a feature here.
It's the whole reason.
Enchant exists because private messaging shouldn't require faith in a company. It should require only mathematics.
Why we built it
Every messenger we tried kept a backdoor to our conversations, in the metadata, in the ads, in the 'we promise to be good' terms of service. So we built the one where the math, not the promise, does the work.
The server is a post office
It sorts sealed envelopes and delivers them. It doesn't open them, read them, or remember who sent what. When someone demands 'the data', there is no data to hand over.
Locked in, not aspirational
Veil hides the sender. The Envelope turns keys anew every message. Backups seal to a key only you hold. These are not roadmap items; they are the build.
Privacy, not a promise
We built the server to not know
Most apps ask you to trust them. We designed Enchant so trust is unnecessary. The infrastructure is cryptographically incapable of seeing your conversations.
You seal it
Your message is wrapped in an Envelope, encrypted with fresh keys that only you and your recipient can ever derive.
We ship it blind
Veil strips away the writer. Our servers see a sealed envelope moving to a known destination, but never the hand that wrote it. That is the entire view, nothing more.
They unseal it
Only your recipient's device holds the matching keys. The message is never readable in transit, at rest, or by anyone in between.
What we see vs. what you see
If our infrastructure were seized tomorrow, the attacker would inherit sealed envelopes, random noise, and zero plaintext. Your conversations would remain exactly as private as the day they were sent.
Questions people ask
Get the app
Almost here. Sealed & ready
Enchant is being prepared for both stores. Pick your platform: you'll be first to know when the seal breaks.