Compliance

Controls reviewers can check, not slides they have to trust

Security, privacy, ethics, and operations controls reviewers can check before clearance.

  • BSI C5
  • ISAE 3000
  • Cyber Essentials Plus
  • GDPR
  • EU AI Act
  • EU-U.S. Privacy Shield
  • HIPAA
  • ISO 27017
  • ISO 14971
  • DORA
  • ISO 27018
  • ISO 13485

Security

Encryption, access control, and redundancy sit in the infrastructure layer, not added after. Each control below is documented and verifiable in the Trust Center.

  • FIPS-compliant AES at rest, TLS 1.2+ in transit
  • Per-customer keys and key management
  • Azure AD roles plus full audit logging
  • Geo-distributed redundancy and automated failover
  • DRATA-backed compliance monitoring

Privacy

What we collect is what the workload needs. Where it runs is your call. These are defaults, not add-ons.

  • Data minimization and tenant isolation by default
  • EU hosting or on-premises, without forced transfer
  • Named subprocessors available for review
  • Documented retention and deletion; no training on your data

Ethics

AI assists people in regulated work; people stay in control. The controls below cover what happens before a feature ships and how concerns get raised.

  • Security review on every feature before it ships
  • Bias, explainability, and safety evaluations where they apply
  • Anonymous concern form for employees, partners, and users
Anonymous concern form

Operations

What ships is meant to be traceable. Every change leaves a trail, and when something fails, traffic recovers without manual intervention.

  • Audit trails, change logs, and version control
  • Regular vulnerability scans and third-party pentests
  • Live failover and automated recovery
  • Incident response with root-cause documentation

In the Trust Center. Policies, reports, and the current control inventory sit there so reviewers can check them without waiting on a slide deck.

Yes. EU hosting is the default, with no forced cross-border transfer. On-premises is available when your own perimeter is the requirement.

No. Customer data is never used to train general-purpose models. Retention and deletion schedules are in the Trust Center.

FIPS-compliant AES at rest, TLS 1.2+ in transit. Each customer gets its own keys.

Through the anonymous concern form. Qualified staff review every submission.

Questions about the controls? Review them in the Trust Center

Start on Corti Labs, or talk to us about a deployment.