Trust and continuity
Preparedness only works if people trust where their information lives
If households are going to centralise important documents, contacts, and shared records, security cannot be a footnote. It has to be part of the product story from the beginning.
Your documents stay encrypted
Sensitive records are encrypted on your device before upload, so the practical value of centralising information does not come at the expense of privacy.
Household access stays controlled
Shared access matters for continuity, but it still needs clear household boundaries, passphrase control, and data isolation.
Trust should be explainable
People need plain-language answers about who can see what, how recovery works, and what happens if something goes wrong.
Security at every layer
Protection that supports continuity
This is where households keep information they may urgently need, so security has to support continuity without making the system unusable. The goal is strong protection with clear, explainable access.
From encrypted documents to household-level permissions and recovery controls, the platform is designed to keep sensitive records private while still making them useful at the moment they are needed.
Security features
- Client-side encryption for vault documents
- Zero-knowledge architecture for encrypted records
- AES-256 document encryption
- Household-scoped Row Level Security
- Recovery key model for vault access continuity
- Global session sign-out on password reset
What households need to understand quickly
Who can see my documents?
Only people with the right household context and vault access model. The server does not hold readable document contents.
What if I lose access?
Recovery needs to be visible and understandable, because continuity fails if access depends on perfect memory.
How does shared access stay safe?
Household collaboration is a strength, but boundaries, permissions, and auditability still matter.