The Short Answer
A law firm preserves attorney-client privilege on an AI platform when client information stays confidential in fact: not trained on, not retained by a third party, and reachable only by the people walled in to the matter. Harvey, CoCounsel, ChatGPT Enterprise and Claude for Enterprise promise this by contract. On ibl.ai you own all the code and the data, inside your own perimeter.
That distinction matters because courts have started deciding confidentiality by reading vendor terms. In United States v. Heppner (S.D.N.Y., February 2026), the privacy policy of the tool the defendant used was part of why his AI chats were not privileged.
No platform makes a communication privileged. What a platform can do is keep the facts that privilege depends on, confidentiality above all, under the firm's control.
What does ABA Formal Opinion 512 require before a lawyer puts client information into an AI tool?
ABA Formal Opinion 512, issued July 29, 2024, requires a lawyer to assess the risk that client information entered into a generative AI tool will be disclosed or accessed, under the confidentiality duty in Model Rule 1.6.
For self-learning tools the opinion is direct: "a client's informed consent is required prior to inputting information relating to the representation into such a GAI tool." It adds that "general, boiler-plate provisions to engagement letters" are not sufficient.
Its baseline instruction applies to every tool: lawyers "should read and understand the Terms of Use, privacy policy, and related contractual terms and policies of any GAI tool they use to learn who has access to the information."
The full text is in the ABA Formal Opinion 512 PDF.
Opinion 512 also names a risk inside the firm: a self-learning tool can surface one client's information to lawyers behind an ethical wall. Access control is part of confidentiality, not a separate IT question.
What did the Heppner ruling decide about AI chats and privilege?
United States v. Heppner decided that about thirty-one documents a criminal defendant created with a publicly available AI tool were protected by neither attorney-client privilege nor work product.
Judge Jed Rakoff ruled from the bench on February 10, 2026, with a written memorandum on February 17.
Per Venable's analysis of the ruling, the court found no reasonable expectation of confidentiality because the tool's consumer privacy terms allowed inputs to be retained, used for training and disclosed to third parties.
The defendant used the tool on his own, without counsel's direction, which also defeated work product. The court did not rule on enterprise tools or attorney-directed use.
The lesson for a firm choosing a platform is narrow and practical: when confidentiality is tested, someone will read the terms that govern the tool, and those terms will be quoted back.
How do Harvey, CoCounsel, ChatGPT Enterprise and Claude for Enterprise handle client data?
Harvey, CoCounsel, ChatGPT Enterprise and Claude for Enterprise each publish no-training commitments and some form of retention control, according to their own pages read on November 16, 2026.
They differ on who sets retention, and all four hold your data on infrastructure you do not run.
| Platform | Training on client data | Retention | Where prompts and documents live | Nature of the protection |
|---|---|---|---|---|
| Harvey | "Never used to train AI models unless explicitly authorized by both the customer and Counsel AI" | Zero retention at subprocessors: "only processed ephemerally" | Harvey's environment on AWS and GCP in the US, EU or Australia | Contract and vendor policy |
| CoCounsel (Thomson Reuters) | Not used to train CoCounsel; partners "contractually prohibited" from training | Zero-retention calls to OpenAI and Google; retention "customized to fit customer needs" | Thomson Reuters' environment | Contract and vendor policy |
| ChatGPT Enterprise | Not used for training by default | Workspace owners set custom retention (OpenAI's admin guidance gives a 90-day minimum) | OpenAI's environment | Contract and vendor policy |
| Claude for Enterprise | Anthropic says it has "never trained on enterprise data without explicit permission" | Indefinite unless an owner sets a custom period, minimum 30 days | Anthropic's environment | Contract and vendor policy |
| ibl.ai (self-hosted) | Nothing leaves for training; the stack is yours | Your database, your retention policy, your deletion | Your own cloud, on-premise or air-gapped network | Infrastructure you control, plus the source code |
Sources: Harvey subprocessor FAQs, CoCounsel Essentials, OpenAI business data, OpenAI Academy on data governance, Claude Enterprise retention controls, Anthropic Enterprise Frontier Safeguards.
These are real, serious commitments, and for many matters they are enough. The column that differs is the last one.
Why does a contractual privacy promise differ from infrastructure a law firm controls?
A contractual privacy promise differs from infrastructure a law firm controls because the vendor can change its terms, a court can order the vendor to preserve data, and the firm learns about either after the fact.
Infrastructure the firm runs changes only when the firm changes it.
The terms do move. Anthropic introduced 30-day data retention starting with Fable 5, then announced on September 1, 2026 that eligible enterprise customers would receive zero retention on Fable 5 and Fable 5.1 until its new Enterprise Frontier Safeguards are ready.
Courts can override retention settings too.
In the New York Times litigation, OpenAI was ordered in May 2025 to preserve consumer and API output logs it would otherwise have deleted (Enterprise was excluded). The order was largely lifted in October 2025, with already-preserved logs still held.
We covered what that meant for firms in NYT v. OpenAI discovery and the law firm AI checklist.
Opinion 512 asks the lawyer to know "who has access to the information." With a hosted vendor the answer is a document that can be revised. With a self-hosted platform it is your own access list and your own logs.
Does a self-hosted AI platform guarantee attorney-client privilege?
A self-hosted AI platform does not guarantee attorney-client privilege. Privilege depends on the communication, the relationship and counsel's direction, as Heppner shows. What self-hosting removes is a third party from the confidentiality analysis.
One honest limit: a self-hosted platform that calls a hosted model still sends each prompt to that model provider, under that provider's terms.
For the most sensitive matters, run an open-weight model inside the same perimeter, or on a fully air-gapped network; see air-gapped AI for law firms.
ibl.ai is the agentic AI platform where you own all the code and the data. Firms run it in their own cloud, on-premise or air-gapped, with role-based access so a matter's agents and documents stay behind its ethical wall, and audit logs the firm holds.
Because ibl.ai is model-agnostic, the same firm can use a hosted frontier model for public research and a local model for privileged drafting. For the Rule 1.6 detail, see ABA Model Rule 1.6 compliant AI, and for pricing against Harvey, the Harvey AI alternative.
ibl.ai is family-owned and operated from New York, NY, and our engineers deploy the platform alongside a firm's own IT team.