HeirVault
How it worksPricingSecurityAlternativesFAQ
HeirVault

Leave docs, logins, bank details, spreadsheets, will copies, and files for contacts you name. They claim when you can't. End-to-end encrypted. Your live vault encrypts in your browser before upload. That means HeirVault stores ciphertext and cannot decrypt your live vault.

Product

How it worksPricingAlternativesReferralsSign upSign in

Trust

SecurityPassword generatorPassphrasesPassphrase strengthContinuityDuress passphraseHelp

Who it's for

FamiliesCryptoFoundersHigh-riskJournalists

Legal

TermsPrivacyCookies

HeirVault. Leave docs, logins, bank details, and will copies for the contacts you name. They claim when you can't. Your live vault is end-to-end encrypted.

© 2026 TrueWear, LLC. All rights reserved.

HeirVault Help Center

How can we help?

Answers for vault owners and for people who received a claim link. Leave docs, passwords, spreadsheets, will copies, and files for contacts you name. They claim when you can't. Your live vault is protected by end-to-end, zero-knowledge encryption.

I own a vault

Check-ins, passphrases, beneficiaries, billing, and setup.

Owner topics

I received a claim link

How to open designated docs and files when vault release starts.

Claim guide

Browse by topic

Pick a topic for detailed answers.

  • Getting started

    What HeirVault is, what it is not, leaving will copies and files, the file editor, and how to begin.

  • Security and privacy

    End-to-end encryption, passphrases, passkeys, MFA, and recovery.

  • Check-ins and release

    Check-in cadence, waiting period, and when access opens.

  • Beneficiaries and claims

    Contacts roles, claim links, beneficiary passphrases, witnesses, and release preview.

  • Billing and plans

    Free, Pro, and Shield limits, same encryption, and canceling anytime.

Popular questions

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 timed disclosure page if that framing fits your situation.

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 if something happens. 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 and Pro; the window you set 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.

50 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, and milestone unlock dates. Shield adds the device check-in API, shorter intervals, configurable waiting period, audit history, and a priority claim and reminder email queue.

Guides

Step-by-step help for the moments that matter most.

  • How to claim access

    Steps for people who received a unique claim link by email.

  • How check-ins work

    Set your schedule, use the waiting period when you miss a check-in, and keep release paused.

  • Save your emergency kit

    Store your recovery phrase offline so you can regain vault access if you forget your passphrase.

Still need help?

Email support@heirvault.io. For security vulnerability reports, use security@heirvault.io on the Security page.