Confidentiality by design
Your client files need not leave the office. DilloLex runs the AI there.
Many legal AI tools send your client files to someone else’s cloud. DilloLex is built the other way: the AI runs on the appliance your firm owns, and client documents are not sent to an outside AI service.
NeverOutside AI cloudClient documents are not sent to an outside AI service.
The exact scope of the claim
What leaves the building, and what doesn’t.
One honest table beats fifteen hedges. If a vendor cannot give you this table, ask why.
| What | Leaves your network? | Where it goes |
|---|---|---|
| Client documents and their contents | Leaves your network? No | Read, OCR’d and indexed on the appliance in your office. |
| AI reasoning over client content | Leaves your network? No | Runs locally on the appliance. No outside AI service is in the loop. |
| Drafts, exhibits and trial packages | Leaves your network? No | Written to your matter folder: a local path or a mapped network drive. |
| Your own cloud storage sync | Leaves your network? Only if you connect it | To the storage provider your firm already chose and controls. Nothing is connected by default. |
| Reference law updates | Leaves your network? Outbound request only | The appliance calls out to public court and legislative sources to stay current. No matter data goes with the request. |
| Remote access and support traffic | Leaves your network? Mutually authenticated | Mutual TLS. The appliance verifies us and we verify the appliance before any traffic moves. |
| Inbound connections to the box | Leaves your network? None accepted | The appliance initiates every connection it makes. Nothing on the internet can open one to it. |
- Full-disk encryption at rest
- Works with the internet down
- Nothing is used to train anyone’s model
- No third-party AI account to provision or audit
- If we disappear, the box keeps working
Rule 1.6
Three questions to ask before you upload anything.
The duty does not transfer to a vendor when you click accept.
Where does the reasoning physically happen?
If the answer is a data center, your client files are leaving the office. Ask for the location, not the marketing word for it.
What happens to our files if we stop paying?
With a subscription, access ends and your work product sits behind someone else’s login. With an owned appliance, nothing happens.
Is our content used to improve the model?
Ask for it in writing, and ask what “aggregated” means in their contract. Here the question does not arise: no outside model sees it.
The rest of the security model.
No, and any vendor claiming that about a machine that syncs your storage is being loose with the truth. The scope of the claim is that no outside AI service is in the loop. The appliance accepts no inbound connections, and it reaches only the storage and managed-service tools your firm selects.
No, and no product does. What it changes is the diligence: no third-party AI processor to vet, no cross-border transfer question, no vendor breach that reaches your client files.
Your matter files live where they always did (your local path or mapped drive), so a replacement machine picks up where the last one stopped. The disk is encrypted at rest.
Book thirty minutes.
We will walk you through the data flow description before the system goes live.
Every day, 8am to 8pm. A founder answers, never a salesperson.