How it works

Built for inheritance, not only storage

The vault stays private until someone requests access and your release rules allow it.

How controlled release works

A secure path from private storage to legitimate access. Nothing starts until a trusted contact makes a request.

LockedRequestWaitConfirmUnlock

What makes it different

This is secure storage with a release plan attached.

Security model

Sensitive records stay protected while you are active and still follow the rules you set after a request.

Release path

The three-step flow behind vault access

This is the full access path.

Step 1

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.

Step 2

Stay active to keep the vault locked

Trusted contacts must request access first. After that, continued owner activity keeps release from completing.

Step 3

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

Timed release, confirmations, or both together.

Inactivity window

30d

A typical owner policy can require a full inactivity period before timed release is even eligible.

Reminder cadence

7d

Checks can happen on a defined interval so release is progressive rather than immediate.

Trusted confirmations

2 total

Owners 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 built for the harder moment: making sensitive records 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.