Artificial Intelligence Policy Tracker

Transparency and disclosure: AI obligations

Practical requirements extracted from policy instruments, with the source article, the actors they bind, evidence examples and original framework mappings. Legal requirements are marked; everything else is voluntary guidance.

Results

31 of 129 obligations match · page 2 of 2 · Download these as CSV

Legal requirement Transparency and disclosure Washington State (United States)

Publish the self-harm protocol and the number of crisis referral notifications issued in the preceding calendar year

Washington AI companion chatbot law (ESHB 2225) · ESHB 2225 (Chapter 168, Laws of 2026), sec. 5(3)

The operator must publicly disclose the details of its section 5 protocols on its website or websites and within any mobile or web application through which the AI companion is offered. The disclosure covers the safeguards used to detect and respond to expressions of suicidal ideation or self-harm, and the number of crisis referral notifications issued to users in the preceding calendar year. The act does not set a date by which the disclosure must be updated.

Pending review (a factual check against the official source, not a legal review) Applies from 1 Jan 2027
Legal requirement Transparency and disclosure New York (United States)

Tell users at the start of an AI companion interaction, and at least every three hours, that they are not communicating with a human

New York AI companion safeguards · N.Y. Gen. Bus. Law § 1702

An operator must give the user a clear and conspicuous notification, spoken or written, that the user is not communicating with a human. It is given at the beginning of any AI companion interaction, which the text says need not happen more than once a day, and at least every three hours during a continuing interaction. The Attorney General may seek an injunction and civil penalties of up to 15,000 dollars per day for a violation (section 1703).

Pending review (a factual check against the official source, not a legal review)
Legal requirement Transparency and disclosure Washington State (United States)

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) · ESHB 2225 (Chapter 168, Laws of 2026), sec. 3

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.

Pending review (a factual check against the official source, not a legal review) Applies from 1 Jan 2027
Legal requirement Transparency and disclosure Washington State (United States)

Where the user is known to be a minor or the chatbot is directed to minors, repeat the not-human notice at least every hour

Washington AI companion chatbot law (ESHB 2225) · ESHB 2225 (Chapter 168, Laws of 2026), sec. 4(1)(a), (2) and (3)

If the operator knows the user is a minor (under 18), or the AI companion chatbot is directed to minors, the operator must issue a clear and conspicuous notification that the chatbot is artificially generated and not human. It is given at the beginning of the interaction and at least every hour during continuous interaction, rather than the three-hour interval that applies to other users. The operator must take reasonable measures to stop the chatbot from claiming to be human, including when asked, and from producing output that conflicts with the notification.

Pending review (a factual check against the official source, not a legal review) Applies from 1 Jan 2027
Voluntary guidance Transparency and disclosure United Kingdom

Provide appropriate transparency and explainability

UK AI regulation framework · Principle 2, Part 3

Organisations should communicate when and how AI is used and provide explanations proportionate to the risk, so that people can understand decisions affecting them. For personal data, UK GDPR transparency and automated decision-making rights make this binding in practice.

Pending review (a factual check against the official source, not a legal review)
Voluntary guidance Transparency and disclosure Singapore

Report incidents and mark AI-generated content (generative AI framework)

Singapore Model AI Governance Framework · Generative AI framework, dimensions on incident reporting and content provenance

The generative-AI framework recommends incident-reporting channels and processes for AI harms, and content provenance measures such as digital watermarking and cryptographic provenance so that users can identify AI-generated content.

Pending review (a factual check against the official source, not a legal review)

Frequently asked questions

What is an obligation on this site?

A single practical requirement pulled out of an instrument and stated on its own: keep a risk management system, log incidents, document training data, provide human oversight, and so on. Each one cites the article or section it comes from so you can check it against the source.

Does a voluntary obligation have legal force?

No, and every obligation is labelled either a legal requirement or voluntary guidance. Voluntary items still matter in practice, because procurement questionnaires and auditors ask about them, but only the binding ones carry legal consequence.

How do I find the obligations that apply to my organisation?

Filter by jurisdiction, category, actor, sector or use case. The applicability check asks a short set of questions and returns the duties that may reach you. It is an educational screen, not a legal determination, and it says so.

Why do some instruments have no obligations listed?

Because nobody has broken them out yet. Most instruments are recorded at summary level first; obligations are added jurisdiction by jurisdiction. The coverage and open-gaps pages publish exactly what is missing rather than hiding it.