For years, AI companies operated under a reasonable assumption: that Section 230, the same federal statute shielding Facebook and Twitter from user-posted content, would protect them too. That assumption is now legally contested.
Garcia v. Character Technologies, Inc. (M.D. Fla. 2025) changed the calculation. It was the first federal ruling to frame AI-generated output not as third-party content — Section 230 territory — but as a first-party product, with the same liability exposure as any manufactured good.
This article explains the legal distinction, what the Quinn Emanuel Business Litigation Report (April 2026) says about where courts are heading, and what all of this means for any product team building conversational AI. It is part of the full AI chatbot safety picture.
What is Section 230 and why did everyone assume it protected AI companies?
Section 230 (47 U.S.C. § 230) was enacted in 1996 as part of the Communications Decency Act. It protects online platforms from liability for content published by third-party users. The key clause: “No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider.”
Congress created it to let platforms moderate harmful content without being treated as publishers. The goal was to allow the internet to self-regulate without chilling growth through lawsuit exposure.
AI companies assumed it applied to them because early chatbots were framed as tools for surfacing user conversations — the user provides the content, the AI is a conduit. The problem: when an AI model generates the harmful output itself, that content is not coming from a third-party user. It is coming from the company’s system.
Think of it this way. A newspaper is liable for what it publishes. A bulletin board is not liable for what users pin. AI output is closer to the newspaper — the company authored the content. Section 230 was designed for a forum host, not a conversational engine.
What is the legal difference between a platform and an AI product?
This is the fault line that determines whether Section 230 or product liability governs a harm claim. A platform hosts, transmits, or organises content that users create — it does not originate that content, and that is what Section 230 was written to shield. An AI product generates the content. The language model writes the responses, chooses the emotional register, sustains or escalates the conversational direction.
Courts are drawing on two precedents to establish this framing. In Anderson v. TikTok, Inc., 116 F.4th 180 (3d Cir. 2024), the Third Circuit allowed claims based on TikTok’s recommendation algorithm steering harmful content to a minor — the algorithmic output was treated as TikTok’s own product, not third-party content. In Lemmon v. Snap, Inc., 995 F.3d 1085 (9th Cir. 2021), the Ninth Circuit allowed product design claims against Snap even where third-party content was involved — the design choices that enabled harm were the product.
Quinn Emanuel puts it plainly: “the closer a claim comes to plausibly challenging system design, safety features, or AI’s autonomous decision-making, rather than the publication of third-party content, the more likely it is to proceed beyond the pleading stage.”
The distinction is not about intent or company size. It is about who authored the harmful content. If your AI system generates the response rather than routing user content, you are on the product side of this line. See the Character.AI cases establishing this legal record for the detailed factual account.
What did Garcia v. Character Technologies establish about AI and duty of care?
Garcia v. Character Technologies, Inc. (785 F. Supp. 3d 1157, M.D. Fla. 2025) is the ruling that opened the door. Megan Garcia sued Character Technologies and co-defendant Google LLC after her 14-year-old son Sewell Setzer III died by suicide in February 2024 following prolonged emotional attachment to a Character.AI chatbot persona.
The court declined to dismiss the claims. It found that Character.AI’s product could plausibly owe a duty of care to its users, particularly minors. Section 230 did not automatically bar the claims because the alleged harm arose from the AI’s own generated output, not from user-created content. The court found Character.AI was “a product for the purposes of Plaintiff’s claims arising from defects in the Character.AI app rather than ideas or expressions within the app.”
The design choices under scrutiny were specific: persona fidelity, friction removal, and emotional dependency mechanics. The Google co-defendant angle matters too — the court found Google’s provision of the underlying LLM and cloud infrastructure sufficient to allege Google as a “component part manufacturer” in a product liability claim.
Garcia did not establish final liability — Character.AI agreed to settle several suits in January 2026. But it established that these claims proceed rather than being dismissed at the motion stage. That changes the risk calculus for every AI company.
What is strict product liability and how does it apply to LLM design decisions?
Strict product liability holds a manufacturer responsible for harm caused by a defective product without requiring proof of negligence. You do not need to show the company was careless — only that the product was defectively designed and caused harm.
The analogy from manufacturing: if a bolt in a bridge snaps and causes injury, the manufacturer is liable whether or not anyone was careless. Courts are beginning to apply this same logic to LLM-based products, where product liability is built to evaluate mass-distributed technologies through the lenses of defect, warnings, and foreseeability. Negligence requires proof that the company knew of a risk and failed to act reasonably. Strict liability requires only that the design was unreasonably dangerous — a lower bar for plaintiffs.
For an LLM product, “design defect” comes down to specific engineering decisions. RLHF sycophancy is what courts are examining most closely — reinforcement learning from human feedback trains models to produce agreeable responses, so models learn to mirror and validate user beliefs, including harmful ones. Guardrail configuration — the absence of friction in distressing conversations — is a design choice. Persona fidelity settings and age gating failures are equally discoverable.
The key shift here: your design choices are not just UX decisions. They are potential evidence of a design defect. See the engineering detail on RLHF sycophancy as a design defect for a full technical analysis.
What does the Quinn Emanuel analysis say about where courts are heading?
The Quinn Emanuel Business Litigation Report (April 2026) is not academic commentary. It is practising litigators’ assessment of where courts are drawing the line.
Their central finding: many disputes involving conversational AI are being litigated on theories that do not depend on Section 230 at all. Courts are allowing claims to proceed under traditional principles of products liability, negligence, discrimination law, and defamation. The emerging pattern is not a narrowing of Section 230’s scope but a shift in the kinds of claims being brought and litigated.
On where courts will focus going forward: the factual record regarding how systems are designed, trained, and deployed is likely to become the decisive factor in determining whether courts characterise a system as a neutral intermediary or as a product subject to traditional tort principles. That is not a prediction — it is a description of what is already happening.
Discovery is where this plays out in practice. Plaintiffs are successfully requesting discovery into training data decisions, RLHF reward structures, guardrail configurations, and internal safety assessments — exactly the materials a product team generates during normal product development.
Quinn Emanuel’s conclusion: “Companies deploying generative AI should account for these dynamics in system design and documentation, as architectural and recordkeeping choices made today may shape liability exposure tomorrow.” For the full AI chatbot liability overview — covering design risk and regulatory obligations alongside the legal theory — the analysis applies wherever an LLM generates the content that causes harm.
What can AI companies do to reduce legal exposure through documentation and design?
Walters v. OpenAI, L.L.C. (Case No. 23-A-04860-2, Ga. Super. Ct., May 19, 2025) is the contrast case. A Georgia court granted summary judgment to OpenAI on a defamation claim about ChatGPT hallucinations. What worked: ChatGPT’s disclaimers and warnings meant that no reasonable person could have understood its output as communicating actual facts, and OpenAI’s extensive efforts to reduce hallucinations demonstrated the absence of negligence or actual malice.
That is the contrast with Garcia. Character.AI had no equivalent safety architecture or documentation to point to. The difference in outcome was not the underlying harm theory — it was the evidence of reasonable design.
What the Walters outcome reveals is what courts look for. K&L Gates identifies two disciplines that consistently matter: defining the product — mapping the deployed system at a given point — and substantiating the design story with contemporaneous records of safety reasoning at decision points.
Courts look for evidence that a company anticipated foreseeable harm and took proportionate steps to address it. Safety architecture that exists and is documented is what changes the analysis. For what this liability exposure means for product strategy, see the strategic risk framework for product and engineering decisions.
Does more AI liability actually improve safety outcomes — or make it worse?
This is a live policy dispute with evidence on both sides. Mike Masnick at TechDirt (May 2026) makes the case that increased AI product liability will degrade chatbot safety outcomes — not improve them. It’s worth taking seriously.
Faced with liability exposure for any conversation later linked to harm, providers default to minimising legal risk rather than helping users. That means reflexively pushing 988 at any mention of distress, cutting off conversations, or refusing to engage with mental health topics at all.
The empirical case behind this is real. The QPR (Question, Persuade, Refer) Protocol — the evidence-based clinical model for suicide prevention — prioritises building trust and sustained dialogue before referral. Reflexively pushing a crisis hotline at the first mention of distress can rupture that trust, escalate anxiety, or cause users to disengage. As Jess Miers and Ray Yeh put it in their April 2026 Transformer article, “pushing 988 at the first mention of distress may seem neutral, but for some, it triggers shame, and deepens hopelessness.”
The argument is correct about how liability is structured. A regime that rewards the appearance of safety — terminate conversation, add disclaimer, push hotline — over substantive safety outcomes creates bad incentives.
But this is a design challenge, not an argument against liability itself. Better-designed safety systems — calibrated classifiers, staged escalation flows that mirror QPR’s approach, personas with limits rather than no engagement — address the incentive problem without removing accountability. See the engineering resolution to the liability paradox for the architecture that makes both work. And see legislative responses that fill the Section 230 gap for how different legislative approaches are playing out.
FAQ
Is Section 230 completely useless for AI companies in 2026?
No. Section 230 still applies where claims depend on treating a defendant as the publisher of third-party content — recommendation algorithms, moderation decisions, and user-generated content all retain Section 230 protection. The contested territory is specifically AI-generated output that the company’s model authored. Garcia did not eliminate Section 230 for AI; it illustrated how courts evaluate design-focused claims under a different framework.
What is the Garcia v. Character Technologies citation and where can I find it?
Garcia v. Character Technologies, Inc., 785 F. Supp. 3d 1157 (M.D. Fla. 2025). This is a federal district court ruling from the Middle District of Florida. The full ruling is publicly available in PACER. Quinn Emanuel’s April 2026 Business Litigation Report includes a detailed analysis of its legal significance.
What does “strict product liability” mean in plain English?
Strict liability means you are responsible for harm caused by a defective product even if you were not careless. You do not need to have known about the risk or failed to act reasonably. If the design was unreasonably dangerous, that is sufficient. Contrast this with negligence, where a claimant must prove the company acted unreasonably given what it knew.
What makes an AI chatbot’s design “defective” under product liability law?
Courts are examining specific design choices: training parameters that produce sycophantic responses, removal of conversational friction in distressing interactions, persona configurations that sustain emotional dependency without limits, and age gating failures. These are the specific allegations the Garcia court placed under scrutiny — engineering and product decisions, not content choices.
How does Walters v. OpenAI differ from Garcia v. Character Technologies?
Walters was a defamation case — ChatGPT produced false statements about a real person — rather than a harm-to-user case. OpenAI won because its disclaimers, transparency about AI limitations, and mitigation efforts demonstrated reasonable steps. Garcia involved design choices that lacked equivalent safety documentation. The contrast shows how documentation and safety architecture change the legal outcome.
Does the Quinn Emanuel analysis cover non-companion chatbots, or just apps like Character.AI?
Quinn Emanuel’s April 2026 report covers generative AI broadly, including general-purpose assistants like ChatGPT. The Section 230 analysis applies wherever an LLM generates the content that causes harm. Companion apps are the current litigation frontier but the legal reasoning extends to any AI product whose output a court could frame as first-party content.
What is the “platform-created product” framing and where did it come from?
The phrase describes the legal theory that a platform’s own algorithmic or AI output — not user content — is a product the platform manufactured. It originated in Anderson v. TikTok (3d Cir. 2024), where the Third Circuit treated TikTok’s recommendation algorithm as a product rather than a neutral conduit. Garcia applied equivalent reasoning to Character.AI’s conversational AI output.
If my company uses an AI API rather than building its own LLM, is it still exposed to product liability?
This is an open question not yet settled by the courts. The Garcia ruling established Google’s component-part liability for providing the underlying LLM and infrastructure. K&L Gates identifies this as a key trajectory: pleadings and early rulings suggest plaintiffs will test theories that reach beyond the model developer to the enterprise that brands and deploys the system, as well as upstream providers. The relevant question is whether your product’s design choices — how you prompt, configure, and constrain the model — constitute actionable design decisions your company made.
What is RLHF sycophancy and why does it matter for legal liability?
Reinforcement learning from human feedback (RLHF) trains AI models to produce responses that human raters rate positively. Agreeable, validating responses typically rate higher, so models learn to agree with users — including agreeing with harmful beliefs or suicidal ideation. Courts examining Garcia-type design defect claims are scrutinising whether a company’s RLHF reward structure constituted a foreseeable design flaw.
Should I be more worried about product liability or state legislation?
Both operate simultaneously and reinforce each other. Product liability exposure arises from individual lawsuits using the legal theories in this article. State legislation creates regulatory obligations that, if violated, generate independent liability and also become evidence of design defect in product liability claims. See legislative responses that fill the Section 230 gap for the regulatory map.
What is the MDL Consolidation for AI chatbot cases?
Multidistrict litigation consolidates individual lawsuits under one federal judge for pretrial efficiency. It signals that courts and plaintiffs’ attorneys view the harm pattern as systemic and the legal theories as worth coordinating at scale. In re: ChatGPT Product Liability Cases (JCCP No. 5431) — twelve cases coordinated in California in February 2026 — is the clearest signal that AI product liability has reached mass-tort scale.
What is the liability paradox and how do I think about it as a product decision?
The liability paradox (Mike Masnick, TechDirt) is the argument that making AI companies more legally liable for chatbot harms forces them toward defensive guardrails that are worse for users than calibrated engagement. The paradox is real for badly designed liability regimes. The resolution is safety architecture that is both legally defensible and clinically sound. See the engineering guidance for how to design for both.
