Skip to content

Menu

Network by SubjectChannelsBlogsHomeAboutContact
AI Legal Journal logo
Subscribe
Search
Close
PublishersBlogsNetwork by SubjectChannels
Subscribe

AI and Legal Privilege: Key Takeaways from US v. Heppner

By Micaela McMurrough, Matthew Harden & Bryan Ramirez on March 2, 2026
Email this postTweet this postLike this postShare this post on LinkedIn

On February 10, 2026, federal district court Judge Jed S. Rakoff ruled from the bench in the Southern District of New York that the attorney-client privilege and the work product doctrine did not protect legal strategy materials that a criminal defendant generated using a generative AI tool, when he used a public version of the tool and was not instructed by his attorney to generate these materials.  On February 17, 2026, the court issued a written memorandum explaining its reasoning.  

The question presented – an issue of first impression – was: “whether when a user communicates with a publicly available AI platform in connection with a pending criminal investigation, are the communications protected by attorney-client privilege or the work product doctrine?”  The court’s answer was no given the unique circumstances of the case – namely, that no lawyer was involved in the back-and-forth with the AI tool, and the tool itself was a public (i.e., non-confidential) version. 

Below, we summarize the background of the case, the decision, and key takeaways on AI and Legal Privilege.

Background.  On October 28, 2025, Heppner, the defendant, was indicted and charged with several federal crimes, including securities fraud, arising from his time as an executive at several corporations.  When Heppner was arrested, the FBI executed a search warrant and seized a number of documents and electronic devices, which included communications that Heppner had with a publicly available version of a generative AI platform that “prepared reports that outlined defense strategy, [and] outlined what he might argue with respect to the facts and the law” of what the government may charge.  Heppner had engaged in these communications with the AI tool after he had received a grand jury subpoena and after it was clear from discussions with the government that he was the target of the investigation.  Heppner had not been instructed by his counsel to engage with the tool.  Heppner asserted privilege and attorney work product over the materials, arguing that he had (1) input into the platform information that he had learned from counsel; (2) created the AI communications for the purpose of speaking with counsel to obtain legal advice; and (3) subsequently shared the AI communications with counsel for the purpose of  obtaining legal advice.

Attorney-Client Privilege.  The court first ruled that the AI-generated materials failed to satisfy the elements of the attorney-client privilege.  Attorney-client privilege attaches to (1) communications between a client and his or her attorney (2) that are intended to be, and were, kept confidential (3) for the purpose of obtaining or providing legal advice.  The court held that at least two, if not all three, elements were not met. 

  1. Not Communications with Counsel – The court held that the AI communications were not between Heppner and his counsel because the AI tool was not an attorney, and Heppner was consulting the tool entirely on his own (i.e., not at the direction of counsel).
  2. Not Confidential – The AI communications were not confidential because Heppner communicated with a public version of a third-party AI platform, and its privacy policy did not support a reasonable expectation of confidentiality.  The court noted that the platform’s privacy policy specified that the platform collects data on user inputs and outputs, which it uses to train the tool, and reserved the right to disclose such data to third parties, including governmental regulatory authorities.
  3. For Legal Advice – Heppner did not communicate with the AI tool for the purpose of obtaining legal advice because he did not do so at the direction of counsel, rather he did so out of his own initiative.  The court added that even if the information inputted into the AI platform was privileged, any such privilege was waived by sharing the information with the platform.

Work Product Doctrine.  The court also held that the work product doctrine did not apply to the materials generated from the public, non-proprietary AI tool.  The court explained that the work product doctrine “provides qualified protection for materials prepared by or at the behest of counsel in anticipation of litigation or for trial.”  Even assuming that the AI-generated materials were prepared in anticipation of litigation, the court concluded that they were not prepared by or at the behest of an attorney and did not reflect defense counsel’s strategy.  As such, the court held that the work product doctrine did not apply.

Because neither the attorney-client privilege nor the work product doctrine applied, the court held that the materials should be disclosed to the prosecution.

Privilege Takeaways.  The court’s decision is one of what will likely be many decisions analyzing the intersection of AI and legal privileges, but its holdings are confined to its facts, which are quite specific.  Of particular note, Heppner was using a publicly available (non-confidential) version of an AI tool and was not operating at the direction of counsel.

As courts continue to address these questions, there are concrete steps that in-house counsel and companies can take to minimize the risks posed by AI in the context of privilege, litigation, and government investigations:

  • Define Acceptable Use of AI – Implement a policy that defines the acceptable use of AI, including the use of AI in circumstances that may implicate legal considerations, such as the risk of creating discoverable documents.  For example, consider limiting use to approved, proprietary enterprise AI tools, providing clear guidelines for the enterprise use of AI, implementing limits on the retention of AI prompts and outputs, and providing special guidance for uses that may implicate legal considerations. 
  • User Training & Awareness – Educate users (including attorneys) on the appropriate use of AI tools and the risks posed by AI, including the potential risk of disclosure of privileged communications and work product.  For example, it may be helpful to convey that if a non-lawyer independently consults a public version of an AI tool on legal matters, those communications are not likely to be privileged. 
  • Beware of “Third-Party” Risk – Keep in mind and train others that the use of publicly available AI tools may be viewed as a disclosure to third parties, which may undermine, weaken, or waive claims of privilege.  To mitigate the risk of disclosure, consider the availability of proprietary AI tools and train users on the benefits of risks of different kinds of tools.
Photo of Micaela McMurrough Micaela McMurrough
Read more about Micaela McMurrough
Matthew Harden

Matthew Harden is a litigation associate in the firm’s New York office and advises on a broad range of cybersecurity, data privacy, and national security matters, including cybersecurity incident response, cybersecurity and privacy compliance obligations, internal investigations, and regulatory inquiries.

Read more about Matthew Harden
Photo of Bryan Ramirez Bryan Ramirez

Bryan Ramirez is an associate in the firm’s San Francisco office and is a member of the Data Privacy and Cybersecurity Practice Group. He advises clients on a range of regulatory and compliance issues, including compliance with state privacy laws. Bryan also maintains…

Bryan Ramirez is an associate in the firm’s San Francisco office and is a member of the Data Privacy and Cybersecurity Practice Group. He advises clients on a range of regulatory and compliance issues, including compliance with state privacy laws. Bryan also maintains an active pro bono practice.

Read more about Bryan Ramirez
Show more Show less
  • Posted in:
    Privacy & Data Security
  • Blog:
    Inside Privacy
  • Organization:
    Covington & Burling LLP
  • Article: View Original Source

LexBlog logo
Copyright © 2026, LexBlog. All Rights Reserved.
Legal content Portal by LexBlog LexBlog Logo