Open the Console See the evidence spine

Does California require AI training-data disclosure?

Yes — California's AB 2013 requires developers of generative AI systems to post, on their website, documentation about the data used to train the system (including sources and characteristics), with compliance required by 2026-01-01. It is a transparency…

register 09 · Compliance pins· California AI Transparency
01 ·

Answer.

Named jurisdictional law · California AI Transparency.

Yes — California's AB 2013 requires developers of generative AI systems to post, on their website, documentation about the data used to train the system (including sources and characteristics), with compliance required by 2026-01-01. It is a transparency mandate about training data, not a ban. Planisphere measures model behaviour rather than authoring your training-data disclosure; it does not provide legal advice, and you should confirm the current statutory text.

Cite-anchor: California AI transparency stack (AB 2013, SB 53/TFAIA, SB 942, CCPA ADMT regs) · Cal. AB 2013 (2024); SB 53 (2025); SB 942 (delayed by AB 853 to 2026-08-02); CPPA ADMT regs (final Sep. 2025)

02 ·

The mark behind the answer.

California AI Transparency is enacted (or near-enacted) law in a specific jurisdiction, with a specific obligation and a…

SB 942 + AB 2013 + SB 53 + CCPA ADMT — the CA frontier/transparency stack.

→ Full reference for California AI Transparency

03 ·

More on California AI Transparency.

Other questions this mark answers.
When does California SB 942 take effect? What is California SB 53 frontier AI law? Do CCPA ADMT rules require a risk assessment?

Try California AI Transparency with a free test key.

Start with the free sandbox. Planisphere measures model behaviour and emits a reproducible, sha-pinned record — it does not certify, file, or give legal advice.

Open the Console See the evidence spine California AI Transparency reference
API ·

When California AI Transparency asks for proof, hand over records — not assurances.

record the duty · seal the receipt · verify offline

Planisphere records each duty event — an output marked, a disclosure shown, a review made — and seals it into a receipt that verifies offline against our published keys. You send hashes, never content. A record is evidence a third party can check; it is not a certification and not a legal determination.

On August 2, 2026, EU AI Act Article 50 and California SB 942 both become enforceable — disclosure and provenance duties on two continents, the same day. Article 50(2) marking carries a transitional: systems already on the market get until December 2, 2026. Audit-grade logging follows: Article 12 binds December 2, 2027 (Annex III) and August 2, 2028 (embedded AI).

Open the Console Read the Docs Read the capability briefing

See how a record is checked · See the ca-sb942 Toolkit →