For litigation practices
Your case files never
leave the building.
The gate between your matter and any AI model — the frontier ones included — and the verifier that refuses to approve a document until every claim points to a real page in your own file. Identity stripped before anything leaves, every claim checked after, the record kept.
Software for licensed attorneys — not a law firm, not legal advice.
Pre-release overview. The container, the audit chain and the verifier are running; the de-identification gateway to outside models is in development. Ask us what is running today.
The practical difference
What changes on your desk
The best drafting models now live in someone else’s cloud, and every one of them will happily take your whole file. LexVault is the part that decides what they may see, checks what they send back, and writes it all down.
The demand package
- 15–25 hours to assemble a demand package from a scanned record set — or an hour with a chatbot and no idea what it made up
- Paralegal time spent transcribing dates and bills into a chronology
- Citations checked by hand, if there is time
- The record sits in whatever tool was convenient — sometimes in a chat window
The same package
- A few hours of attorney review on a package drafted by the strongest model you allow for that matter — and checked by one that answers to you
- The chronology is built from the pages and linked back to them
- Every claim is machine-checked against the source before you read it
- The record sits in an encrypted container, one per matter, on your own machine
And must not
- You select the matters, set the fees and make every legal judgement
- You read the draft and you sign it
- Nothing leaves your office without a decision you made, and that was recorded
- The AI never speaks to a client and never gives legal advice
Who does what
Your digital staff — seven roles, one gate
The third column is the point. Each role is deliberately narrow, because a narrow assistant is one you can actually supervise. Two of the seven may work outside the building, on de-identified text, if you allow it for the matter; the rest never do.
| Role | What it does | What it never does |
|---|---|---|
| 1. Intake | Structures the facts from the file; flags limitation periods. Inside. | Advise the client, or decide whether to take the matter |
| 2. Documents / OCR | Reads scanned records page by page. Inside. | Discard the original — the source page is always kept |
| 3. Medical timeline | Builds a dated treatment chronology, every entry tied to a page. Inside — it touches health information. | Infer a treatment that is not written on a page |
| 4. Research | Searches your file and the law. May use a frontier model through the gate, on de-identified questions, if you chose that for the matter. | Cite an authority that cannot be found in a registry |
| 5. Drafting | Demands, disclosures, briefs — citing located sources only. May use a frontier model through the gate, on de-identified text, if you chose that. | Invent a supporting quotation |
| 6. Verification | Re-checks every claim against the source it cites. Always inside, always ours — whichever model drafted. | Take the drafting model’s word for anything |
| 7. Attorney review | You: review, judgement, signature | Be skipped, in any mode |
How a matter moves through
Nothing is lost, nothing is silent
Each step hands the matter on through a durable work queue; a failed step is retried rather than dropped, and the failure is visible. Every hand-off writes a line in that matter’s audit log in the same database transaction — so a matter cannot advance without its log entry.
The last step waits for a person
Verification loops back on itself for up to three passes while any flag remains, and will not release a document while one is open. Attorney review is the only stage with no queue behind it: nothing downstream happens until a person acts.
Verification
Every claim, traced back to a page — whoever wrote it
The draft is broken into atomic claims — one checkable fact each, like separately numbered paragraphs in a pleading. For each one, the verifier reopens the actual file and page in your case container and looks for the supporting words. It never checks the draft against the draft, and it does not care which model produced the draft: a checker that belongs to the same vendor as the writer is not a checker.
A verbatim quotation, or a flag
A claim is accepted only with a verbatim supporting quotation. That is what catches a “citation-shaped” hallucination: a plausible-looking cite to a real document that does not in fact support the sentence. Anything else is flagged [VERIFY] and sent back for up to three passes.
The rule lives in the database
One unresolved flag and the document cannot be marked approved — a constraint enforced by the database itself, so it cannot be clicked past in the interface. And because the checking runs on your own hardware, it is free: no per-query cost pushes anyone to check less thoroughly.
What you see: the weakest points, first
Flagged claims sort to the top. The weakest sentence in the document is the first one you read — not the one hidden in the middle of polished prose.
Illustrative screen on a fictitious matter. The first row is real in one sense: in a controlled measurement on that synthetic matter, the verifier caught exactly this planted $3,800 overstatement of our own side’s figure, and a fabricated assertion with it, while passing all ten sound claims with verbatim quotes. Twelve claims is a first measurement, not a rate.
Confidentiality
Where your data goes — you choose, per matter
The mode is chosen per matter and recorded in that matter’s log: a deliberate decision by a lawyer, on the record, not a default inherited from somebody’s terms of service. It is the informed-consent record your bar opinion asks for. Every mode keeps the same protections — verification, your signature, per-matter encryption, and a gateway that blocks by default rather than warns.
| Mode | Where the work runs | What leaves your office | Typical use |
|---|---|---|---|
| A. Fully local | Everything on your office device, with local models | Nothing. There is no route out. | Protective orders, sealed records, health information, criminal and immigration matters, clients who require zero transfer |
| B. Hybrid | Protected data stays local; research and drafting by a frontier model of your choice, through the de-identification gateway | Pseudonymised text only, under a signed BAA with zero data retention | Matters where the best available drafting quality materially helps and nothing bars an outside model |
| C. Outside review | Draft built locally; an independent outside model gives a second opinion on citations | Pseudonymised text only | High-stakes documents you want double-checked |
If you choose hybrid: what actually crosses
Before it leaves
- Names, dates of birth and addresses are replaced with stable placeholders: [PATIENT_1], [DOB], [ADDRESS_1]
- The table mapping placeholders back to real people never leaves the office
- Only one kind of message can cross the gate at all, and only the de-identification step can build it — there is no other path in the code
At the gateway
- A second, independently built detector re-scans the text just before it goes out
- A match blocks the transfer and writes a log line — it does not warn and proceed
- If the gateway, the key registry or the audit log is unavailable, nothing is sent: the matter falls back to fully local
When it returns
- Real names are substituted back inside your office, after the answer arrives
- The outside model saw [PATIENT_1] and never learned who that was
- The answer goes through the same verifier as any local draft, and the exchange is recorded in the matter’s audit log either way
Stated honestly: pseudonymisation lowers risk; it does not make data anonymous. That is exactly why fully local mode exists, and why it is the default posture for sensitive matters.
How your files are held
Security, in plain terms
One encrypted container per matter
Each case is its own sealed evidence box with its own key: a stored page that has been tampered with does not decrypt at all, and no page can be overwritten once written. A lost or stolen drive is unreadable ciphertext.
Keys we never hold
Every key is created on your machine at first boot; nothing secret ships in the software. The key that wraps all your matters goes into a sealed envelope in your safe, written down by your own staff with us out of the room. Sealing it to the machine’s security chip and your hardware key is the production design, in development.
An append-only audit log
Per matter: what was processed, when, by which model — identified by its fingerprint, not its name. It cannot be edited afterwards — enforced by the database, not by an application setting.
Backups that are rehearsed
Encrypted nightly with a key the machine cannot read, so a stolen copy is inert; a second copy on a drive you attach; restores rehearsed before you rely on them. The off-site copy is your firm’s procedure, not ours — the machine has no route out to make one, and we say so.
Evidence you can hand over
The question “can you show this file never went anywhere?” has a one-page answer here — and the answer does not depend on trusting the software vendor, or the model vendor.
Per-matter report
- States the confidentiality mode, the number of logged events, and any outbound transfers
- For a fully local matter, the answer is that no route out existed
- Printed and signed, it is the document you produce when the question is asked
The audit chain
- Each log entry is chained by hash to the one before it, computed by the database itself
- The application can add entries. It cannot alter or delete them.
- Removing or editing a past entry breaks the chain visibly
The anchor sheet
- A short sheet carrying the chain values as of that date, kept with the file
- It ties today’s report to a record made weeks earlier
- Without it, any log proves only that it agrees with itself
Next, in development: an AI-use attestation to attach to a filing where a court’s standing order asks for one — which claims were verified and with what quotes, which authorities were validated, what left the building and to whom, or that nothing did. It is built from the three artefacts above, which already exist.
Practical requirements
What you need to run it
No data-centre, no cloud account that holds your files. The equipment is yours, and you can unplug it. An outside model, if you use one, is paid per query and sees only what the gate lets through.
| What | Detail | Note |
|---|---|---|
| The hub device | A small machine sized for what stays inside: reading, de-identification, the timeline, verification | Sits in a locked room. If you want drafting fully local as well, a desktop AI machine with 128 GB of unified memory does it. |
| A room and a lock | Physical control of the device | Physical security is part of the design, not an afterthought |
| Office network only | Workstations reach the hub over your own network | In fully local mode no internet connection is required at all |
| Attorney workstations | Any current PC | The browser is the interface |
| An outside model, optional | Your own account with a frontier model provider, used only through the gate | For hybrid matters; under a BAA and zero data retention where the matter needs it |
| Installation | We install, verify and hand over | Including a rehearsed restore and the key ceremony, with your staff at the keyboard |
Getting started
We install the device in your locked room, verify it, rehearse a restore, and your staff seal the key envelope with us out of the room.
We run one of your closed matters through the pipeline end to end, so you can compare the output against work you already trust.
You open live matters, choosing the confidentiality mode for each one. We stay on support.
The one thing to test before you commit: ask us to run a matter you already know the answer to.
Limits, stated plainly
What LexVault does not do
- It does not practise law. It gives no legal advice, to you or to a client, and makes no judgement about a case. It is software, not a law firm, and creates no attorney–client relationship.
- It does not compete with frontier models on research or drafting. It decides what may reach them, strips identity first, and checks what comes back. The strongest writers are outside your building; that is why the gate exists.
- It does not file, serve or send anything. There is no outbound path from the pipeline to a court system or a mail server.
- Verification is not infallible. It confirms a claim is supported by a verbatim quotation on a cited page; it cannot tell you the quotation is the whole story, and it cannot see what a draft left out. Your review is the control for completeness, not a formality — and no outcome is guaranteed.
- OCR quality depends on the scan. A page a person cannot read is a page the system flags rather than guesses at; handwriting is not read.
- Hybrid mode is not made safe by declaration. Pseudonymised data is still regulated data, and we say so on the section where we describe it. Nothing goes through the gate without your per-matter decision.
A tool that claims no limits is telling you it has not looked for them. These are ours, in writing, before you buy. Use is subject to our Terms of Use and Privacy Policy.
Book a demo
Run a matter you already know
The strongest test we can offer is a falsifiable one: give us a closed matter where you already know the right answer, and compare.
- See the verification screen catch a planted error
- Walk the audit chain and the per-matter report
- Talk deployment in your own locked room
Prefer email? Write to hello@lexvault.associates. Raising or investing? See the investor overview.
Request ready
Thanks — we’ll be in touch to lock a time.