Trust Centre

Your risk data deserves serious security

Multi-tenant isolation, externalised authentication, append-only audit trails, and a minimal attack surface. Security is the default, not an add-on.

Your data is yours. Completely.

Tenant Isolation

Every tenant's data is isolated using PostgreSQL Row-Level Security. This means isolation is enforced at the database level — not just in application code. Even if an application bug bypasses a check, the database will not return another tenant's data. The application runs with a restricted database role that cannot bypass RLS policies.

We never store your passwords

Authentication

RiskQuilt uses OIDC (OpenID Connect) for authentication. Your users sign in through your existing identity provider — Google Workspace, Microsoft Entra ID, or any OIDC-compatible provider. We validate tokens issued by your IdP. We never store passwords, and we never manage credentials.

During trials, magic link authentication is available as a first-class option. No IT involvement needed to get started.

Where your data lives and who can access it

Data Handling

All data is stored in PostgreSQL databases hosted on Google Cloud Platform. Data is encrypted at rest and in transit. RiskQuilt staff do not have access to customer data in production. Administrative access is limited, audited, and requires explicit justification.

Every change is recorded. Nothing is overwritten.

Audit Trail

Risk, control, and event records use append-only history tables. Every change creates a new history entry with a timestamp and the user who made the change. History cannot be modified or deleted.

Cloud-native, minimal surface

Infrastructure

RiskQuilt runs on Google Cloud Platform using containerised services. The backend is written in Go — a compiled, statically-typed language with a strong security track record. A minimal dependency footprint is a design constraint: every dependency is individually justified and tracked, and code that processes user input has the smallest possible dependency surface. Every commit is scanned for known vulnerabilities.

Independent security testing

Penetration Testing

RiskQuilt was independently penetration tested by ReliSec Ltd from 22 to 25 June 2026, covering the web application, API, and all three MCP endpoints. The assessment identified only ten low and four informational with no critical, high, or medium-severity findings.

Download the summary report (PDF)

Report a vulnerability

If you've found a security issue, we want to hear about it. Contact security@riskquilt.com with details. We'll acknowledge receipt within 24 hours and keep you informed of our response.