Plain writing on digital legacy, password manager inheritance, crypto handoffs, and calm contingency plans. No legal advice, no scare tactics.
17 guides
17 results
A delivery service that cannot read your vault sounds like a contradiction. Here is the per-beneficiary handoff design that resolves it, mode by mode, including the one path that is not end-to-end and says so.
What ships today, who it is for, what the free plan includes, and the one delivery boundary we state up front. A launch note written the way we hope to run the product.
Passwords without authenticator codes are often useless. Here is why TOTP locks heirs out, what actually travels with a password export, and how to leave working codes without handing over your phone.
Passkeys are excellent while you are alive. Here is what they do not solve for inheritance, how they differ from TOTP and password managers, and what to set up so someone you trust is not stuck at a biometric wall.
HeirVault's client-side live vault library is public on GitHub and npm. Here is what is open, what stays private, and where assisted delivery still differs.
Encrypted at rest and zero-knowledge are not the same claim. Here is a plain threat-model guide to what browser-side encryption defends, what it cannot, and where handoff design still matters.
A claim email from an unknown company looks like phishing. Tell people the plan exists while things are calm. Here is what to say, and what never to share early.
The objection is fair. One strong secret that unlocks everything sounds fragile. Here is what it actually protects against, what it does not, and why vendor-readable storage is a different kind of risk.
1Password has real recovery paths for families and teams, and real gaps for everyone else. Here is what your people can and cannot reach, and how to cover the difference.
If your work could put you out of contact, named people still need a calm path to what you left. Here is how to think about leave, check-in, and claim.
