Data classification
Status: Accepted · Version: 0.1
| Class | Examples | Handling |
|---|---|---|
| Public | Marketing pages, category names, “what not to store” | May be cached on a CDN |
| Internal | Specs in this repository, non-secret runbooks | Org-visible |
| Confidential | Owner name, contact emails and phone numbers, vault titles, recipient display names, policy parameters | Access only for the owning user flow and least-privilege services. Not in analytics |
| Restricted | Instruction bodies, document bytes, verification artefacts, release-package payloads | Envelope-encrypted. Not in logs, traces, AI training, or notices |
| Prohibited | Passwords, PINs, OTPs, CVVs, recovery phrases, seed phrases, private keys | Must not be collected. Writes rejected |
Examples
Restricted, allowed:
Institution: Bank ABC. Account type: Savings. Instruction: I have an account with Bank ABC. Contact their deceased-estate team. The original supporting documents are stored in the blue folder in the study.
Prohibited, rejected:
PIN: 123456 Password: … Seed phrase: …
Confidential metadata may say the vault is called “Insurance” and the recipient is “Wife” so the owner’s home screen can render without decrypting the instruction.
Logs and errors
Validation errors may say “password fields are not accepted.” They must not echo the rejected secret back to logs.
Analytics
Product analytics may count “vault created” and category enums. They must not receive free-text instructions or contact channels.