Topic starter
11/11/2026 6:00 pm
TL;DR: California SB 243 now puts companion chatbots that sustain relationships across sessions under disclosure, minor-safety and crisis-response duties, Private AI reports. Conversation logging, age handling and escalation paths need tighter controls because the law targets both user-facing behaviour and retained data.
Editorial analysis by NHI Mgmt Group, based on content published by Private AI: “California SB 243 Explained: What the Companion Chatbot Law Means for Your Business”.
Key questions
Q: What should teams do first when a companion chatbot may be in scope?
A: Teams should first classify the chatbot’s use case, data inputs and user group, then decide whether a disclosure, consent, age-gating or restricted deployment is required before launch.
Q: Why do companion chatbots create privacy risk even when notices are present?
A: Privacy risk persists because a notice does not stop the chatbot from collecting, inferring, retaining or sharing personal data through prompts, logs, memory features and connected tools.
Q: How should teams classify companion chatbot systems for legal scope?
A: Teams should classify a system by what it does, not by what it is called.
Practitioner guidance
- Classify products by companion behaviour Review whether the system sustains relationships across sessions, adapts to emotional state or presents as a confidant rather than a tool.
- Build visible AI disclosure into the interface Place notice at the point of interaction so a reasonable user is not misled into thinking the chatbot is human.
- Engineer crisis-response routing and evidence trails Create detection, escalation and referral workflows for self-harm content, then preserve the artefacts needed to prove the protocol exists and works.
Bottom line: Companion chatbots are being regulated as a distinct behavioural class, which means scope depends on how the system interacts over time rather than on generic chatbot branding.
Glossary terms: Companion Chatbot, Artificial Intelligence Disclosure, Crisis-Response Protocol, De-Identification
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
SB 243 makes companion chatbot governance a behavioural test, not a branding test. The law is aimed at systems that build ongoing social relationships, so product teams cannot rely on generic chatbot labels or customer-service exceptions. If the bot remembers users and adapts emotionally, the governance burden shifts from simple disclosure to lifecycle control over how the system behaves in context. That is a material change for product, legal and security teams alike.
A question worth separating out:
Q: How do age-based controls work in minor-facing chatbot flows?
A: Age-based controls usually combine age verification or age estimation, policy rules, and step-up restrictions that limit what the chatbot can ask, store or generate for minors. They may block certain topics, disable profiling or memory, require guardian consent, and route higher-risk interactions to a safer experience or human review.
👉 Read our full editorial: California SB 243 puts companion chatbot operators under new duties