DocAI methodology.

Source handling.

When you submit a document, the text is processed for analysis and the result is made available to you. Submitted documents are retained for 30 days unless you request earlier deletion, then purged. We do not use customer documents to train shared models. The privacy page sets out transfer and retention particulars.

Knowledge-base retrieval.

For questions DocAI can answer without a submitted document, retrieval runs against a vetted knowledge base of public regulatory texts and guidance. Every answer cites the source passages it drew from. If the knowledge base does not cover a question, the system says so rather than hallucinate.

Confidence scoring.

Every response carries a confidence score in [0, 1] composed of four weighted components, published as part of this methodology and versioned with the disclosure stamp:

• Retrieval signal (40%) — top-hit relevance from the knowledge base.
• Model certainty (35%) — 1 minus the model's reported uncertainty.
• Citation integrity (15%) — 1 if every claim in the draft ties to a retrieved item, else 0.
• Limits admitted (10%) — trust signal when the draft admits what it does not know.

Tiers at disclosure v1.0.0-p4: score ≥ 0.75 auto-delivers on free tiers; 0.45 ≤ score < 0.75 routes to a named human analyst; score < 0.45 holds with a request for more information from the submitter. Retrieval hits below 0.15 trigger the canonical "out of scope" response automatically — no fabrication path.

Human review.

On paid tiers, a named analyst reviews every generated answer or drafted clause before delivery. The reviewer verifies that the cited sources actually support the claim, flags uncertainty the model did not, and can hold delivery if any assertion cannot be substantiated.

What we do not do.

We do not practice law. We do not send filings on your behalf. We do not represent you in any transaction or proceeding. A generated clause is a starting point for your attorney, not a finished product for execution. The seven-clause disclosure on every page governs.

Versioning.

Every generated response carries a disclosure version stamp (v1.0.0-p4 at the time this page was generated) and an issued_at timestamp. If a response is ever challenged, the stamp lets us reproduce exactly which disclosure was in force and which knowledge-base version was active when the response was produced.

Incident response.

If a response is challenged — by a customer, opposing counsel, or a regulator — we follow the Liability Incident Response SOP on the hub workflows library. Preservation first, notification to counsel next, no fault admission prior to review.