How governance data is protected.

Tenant isolation

PostgreSQL row-level security on tenant tables: each organisation’s rows are filtered in the database.

Confidential items

Part 2 items and confidential documents are excluded from public packs and the public portal; only roles with Part 2 access can see them.

Audit log

Append-only: database triggers reject updates and deletes outside the retention job. Exportable by officers.

Uploads

File types are validated before a document is served, and downloads of files flagged as infected or quarantined are blocked.

Headers

Content Security Policy, frame protection and a restrictive permissions policy on every response.

Passwords

Hashed with bcrypt (12 rounds) and checked against known-breached passwords using a k-anonymity lookup.

MFA

Authenticator-app MFA is available on every account, with recovery codes, and organisations can turn on the sign-in check for members who have set it up.

Single sign-on

Microsoft Entra ID and Google.

Sessions

Server-side sessions; users can see and end their own sessions. Sensitive actions ask you to re-authenticate.

Brute-force protection

Accounts lock after repeated failed sign-ins, and magic-link, verification and recovery requests are rate-limited.

If you think you have found a security issue, email support@quorate.app with “Security” in the subject and enough detail to reproduce it. Please do not test against other organisations’ data.

Certifications and audits are set out on the trust page.