Washington Governor Bob Ferguson signed House Bill 2225 on March 24, 2026, making Washington believed to be the first U.S. state to enact legislation specifically targeting AI companion chatbots. The law’s effective date is January 1, 2027. That’s a compliance window, not breathing room.
The law applies to AI chatbots that use natural language interfaces, provide adaptive human-like responses, and sustain ongoing relationships across multiple interactions. Think AI companions, social AI platforms, and emotionally-oriented personal assistant products. The law explicitly excludes business-oriented bots, gaming bots, general virtual assistants, consumer electronics interfaces, and narrowly tailored educational tools, so the scope is deliberate and specific.
What operators must do
The core obligation is disclosure. Operators must clearly and conspicuously disclose at the start of every interaction that the chatbot is not human. That’s not a terms-of-service footnote, it has to appear upfront, before the conversation begins.
It doesn’t stop there. The law requires periodic reminder disclosures throughout extended interactions: every three hours for adult users, and every one hour for users under 18. The minor-specific interval is tighter, and the law includes additional enhanced protections for users under 18 beyond disclosure frequency, the full scope of those protections is documented in Hunton Andrews Kurth’s analysis of the Act.
Private right of action
This is what makes HB 2225 consequential in a way most state AI bills aren’t. Per legal analysis from Hunton Andrews Kurth LLP, the Act reportedly includes a private right of action, meaning individual users can bring civil claims for violations, not just wait for a regulator to act. That converts a compliance obligation into active litigation exposure. Builders should treat this as a product liability issue, not just a regulatory checkbox.
The private right of action claim is corroborated across multiple legal sources but has not been confirmed against the full statutory text in this analysis. Treat it as reported, not definitively confirmed, but treat it seriously.
Why this matters beyond Washington
State-level AI legislation is accelerating. Washington’s law is among the first to specifically define the category of AI companion chatbots as regulated systems with enforceable disclosure requirements and civil enforcement mechanisms. The definitional precision here, the included and excluded categories, gives other state legislatures a template. If this model spreads, companion AI developers face a patchwork of state-level disclosure obligations with varying reminder intervals, age thresholds, and enforcement mechanisms.
The January 1, 2027 deadline is real. Product teams building companion, social, or emotionally-oriented AI systems that serve Washington users need to audit their disclosure architecture now. Building compliant disclosure flows into existing products takes more calendar time than most legal teams expect.
What to watch
Track whether other states, California, Illinois, and Texas are the most active AI legislative environments, introduce similar companion chatbot legislation citing HB 2225 as precedent. Watch for enforcement activity in Washington after January 1, 2027, which will clarify how aggressively the private right of action provision is used. And watch whether the Act’s definitional boundaries (specifically the “educational tools” exclusion) prompt legal challenges from platforms that straddle companion and educational use cases.
TJS synthesis
HB 2225’s significance isn’t the disclosure requirement itself, periodic AI identity reminders are a modest ask. The signal is structural: Washington has created an enforceable, consumer-actionable AI obligation for a specific product category, with precision exclusions that reflect real-world product distinctions. That legislative architecture, more than any single requirement, is what compliance teams and product counsel should study. The question isn’t whether your product is covered in Washington. It’s whether this is the first version of a requirement that will follow your users everywhere.