The evidence index, in the open.

Certifications and attestations

Stated first because it is the first question a reviewer asks. Nothing on this page is a certification, and this page never claims one.

SOC 2

Not held

Not held. A SOC 2 Type I/II engagement requires auditor selection and an observation period. The control matrix and test evidence below are structured so an auditor can map onto them, but nothing here is described as “SOC 2 ready.”

HITRUST / ISO 27001

Not held

Not held, not claimed.

Independent penetration test

Business action (open)

A third-party penetration test has not yet been engaged. Internal adversarial review evidence exists: repeated external code audits and the automated negative test matrices described below.

Cyber insurance, contractual SLAs, DR commitments

Business action (open)

Contracted per customer engagement; the application claims none publicly.

Source: docs/compliance/TRUST_PACKAGE.md

Control matrix

Acceptance matrix

Implemented

41 stable-ID acceptance criteria across access and tenant isolation, data integrity and concurrency, audit and evidence, export governance, and clinical workflow enforcement, each mapped to the automated suite or live probe that proves it, with run commands and evidence tiers.

Security review

Implemented

A maintained inventory of the row-level-security policies on customer-data tables, every service-role call site, browser-facing hardening (content security policy, security headers), and the token-gated public paths.

Source: docs/compliance/ACCEPTANCE_MATRIX.md · docs/compliance/SECURITY_REVIEW.md

Test evidence

Continuous integration

Implemented

Every push runs the type checker, the full pure test suite, and a production build. CI fails on unapproved high or critical production dependency advisories; the sole expiring upstream exception and its compensating controls are recorded in a dependency risk register.

Live negative matrices

Implemented

Authenticated probes exercise role-by-surface denial, cross-tenant denial including leaked-identifier attempts, session lifecycle (expired, removed, banned, and deleted accounts), write concurrency, audit search and export determinism, and report-finalization integrity, on development fixtures and, data-neutrally, against production.

Production reconciliation

Implemented

A read-only reconciliation verifies that every finalized report event has its artifact, every artifact has its event, and every stored payload re-hashes to its recorded digest.

Source: docs/compliance/TRUST_PACKAGE.md · docs/compliance/ACCEPTANCE_MATRIX.md

Data handling

Tenant isolation

Implemented

Row-level security scoped to the owning organization on customer-data tables, with server-side role and entitlement checks on every privileged operation. Browser visibility is never treated as authorization.

Audit history

Implemented

Append-only audit entries with the actor stamped from the server session, never supplied by the client. Core clinical writes record their audit entry in the same transaction as the change.

Export governance

Implemented

Record-level exports require a stated purpose, recipient, and attestation; columns are classified and de-identified profiles exclude identifier and clinical fields, with redaction of stray identifiers; manifests carry a cryptographic digest of what left.

AI usage

Implemented

Extraction output passes a strict structural validation gate and human review before anything becomes part of the tracker. Ask-style features receive schema and label context, never spreadsheet data.

Source: docs/compliance/TRUST_PACKAGE.md · docs/compliance/SECURITY_REVIEW.md

The PHI gate

Production PHI is gated deliberately, and the posture is contractual and operational; the wording here matters and is guarded by tests.

Current posture

Documented

Workspaces run on synthetic or de-identified data only, stated in the application, on the public site, and in the Terms. A database constraint pins the PHI-mode policy flag off; that constraint locks a policy flag; it is not a technical control that prevents a person from typing patient data, which is why the gate is contractual.

Unlock preconditions

Business action (open)

Unlocking PHI mode is a deliberate, reviewed change preconditioned on: the database platform's HIPAA add-on and BAA, an AI-provider BAA, a BAA with the customer, and a security review of the customer environment. The vendor BAAs are open business actions.

Source: docs/compliance/PHI_READINESS.md · docs/compliance/TRUST_PACKAGE.md

Backups, recovery, and incident response

Backups and restore drill

Documented

Daily managed-platform backups with a documented isolated restore drill: observed restore time 6m 34s; scheduled-backup recovery-point exposure 11h 13m 43s at the time of the drill. Point-in-time recovery remains disabled and is not claimed.

Incident response

Documented

A written plan sized honestly to a small vendor: founder-led response with no 24/7 security operations center, covering detection sources, severity classification, containment and recovery steps, evidence preservation, and a counsel-approval placeholder for notification-timing commitments.

Source: docs/compliance/INCIDENT_RESPONSE.md · docs/compliance/TRUST_PACKAGE.md

Subprocessors

Named in the privacy policy; listed here for the reviewer's register.

Supabase

Implemented

Authentication, managed Postgres, and private file storage. HIPAA add-on and signed BAA are preconditions for any PHI unlock.

Vercel

Implemented

Application hosting and build/deploy infrastructure.

Anthropic

Implemented

Document-extraction AI, server-side only, behind the validation gate and human review. A BAA is a precondition for any PHI unlock.

Resend / Upstash

Implemented

Outbound operational email and durable rate limiting, where configured. Absent configuration degrades to logged no-ops, never failures.

Source: docs/compliance/TRUST_PACKAGE.md · app/privacy

Open items: tracked, not hidden

1. 01Vendor BAAs (database platform HIPAA add-on, AI provider): business.
2. 02Independent penetration test: business.
3. 03SOC 2 engagement: business.
4. 04Production point-in-time recovery enablement and a target-time restore drill.
5. 05Counsel-approved breach-notification timing commitments.
6. 06A consolidated full-matrix acceptance re-pass at the current schema.