How can we help?

Yes. Check-ins and the waiting period are dead man's switch mechanics. HeirVault builds that around docs, passwords, document copies, and files beneficiaries claim after release rules are met. Your live vault is protected by end-to-end, zero-knowledge encryption. That means HeirVault stores ciphertext and cannot decrypt it. See Alternatives for other dead man's switch tools, or the high-risk contingency handoffs page if that framing fits your situation.

HeirVault does not detect death or contact authorities. It detects missed check-ins: absence on the schedule you set. You choose how often to check in. If you miss one, a waiting period starts with email notices so you can stop release with a single check-in. Only after that waiting period ends without a check-in can beneficiaries begin to claim what you designated. Longer walkthrough: /blog/dead-mans-switch-explained.

Docs, logins with 2FA (TOTP) codes, bank accounts, cards, crypto wallets, API and SSH keys, spreadsheets, notes, step-by-step instructions, house codes, account context, and files for contacts you name, including copies of wills, insurance policies, and other legal documents you already have. They claim what you set aside when you cannot hand things over. Keep daily autofill logins in a password manager. We store those copies under end-to-end encryption until claim. We do not draft wills or give legal advice.

If something happens and you miss check-ins past the waiting period (14 days on Free; 7 to 14 on Pro; 1 to 14 on Shield), they can claim what you set aside. Until then, designated content stays protected by end-to-end encryption.

When release starts, they get a unique claim link by email and create or sign in to an account. Depending on delivery mode, HeirVault assists with the handoff key, they use an enrolled account key, or they enter a beneficiary passphrase you shared. Contents decrypt in their browser.

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.

Your live vault is protected by end-to-end, zero-knowledge encryption. It encrypts in your browser before upload, so HeirVault cannot decrypt it. HeirVault-assisted delivery stores a protected key for that beneficiary handoff only and transfers it after claim. That means assisted handoffs are not end-to-end to the beneficiary alone. Direct-account and owner-shared delivery keep the handoff key off HeirVault servers.

Create an account, set one passphrase 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.

Yes. HeirVault uses one passphrase to sign you in (via OPAQUE, without sending the cleartext) and to unlock vault encryption on your device. Compatible passkeys can also unlock the vault. Email codes sign you into the account only and never unlock the vault. If you lose the passphrase and your emergency kit, those contents cannot be recovered by us.

Add contacts (and optional groups) on the Contacts page. Mark each contact as a beneficiary, a witness, or both. Groups are for beneficiaries only. Assign beneficiaries on each file for who should receive it after release. You can also assign contacts on the Vault page or a folder for vault-wide or folder-level defaults. Each beneficiary opens only their handoff using the delivery mode you chose.

500 MB vault storage, up to 3 beneficiaries, 3 groups, 10 folders, and a custom check-in schedule from 7 to 365 days. Same leave-and-claim path as Pro and Shield. Your live vault is protected by end-to-end, zero-knowledge encryption. That means HeirVault stores ciphertext and cannot decrypt it. Pro raises vault storage first, then contacts and folder limits, plus witnesses, session history, milestone unlock dates, and a waiting period you can set from 7 to 14 days. Shield adds the device check-in API, shorter intervals, waiting period from 1 to 14 days, audit history, and a priority claim and reminder email queue.