How Certus handles customer and user data.

Data minimisation

Certus is designed to collect the minimum operational data required for evidence workflows, access control, reliability, and support. Repository source code remains in your SCM unless you explicitly provide it elsewhere.

Org-scoped access

User access, API keys, evidence records, and dashboards are partitioned by organization. Administrative actions are attributable and auditable.

Documented processing

Retention, residency, and deployment commitments are defined through product configuration and commercial scope rather than hidden operational assumptions.

Identity and access

• Authentication is handled through Auth0-backed identity flows.
• Session state is stored in secure, HTTP-only cookies.
• API keys are hashed before storage and cannot be recovered once issued.
• State-changing actions may be recorded in an audit trail for forensics and support.

CLI data handling

• When dashboard sync is enabled, Certus stores scan metadata, severity counts, grades, commit references, and mapped control results.
• Evidence hashes and signatures may be stored for integrity verification.
• Source code is not uploaded as part of normal CLI dashboard sync.
• Repository identifiers, branch names, and commit SHAs are retained for traceability.

Encryption and integrity

• Public routes and CLI communication use HTTPS/TLS.
• Hosted data is encrypted at rest through provider-managed controls appropriate to the deployed environment.
• Evidence packs may be hashed or signed to support integrity verification and tamper detection.