Certification-grade data, protected end to end

Tenant isolation & access control

• Row-level security on every table — all application tables run RLS; access is filtered per row.
• Workspace & project scoping — membership and role are checked in the database on every read and write.
• Least-privilege roles — owner / admin / editor / reviewer / member, evaluated server-side.
• No shared tenancy in the client — the browser only ever holds a public, anon-scoped key; privileged keys never reach it.

Encryption

• In transit — TLS 1.2+ on every connection to the application and API.
• At rest — AES-256 encryption of the database and stored objects.
• Managed key handling — encryption keys are managed by the hosting platform, not embedded in the app.
• No secrets in the browser — AI and privileged operations run behind a server-side proxy.

Authentication & account security

• Email + password with verification — accounts must confirm their address before use.
• Two-factor authentication (TOTP) — optional authenticator-app second step, enforced at sign-in once enabled.
• Microsoft Entra ID (Azure AD) SSO — work-account sign-in, restricted to an approved-tenant allowlist enforced server-side.
• Idle auto–sign-out — sessions lock after 20 minutes of inactivity, every session, no exemption.
• Forced reset on recovery — a password-reset link cannot become passwordless inbox access; a new password is required.
• Password minimums & safe error handling — no account-existence disclosure on failed sign-in.

AI safety & data handling

• The engine owns every number — safety math, allocations, and robustness claims come from a deterministic core that carries its basis and citation. The AI never authors a number, a requirement, or a verdict.
• AI drafts within guardrails — the assistant is scoped to drafting and explanation; its output is reviewable and never silently written into the safety case.
• Server-side proxy — AI calls route through a controlled gateway; the client never holds a model provider key, and requests are logged for audit.
• Customer content may be used to improve our models — content you submit, including your corrections to AI drafts, may be used to train and evaluate Safety Lab Aero’s own models. Content from projects you flag as export-controlled is excluded entirely. We never expose one customer’s content to another, and you can opt out at any time. A zero-data-retention addendum with our AI subprocessor is being finalized (see roadmap).

Data residency & export control

• US-region infrastructure — primary data stores run in a US region (US-East).
• ITAR-aware egress — an egress control governs where flagged content may be sent for processing.
• Subprocessor transparency — the full list is below and kept current.
• GCC High & on-prem — separate deployment tiers for defense programs are on the roadmap.

Data lifecycle, audit & integrity

• Self-service erasure — an account owner can permanently erase their account and all analysis data.
• Certificate of destruction — every erasure issues a signed certificate with a SHA-256 manifest of what was deleted.
• Tamper-evident sign-offs — review sign-offs are chained with a verifiable hash chain; the chain can be re-verified on demand.
• Audit logging — workspace and review activity is recorded for accountability.

Infrastructure & subprocessors