Recommended Articles
Legal & Policy

AI in the Courts: Privilege and Discovery Lessons for Founders and Counsel

By Angeled · October 25, 2026 · Legal & Policy
AI in the Courts: Privilege and Discovery Lessons for Founders and Counsel
AI in the Courts: Privilege and Discovery Lessons for Founders and Counsel

Two court decisions now frame how AI chats are treated in litigation, and founders should understand both — without overstating either. In United States v. Heppner (S.D.N.Y., February 17, 2026), Judge Jed S. Rakoff held that a defendant's chats with a consumer AI assistant were neither privileged nor protected as work product. In Fontainebleau Florida Hotel, LLC v. Botach (S.D. Fla., October 21, 2026), Magistrate Judge Marty Fulgueira Elfenbein allowed narrowed AI-provider subpoenas, rejected a blanket work-product objection, and required a privilege log for anything withheld. Together, they teach a simple lesson: writing to a chatbot does not make a document secret.

This article is general information, not legal advice. Both rulings are fact-specific and interim in different ways, and other courts have reached different results on different facts.

Heppner: why the chats were not protected

Bradley Heppner was indicted on securities fraud, wire fraud, and related charges. After receiving a grand jury subpoena and learning he was a target, he used Claude, Anthropic's AI assistant, on his own — his lawyers conceded they did not direct him to run those searches — to prepare reports outlining defence strategy. FBI agents seized about 31 of these documents under a search warrant when he was arrested. Heppner had shared their contents with his lawyers, who claimed privilege over them. Judge Rakoff ruled from the bench on February 10, 2026, and filed a written memorandum on February 17.

The court gave three reasons: the chatbot is not a lawyer, so there was no attorney-client communication; the provider's terms allowed collection, training use, and disclosure, so there was no reasonable expectation of confidentiality; and Heppner did not use the tool at his lawyers' direction, and sharing outputs with counsel afterwards did not make them privileged. Work product failed because the documents were not prepared by or at counsel's behest.

Analysis: Heppner is not a blanket ruling that every use of AI destroys privilege. It is a district-court decision on specific facts: a represented defendant acting alone, on a consumer account, after becoming a target. Other courts have differed — a Michigan federal court protected a self-represented litigant's AI-assisted materials, and a Texas business court disagreed in an interim ruling. The law is unsettled; the facts — who directed the work, on what account, under what terms — matter.

Fontainebleau v. Botach: narrowed discovery, not a free-for-all

Fontainebleau Florida Hotel, LLC sued Jacob Shmuel Botach for defamation. The hotel served a seventh request for production and circulated four proposed subpoenas to AI service providers, seeking Botach's communications with AI platforms since December 3, 2024 across several subject categories. In a 25-page Second Order After Discovery Hearing (ECF No. 289) on October 21, 2026, following a hearing on October 8, Judge Elfenbein overruled his blanket objections to three categories and part of a seventh, sustained them as to three others and the rest of the seventh, denied the request to force him to consent to the subpoenas, and permitted narrowed Rule 45 subpoenas to the providers.

The permitted categories cover communications since December 3, 2024 concerning the hotel, plaintiff's counsel, or hotel employees, owners, or representatives — relevant to intent, malice, and whether an exception to Florida's punitive-damages cap applies. Requests for all AI communications about the litigation generally, court orders, or judicial officers were overbroad. The court rejected a blanket work-product objection, but document-specific claims remain available with a privilege log. The ruling is interim, not on the merits, and not binding on other courts.

Practical guidance for founders and counsel

First, treat every AI prompt as potentially discoverable. Do not put sensitive strategy or confidential information into a consumer chatbot and assume it is private; labelling a prompt "privileged and confidential" does not create privilege. For sensitive matters, use counsel-directed channels and tools whose terms counsel has reviewed.

Second, separate personal experimentation from case preparation. Heppner turned partly on the absence of counsel direction. Founders involved in a dispute should ask counsel, before using AI for anything case-related, how that work should be done, on which account, and with what retention settings. A short conversation before the work is far cheaper than a privilege fight after seizure or discovery.

Third, preserve and log. If litigation is likely, AI chat histories belong on the preservation list. If protection is claimed, be ready to explain, document by document, why that chat was made for the case at counsel's direction. A blanket claim is exactly what Fontainebleau rejected.

Fourth, check provider terms before adopting a tool for sensitive work: who can access inputs, how long they are retained, whether they can be used for training or disclosed, and whether an administrator can apply a litigation hold?

Finally, expect providers to be subpoenaed. Fontainebleau shows a party can seek provider records directly, within narrowed limits. The courts are not banning AI in legal work; they are applying familiar privilege and discovery principles to a new medium — and finding that the medium does not, by itself, confer protection.

Angeled.com connects founders with investors.

Sources: https://optivis.dev/insights/chatgpt-attorney-client-privilege ; https://spellbook.com/learn/does-chatgpt-have-legal-privilege ; https://www.recordinglaw.com/news/ai-chat-logs-defamation-discovery-order/ ; https://reason.com/volokh/2026/10/24/some-communications-by-rabbi-shmuley-with-ai-platforms-may-be-discovered-in-order-to-determine-punitive-damages/printer/

Read Next