DraftCounsel · Trust center
How your clients’ documents are handled — verifiably
One rule governs this page: every claim is verifiable against the running product, or it says plainly that it is a posture or a roadmap item. Live numbers are computed, not written.
14
Hard gates active
26/27
Official sources verified
Security architecture — the facts
Model and database keys never reach the browser.
All provider keys are server-side environment secrets; nothing sensitive ships as NEXT_PUBLIC_*. The public /api/ai/health probe reports configuration presence as booleans only.
Locked work product cannot leak to an unpaid session.
Previews are server-side projections — the full report/checklist is never serialized to a client that has not unlocked it. Verified in the June 2026 adversarial audits.
The database denies by default.
Every table runs row-level security with no client policies plus explicit privilege revokes — only the server (service role) reads or writes, with authorization enforced in the application layer.
Access codes are never stored in recoverable form.
Codes are stored as SHA-256 hashes; the plaintext exists once, in the purchase email. Sessions and trial cookies are HMAC-signed with constant-time comparison.
Your document is handled as data to analyze, not as instructions.
Uploaded content rides in the user turn behind an immutable injection-guard system rule: document text is data to analyze, never instructions — an injection attempt becomes a red-flag finding.
Every artifact link is unguessable and brand-scoped.
Capability IDs are 26 hex characters of CSPRNG output; reads are scoped to the issuing brand; shares use one-way HMAC handles that never expose the underlying capability ID.
Payments cannot silently fail into paid-but-not-delivered.
Webhook signatures are verified, grant-write failures return 5xx so the processor redelivers, refunds and chargebacks revoke access, and single-use codes consume atomically.
Audit discipline: three independent senior-engineer reviews (June 2026) plus a five-perspective adversarial re-audit; every actionable finding was remediated and re-verified, and re-audits recur.
The supervision record
Every AI finding on a matter must be approved, rejected, or revised by the supervising attorney — there is no bulk approval, and the finalization gate stays locked until the last finding carries a decision. Adjudications are written to an append-only event store: decisions can be superseded, never erased. A print-ready decision packet exports the record for the matter file. This is the platform’s core design, not a feature flag — the engines exist to feed the workstation, and nothing finalizes around it.
Data handling, plainly
What we store
Documents you submit for review or drafting, the reports and drafts the engines produce, and the adjudication trail—bound to your authenticated account and tenant. Explicit shares are limited, expiring, recipient-bound, and revocable.
Where it lives
United States infrastructure: Vercel (hosting/compute) and Supabase (database, region us-east-1 — verified against the live project). No EU residency is offered today, and we do not imply otherwise.
Retention & deletion
Active matter files stay available to the authorized account. Closed matters follow the published seven-year schedule; the signed-in account privacy center provides a data export and a seven-day, cancellable deletion request. Eligible requests complete within 30 days. Legal holds, payment disputes, and required firm-data transfers pause deletion; support@draftcounsel.io handles assisted requests.
Uploads and parsing
Uploads are checked before parsing: the byte signature must match the declared type, the size must sit under the published cap, a Word file must expand within fixed limits with no nested archives, and plain text must be text. Parsing runs in an isolated serverless function with a fixed time budget. Uploads are not scanned by antivirus software; a refused upload returns a receipt naming the check that failed.
Attorney authority
The firm attests to each attorney's licence (bar number and jurisdiction); DraftCounsel records the attestation and does not verify a bar registry. Administration alone never confers approval authority; paralegals prepare and an attorney signs off.
Verification you can run yourself
The coverage matrix
Which documents assemble deterministically, which are statute-cited AI drafts, and exactly which citation-verification layers are live — computed from the running configuration.
/coverage →
The Authority Graph
26 of 27 cited Florida statutes verified against the official publisher (last check 2026-08-24) — content-hashed, history in source control, official links on every clause card.
/florida →
The health probe
A public, secret-free endpoint reporting which capability layers are configured on this deployment — the same booleans this page and /coverage compute from.
/api/ai/health →
The live engine dashboard
Gateway state (with the reason it refuses when disabled), verification layers, gates, the authority monitor, and the published eval — read at request time from the running configuration.
/engine →
What each ledger proves
Three kinds of record stand behind the platform's claims. Each proves something specific and none proves completeness, original authorship or legal correctness. A consistent chain is never presented as proof that nothing is missing; an authorized removal stays on the chain as its own row and is never rendered as healthy.
- Hash chain (the adjudication trail, the attorney decisions, the authority checks)
Proves
- Every row since genesis links to the previous one and hashes to what it claims.
- A row cannot be edited, deleted, reordered or duplicated without the walk naming the sequence where it happened.
- An authorized removal is a row of its own: the chain stays walkable and the removal stays visible.
Never proves
- That the chain is complete: a chain that was never written to is consistent too.
- Who originally authored a payload.
- That any decision was legally correct.
- Labelled set digest (the DraftBench runs)
Proves
- The labelled items existed in exactly this form when the digest was taken.
Never proves
- Anything about items that were never labelled.
- That the set was the whole population.
- High-water receipt (the tip of a ledger at a time)
Proves
- The ledger reached this sequence and this tip hash by the receipt time.
- A shorter chain presented later is truncated, and an older tip presented as current is a replay.
Never proves
- What happened after the receipt.
- Completeness or correctness of the rows.
A recipient can re-derive a decision packet offline with the verifier on /verify; no account and no upload are needed.
Subprocessors
| Provider | Role | Activation | What reaches it | Note |
|---|---|---|---|---|
| Supabase | Database (matters, documents, findings, decisions, ledgers) | Always on | the platform record itself (matters, documents, findings, decisions, ledgers) | Region us-east-1 (United States), verified against the live project; uploads are parsed in memory, and the original files a matter keeps are stored in one private bucket of the same project, opened only through five-minute signed addresses. |
| Vercel | Hosting, serverless compute, CDN, cron | Always on | the platform record itself (matters, documents, findings, decisions, ledgers) | United States infrastructure for both brand deployments; request metadata in server logs. On its deployments the layout also loads its Web Analytics and Speed Insights scripts, which report page views and Core Web Vitals. |
| Stripe | Card payments (staged) | Built, not reached | order and amount metadata; an email address | Webhook hardening shipped; checkout stays closed until the commerce interlock opens. |
| Cloudflare Turnstile | Bot check on the consumer account forms (create an account, sign in, sign-in links, password reset) | Built, not reached | the browser and network signals a bot check reads, never a document or an answer | Runs in the visitor's browser on the account page only; Supabase Auth verifies the resulting token. It never receives a document, an answer or an account record. |
| Anthropic | Primary model: drafting, review, redline, counsel, verification, claim extraction, synthesis. | On by default | client document content or a prompt built on it; a search or lookup string derived from the run, never the document | API inputs and outputs are not used to train Anthropic models. |
| OpenAI | The OpenAI engines (ChatGPT-5.6 Sol, included; ChatGPT-6 Astra, per-document upgrade) and the second engine of the dual run; receives the same grounded prompt as the primary, with store: false. | Firm-enabled | client document content or a prompt built on it; a search or lookup string derived from the run, never the document | The second engine of the dual run, a per-document upgrade the firm chooses. |
| Resend | Transactional email: access codes, share notices, winback, support receipts. | Built, not reached | an email address | Transactional email only; no document content. |
| Dropbox Sign | E-signature delivery of an approved document to named signers. | Built, not reached | client document content or a prompt built on it; an email address | E-signature of an approved document to named signers. |
| Proof | Remote online notarization of an approved document. | Built, not reached | client document content or a prompt built on it; an email address | Remote online notarization of an approved document. |
| Square | Hosted checkout, order retrieval and payment reconciliation. | Built, not reached | order and amount metadata; an email address | Hosted checkout; commerce stays closed behind the two-flag interlock. |
| Brave Search | Open-web exemplar discovery: query strings derived from the document type and venue, never document text. | Built, not reached | a search or lookup string derived from the run, never the document | Query strings derived from the document type and venue; never document text. |
| CourtListener (Free Law Project) | RECAP and opinion search (queries) and the citation lookup (the cite-check posts the document text it checks). | On by default | client document content or a prompt built on it; a search or lookup string derived from the run, never the document | RECAP and opinion search by query; the citation lookup posts the checked text. |
| UniCourt | Licensed exemplar connector (dormant until keyed): search queries and document-text reads. | Built, not reached | a search or lookup string derived from the run, never the document | Licensed exemplar connector; dormant until keyed. |
| Trellis | Licensed exemplar connector (dormant until keyed): search queries and document-text reads. | Built, not reached | a search or lookup string derived from the run, never the document | Licensed exemplar connector; dormant until keyed. |
| Operator statute endpoint | Operator-configured statute endpoint (dormant until STATUTE_API_URL is set): jurisdiction, family, document type and topics only. | Built, not reached | a search or lookup string derived from the run, never the document | An operator-configured statute source; jurisdiction, family and topics only. |
| Florida clerks of court (docket APIs) | The Broward and Miami-Dade clerks’ docket APIs (dormant until a clerk’s key is set and the owner overrules the key-in-URL law): the case number, with the clerk’s key in the address as the clerk requires (F-1-01, 2026-10-10: the pull reached them outside the gate). | Built, not reached | a search or lookup string derived from the run, never the document | Docket pulls from the Broward and Miami-Dade clerks by case number; dormant until a clerk’s key is set and the owner overrules the key-in-URL law. |
| Clio Manage (firm connection) | Clio Manage, the firm’s own practice system (dormant until a firm connects its account): OAuth code exchange, token renewal and revocation, the connected user’s identity, matter searches and links, the firm’s subscriptions to matter, bill and payment changes, and the approved document versions a firm owner or admin sends to the linked Clio matter (the document’s name to Clio, its bytes to Clio’s storage host confirmed for the region), and the approved time and expense entries a firm owner or admin sends to the linked Clio matter as activities (the member’s description is client content), and reads of the linked matters’ bills and trust balances, in the firm’s Clio region (WK-32-01, WK-32-02, WK-33-02, WK-33-03, WK-33-04, WK-33-05). | Built, not reached | nothing (a public read); a search or lookup string derived from the run, never the document; client document content or a prompt built on it | Reached only after a firm owner or admin connects the firm’s own Clio account: the authorization, renewal, revocation and identity calls, matter searches and links, the firm’s subscriptions to matter, bill and payment changes, the approved document versions a firm owner or admin chooses to send to the linked Clio matter, the approved time and expense entries a firm owner or admin sends to it as activities, and reads of the linked matters’ bills and trust balances (stored by Clio, the firm’s own practice system). |
| Microsoft 365 (member mailboxes) | Microsoft 365, a member’s own mailbox, calendar and drive (dormant until the firm allows it and the member connects): the sign-in code exchange and token renewal at the Microsoft identity platform, the member’s own identity, searches of their own mail (the words they typed), and reading the messages and attachments they choose to bring into a matter and the calendar events they link to one, and searches of their own OneDrive and the files shared with them (the words they typed) and the files they choose to bring into a matter, whose bytes come from the short-lived download address on the tenant’s SharePoint host. Read only; nothing of the firm’s client content is sent and nothing is written to the mailbox or a drive (WK-32-04). | Built, not reached | nothing (a public read); a search or lookup string derived from the run, never the document | Reached only after a firm owner or admin allows Microsoft 365 mailboxes and a member connects their own: the sign-in and renewal calls, that member’s identity, searches of their own mail, the messages and attachments they choose to bring into a matter, their calendar events in a window they choose and the events they link to one, and searches of their OneDrive and the files shared with them and the files they choose to bring into a matter. Read only; nothing is sent from the mailbox and nothing is written to the calendar or a drive. |
| Google (member mailboxes, calendars and Drive) | Google, a member’s own Gmail, Calendar and Drive (dormant until the firm allows it and the member connects): the sign-in code exchange, token renewal and revocation, the member’s own identity, searches of their own mail (the words they typed), reading the messages and attachments they choose to bring into a matter, their calendar events in a window they choose and the events they link to one, and Drive searches (the words they typed) and the files they choose to bring into a matter. Read only; nothing of the firm’s client content is sent and nothing is written to the mailbox, the calendar or Drive (WK-32-04). | Built, not reached | nothing (a public read); a search or lookup string derived from the run, never the document | Reached only after a firm owner or admin allows Google mailboxes and a member connects their own: the sign-in, renewal and revocation calls, that member’s identity, searches of their own mail, the messages and attachments they choose to bring into a matter, their calendar events in a window they choose and the events they link to one, and searches of their Drive and the files they choose to bring into a matter. Read only; nothing is sent from the mailbox and nothing is written to the calendar or Drive. |
| Public web (court and publisher sites) | Public exemplar, court-form and robots reads: https GET with no body, policed by publisher policy, robots and redirect hops. | On by default | nothing (a public read) | Public GET reads policed by publisher policy, robots and redirect hops; nothing is sent. |
| Clio | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. Nothing connects to Clio today; early access is a request, not an activation. |
| MyCase | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. Nothing connects to MyCase today; FamilyLawGPS built the adapter dormant, and a practice connector is activated only on confirmed demand. |
| LawPay | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. No payment request is created and no money moves today; a charge would ship only behind its own end-to-end audit. |
| DocuSign | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. No envelope is created today. |
| Google Calendar | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. No event is written to any calendar today; a date would travel with its caveats, never as a deadline. |
| Plaid | Practice-system connector (roadmap) | Built, not reached | nothing today | On the roadmap. No account verification runs today. |
| Westlaw | Citator or research slot (pilot) | Built, not reached | a search or lookup string derived from the run, never the document | A dormant integration slot that activates on partner credentials; a pilot request, never a live check. |
| LexisNexis | Citator or research slot (pilot) | Built, not reached | a search or lookup string derived from the run, never the document | A dormant integration slot that activates on partner credentials; a pilot request, never a live check. |
The register is derived at render time from the code’s permitted-vendor constant and the connector registry; a provider whose key is absent reads “Built, not reached”, whatever its class would be once keyed. The list with its date and its change log is on /subprocessors.
Data lifecycle, plainly
- Storage
- Documents you submit for review or drafting, the reports and drafts the engines produce, and the adjudication trail are stored under your authenticated account and tenant in the platform database (United States, us-east-1). Four kinds of file are kept whole, in one private storage bucket of the same platform project, under paths the server sets: the original a firm keeps beside a matter's source, a file a client adds to an intake link, a file a client adds to a request, and the Word file kept beside an imported version. Verified deletion removes each file before its record. Every other upload is checked and parsed in memory and is not written to storage.
- Sub-processors
- Only the providers in the register above can receive data, each only the classes it is cleared for; the software refuses every other destination before a byte leaves. A provider whose key is absent is built but not reached.
- Sharing
- Nothing leaves your account except through an explicit share (limited, expiring, recipient-bound, revocable), an export you approve, or a delivery you confirm.
- Retention
- Active matter files stay available to the authorized account. Closed matters follow the published seven-year schedule.
- Deletion
- The signed-in account privacy center provides a data export and a seven-day, cancellable deletion request; eligible requests complete within 30 days. Legal holds, payment disputes and required firm-data transfers pause deletion.
Every route links here; the register above and this explanation are generated from the same code.
Engine health
- Claude Opus 5.5 — included; available: last successful call 2026-11-21 00:23 UTC. Available: permitted, configured, callable and proved by a recent successful call.
- ChatGPT-5.6 Sol — included; available: last successful call 2026-11-21 00:23 UTC. Available: permitted, configured, callable and proved by a recent successful call.
- Claude Fable 5.1 — per-document upgrade; available: last successful call 2026-11-21 00:23 UTC. Available: permitted, configured, callable and proved by a recent successful call.
- ChatGPT-6 Astra — per-document upgrade; available: last successful call 2026-11-21 00:23 UTC. Available: permitted, configured, callable and proved by a recent successful call.
Compliance posture — no badges we haven’t earned
SOC 2
DraftCounsel is not SOC 2 certified today, and this page will never claim otherwise before an audit exists. Control-evidence collection toward a Type I engagement is underway — the CI gate, the append-only adjudication trail, access posture, and incident discipline above are the control set being documented.
Data processing addendum
A firm-signable DPA is in preparation with counsel. Until it ships, the Privacy Policy and Terms govern; ask via support@draftcounsel.io and we will say exactly where it stands.
Professional posture (read this one)
LegalDraft Technologies LLC is not a law firm. DraftCounsel is professional drafting and review software for licensed attorneys and supervised staff: an attestation gate fronts the engines, the supervising attorney remains solely responsible for every work product, and communications with the service are not attorney-client privileged — your own privilege and work-product positions are yours to establish and preserve, and nothing here purports to create them.
Responsible disclosure
Found a security issue? Email support@draftcounsel.io with “SECURITY” in the subject — security reports are triaged ahead of everything else. Machine-readable contact lives at /.well-known/security.txt. Each security fact, with the code that makes it true and the law that holds it, and every governance document with the date its words last changed, are on /security.
DraftCounsel is professional drafting software for licensed attorneys, operated by LegalDraft Technologies LLC. DraftCounsel is not a law firm and does not provide legal advice. All output is AI-generated draft work product offered for attorney review; the supervising attorney is solely responsible for reviewing, revising, approving, and using any work product, and for compliance with applicable rules of professional conduct. Communications with DraftCounsel are not protected by attorney-client privilege.