California SB 243 Explained: What the New AI Companion Chatbot Law Requires

California's law for AI companion chatbots took effect in January 2026. Unlike New York's, it lets users sue, which changes who enforces it and how often.

What SB 243 is

California Senate Bill 243, signed on October 13, 2025, is one of the first two US laws written specifically for AI companion chatbots (New York's took effect slightly earlier, on November 5, 2025) — products designed to simulate a sustained, personal relationship with a user, as distinct from general-purpose AI assistants. It took effect on January 1, 2026, and applies to companies operating companion chatbot products with users in California, regardless of where the company is headquartered.

The bill was introduced against the backdrop of the litigation and public scrutiny covered in our Character.AI business analysis — lawsuits alleging companion AI products caused serious harm to minors, and broader concern that sustained emotional engagement with an AI system carries risks existing consumer-protection law didn't clearly address.

Late 2024 Oct 2025 Jan 1, 2026 Oct 28, 2026 Safety lawsuitsfiled againstcompanion apps US senators askthe FTC toinvestigate SB 243 takeseffect, with aprivate right of action New York signsS9051B; dutiesstart Jan 2027
Litigation came first, federal attention second, binding state law third. The pattern — private suits, then regulator interest, then statute — is the same one data privacy followed.

Core requirements

  • AI disclosure. Operators must clearly and conspicuously tell users they are interacting with AI, and must disclose that companion chatbots may not be suitable for some minors.
  • Reminders for minors. For users the operator knows are minors, the AI notice must repeat at least every three hours during ongoing conversations, with a reminder to take a break.
  • Sexual content and minors. For known minors, operators must take reasonable measures to stop the chatbot producing sexually explicit visual material or telling the minor to engage in sexually explicit conduct.
  • Suicide and self-harm protocols. Operators must have a protocol for responding when users express suicidal ideation or self-harm, including referring them to crisis services. From July 1, 2027, they must also report annually to California's Office of Suicide Prevention.

These are narrower and more specific than general platform-safety guidance. They're written as concrete, auditable product behaviors rather than broad principles — which is part of why compliance has been treated as a near-term engineering task rather than a policy statement.

The private right of action

The enforcement mechanism is what makes SB 243 unusually consequential. The law includes a private right of action: individual users, not just the California Attorney General, can sue a noncompliant platform directly. A successful plaintiff can recover the greater of actual damages or $1,000 per violation, plus injunctive relief and attorney's fees (Morrison Foerster summary).

$1,000 Damages per violation (or actual damages, if greater), plus attorney's fees, recoverable by individual users

This matters structurally. It removes the enforcement bottleneck that limits many consumer-protection statutes — where practical enforcement depends on a state regulator's limited resources and priorities — and instead makes every user a potential enforcer. For a platform with a large user base, even a modest per-user violation rate translates into meaningful exposure.

The federal angle

SB 243 is a state law, but it arrived alongside growing federal attention to the same category. In September 2025, the FTC opened a formal Section 6(b) inquiry into seven companies — Alphabet, Character Technologies, Meta, OpenAI, Snap, Instagram, and xAI — seeking data on their AI chatbots' safety practices, monetization approach, and impact on minors. That inquiry followed weeks of reporting on Meta's own internal chatbot policies specifically — see our breakdown of the Meta case for what that reporting found and how it escalated into a Senate investigation, and our case studies on Snap's My AI lawsuits, the OpenAI wrongful-death suit, and Google's Gemini lawsuit and child-safety fight for how three of the other named companies are facing similar scrutiny. In October 2025, California's senators Alex Padilla and Adam Schiff wrote to the FTC asking it to broaden that review, including crisis detection, parental tools and transparency about safeguards.

No federal companion-chatbot statute has passed as of this writing. But state laws, a federal inquiry and continued legislative pressure all arrived within about a year, much as they did in data privacy, so operators should treat SB 243 as a leading indicator rather than an isolated state requirement.

The cross-state trend

California has also gone further itself. On September 10, 2026, Governor Newsom signed SB 1119 ("Adam's Law"), which builds on SB 243 for child users: annual child-safety risk assessments, independent audits, parent-adjustable default protections and time limits, and limits on advertising to children. Most of its duties start July 1, 2027. Public prosecutors can seek up to $5,000 per affected child for each negligent violation and $15,000 for each intentional one, and children who suffer actual harm can sue (FPF). SB 243 stays in force alongside it.

California isn't alone. New York's AI companion models law (General Business Law Article 47) took effect November 5, 2025. It requires an AI notice at the start of a session and every three hours for all users, plus self-harm protocols, and is enforced by the attorney general with penalties of up to $15,000 a day rather than by private lawsuits. New York’s S9051B was signed on October 28, 2026 as Chapter 368. Its restrictions on unsafe AI companion features for minors take effect January 1, 2027; it is signed law with a future effective date. The existing Article 47 safeguards remain distinct. See our state-by-state reference for the dated comparison.

Compliance checklist for operators

  1. Implement AI disclosure, with three-hour repeats for minors (New York requires them for everyone).
  2. Know which users are minors and build the break-reminder flow for them.
  3. Filter sexually explicit content for known minors.
  4. Define and test a self-harm response protocol: what the system says, which crisis services it refers to, and how you will report on it from July 2027.
  5. Document your compliance measures. Given the private right of action, an auditable record of what safeguards exist and when they shipped is meaningful risk reduction on its own.
  6. Plan for California's SB 1119 (from July 1, 2027) and monitor New York and other state legislation before assuming a single national configuration is sufficient.

Why this matters beyond California

Character.AI's safety changes, such as time limits and then an end to open-ended chat for under-18 users by November 2025, arrived around the same time as SB 243 and point the same way. They show that compliance is achievable, and that it changes the product users get. Meeting SB 243's requirements is now a baseline cost of operating in this category, not an optional risk-management choice.

Weighing a platform switch because of compliance risk? Our calculator shows the month it pays back, including migration labour and the stretch where you pay both vendors.
Open the switching cost calculator
Sources: California SB 243 bill text and status; the FTC announcement of its September 2025 Section 6(b) inquiry into seven AI chatbot companies; Sen. Padilla's release on the Padilla/Schiff letter to the FTC (October 22, 2025); legal alerts from Manatt, Fenwick and Troutman Pepper Locke on New York's AI Companion Models Law (effective November 5, 2025); New York S9051B legislative history via the NY State Senate (signed October 28, 2026 as Chapter 368; Section 3 sets January 1, 2027 as the effective date); Morrison Foerster's comparison of the California and New York laws; Asm. Bauer-Kahan on the signing of SB 1119 (September 10, 2026); Future of Privacy Forum, "Regulating the Conversation" (September 2026).

Updated November 10, 2026: corrected the New York comparison, timeline and source note to reflect S9051B’s October 28 signing. California’s provisions retain the October 2026 review date. In September, the earlier premature description of S9051B as enacted was corrected to pending; the October 28 signing is a subsequent event. Verify current statutory language before relying on this summary. This article is analysis, not legal advice.