Artificial Intelligence Policy Tracker

AI policies in California (United States)

Search and filter source-backed AI laws, regulations, standards, guidance and consultations. Each record shows its status, key dates, verification state and official source.

Results

2 of 244 instruments match

California (United States) Act / statute Adopted Binding

California chatbot child-safety law (SB 1119)

California SB 1119: Companion chatbots: children's safety (Chapter 190, Statutes of 2026)

Operators must carry out a documented, child-focused risk assessment before releasing a new or substantially modified companion chatbot, from 1 July 2027, and commission child-safety audits by 1 January 2029 or before first public release if later. The Attorney General must set up a public incident-reporting mechanism by 1 January 2028.

Applies from 1 Jul 2027 Pending review (a factual check against the official source, not a legal review) Official source
California (United States) Act / statute Adopted Binding

California companion chatbot law (SB 243)

California SB 243: Companion chatbots (Chapter 677, Statutes of 2025)

Operators of companion chatbots must disclose that the chatbot is AI and maintain a protocol for responding to suicidal ideation and self-harm that refers users to crisis services. Users known to be minors get break reminders and protection from sexual content. Annual reports to the Office of Suicide Prevention begin 1 July 2027, and a person injured by a violation can bring a civil action.

Adopted 13 Oct 2025 Pending review (a factual check against the official source, not a legal review) Official source

Frequently asked questions

What counts as an AI policy instrument here?

Anything a government or standards body has actually issued: acts, regulations, executive orders, rules, national strategies, frameworks, guidance, codes of practice, voluntary standards and open consultations. Each record states which of those it is, whether it binds anyone, and links the official source it was read from.

Are these records legally verified?

A record is marked verified only after a named reviewer has opened its official source and confirmed each field. Anything that has not been through that carries "pending review" on the record itself, and the data-health document reports the current totals. Nothing here is legal advice.

How current is the information?

Every record carries the date its source document was published and the date it was last checked. A record not re-checked within the freshness window set by the verification policy is flagged as stale rather than quietly presented as current.

Can I reuse this data?

Yes. The records are published under CC BY 4.0 with attribution, and are available as CSV, newline-delimited JSON and a read-only REST API that needs no key. Cite the record URL, the date accessed and the official source alongside it.