MTC: When Your CEO Asks ChatGPT How to Take Over: Lessons for Lawyers on Public AI, Ethics, and Confidentiality 🧠⚖️

Lawyers need to evaluate public AI chatbot against ABA confidentiality and privilege rules

In March 2026, the Delaware Court of Chancery in Fortis Advisors, LLC v. Krafton, Inc. handed lawyers one of the clearest cautionary tales yet about public AI chatbots, corporate governance, and the limits of “move fast and break things.” A South Korean gaming conglomerate, Krafton Inc., used an artificial intelligence chatbot to help devise an internal “Project X” takeover plan against its own studio, Unknown Worlds Entertainment, and then tried to defend the fallout in court. The result: a detailed opinion reinstating the studio’s CEO, extending a $250 million earnout period, and spotlighting how AI misuse can become Exhibit A when things go wrong.

If you’re a solo, a small-firm lawyer, or an AI‑curious practitioner dabbling with ChatGPT or similar tools, this case is your wake‑up call. The message is not “don’t use AI.” The message is: treat public chatbots the same way you treat email, cloud storage, or texting — through the lens of ABA ethics, client confidentiality, and privilege. 😬

In this editorial, I’ll unpack what happened, how the court framed the misuse of a chatbot, and what you should do in your own practice to stay on the right side of the rules.

The Case in a Nutshell: AI as a Takeover Co‑Pilot

Krafton bought Unknown Worlds — the studio behind Subnautica — for $500 million upfront plus up to $250 million in contingent earnout payments, with a contractually guaranteed structure: the founders and CEO (the “Key Employees”) retained operational control and could only be fired for defined “Cause.”  As Subnautica 2 approached early‑access launch, internal projections showed the game would easily trigger a massive earnout.

The CEO of Krafton grew concerned he looked like a “pushover” under the deal and turned to a public AI chatbot for advice on how to avoid paying the earnout and seize control of the studio. The chatbot’s “response strategy” included:

  • Locking down publishing rights and code access.

  • Crafting messaging to “secure public support” and undermine the “large corporation vs. indie” narrative.

  • Preparing a “takeover” path that blended hardball legal tactics with PR framing. 

Krafton’s internal team implemented much of that plan — cutting off the studio’s access to its Steam publishing console, posting unilateral public statements, and ultimately terminating the founders and CEO on a pretext of “premature release” risk.  When sued, Krafton tried to pivot to new justifications, including the executives’ role changes and their defensive downloads of company data. 

The court was having none of it. Vice Chancellor Will held that:

  • The terminations were not “for Cause” under the negotiated contract.

  • The “Project X” takeover guided by the chatbot was a pretext to avoid the earnout.

  • The studio’s CEO, Ted Gill, must be reinstated with full operational control, and the earnout period equitably extended by the length of his ouster. 

In other words, the AI‑assisted takeover strategy became part of the factual narrative of bad faith and breach — not a clever workaround.

Public Chatbots and ABA Model Rules: Three Pressure Points ⚖️

Attorneys must consider ethical AI chatbot use for confidential client case analysis

Even though this is a corporate earnout case, the opinion gives lawyers a concrete frame for thinking about public AI tools under the ABA Model Rules.

1. Confidentiality — Model Rule 1.6

Rule 1.6 requires lawyers to keep “information relating to the representation of a client” confidential, absent informed consent or a specific exception. Public chatbots are not your firm’s Document Management System (DMS) — they’re third‑party services that typically ingest prompts for training, quality, and logging. When Krafton’s CEO ran “Project X” through a chatbot, he was effectively outsourcing high‑stakes strategy to a non‑privileged third‑party system that could store and learn from those prompts. 

For lawyers, the parallels are obvious:

  • Dropping fact patterns, names, or deal structures into a public chatbot can mean you’ve disclosed client information to a non‑controlled vendor.

  • Even “sanitized” prompts can be re‑identified when combined with other data.

Under 1.6, that’s a potential confidentiality breach unless you’ve vetted the tool, negotiated appropriate terms (including data handling and retention), and obtained informed client consent for that mode of assistance. Emojis and “it’s just drafting help” don’t change that. 😉

2. Privilege — Model Rules 1.1 and 1.4 (Competence and Communication)

Privilege isn’t framed in the Model Rules, but Rule 1.1 (competence) and 1.4 (communication) require you to understand how your technology choices affect the protection of client communications. When you route strategy discussions through a public chatbot:

  • You may jeopardize attorney–client privilege by involving a third‑party with no need‑to‑know and no formal role in the representation.

  • You may create discoverable records that live outside your control, just as Krafton’s CEO created chat logs he then tried to delete. 

