If you go quiet,
the people you love won't be left guessing.
Write down what they'll need: passwords, accounts, where the papers are, a few words for them. It's encrypted on your device. If you stop answering check-ins, it goes to the people you chose. We can never read it.
How it works
Write it down
Add notes and files to a vault. Everything is encrypted in your browser before it's uploaded.
Choose your people
Each recipient gets a personal link that holds half of the key. You send it to them yourself: by message, QR code or a printed page. Or invite them by email.
Check in
Every week or month we ask, by email or Telegram, if you're OK. One tap on "I'm OK" is enough.
If you go quiet
We remind you a few times, then start a final countdown. Only then is the other half of the key released, so your recipients can open the vault.
Three ways to leave something
For the people you choose
End-to-end encrypted. Only your recipients can open it, and only after you go quiet. We can never read it.
A public page
Something for everyone: a letter to the future, an announcement. Sealed until a date you pick, or until you go quiet. With a date, nobody can open it early, not even us; "if I go quiet" relies partly on our word, and the app explains exactly how.
A plain message
A simple text we email to your people when the time comes, with no links or accounts. We can read this kind, and the app says so wherever it appears.
We can't read it. By design.
Your notes and files are encrypted on your device with keys we never see. We only store ciphertext. A recipient needs both halves of the key: the half in the link you gave them, and the half we release only once your vault is due. The half in the link sits after the #, a part of a web address that browsers never send to a server.
The encryption is built on libsodium, a widely used, audited library. Every byte of our format is written down and checked against the same test vectors on every platform.
What we can see
- Your email address and your recipients' contact details, so we can reach you and them.
- Your check-in schedule and whether a vault is due.
- How much you store.
What we can't
- Your password.
- The names of your vaults and files.
- Anything inside them (unless you choose a plain message).
For the technically curious: how the encryption works
All cryptography runs in your browser (libsodium compiled to WebAssembly, in a Web Worker). Our servers only ever receive ciphertext, wrapped keys and one half of each recipient key.
Your password
Your password goes through Argon2id (64 MiB, 3 passes, random 16-byte salt) to a master key, which a BLAKE2b key derivation splits in two: an authKey that logs you in (we store only an Argon2id hash of it) and an encKey that never leaves your device. So logging in doesn't hand us your password, or anything that decrypts your data. Your browser refuses weak Argon2 settings, even if a server asked for them.
Keys and content
encKey wraps a random 256-bit account key; the account key wraps a random data key per vault. Notes are sealed with XChaCha20-Poly1305 (random 192-bit nonces) and padded to 256-byte blocks, so their length doesn't show. Files are encrypted as a stream (crypto_secretstream, 64 KiB chunks) that detects truncation and reordering. Every ciphertext is bound to its vault and item IDs as associated data, so nothing can be swapped between vaults.
Recipient links
For each link, your browser draws two random 256-bit shares, A and B, derives KEK = BLAKE2b("jc-release-v1" ‖ A ‖ B) and wraps the vault key with it. Share A goes only into the link, after the #: browsers never send that part to a server. Share B is stored on our server, encrypted again with a server key, and handed out only after release. Invited recipients don't get share A in a link: it is sealed to their own public key (X25519).
Why neither side can read early
Before release we hold B but never A; your recipient holds A but can't get B. After release, the recipient's browser downloads B and the ciphertext and decrypts everything locally. We never see the plaintext, at any point.
Public pages: a time-lock
A public page's key is time-locked with drand, a network run by about 20 independent organisations that publishes a signed value every 3 seconds. Your browser encrypts the key to the value for your date (identity-based encryption on BLS12-381). Before that value exists nobody can decrypt it; after, anyone can. We keep the lock outside our database and serve it only from that date on. The visitor's browser fetches the drand value, checks its signature, and decrypts.
For a page that publishes "if I go quiet", the date moves with every check-in: your browser seals it again, to the earliest moment your timer could release, and we delete the old seal. An old seal would still open on its own date, so this part relies on our word, and the app says so before you use it.
What it doesn't protect against
The web app's code is delivered by us, so a malicious version could leak keys; to make that harder it is hosted separately from our servers and shows its exact build at the bottom of every page. We decide when a vault is released: a malicious operator still couldn't read your vaults, but could release them early. Metadata (emails, schedules, sizes) is not encrypted, because we need it to reach you. And if you forget your password, nobody can recover your data: not you, not us.
The exact byte format is documented, with test vectors that every platform must reproduce byte for byte.
Honest limits
- What if I forget my password?
- We can't recover it, because it's what encrypts your vaults. You can set a new one, but your existing vaults become locked: you can't open them any more. They are still delivered to your recipients as planned.
- What if a recipient loses their link?
- We can't send it again: we never had it. Make a new link for them from your account while you still can, or invite them by email.
- Do I have to trust you at all?
- A little. The web app's code is served by us, so in theory a malicious version could steal keys. To make that harder, the app is hosted separately from our servers and shows the exact build it runs at the bottom of every page. The mobile apps (coming later) are signed and reviewed by the app stores.
- What happens if your service is down?
- Nothing gets released by accident. After an outage, every running countdown is extended by the length of the outage, and a vault is never released unless the warnings to you were actually delivered.
- What does it cost?
- The preview is free, with 10 MB of encrypted storage. More space will be part of a paid plan later.
- Can I delete my account?
- Yes, in Settings, with everything in it, and nothing is delivered after that. You can download all your data first, decrypted in your browser.