Founder Privilege: How to Use AI Without Creating Evidence Against Yourself

In February 2026, a federal judge ruled that a founder's AI conversations were not privileged. He had a lawyer when he typed them. It did not help.

You have years of conversations you typed into ChatGPT or Claude while thinking through a lawsuit, a termination, a regulator, an investor, a co-founder. You were candid, because it felt like thinking. All of it is discoverable.

Your chat history is a deposition you gave yourself in advance, and nobody told you that you were giving it.

Founder Privilege is the operating manual. It explains the sixty-five-year-old doctrine that closes the gap, shows you how to put it in place this week with your own counsel, and tells you the truth about the old chats you cannot retroactively protect.

What you will learn

• Why "I have a lawyer" is not enough. The five-element test courts actually apply, drawn from United States v. Kovel (2d Cir. 1961) and Upjohn.
• What a directed channel looks like. Engagement, direction, and a contemporaneous record: the three things that have to exist before the subpoena, not after it.
• The four surfaces your chats live on. Visible history, the provider's back end, your enterprise admin layer, and the synced device in your pocket. Deleting clears exactly one of them.
• What to do about the archive you already have. Including what does not work, and why telling anyone to delete is the one move that turns a discovery problem into a spoliation problem.

Then it turns the board around

The same ruling that exposed one founder exposed everyone else's chat history too, and almost no litigator is asking for it yet. The last third of the book is how to ask: the requests for production that actually reach AI conversation data, why the Stored Communications Act sends you at the party instead of the provider, the deposition topics, and how to test a privilege claim when the other side asserts one.

A working forms kit, not just an argument

• Master engagement letter for attorney-directed AI research, plus an addendum for an existing engagement
• The direction memo and a one-page client instruction sheet
• Litigation hold notice that names AI tools by product, and the preservation demand to an opposing party
• Requests for production, interrogatories, and 30(b)(6) deposition topics
• Conversation-level privilege log format, custodian response letter, and a motion to quash skeleton
• ESI protocol language and a case law reference

Every template is also downloadable free in Word and Markdown. The QR codes inside the book take you straight there.

Who this is for

Founders and executives who use AI for real thinking. In-house counsel writing the policy. Outside counsel who would rather direct the tool than find it in production. There is a chapter written specifically for the lawyer whose client is already typing.

Not legal advice, and reading it does not create an attorney-client relationship. The templates are starting points for licensed counsel to adapt to the facts of a matter and the rules of a jurisdiction.