The court noted that relevant chatbot logs were deleted, which did not play well in evaluating Krafton’s narrative.  Privilege analysis is already complex with cloud tools; adding public AI as a “secret co‑counsel” without protections only compounds that risk. 

Competent use of technology now includes understanding whether your AI stack is preserving or eroding privilege and communicating those risks to clients when you propose AI‑assisted workflows.

3. Candor and Misrepresentation — Model Rule 4.1 and 8.4(c) 🚨

Although this case turns on contractual “Cause” and good faith, the court’s language about “pretextual” justifications and manufactured defenses should resonate with litigators. Model Rule 4.1 prohibits knowingly making false statements of material fact to third parties; Rule 8.4(c) bars conduct involving dishonesty, fraud, deceit, or misrepresentation. 

When you:

  • Use a chatbot to generate strategic messaging designed to mislead stakeholders.

  • Craft public statements or demand letters that you know are pretextual, but you’ve optimized with AI for tone and impact.

… you’re still responsible for the truthfulness of that content. The court saw through Krafton’s attempt to re‑frame events after the fact, and its internal AI‑assisted playbooks did not help. 

For lawyers, the lesson is simple: AI‑generated output is yours once you sign or speak it. If it’s misleading, you own the ethics problem — not “the algorithm.”

Practical Takeaways for Solo and Small‑Firm Lawyers 🧩

So what do you do if you’re a tech‑savvy lawyer who likes AI, but doesn’t want your prompts quoted in an opinion like this?

Here are grounded, practice‑ready steps.

1. Establish an AI Use Policy

Even if you’re a solo, write down what you will and won’t do with public chatbots.

lawyers need to build practical, ethical AI policies for practice.

  • No client names, exact fact patterns, or identifiable deal terms in public tools.

  • Use AI for structure and language, not for strategy or confidential analysis.

  • Prefer client‑specific, non‑logging enterprise tools when handling sensitive material.

Treat this like you treat your cloud storage or remote‑work policy — it’s part of your competence under Model Rule 1.1 and your supervisory obligations under 5.1/5.3 if you have staff.

2. Separate “Public Prompting” from “Privileged Thinking” 🧠

Use public chatbots for:

  • Headline and meta description drafting.

  • Blog outlines, post ideas, or simple explainer language for non‑client scenarios.

  • Rough templates for standard documents that you will heavily edit.

Avoid using them for:

  • Fact‑specific case assessments.

  • Litigation strategy, negotiation plans, or internal “playbooks” like Krafton’s “Project X.” 

  • Anything that feels like the kind of conversation you’d normally have only with a colleague behind closed doors.

This separation keeps your privileged work product inside tools and workflows you control.

3. Vet Vendors Like You Vet e‑Discovery Platforms

If you move beyond public chatbots to paid AI tools, evaluate them as you would any major legaltech vendor:

  • Where is data stored?

  • Is training on your material disabled by default?

  • Can you get a Business Associate Agreement or Data Processing Agreement / Data Protection Impact Assessment that aligns with your jurisdiction’s expectations?

The ABA’s Formal Opinion 477R on secure communications and cloud ethics opinions from state bars all provide analogies: reasonable steps, not perfection, are required — but “type client memo into random website” is not reasonable. 😄

4. Document Client Consent When AI Is Material to the Representation

If you expect to use AI in a way that materially affects how you deliver legal services, communicate that to clients under Rule 1.4:

  • Explain benefits (efficiency, faster drafting).

  • Explain risks (data handling, reliability, hallucinations).

  • Offer an AI‑free option.

Written engagement terms that address AI use can save hard conversations later if something goes sideways.

5. Revisit Your “Bad Facts” Mindset

Reading this Delaware opinion, you see how internal strategy — including AI‑assisted plotting — can become a litigation exhibit.  For lawyers, that’s an invitation to ask: 

“If this prompt or chatbot conversation showed up in an opinion, would I be comfortable defending it under the Model Rules?”

If the answer is no, don’t send it. That simple heuristic scales across tools and platforms.

What This Case Signals for the Next Wave of Legal Tech 🌊

There can be significant legal consequences for AI chatbot misuse in legal disputes.

The opinion in Fortis Advisors v. Krafton is not an ethics decision aimed at lawyers, but it shows courts will:

  • Scrutinize AI‑assisted strategies as part of broader narratives about good faith, bad faith, and pretext.

  • Expect parties — and by extension, counsel — to maintain and produce AI‑related records where relevant.

  • Be unimpressed by attempts to retroactively justify decisions made for economic reasons with thin “quality” or “readiness” arguments. 

