How it works
Encrypt on your device with AES-256-GCM before anything is stored. Your browser creates a 12-word passcode (BIP-39). The recipient enters those words on this site — we only ever store ciphertext; your passcode and message NEVER touches our servers.
Three steps
- Open the app and write your message. No account, no email — your browser gets a random 12-word passcode.
- Encrypt locally. Keys use PBKDF2-SHA256 (310,000 iterations). We only receive the ciphertext and a fingerprint — not your actual message.
- Share the passcode with the recipient. They enter the passcode, load the ciphertext, then decrypt in their browser. Once the message is read, the ciphertext is deleted. After the recipient views the message, it is gone forever.
Who it’s for
- A founder sharing terms ahead of a signed deal
- A journalist receiving a confidential tip
- An attorney sending privileged material
- Boards discussing matters off the record
- Investors aligning before disclosure
- Any message not meant to persist
What makes this different
Signal protects your message. We protect that the message ever existed — on our side.
There are no accounts to freeze. No plaintext for us to hand over.
Limitations
No warranty. You are responsible for passcode handling. TLS still terminates at our server, so ciphertext is visible in transit on the one fetch that delivers it. A second load returns nothing by design.