How your evidence is handled — stated plainly
Defense work runs on confidentiality and chain of custody, so this page describes the posture we can actually stand behind today — including what we haven't done yet. No badges, no implications.
Published pricing · 14-day money-back guarantee · Export everything, any time
The posture, point by point
Originals are immutable
The discovery you received is never modified. Transcripts, frames, clips, and redactions are stored as separate derived files. Revoking a derived file never touches the original — and every action that produced it is recorded.
Audit trail on everything
Logins, uploads, redactions, exports, playbook runs, review-signal changes, and every external AI-app call are written to an audit log. If something happened to your evidence, the trail shows who, what, and when.
Access is org-scoped
Your workspace is the boundary: organization roles (admin, attorney, clerk, investigator, viewer), refined by per-case membership, with separate permissions for verifying review signals and exporting. Cross-org access is denied even with a valid session.
Media served through signed expiring links
Evidence media doesn't sit on permanent public URLs. Files are served through signed links that expire — nothing for a forwarded email or a browser history to leak.
Never trained on your evidence
Your case data is not used to train models. AI features process your evidence to answer your questions, and the outputs stay marked as AI-generated pending human review.
AI never acts without you
Redaction suggestions, multi-camera sync proposals, timeline events, cross-exam drafts, and playbook outlines all file as suggestions for human review. Nothing is auto-applied to your case record, and the product never makes legal conclusions.
AI-app connections are scoped and revocable
The MCP server speaks OAuth 2.1 with PKCE — browser sign-in, rotating refresh tokens, no long-lived keys pasted into chat apps. Connections are read-only (cases:read), see exactly your access, and die instantly when you revoke them in Settings.
Email intake is hardened by default
Sender allowlists, attachment-size caps enforced before download, loop guards for automated mail, and deduplication by message ID. Unmatched senders are logged and dropped — you get a rejection, not a silent failure.
What we haven't done yet
No formal certifications yet
We do not currently hold SOC 2, ISO 27001, or similar certifications, and we won't imply a badge we haven't earned. The controls above are real and described accurately; the audit reports are not.
Ask us anything before you upload
Every walkthrough doubles as a security review — bring your IT or compliance questions and we'll answer them directly, including the ones this page doesn't cover. If the posture doesn't fit your obligations yet, we'll say so rather than round up.
What that means in practice
Chain of custody: the original file you uploaded is the original file you can produce — byte for byte — with an audit entry for everything that was ever derived from it. Redacted turnover copies are new files, revocable, with their own trail.
Team boundaries: a clerk can prepare exports without seeing what an attorney hasn't verified yet; an investigator's access is limited to the cases they're on; and connecting Claude or ChatGPT grants read-only access to exactly the cases that user can already see — revocable in one click.
Getting out: exhibit packs and review memos export at any time with a citation manifest, and your cases remain accessible even when a plan lapses — processing pauses, access doesn't.
Bring your hard questions
Book a 20-minute walkthrough and put the security posture in front of someone who can answer it — or start the 7-day full-access trial and inspect the audit trail yourself.