Ship it.
Read it. Burn it.
Chain Vault encrypts passwords, API keys, and notes right in your browser. We store only ciphertext — never the plaintext, never the key. One link. You set the limit. Then it's destroyed for good.
Currently limited to approved Chain accounts.
Four steps between “I need to send this” and “it's gone for good.”
Compose
Type a password, API key, or note. It's encrypted in your browser before anything leaves your machine.
Seal
Set a self-destruct timer, a view limit, and an optional password gate.
Share
Forward the one-time link however you like — Slack, email, SMS.
Burn
The moment it's opened, it's destroyed. No copies, no record of the contents — before or after.
Built so we physically can't read what you send.
Zero-knowledge encryption
AES-256-GCM, entirely in your browser. The decryption key lives only in the URL fragment — it never reaches our servers.
Burns after reading
Every dispatch has a view limit. Once the limit is hit, the ciphertext is gone from our database — permanently.
Password gate
Add a passphrase the recipient gets out-of-band. Five wrong guesses and the dispatch destroys itself.
Notify on open
Get an email the instant your dispatch is opened, or send the link straight from Chain Vault instead of copy-pasting it.
Approved access only
Chain Vault is gated to approved Chain accounts behind its own login — no public sign-up loophole.
File drops
SoonEncrypted file attachments are on the roadmap. Text secrets — passwords, keys, notes — ship today.
The key never travels with the message.
Your secret is encrypted with AES-256-GCM using the WebCrypto API, right in your browser, before it ever touches the network. What lands on our servers is opaque ciphertext — we couldn't decrypt it even if we wanted to.
The decryption key lives only in the URL fragment, after the #. Browsers never send that part of a URL to a server — so the key travels only from your machine to the recipient's, over whatever channel you choose to share the link.