Artificial Intelligence Policy Tracker

Tell users that an AI companion chatbot is artificially generated and not human, at the start and at least every three hours

Download: JSON · MarkdownUnder Washington AI companion chatbot law (ESHB 2225), ESHB 2225 (Chapter 168, Laws of 2026), sec. 3

Pending review · linked to the official source, waiting for a reviewer to confirm it (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
Record updated on 12 Nov 2026 · Summary · official source last checked
On this page 8 sections

In brief

Tell users that an AI companion chatbot is artificially generated and not human, at the start and at least every three hours is a legal requirement under the Washington AI companion chatbot law (ESHB 2225) in Washington State (United States) (ESHB 2225 (Chapter 168, Laws of 2026), sec. 3). It applies from 1 January 2027.

Nature
Legal requirement
Source reference
ESHB 2225 (Chapter 168, Laws of 2026), sec. 3
Applies from
1 January 2027
Who it binds
Provider / developer, Deployer / user organisation
Evidence examples
2
Controls that meet it
2
Official source
Open official text
Verification
Pending review · source-linked

What does it require?

An operator (anyone who makes an AI companion chatbot available to users in Washington, or controls access to it) must give a clear and conspicuous disclosure that the chatbot is artificially generated and not human. The notice is given at the beginning of the interaction and again at least every three hours while the interaction continues. The operator must also take reasonable measures to stop the chatbot from claiming to be human, including when the user asks, and from producing any other output that contradicts the disclosure.

Practical action

Show a prominent "you are talking to an AI, not a person" notice when each interaction starts and on a timer of three hours or less, and instruct and test the model so it never says or implies it is human, especially when asked directly.

Who does it apply to?

Applies from:

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesProcessProduct owner · at launch and on material change
    AI interaction and use disclosure notices

    Serves 23 recorded duties · evidence: AI interaction or use notice, Notice catalogue, Notice wording approval

    The notice at the start and at least every three hours that the user is talking to an AI.

  • supportsTechnical measureAI security or safety lead · at launch and on material change
    Adversarial and red-team testing for generative AI

    Serves 12 recorded duties · evidence: Red-team exercise report, Red-team rules of engagement and scenario library, Adversarial findings tracker

    Adversarial testing that the chatbot cannot be led to claim it is human or contradict the notice.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

All 7 templates that cover it →

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Screenshots or recordings of the opening notice and the repeated notice, with the timer settingdocument
Test results showing the chatbot does not claim to be human when askeddocument

Frequently asked questions

Is this a legal requirement?

Yes. It is a legal requirement under Washington AI companion chatbot law (ESHB 2225) (ESHB 2225 (Chapter 168, Laws of 2026), sec. 3).

When does this obligation apply?

It applies from 1 January 2027.

What evidence shows compliance?

A reviewer would expect: Screenshots or recordings of the opening notice and the repeated notice, with the timer setting; Test results showing the chatbot does not claim to be human when asked.

Which controls satisfy this obligation?

Adversarial and red-team testing for generative AI; AI interaction and use disclosure notices.

What should an organisation do in practice?

Show a prominent "you are talking to an AI, not a person" notice when each interaction starts and on a timer of three hours or less, and instruct and test the model so it never says or implies it is human, especially when asked directly.

Cite this record

AIPolicyTracker (2026). “Tell users that an AI companion chatbot is artificially generated and not human, at the start and at least every three hours (Washington AI companion chatbot law (ESHB 2225))” [AIPT-OBL-0123, not yet verified]. https://aipolicytracker.org/id/AIPT-OBL-0123 (accessed 12 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0123: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Washington State Legislature: HB 2225 (2025-26) bill summary, Washington State Legislature, https://lawfilesext.leg.wa.gov/biennium/2025-26/Pdf/Bills/Session%20Laws/House/2225-S.SL.pdf.

BibTeX
@misc{aipolicytracker2026_tellusersthatanaicompani,
  author       = {{AIPolicyTracker}},
  title        = {{Tell users that an AI companion chatbot is artificially generated and not human, at the start and at least every three hours (Washington AI companion chatbot law (ESHB 2225))}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/us-washington-eshb-2225-ai-disclosure}},
  url          = {https://aipolicytracker.org/obligations/us-washington-eshb-2225-ai-disclosure},
  urldate      = {2026-11-12},
  note         = {Data licensed CC BY 4.0. Accessed 12 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.