What you can verify.

This page states floors, not aspirations. Each one has a date, and each one can be reproduced on request. If a floor isn't on this page, we haven't proven it yet — ask us, and we'll tell you where it stands.

Last updated October 6, 2026

Environment

  • A dedicated production environment — its own network, identity pool and tenant broker — since September 14, 2026. Development is not customer-serving.
  • The production database runs Multi-AZ with automatic failover, since October 1, 2026.

Tenant isolation

  • Every customer’s data lives in its own tenant. Nothing is deployed to production unless an automated check confirms that every query by record ID is scoped to the requesting customer.
  • The platform refuses any sign-in token not issued for it — a 401 before any data is read.
  • Isolation is re-proven end to end when each new customer’s tenant is brought up.

Backup and recovery

  • A full production restore was exercised on September 29, 2026: a usable copy in 11 minutes, with a recovery point under 5 minutes.
  • Database backups are replicated to a second AWS region.

Access and secrets

  • Two-factor authentication (authenticator app) is available to every customer, scoped to admins or to everyone.
  • Production reads its secrets from a managed secrets store when it starts. No password or API key is written into its configuration.

Deployment

  • Nothing reaches production unless the tenant-scope check and the test suite pass. A visual regression check runs before every release.
  • Continuous vulnerability scanning of the servers, and automated dependency alerts on the platform, the tenant broker and both public websites.

AI

  • The platform calls a model for two things: drafting the report of a completed investigation for the investigator to review, and turning a Spanish or Korean search into English so it can search the training content. Before an investigation draft is requested, the names of the people in the record are replaced with placeholders; a search sends only the words typed.
  • The model vendor is a subprocessor.

Evidence integrity

  • Retraining records carry an integrity hash that is re-checked every time the record is opened.
  • Attestation signatures are bound to the deficiency they attest.
  • Times are recorded by the server in UTC; inspections, deadlines, certificates and reports are shown in your organization’s timezone.

Your data

  • You own your data and your compliance records. Complete export during the term and at termination is in the contract.

Where the photographs live

  • For sites with trade-secret or security sensitivity, Compligence is designed so that inspection photographs can reside in storage the site owner controls, with the platform holding only the record and the reference.

Security contact: security@compligence.ai

Due Diligence Safety and Health LLC is not a law firm and does not provide legal advice.

Questions about how this applies to your sites? See the FAQ or request a demo.