The release path begins only when a trusted contact actually asks for access.
Secure release planning
How it works
Built for inheritance, not only storage
The vault stays private during everyday life, and any release path starts only after a trusted contact requests access.
Collection-specific access keeps family, finance, and personal records on different release tracks.
Trusted-contact requests start the flow, but owner activity and confirmation rules still control completion.
Vault records stay encrypted while the release model stays readable enough for real families to use.
How controlled release works
A secure path from private storage to legitimate access. Nothing starts until a trusted contact makes a request.
Timers, reminders, and inactivity rules keep requests from turning into instant release.
Access opens only after the chosen timed-release and confirmation rules are truly satisfied.
What makes it different
This is not only secure storage. It is a release plan built around real people, roles, and delayed access.
Security model
Sensitive records stay protected while you are active, and even after a request they remain governed by the rules you set in advance.
Release path
The three-step flow behind vault access
The home page summary is the short version. This is the full path the product is designed around.
Add trusted contacts and leave clear instructions
Set up the vault first: passwords, documents, inheritance notes, and the people who should be able to act later.
Stay active to keep the vault locked
Trusted contacts must request access first. After that, continued owner activity keeps release from completing.
Allow delayed release only when your chosen conditions are met
After a request is made, the vault opens only when the selected release path is satisfied: timed release, trusted confirmations, or both together.
Policy controls
The owner decides what release really means
Access is not one switch. It is a set of rules that the owner can tune around timed release, trusted confirmations, or a combination of both.
Inactivity window
30dA typical owner policy can require a full inactivity period before timed release is even eligible.
Reminder cadence
7dChecks can happen on a defined interval so release is progressive rather than immediate.
Trusted confirmations
2 totalOwners can require total confirmations on a request, counting the requester first and additional trusted contacts after that.
What the app is trying to solve
Most vaults stop at storage. This one is designed for the harder moment: keeping sensitive digital records protected now while still making them reachable later by the right people, under the right conditions.
FAQ
Questions about the release model
These answers fill in the operational details behind the release model.
What starts the release path?
A trusted contact must request access first. The vault does not start a release window just because a contact exists on the account.
Can the owner combine timed release and trusted confirmations?
Yes. The owner can choose timed release only, trusted confirmations only, or require both together before access can complete.
Do collections matter, or is everything unlocked at once?
Collections matter. Access requests are collection-specific, so different groups of records can follow different grants and release rules.