Trust — claims == terms == configuration
Claims == terms == configuration. What this page says is what the code does and what the terms will say — one source, pinned by the bench, and a claim that is not here does not exist.
The retention matrix — per layer, stated
Application
livePublic tools run in the browser; nothing entered on them is transmitted. Workspace matters persist only what you save.
Database
liveMatter records live in Postgres (Supabase), tenant-scoped by owner; decisions and audit events are append-only by design.
File storage
liveUploaded originals are hashed (SHA-256) at intake and stored in a private bucket; the hash rides every record that references the file.
Backups
liveDatabase backups follow the managed provider's schedule; deleted rows persist in backups until the backup window rolls.
Logs
liveThe audit ledger stores event metadata and content hashes for release/decision events — not document bodies.
Upstream model
liveThe AI gateway sends matter text to the model provider only when AI features run; the gateway records request HASHES for audit, retains no content itself, and honors the kill switch (AI_DISABLED). The provider's own retention terms govern its side and are linked, not paraphrased.
Human support access
founding-modeFounding mode: the founder-operator can access workspace data for support and verification runbooks; every such lane writes to the audit ledger.
Engineering exceptions
liveNo standing engineering access to matter content; incident access would be logged in the same append-only ledger.
Deletion
activates-with-billingDeletion is manual on request in founding mode; a published deletion SLA ships when billing activates — no number is promised before the machinery behind it is real.
PHI / BAA — the whole posture, one sentence
No BAA is offered, and the platform is not marketed for PHI. If your matter involves protected health information, do not upload it. This sentence is the whole posture, and it appears identically everywhere the topic appears.
Subprocessors
Supabase
database, authentication, file storage
Vercel
application hosting and edge network
Anthropic
AI model provider — engaged only when AI features run; kill-switch honored
Stripe / Square
payment processing — activates with billing; no card data touches TrialVector servers
Integrations — the declared seams
No external providers are connected in this build. The six seams above are the declared shapes integrations will use — a connector that does not exist is stated here, never implied on a marketing page.
External calendars receive labeled conditional events and never become the source of truth — the matter record is the truth; the calendar is a reminder surface.
The public eval bench — the Discovery Desk lanes
Each lane says whether it runs today and where — a lane in the queue is stated, never implied as live.
Caption-extraction accuracy
liveDD-2 golden sets (court, case number, parties, set number)
Segmentation accuracy
liveDD-2 golden sets + the five-way fail-closed suite (mismatches block, never truncate)
Bates continuity
liveDD-7 sequencing suite (gapless, prefix-validated, excluded-never-mapped)
Retrieval recall/precision
queuedrequires a labeled corpus — stated as a queue until one exists; v1 retrieval is deterministic keyword and says so on every candidate
Privilege false-negative tests
liveDD-7 fail-closed suite (deterministic layer: undetermined candidates block assembly); model-layer tests join with the gateway lane
Cross-jurisdiction contamination
livethe state benches (FL/TX/NC/AZ prefix disjointness; a foreign cite never resolves)
Citation-resolution rate
livethe cite-check gates (existence before proposition, corpus-verified)
DOCX rendering
livethe export ceremony re-renders from the reviewed AST; watermark + adoption-state suites
Drift
livethe corroboration gates (150+ verbatim pins) + the DD-5 authority-dependency sweep + the AZ session date bomb