Security and privacy

The product is designed so a database leak, a curious beneficiary, or a missed email is not enough to open a vault. Marketing does not call this zero knowledge: a verified release process can, later, decrypt what the owner stored.

Vault isolation
Row Level Security limits every vault table to the owner, and only after multi-factor authentication.
Silent unless you choose otherwise
Naming a person does not create an account. Silent is the default. Notified and Notified with details are choices you make, and you can revoke them.
Encryption
Sensitive fields and files use a per-vault key.
Death Alarm
State changes go through one database function. A missed check-in cannot reach Released.
Audit
Important actions append to a hash-chained log. Updates and deletes on that log are rejected.
Staff
Billing staff can edit plan limits. They have no query path to vault content.
Security and privacy · INHERIT