The map, not the keys
A useful continuity plan identifies where lawful instructions and authoritative records are kept. It does not need passwords, PINs, safe combinations, recovery codes, private keys, or complete account numbers.
Privacy & security
Preparedness should not require handing over the secrets that unlock your life.
Vault & Ledger follows a simple principle: collect enough structured information to create continuity, while deliberately leaving high-risk credentials and complete identifiers outside the platform.
Privacy by deliberate restraint
The strongest unnecessary secret is the one a continuity platform never collects.
Multi-factor access
Protected Owner, Staff, Admin, and Client areas require password authentication and a verified authenticator factor before continuity information can be accessed.
Role-specific boundaries
Portal access is separated by role. Clients, Staff, Admins, and the Owner receive different capabilities, and inactive identities are blocked rather than silently routed elsewhere.
Private records and files
Household data and private files are protected by database and storage access policies in addition to application-level route checks.
Accountable activity
Operational activity, updates, important access changes, and integration events are recorded to support review and investigation.
Careful communication
Email is used for notifications and safe client communication—not as a replacement for the private portal or as a channel for sending continuity-plan secrets.
A clear information boundary
What belongs in a continuity plan—and what stays out.
Appropriate to map
- Names of institutions and professional relationships
- Types of policies, documents, properties, and responsibilities
- Locations of authoritative records and lawful instructions
- Trusted contacts and practical next steps
- Missing information and unresolved continuity gaps
Keep outside V&L
- Passwords, PINs, and security answers
- Authenticator and account-recovery codes
- Safe or lockbox combinations
- Seed phrases and private cryptographic keys
- Complete Social Security, tax, or account numbers
Security is ongoing work
No responsible service should promise that any internet-connected system is breach-proof.
Our responsibility is to reduce what is collected, enforce access boundaries, maintain the application carefully, monitor meaningful activity, and improve controls as risks evolve.
Clients also remain part of that protection: use a unique password, protect the authenticator connected to the account, and never send private access secrets through email or support messages.
Questions are welcome
Privacy concerns should be discussed before a household begins.
We will explain what the service records, what it deliberately excludes, and how portal access works.