Security & Trust

Built for partner-grade trust.

Pharma diligence teams ask three questions: who can see our data, what is the cryptographic provenance, and which regulations does the platform respect. We document the answers in plain language.

Evidence Bundle provenance pipeline: design result, canonicalize, SHA-256, Merkle root, OpenTimestamps, public-chain anchor, verify — left to right, with what-you-can-prove footnotes. EVIDENCE BUNDLE — PROVENANCE PIPELINE EVERY RESULT → CRYPTOGRAPHICALLY VERIFIABLE 01 DESIGN RESULT Candidate + metrics Kd · pTM · ADCC sequence · structure · run cfg 02 CANONICALIZE Serialize deterministic byte order inputs · commands · outputs 03 HASH SHA-256 one digest per artifact 9f2c…a17b · 4e0d…c8f1 04 COMBINE Merkle root hash tree → one root root: 7a1f…e29d ROOT HASH CARRIED FORWARD 05 TIMESTAMP OpenTimestamps root submitted to calendar pending → attestation receipt 06 ANCHOR · CONFIRMED Public-chain anchor root committed to Bitcoin block 944,517 · illustrative 07 VERIFY · ANYONE Re-derive the root re-run commands → same root match ⇒ bundle is authentic WHAT YOU CAN PROVE INVENTION DATE existed at/before the anchor block REPRODUCIBILITY same inputs + commands → same outputs INTEGRITY no artifact altered after anchoring
Figure — Evidence Bundle provenance. Every NOVA-3 result is canonicalized, hashed, and folded into a Merkle root that is timestamped and anchored to a public chain — so invention date, reproducibility, and integrity are verifiable by anyone, without trusting us. Block height shown is illustrative.

Live = active on current infrastructure  ·  Architecture = designed and specified; implemented for the partner platform, not yet on the current public demo stack  ·  Roadmap = explicitly planned, not yet built.

Cryptographic provenance

OpenTimestamps anchoring Live

Evidence Bundles from internal program runs are SHA-256 hashed and committed to the Bitcoin chain via OpenTimestamps. The public verification widget on the Predict page demonstrates the verification flow; production bundles are anchored at the time each program design run is sealed.

  • No trusted timestamper — verifiable independently by any partner
  • Inventor attestations filed at provisional time alongside the bundle
  • Reproducibility command attached to every sealed bundle
Data security · encryption

TLS 1.2+ in transit · AES-256 target at rest Architecture

The public site and demo API are served over TLS 1.2+ (HTTPS enforced via Vercel/Cloudflare). The partner platform architecture specifies AES-256-GCM at rest across primary storage with per-tenant encryption keys and a dedicated KMS — this is the design standard for the production partner data plane, not yet deployed on the current demo backend.

  • TLS 1.2+ and HTTPS enforced on all current hosts (Live)
  • AES-256-GCM at rest + KMS key rotation: partner platform spec (Architecture)
  • Secret material: managed through environment-variable isolation on current stack
Access control

MFA + RBAC + audit logging Architecture

The partner platform architecture specifies mandatory MFA, role-based access control (Viewer · Designer · Reviewer · Admin · Partner), and an append-only audit log across all read, write, and quantum-job events. The current demo uses access-controlled admin credentials. Full MFA/RBAC/audit infrastructure is specified for the production partner platform.

  • Current: admin access gate; production: MFA mandatory on all accounts
  • RBAC roles defined in schema; enforcement live in production partner platform
  • Append-only audit log: partner platform spec; export available for partner audits
External assurance

SOC 2 Type I Phase 2

SOC 2 Type I is on the Phase 2 roadmap. Scope covers Security and Confidentiality trust services criteria across NOVA-Compute, NOVA-Dashboard, and the Module Library backend. A Type II report follows once a sufficient observation window has elapsed.

  • Phase 1 (now): policies, vendor risk register, incident response runbook
  • Phase 2: Type I attestation, scoped to platform & data plane
  • Phase 3: Type II with observation window of at least six months
Module Library · IP segregation

Partner-IP carve-outs Architecture

Module Library records carry an IP_status enum and a partner_co_owned flag. The schema is live; query-time segregation and cross-partner exclusion enforcement is part of the production partner platform specification and is implemented when the partner data plane is deployed.

  • IP_status schema: internal · licensed · partner_co_owned · public (Live)
  • Query-time RBAC carve-out enforcement: partner platform (Architecture)
  • Carve-out events logged to append-only audit log: partner platform (Architecture)
Compliance posture

GDPR · PDPO · CCPA · BWC Architecture

QAI Labs is designed to operate across US, EU, and APAC partner jurisdictions. A GDPR-ready Data Processing Addendum (with SCCs) and a HK PDPO addendum are drafted and available for execution with counterparties. CCPA service-provider posture is in preparation. The platform's biological scope is reviewed against the Biological Weapons Convention at design intake.

  • GDPR-ready DPA drafted; executed per counterparty at engagement
  • HK PDPO addendum available for APAC counterparties
  • CCPA service-provider posture: in preparation
  • BWC dual-use review on every program at design intake (Live)
Subprocessor transparency
Vendor
Purpose
Region
AWS
Primary compute, object storage, and database hosting for NOVA-Compute and NOVA-Dashboard.
US · EU
Modal
Serverless GPU bursts for generator inference and structure prediction workloads.
US
Vercel
Edge hosting for the public site, dashboard frontend, and developer documentation.
Global edge
Cloudflare
DNS, DDoS protection, and CDN for qailabs.co and platform API endpoints.
Global edge
IBM Quantum
Quantum hardware backend: Heron r3 (ibm_boston · 156Q) for CVaR-VQE active-space corrections.
US
Quantinuum
Quantum hardware backend: Helios (98Q, all-to-all) for QAOA assignment optimization.
US · UK
Stripe
Payment processing and subscription billing for platform tiers.
US
OpenTimestamps
Public timestamping calendar servers; Bitcoin-anchored proof of Evidence Bundle existence.
Public infrastructure
Google Workspace
Internal email, calendar, and document collaboration for QAI Labs personnel.
US
Responsible disclosure
Report a vulnerability or security concern: security@qailabs.co
Verify a bundle →