English

Places to contact

California SB 53 (Transparency in Frontier Artificial Intelligence Act) — whistleblower protections and public incident reporting

Type
Public reporting channel
Place
California, United States — California
Last checked
2026-09-22
Next check due
2027-03-21

Ways to reach them

  • Submission page · Whistleblower channel
    Open contact route · 2026-09-22

    Who may use it: public

    Evidence that this route accepts contact · 2026-09-22

    Two distinct things. (1) Whistleblower protection: employees and contractors of frontier developers are protected against retaliation for reporting activity connected to catastrophic risks — defined around foreseeable risks of a frontier model causing death or serious injury to 50+ people, enabling weapons creation, engaging in criminal conduct without meaningful human intervention, or evading developer control. Employers must give notice of these rights and maintain anonymous internal reporting channels. (2) Developer reporting: frontier developers must report critical safety incidents to OES within 15 days of discovery, or 24 hours where there is imminent danger of death or serious injury.

    Employees: use the employer's mandated anonymous internal channel, and take legal advice before external disclosure. Critically for this playbook: SB 53 requires OES to establish a mechanism for the public to report critical safety incidents — meaning a member of the public, not just an insider, has a statutory route to a state emergency agency. Verify the current status and URL of that OES mechanism directly with OES before relying on it; implementation detail was not published in the sources reviewed.

  • Homepage · Homepage
    Verification expired

    Evidence that this route accepts contact

What it does

Two distinct things. (1) Whistleblower protection: employees and contractors of frontier developers are protected against retaliation for reporting activity connected to catastrophic risks — defined around foreseeable risks of a frontier model causing death or serious injury to 50+ people, enabling weapons creation, engaging in criminal conduct without meaningful human intervention, or evading developer control. Employers must give notice of these rights and maintain anonymous internal reporting channels. (2) Developer reporting: frontier developers must report critical safety incidents to OES within 15 days of discovery, or 24 hours where there is imminent danger of death or serious injury.

Honest assessment

The most concrete AI-specific whistleblower protection actually in force in the United States, and materially more than the federal position. Two honest caveats: the catastrophic-risk threshold is high and excludes most real concerns, and the public reporting mechanism's practical operation is unproven. It applies only to large frontier developers, though that captures most of the companies that matter.

How to file

Employees: use the employer's mandated anonymous internal channel, and take legal advice before external disclosure. Critically for this playbook: SB 53 requires OES to establish a mechanism for the public to report critical safety incidents — meaning a member of the public, not just an insider, has a statutory route to a state emergency agency. Verify the current status and URL of that OES mechanism directly with OES before relying on it; implementation detail was not published in the sources reviewed.

Format

Internal anonymous channel for employees; OES mechanism format not yet documented publicly.

Timing

In force. Developer reporting deadlines are 15 days / 24 hours as above.

What happens after

Incidents go to OES; whistleblower retaliation claims are pursued under the statute.

What it accepts

Two distinct things. (1) Whistleblower protection: employees and contractors of frontier developers are protected against retaliation for reporting activity connected to catastrophic risks — defined around foreseeable risks of a frontier model causing death or serious injury to 50+ people, enabling weapons creation, engaging in criminal conduct without meaningful human intervention, or evading developer control. Employers must give notice of these rights and maintain anonymous internal reporting channels. (2) Developer reporting: frontier developers must report critical safety incidents to OES within 15 days of discovery, or 24 hours where there is imminent danger of death or serious injury.

What it does not accept

Concerns below the catastrophic-risk threshold are outside the protected category. Ordinary product-safety, bias or misuse concerns are not covered by the whistleblower provisions.

Operated by

State of California; critical safety incident reporting to the California Office of Emergency Services (OES)

Sources

Something wrong here?