Retention schedules
Policy by data class and jurisdiction, not one indefinite retention period.
DATA GOVERNANCE CONSOLE
Know what data exists, why it exists, who owns it and when it leaves.
The target governance layer makes data classification, legal basis, retention, residency, export and deletion operational rather than burying them in a privacy policy.
| Data class | Example | Default handling | Control |
|---|---|---|---|
| Public intelligence | Published institutional capability | Versioned + provenance | Freshness/review |
| Organisation confidential | Internal workflow configuration | Tenant restricted | RBAC + audit |
| Personal data | User identity/contact data | Minimise + protect | Access/export/delete |
| Special-category health data | Production patient information | Not part of public demo | Strict lawful basis, encryption, consent/policy, audit |
| Secrets | API/database credentials | Never in page source | Managed secret store + rotation |
Data rights
Export, correction, deletion/anonymisation and consent withdrawal workflows where applicable.
Residency
Track where production data is stored and which subprocessors receive it.
Ownership
Assign business and technical owners for every governed dataset.