Encrypted letter of instruction Prototype
Write instructions for the people who would have to figure things out, then lock them with a passphrase. It happens inside your browser. We never receive the letter, the passphrase, or the locked file, and this page makes no network requests.
Prototype. This tool has not had an independent security review. It uses AES-256-GCM with a key derived from your passphrase by PBKDF2-SHA256 (browsers do not yet offer Argon2, so we use a high iteration count). Anyone who guesses your passphrase can open the file, so use a long one and keep it apart from the locked file. If you forget the passphrase, nobody can recover the letter. Do not rely on this as your only copy of anything important. See Trust the code.
Your browser does not support the encryption features this page needs. Try a current version of Firefox, Chrome, Safari, or Edge over a secure (https) connection.
The page also clears itself when you close the tab.
Next: set up a full plan with check-ins and a passphrase split into shares.
Your letter is only as strong as your passphrase
The lock itself (AES-256) is not the weak point. Guessing a random 12-word recovery phrase is a different story from guessing a short passphrase, and the gap is enormous. Here is what a machine making a trillion guesses a second would get against a random 12-word phrase:
But a weak passphrase can be cracked in seconds; a long random one can't. The meter under the passphrase box shows how a real attacker would fare against yours, and the Plan demo can generate a strong one for you.
The real risks are weak passphrases, phishing, and lost shares, not brute-forcing a random key. Quantum computers are a long-term consideration for some algorithms, but they do not change this advice today.
Opening it without us
A locked letter should never depend on this website. The format is documented on Trust the code, with a short script that opens it using standard tools.