What HeirVault is, what it is not, leaving will copies and files, the file editor, and how to begin.
No. HeirVault does not draft wills, create trusts, or give legal advice. You can store encrypted copies of a will, insurance policies, and other documents you already have, plus instructions, for contacts you name. See the Alternatives page for how we differ from will and estate apps.
Yes. HeirVault does not create a will, appoint an executor, or give legal advice. You can store encrypted copies of your will and other legal documents in the vault so named contacts can claim them after check-ins and the waiting period, alongside the notes and files you leave.
No. HeirVault does not autofill or sync logins for daily use. It is a dead man's switch for docs, logins, bank details, wallets, keys, and files beneficiaries claim after your check-in rules are met. Logins can carry a 2FA (TOTP) secret so the contact who claims sees working verification codes, and a built-in generator creates strong passwords and PINs. See the Alternatives page for password manager differences.
No. Those products are for everyday file sync and can usually read what you store. HeirVault is for what you leave: contacts you name claim it when you cannot hand things over. Your live vault is protected by end-to-end, zero-knowledge encryption. That means HeirVault stores ciphertext and cannot decrypt your live vault.
Create an account, set one password for sign-in and vault unlock, save your emergency kit offline, then leave docs, document copies, or files and name who should receive them. Check in on your schedule so nothing opens until your rules say otherwise.
You can leave:
Keep daily autofill in a password manager. We do not draft wills or give legal advice. For a practical packing list, see /help/what-to-leave.
Yes. Structured vault credentials support formats for logins, API keys, SSH keys, crypto wallets, bank accounts, and cards. Logins can include a 2FA (TOTP) secret that shows live verification codes, a built-in generator creates strong passwords, PINs, and API keys, and you can add custom sections when you need more. These files are for release handoff after check-in rules are met, not for day-to-day autofill. Keep offline backups of anything you cannot afford to lose.
Yes. Import CSV exports from Chrome, 1Password, Bitwarden, Proton Pass, and LastPass, or map columns from an Excel spreadsheet. TOTP columns import too, so 2FA codes keep working for whoever claims. Parsing happens in your browser and every entry is encrypted on your device before it is saved. Imports are for release handoff; keep daily autofill logins in your password manager.
Yes. Sign in on each device with your account. Unlock the vault with your password, a PRF-capable passkey that has vault unlock enrolled, or recovery flow on that device. Vault contents stay encrypted in transit and at rest; plaintext unlock happens in the browser on the device you are using.
HeirVault includes a built-in editor in the browser. You can use headings, lists, tables, callout panels, links, and inline formatting. Add images with crop and rotate tools, and attach encrypted files (PDF, Office, images, audio, video, ZIP) within your plan limits. Bodies use end-to-end encryption before upload.
A practical list of docs, accounts, and instructions people actually need in the first week.
Hand off the master key and context without replacing your day-to-day password manager.
Store seed phrases and recovery notes so heirs can act without getting the keys today.
Set your schedule, use the waiting period when you miss a check-in, and keep release paused.
Store your recovery phrase offline so you can regain vault access if you forget your password.
Tell people the plan exists, run a practice claim, and avoid a real claim email looking like phishing.
Steps for people who received a unique claim link by email.