As public models get more powerful and more embedded in practice, ABA Model Rules on competence, confidentiality, supervision, and candor apply just as they did when lawyers moved to email, smartphones, and the cloud. AI is just the next tool — but it’s a tool that makes it very easy to generate sophisticated bad ideas quickly.

Your job is to keep your ethical compass steady, even when the chatbot is very persuasive. 🧭

MTC

TSL Labs 🧪 Bonus: Deep Dive on our April 27, 2026, Editorial, MTC: Smart Recording, Client Secrets, and HeyPocket: What Every Lawyer Needs to Know in 2026 📱⚖️

📌 To Busy to Read This Week’s Editorial?

Join us for an AI-powered deep dive into the ethical challenges facing legal professionals in the age of generative AI. 🤖 In this episode, we unpack how AI note takers and “always-listening” devices can quietly route client secrets to third-party vendors, why that matters under the ABA Model Rules, and how a 2026 federal decision out of the Southern District of New York turned one defendant’s AI chats into discoverable evidence. Whether you are a solo practitioner, in-house counsel, or a tech-curious professional in another field, this conversation will help you balance convenience with confidentiality and avoid turning your favorite AI assistant into your biggest evidentiary risk.

👉 Before your next client meeting, listen to this episode, check out our editorial, and run your current AI tools through the checklist we outline—then subscribe and share with a colleague who is still “just trusting the app.” 🎧

In our conversation, we cover the following:

  • 00:00 – The “ambient microphone” problem: phones, smart speakers, wearables, and connected cars as a continuous surveillance layer around client conversations.

  • 01:00 – How technology competence has shifted from locking file cabinets to understanding data custody, cloud routing, and API-driven services.

  • 02:30 – What makes AI note takers like HeyPocket different from passive telemetry and why capturing the spoken “payload” changes the threat model.

  • 04:00 – The invisible “third party in the room”: routing privileged audio through external AI models and the malpractice risk of default “Allow” clicks.

  • 05:30 – Applying ABA Model Rules 1.1 and 1.6 to AI workflows: competence, confidentiality, and “reasonable efforts” in a world of automated transcription.

  • 07:00 – Risk-based analysis from ABA Formal Opinions 477R and 498: weighing sensitivity, likelihood of disclosure, and available safeguards before using AI.

  • 08:30 – Why secretly recording clients or opponents with AI tools can implicate Rule 8.4(c), even in one‑party consent jurisdictions.

  • 10:00 – Inside United States v. Heppner (SDNY 2026): how public generative AI platforms destroyed privilege and work-product protections for a criminal defendant.

  • 12:00 – How AI training and tokenization work, why “military‑grade encryption” does not save privilege if terms of service allow internal data use.

  • 14:00 – Treating every AI note taker like an outsourced e‑discovery vendor: NDAs, retention policies, security audits, and data destruction timelines.

  • 16:00 – Practical minimization strategies: defaulting to no recording, segmenting AI-generated content by matter, and restricting access via role‑based controls.

  • 17:30 – Establishing bright-line “no‑AI” categories (criminal defense, internal investigations, sensitive family/immigration, high‑value trade secrets).

  • 18:30 – Counseling clients not to “prep their case” with public chatbots after Heppner and why this is now part of competent representation.

  • 19:30 – Building a simple vendor-vetting checklist for law firms and professional practices adopting AI note takers.

  • 20:00 – Looking ahead: when failure to use secure, vetted AI may itself become a competence issue due to inefficiency and overbilling.

  • 21:00 – Rethinking privilege in a world where an algorithmic “third party” is always in the room and devices are never truly off

RESOURCES

Mentioned in the episode

TSL LABS BONUS: Dynamic Random-Access Memory (DRAM): Why It Matters for Law Firm Performance and Data Security ⚖️💻

Join us for an AI-powered deep dive into the ethical challenges facing legal professionals in the age of generative AI. 🤖 In this episode, we break down our April 20, 2026, Tech‑Savvy Lawyer editorial on how a global DRAM shortage and AI data center demand are driving up PC prices, pushing many legal professionals toward Apple hardware, and redefining what technological competence really means. We explore how unified memory, on‑device AI, and long‑term support lifecycles are changing the Mac vs. Windows calculus, and why “cheap but weak” laptops may now create serious competence and confidentiality risks for your clients.

