Keep your important files within reach, even when you cannot reach them yourself.
Add your files, choose who to trust, and set how many must agree for recovery. Each person gets a self-contained bundle.
Everything runs locally. Nothing leaves your browser.
How this works and how to use it securely
Everything happens on this device. Your files are encrypted in the browser. The recovery key is split into pieces. Nothing is uploaded and no server is involved.
This page works completely offline. For the most sensitive material, save this page with File › Save As, disconnect from the internet, then create your bundles.
Use a private machine. Prefer a computer you control over a shared or public one.
Hand bundles over privately. Give each guardian their bundle by the most private channel available: in person on a USB drive, or through encrypted messaging.
Never put seed words or private keys in a bundle. Bitcoin seeds belong on steel backup or codex32, not in Bitcoin Inheritance.
Everything runs in your browser and nothing leaves your device
This page works offline. Save it with File › Save As
Protected with age encryption
Open source (Apache-2.0)
1Guardians
Each person here will hold one piece of your recovery key
must agree to recover
Think about who might be reachable at the same time. A lower number is more forgiving if someone is unavailable.
Import contacts from existing project.yml
2Files to Protect
Drag & drop a folder here, or click to select files
These files will be encrypted and split among your guardians
3What Your Heirs Need To Know
Write these in your own words. Your guardians and your heirs read them, never us.
Where these words go
Your guardians hold everything. Nothing is published.
The method also goes on the Bitcoin chain, so it survives if every bundle is lost. This costs a small fee and cannot be undone.
Export it from your coordinator. In Sparrow: Settings, then Export, then Output Descriptor.
That is long for the chain. The bundles carry the same words for nothing, so keep the chain copy to the method a stranger would need.
Publish the text above first, then paste the id here and generate. Leave it blank and the bundles still work: the id then lives only on your estate page, so write it there either way.
goes on the chain and in the bundles
Recovery steps
This stays sealed inside the encrypted archive. It appears only when enough guardians come together.
If you also put it on the chain it becomes public and permanent. Any ONE of your keys opens that copy, now or in twenty years. Write the method, not the people.
bundles only
People and places
This stays sealed inside the encrypted archive. It appears only when enough guardians come together. It never goes on the chain.
4Generate Bundles
Even with enough pieces, the files stay locked until this date.How does this work?
Recovery will need a brief internet connection to verify the time lock.
Owner key (optional)
Paste an age public key (starts with "age1"). Each bundle then also holds OWNER.age: the recovery passphrase locked to that key. With the matching secret identity you can open your backup alone, without your guardians. Guardians see no difference.
Never paste seed words here. Use an age public key only.
You have not written anything for your heirs. The bundle still works. It will not tell them what to do with it.
Do a test run first. It makes throwaway bundles from a sample file, so you can practise a recovery without touching anything real.
TEST RUNThese bundles are for practice. They are built from a sample file, not yours, and every one is marked TEST. Turn this off before you make the real ones.