State AI Tracker · California

California AI law: frontier model safety

A bounded reference to selected enacted measures and their limits, updated October 5, 2026. Provision verification dates appear separately from this analysis date.

Source status reviewed
October 5, 2026
Published analysis updated
October 5, 2026
Scope
Selected measures; statewide review incomplete

Selected laws in force

In force since 2026-01-01 · provision verified 2026-10-05

Transparency in Frontier Artificial Intelligence Act

SB 53 requires covered large frontier developers to publish safety frameworks and addresses critical safety incidents, whistleblower protection, and state oversight. Coverage depends on statutory definitions; the duties do not apply identically to every developer or AI product.

SB 53 — official bill status ↗

Effective dates and implementation milestones

  1. 2026-01-01: SB 53 took effect. Later implementation deadlines are separate from this date. SB 53 — official bill status ↗

Policy vectors

Developer transparency
Public safety frameworks make covered developers explain their risk controls.
Incident accountability
Critical incident reporting and whistleblower protections support oversight.

Analysis · October 5, 2026

California connects developer transparency to institutional oversight. The framework is a model-level intervention, so an application deployer must first establish whether it falls within the covered developer class. This page does not treat a public framework as certification that a model is safe.

Coverage still under review

Review AB 853 phased transparency duties, AB 2013 training data disclosures, chatbot and police-report laws, 2026 amendments, and implementation. Selected current and concluded bills, agency rules, enforcement, and litigation have not been comprehensively screened. An omitted measure is not a finding that no relevant law exists.

Scope and method

This update expands the existing selected-law baseline using official legislative texts, codification, bill histories, and agency material. It distinguishes the act’s effective date from later duties and does not infer implementation from the passage of a deadline.

The analysis date is not a new verification date for every provision. Earlier dates remain where final text or date evidence was inaccessible. Only the separately identified in-force records enter the national export; proposed, future, and uncertain measures are excluded.

See the Illinois reference methodology for selection principles and the distinction between legislation and legal advice, or send a correction.