In our conversation, we cover the following:

  • 00:00 – Why upgrading your work laptop in 2026 feels like buying a luxury vehicle, not a routine office expense.

  • 00:45 – Setting the stage: a “seismic shift” in hardware pricing hitting professional industries, with a focus on the legal field.01:30 – Introducing Michael D.J. Eisenberg’s Tech‑Savvy Lawyer editorial and its core thesis about a tech hardware crisis.

  • 02:15 – The global DRAM crunch: how AI data centers are buying up memory like airlines hoard jet fuel, and why PC OEMs are getting squeezed.

  • 03:30 – Microsoft’s April 2026 Surface price hikes and the end of the “Windows is cheaper” assumption for law firms.

  • 05:15 – The “value inversion”: when high‑end Windows laptops now cost more than roughly comparable MacBooks.

  • 06:30 – Why this isn’t a normal tech price cycle and how it breaks 20 years of corporate IT purchasing assumptions.

  • 07:15 – Apple’s structural advantage: vertical integration, unified memory, and shielding itself from spot‑market DRAM volatility.

  • 08:30 – The M‑series (M5) advantage: performance per watt, thermal behavior, battery life, and running local AI plus heavy legal workloads.

  • 09:45 – Yes, Apple prices are rising too—why the relative “security‑to‑cost” and performance story still favors Macs for many professionals.

  • 10:45 – When “cheap but weak” hardware crosses the line: connecting underpowered laptops to ABA Model Rule 1.1 (competence) and Comment 8 on tech competence.

  • 12:00 – From annoyance to ethical exposure: how sluggish systems cripple eDiscovery, AI‑driven research, and document automation.

  • 13:00 – Why laptop purchasing is now core client‑service strategy, not just a back‑office procurement task.

  • 13:45 – On‑device vs. cloud AI: where computation happens, why that matters, and how it ties into ABA Model Rule 1.6 (confidentiality).

  • 14:30 – The role of Apple’s Neural Engine and local processing in reducing reliance on external AI APIs and third‑party servers.

  • 15:30 – Clarifying the security nuance: Windows is not inherently less secure, but comparable on‑device AI capability often costs more.

  • 16:30 – Redefining security in 2026: it’s not just antivirus and passwords; it’s where the AI thinking physically happens.

  • 17:15 – Building a documented purchase matrix: price, performance, storage, memory, security, lifecycle, and critical software compatibility.

  • 18:15 – When you can’t leave Windows: legacy legal software, state e‑filing systems, and the hidden costs of moving to macOS.

  • 19:00 – Survival strategies for Windows‑locked practices: non‑Surface OEMs, staggered refresh cycles, and buying fewer but higher‑quality machines.

  • 19:45 – Treating laptops as long‑term infrastructure instead of disposable commodities.

  • 20:15 – Big‑picture recap: DRAM shortages, unified memory, ethical duties, and shifting hardware norms in law practice.

  • 20:45 – The closing question: will AI‑driven hardware requirements quietly raise the price of access to justice?

RESOURCES

Mentioned in the episode

Hardware mentioned in the conversation

Software & Cloud Services mentioned in the conversation

If you want your next laptop purchase to strengthen—not weaken—your ethical obligations, client security, and AI‑powered workflows, hit play now and learn how to build a smarter, future‑proof hardware strategy. 🎧💡

🚨🎙️📘 Three Days Left: The Lawyer’s Guide to Podcasting releases NEXT WEEK! 🥳🥳🥳

Inside title page of The Lawyer’s Guide to Podcasting, releasing January 19, 2026.

“The Lawyer’s Guide to Podcasting” will be released on Monday, January 19, 2026, through Amazon!!!

Designed for legal professionals, this book walks through every step of launching and sustaining an effective, ethically sound podcast that supports your practice and professional reputation.​

You will learn:

  • Show formats

  • Equipment needed

  • Show hosting platforms to use

  • Growing your audience

  • Maintaining Professional Ethics

  • Maybe earn some $Money$ too!

Want the release link the moment it’s live?
Email Admin@TheTechSavvyLawyer.Page with subject “Book Link.” I’ll send it on launch day. 🚀

🎙️📘 Quick reminder: The Lawyer’s Guide to Podcasting releases NEXT WEEK!

Inside title page of The Lawyer’s Guide to Podcasting, releasing January 19, 2026.

If you want a podcast that sounds professional without turning your week into a production project, this book is built for you. It’s practical. It’s workflow-first. It keeps ethics and confidentiality in view. 🔐⚖️

✅ Inside you’ll learn:

  • How to choose a podcast format that fits your goals 🎯

  • A simple, reliable setup that sounds credible 🎤

  • Recording habits that reduce editing time ⏱️

  • Repurposing steps so one episode powers your content plan ♻️

📩 Want the release link the moment it’s live? Email Admin@TheTechSavvyLawyer.Page with subject “Book Link.” I’ll send it on launch day. 🚀

