On your device
Kept, encrypted, free
History lives in an encrypted database on your own hardware, with no cap and no charge. It is yours. We could not hand it over if we were asked, because we do not have it.
End-to-end encrypted · No phone number
Encrypted messaging that forgets.
Your device remembers everything, free and for as long as you like. Our servers hold a message only until it is delivered, and never past 24 hours.
server copy expires in
23:59:59
Three places a message can live. We removed two.
On our servers
At most 24 hours
A message is deleted the moment your device confirms it arrived, and unconditionally at the 24-hour mark whether it was delivered or not. The limit is enforced by the protocol, not by a policy page — a client cannot ask for longer.
In a cloud backup
Nowhere at all
There isn't one. Most encrypted messengers protect your words in transit and then copy them, in the clear, to a cloud drive. That is the hole this exists to close.
What we don't have.
A messenger paid for by advertising has to know who you are, who you talk to, and what you are interested in. We are not paid for by advertising, so we don't need any of it.
- No phone number. A handle and a passkey. Nobody you message learns your number, because we never asked for it.
- No social graph. Who you talk to is not recorded. Your address book is never uploaded in a form anybody can read.
- No advertising. Not now and not later. There is nothing here for an advertiser to buy.
- No memory. Not a retention policy that could change. A ceiling the protocol enforces three times over: when a message is written, when it is read, and at the router.
Everywhere, from one core.
The cryptography is written once, in Rust, and every app runs that same audited code. The difference between the phone and the browser is what you see, not what protects you.
Browser
Available
macOS
Available
Windows
Available
Linux
Available
iOS
In testing
Android
In testing
What isn't built yet.
Landing pages usually leave this out. A product whose entire claim is that you can check what it does should say where it has got to.
Working today
- One-to-one and group messages
- Voice and video calls, browser and desktop
- Attachments, encrypted under their own key
- Delivery and read receipts
- Multiple devices, none of them primary
Not there yet
- Calls and attachments on the phone apps
- Push notifications
- An encrypted archive for those who want one
- An independent security audit
Until that audit is published, treat this as software you can read rather than software that has been vouched for. The source is open for exactly that reason.