Platform
Data handling and retention
This page describes how platform data is classified, isolated, retained, and deleted across ingestion, lifecycle operations, exports, and governance history.
For: data protection officers, procurement teams, legal reviewers, and security operations owners.
Last updated: 28 April 2026
Ingested report handling
Uploaded assessment content is processed in tenant context and normalized into structured findings and metadata. Processing is restricted to platform operations required for scoring, triage, reporting, and audit workflows.
Workspace isolation and access
Workspace isolation controls ensure only authorized tenant users can access tenant records. Privileged actions require explicit authorization checks and are tracked as auditable events.
Exports and distribution
Exported reports and board packs are point-in-time outputs. Distribution rights should be controlled through tenant access governance and internal data-classification policy.
Retention and deletion
Retention is aligned to contractual, legal, and governance needs. Deletion workflows remove tenant-scoped data according to policy while preserving required legal and audit artifacts where obligations still apply.
This separation protects evidence integrity: operational records can be retired by policy while immutable governance artifacts remain available for defensibility and statutory review windows.
Backup and governance records
Operational backups support resilience and recovery. Governance evidence such as immutable snapshots and append-only audit records is retained according to policy so audit trails remain trustworthy.