Your compliance data, protected by design

Every organisation's data is isolated at two layers. The application verifies your membership before any data access, and the database enforces PostgreSQL row-level security on org-scoped tables — the application's database role cannot bypass it. A query without an established organisation context returns nothing.

Access is via single sign-on (OIDC) through our identity provider, with role-gated entry to the portal. There is no open self-registration — accounts are provisioned, and MFA is enforced at the identity provider.

All traffic is encrypted in transit with TLS. Data at rest is encrypted by our managed PostgreSQL provider. Secrets and API keys are held in the platform's encrypted environment configuration, never in source control.

Every state-changing action — create, update, delete — is written to an append-only audit log with the acting user, organisation, and resource. Coverage is enforced in our build pipeline: a mutation route that doesn't log is a failing build.

Tiered rate limits protect every public and authenticated endpoint, with tighter per-user burst limits on AI endpoints. Outbound requests are guarded against server-side request forgery (SSRF), and all input is validated at the boundary.

User-supplied content is sanitised, sensitive values are masked, and inputs are delimited before they ever reach a language model; model responses are schema-validated before returning. We do not use your compliance data to train models.