What is the first pass costing your firm? Run your numbers
All briefings Security

Why law firms banned ChatGPT, and what should lift the ban.

The bans were a correct reading of where client material goes when it leaves the building, and they set the standard any vendor should have to meet.

8 July 2026 · 7 min read · The Solicia team

The policy

By the end of 2023, most firms of any size had arrived at the same policy: no client material in public AI tools. It has become fashionable to describe those bans as a profession flinching at new technology. We read them differently. A lawyer who pastes a clause into a free chatbot has, in the plain meaning of the words, shown a client’s confidential document to a stranger who keeps notes. The managing partners who wrote those policies understood the technology perfectly well. That is why they wrote them.

Where the prompt goes

Trace what actually happens. The text leaves the firm’s network and lands on servers governed by the vendor’s terms, not by the engagement letter. Depending on the tier, it may be retained indefinitely, read by the vendor’s own staff, and used to train the models sold to everyone else, including, in principle, the counterparty. Those defaults change whenever the terms of service change. The firm’s duty of confidence does not.

None of this is hypothetical. In 2025, an American court ordered a major AI vendor to preserve every user conversation on its servers, including the ones users believed they had deleted, as potential evidence in litigation those users had nothing to do with. Whatever the merits of the order, the lesson is that material sent to a shared service inherits that service’s legal exposure. A client’s clause can end up preserved and produced in someone else’s lawsuit.

The shared-room problem

The deeper issue is architectural, and it survives even where a vendor’s intentions are good. Most consumer AI products, including some sold to lawyers, run your material through their own shared service: your documents and prompts flow into the same systems as every other customer’s, retained on the vendor’s terms, sometimes used to tune the very model your counterparty queries. The problem is not that software has tenants, since every system a firm already trusts does. It is that your material lives on infrastructure you neither control nor can inspect, governed by terms you did not write.

And privilege is less forgiving than security. Disclosure to a third party can waive it; “the vendor promised not to look” has never been the standard. When your matter is retained on a shared service you never engaged, its confidentiality rests on that vendor’s policies holding, and on those policies not being changed, subpoenaed, or breached out from under you.

What a vendor owes a firm

So the bans were right. The honest question is what would justify an exception. Our answer, the one we built Solicia against, is that a vendor asking to touch client files owes the firm six things:

  • Its own inference, not a shared endpoint. A firm is provisioned its own Azure subscription, with its own model deployment reachable only over a private endpoint and its own log workspace, not one endpoint every customer’s matters flow through. Ask any vendor whose endpoint your matters reach, and who holds the contract with the model provider.
  • A no-training clause in the contract. If it lives only in a FAQ, it is copy, not a commitment.
  • Retention the firm sets, with a purge that actually runs, and a log entry proving it ran.
  • A record a partner can read. Every step on every matter, in plain language, without an engineer in the room.
  • Delivery inside a channel the firm already governs. For us that is email: archived, discoverable, covered by policies that predate us.
  • A residency preference honoured in the contract, so it is not left to the vendor’s discretion.

Ask for these in writing. A vendor that hesitates has answered the question.

What it costs

Building this way is slower and more expensive than putting a chat window in front of someone else’s API. Isolation costs more than pooling. Deletion has to be engineered as carefully as creation. A plain-language log is a product surface most vendors never bother to build. We accepted the cost because the alternative was asking firms to lower their standard to fit the tool. The firms we want as clients were never going to do that.

The ban is the specification.

So keep the ban. It is doing exactly what it was written to do. Then hold every vendor who wants an exception, including us, to the standard above, in the contract, on the record.

The controls, in detail, are on the Security page. Questions go to admin@solicia.ai. A person reads them.

Writing your firm’s AI policy? Get the AI use policy template for Australian law firms, free in Word.

Get the next briefing by email.

New briefings by email, a few times a year.

One email to confirm, then the briefings. Unsubscribe in one click, any time. Privacy Policy.