Digital legacy planning
Plan for absence without exposing the vault too soon.
Store passwords, documents, and final instructions in one secure vault, then release access only through the rules you choose.
Vault flow
The vault stays closed during everyday life. A release path starts only after a trusted contact asks for access.
For owners
Organise passwords, documents, letters, and instructions into collections that match real life.
For trusted contacts
Give people a limited role, let them request access later, and keep the release path controlled.
Inside the vault
What people usually place here
Enough structure for real planning, without turning the page into documentation.
Logins
Passwords, recovery codes, and device access.
Documents
Wills, policies, scans, and signed records.
Instructions
What to do, who to contact, what matters.
Collections
Separate personal, family, or business records.
Process
One clear release path
Trusted contacts request access first, the vault stays locked while your chosen release path runs, and release happens only when your safeguards are satisfied.
Why it feels safer
Designed for real-life planning
Private now
Sensitive records stay locked while you are active.
Scoped later
Different contacts can support different collections.
Organized clearly
Policies, documents, and instructions stay grouped by collection.
FAQ
Questions people usually ask first
The short answers most visitors usually need before they decide to try the vault.
Does access happen automatically when I add a trusted contact?
No. Trusted contacts still need to request access later, and your chosen release rules must still be satisfied before anything unlocks.
Can different people access different parts of the vault?
Yes. Vault collections let you separate records and decide which trusted contacts are even eligible for each collection.
Are passwords and documents stored in plain text on the server?
No. Sensitive vault content and attached documents are encrypted before they are stored, while the app keeps only the operational metadata it needs to function.
Contact
Questions or planning help?
Send a note and we’ll reply by email. Keep it simple: planning help, release-path questions, or product support.