📖 WORD OF THE WEEK YEAR🥳:  Verification: The 2025 Word of the Year for Legal Technology ⚖️💻

all lawyers need to remember to check ai-generated legal citations

After reviewing a year's worth of content from The Tech-Savvy Lawyer.Page blog and podcast, one word emerged to me as the defining concept for 2025: Verification. This term captures the essential duty that separates competent legal practice from dangerous shortcuts in the age of artificial intelligence.

Throughout 2025, The Tech-Savvy Lawyer consistently emphasized verification across multiple contexts. The blog covered proper redaction techniques following the Jeffrey Epstein files disaster. The podcast explored hidden AI in everyday legal tools. Every discussion returned to one central theme: lawyers must verify everything. 🔍

Verification means more than just checking your work. The concept encompasses multiple layers of professional responsibility. Attorneys must verify AI-generated legal research to prevent hallucinations. Courts have sanctioned lawyers who submitted fictitious case citations created by generative AI tools. One study found error rates of 33% in Westlaw AI and 17% in Lexis+ AI. Note the study's foundation is from May 2024, but a 2025 update confirms these findings remain current—the risk of not checking has not gone away. "Verification" cannot be ignored.

The duty extends beyond research. Lawyers must verify that redactions actually remove confidential information rather than simply hiding it under black boxes. The DOJ's failed redaction of the Epstein files demonstrated what happens when attorneys skip proper verification steps. Tech-savvy readers simply copied text from beneath the visual overlays. ⚠️

use of ai-generated legal work requires “verification”, “Verification”, “Verification”!

ABA Model Rule 1.1 requires technological competence. Comment 8 specifically mandates that lawyers understand "the benefits and risks associated with relevant technology." Verification sits at the heart of this competence requirement. Attorneys cannot claim ignorance about AI features embedded in Microsoft 365, Zoom, Adobe, or legal research platforms. Each tool processes client data differently. Each requires verification of settings, outputs, and data handling practices. 🛡️

The verification duty also applies to cybersecurity. Zero Trust Architecture operates on the principle "never trust, always verify." This security model requires continuous verification of user identity, device health, and access context. Law firms can no longer trust that users inside their network perimeter are authorized. Remote work and cloud-based systems demand constant verification.

Hidden AI poses another verification challenge. Software updates automatically activate AI features in familiar tools. These invisible assistants process confidential client data by default. Lawyers must verify which AI systems operate in their technology stack. They must verify data retention policies. They must verify that AI processing does not waive attorney-client privilege. 🤖

ABA Formal Opinion 512 eliminates the "I didn't know" defense. Lawyers bear responsibility for understanding how their tools use AI. Rule 5.3 requires attorneys to supervise software with the same care they supervise human staff members. Verification transforms from a good practice into an ethical mandate.

verify your ai-generated work like your bar license depends on it!

The year 2025 taught legal professionals that technology competence means verification competence. Attorneys must verify redactions work properly. They must verify AI outputs for accuracy. They must verify security settings protect confidential information. They must verify that hidden AI complies with ethical obligations. ✅

Verification protects clients, preserves attorney licenses, and maintains the integrity of legal practice. As The Tech-Savvy Lawyer demonstrated throughout 2025, every technological advancement creates new verification responsibilities. Attorneys who master verification will thrive in the AI era. Those who skip verification steps risk sanctions, malpractice claims, and disciplinary action.

The legal profession's 2025 Word of the Year is verification. Master it or risk everything. 💼⚖️

ANNOUNCEMENT (BOOK RELEASE): The Lawyer’s Guide to Podcasting: The Simple, Ethics-Aware Playbook to Launch a Professional Podcast (Release mid-January, 2026)

Anticipated release is mid-january 2026.

🎙️📘 Podcasting is still one of the fastest ways to build trust. It works for lawyers, legal professionals, and any expert who needs to explain complex topics in plain language.

On January 19, 2026, I’m releasing The Lawyer’s Guide to Podcasting. This book is designed for busy professionals who want a podcast that sounds credible, protects confidentiality, and fits into a real workflow. No studio required. No tech overwhelm.

✅ Inside the book, you’ll learn:

  • How to pick a podcast format that matches your goals 🎯

  • The “minimum viable setup” that sounds professional 🎤

  • Recording workflows that reduce editing time ⏱️

  • Practical ethics and risk habits for public content 🔐

  • Repurposing steps so one episode becomes a week of marketing ♻️

📩 Get the release link: Email Admin@TheTechSavvyLawyer.Page with the subject line “Podcasting Book Link” and I’ll send the link as soon as the book is released. 📩🎙️