AAI Compliance Atlas
FrameworksState lawsIndustriesToolsNews
GuidesMap my obligations →
AAI Compliance Atlas

Structured, continuously verified reference for US AI compliance — federal frameworks, state laws, and the obligations that connect them.

Atlas

  • Frameworks
  • State laws
  • Industries
  • By role
  • Comparisons

Tools

  • Compliance Checker
  • Penalty Calculator
  • Impact Assessment
  • Vendor Questionnaire

Resources

  • Guides
  • News
  • Blog
  • Methodology

Company

  • About
  • Contact
  • Privacy
  • Terms
© 2026 AI Compliance Atlas. Informational only — not legal advice. Consult qualified counsel before making compliance decisions.Verified Jul 28, 2026
  1. Home/
  2. California/
  3. California Generative AI: Training Data Transparency
In effectAB 2013 (2024)California

California Generative AI: Training Data Transparency

Compliance reference — obligations, penalties, applicability, and primary sources.

Last verified July 27, 2026

Effective
January 1, 2026
Max penalty
Not specified
Applies to
developer
Status
In effect

Summary

California AB 2013 — the Generative AI Training Data Transparency Act, also searched as "CA AB 2013" or "AB 2013 California" — is codified at Civil Code Title 15.2, Sections 3110 and 3111. It requires a developer of a generative AI (GenAI) system or service that was released on or after January 1, 2022 and made publicly available to Californians to publish training-data documentation on the developer's public website. AB 2013 regulates developers, not deployers or end users: the disclosure duty falls on the entity that designs, codes, produces, or substantially modifies the GenAI system or service.

AB 2013's training-data documentation duty is one part of California's generative-AI transparency regime; it operates alongside California SB 942, the AI Transparency Act, which governs disclosure of AI-generated image, video, and audio content, and California SB 53 (TFAIA), which imposes safety-framework and critical-incident-reporting duties on frontier-model developers.

Who must comply with AB 2013

The statute reaches a developer that makes a covered GenAI system or service available to people in California, regardless of where the developer is located. A "developer" includes a person that substantially modifies a GenAI system or service, so fine-tuning or materially retraining a third-party model can bring an organization into scope.

Required training-data documentation (Civil Code § 3111)

The developer must post a high-level summary of the datasets used to develop the GenAI system or service. The summary must address each of the following:

  • Sources or owners of the datasets
  • How the datasets further the intended purpose of the AI system or service
  • The number of data points in the datasets (general ranges and estimates are permitted)
  • The types of data points, with a general description for unstructured data
  • Whether the datasets include data protected by copyright, trademark, or patent, or are entirely in the public domain
  • Whether the datasets were purchased or licensed by the developer
  • Whether the datasets include personal information as defined in Civil Code § 1798.140
  • Whether the datasets include aggregate consumer information as defined in Civil Code § 1798.140
  • Whether there was any cleaning, processing, or other modification of the datasets by the developer, including the intended purpose of those alterations
  • The dates the datasets were first used during development
  • The time period over which the data was collected, including a notice if collection is ongoing
  • Whether the GenAI system or service used or continuously uses synthetic data generation (a description of the functional need or operational outcome may be included)

When the documentation must be posted

The first posting deadline is January 1, 2026. Because the requirement is keyed to public availability, a developer that releases a new covered model — or substantially modifies an existing one — after that date must post updated documentation before that release or modification reaches Californians. The obligation is therefore continuous, not a one-time filing.

Exclusions

Civil Code § 3110 excludes a GenAI system or service whose sole purpose is to help ensure security and integrity, the operation of aircraft in the national airspace, or that is developed for national security, military, or defense purposes and is made available only to a federal entity.

Penalties and enforcement

Civil Code §§ 3110–3111 do not state a standalone civil-penalty amount or create an express private right of action. The Atlas therefore records no fixed statutory penalty for AB 2013 rather than importing a dollar amount or enforcement theory from another California law.

Primary sources: California Civil Code Title 15.2, §§ 3110–3111, leginfo.legislature.ca.gov, and the chaptered AB 2013 text — retrieved July 27, 2026.

California Generative AI: Training Data Transparency by compliance topic

Focused breakdowns of each part of the law — obligations, scope, penalties, and disclosures — with the primary source behind every requirement.

  • California Generative AI: Training Data Transparency compliance checklist

    A step-by-step checklist of the obligations to satisfy, each tied to the statutory section behind it.

  • Who must comply with California Generative AI: Training Data Transparency

    The organizations, roles, and thresholds that bring an AI system within scope of the law.

  • California Generative AI: Training Data Transparency penalties and enforcement

    Civil penalty amounts, how violations are counted, and the enforcement path under the statute.

  • California Generative AI: Training Data Transparency disclosure requirements

    The notices and disclosures the law mandates, and which consumers, employees, or downstream parties must receive them.

Key obligations

Specific compliance requirements derived from the primary source. Each item links to the relevant statutory section where applicable.

  • TransparencyRole: developerCal. Civ. Code § 3111

    Publicly post on the developer's website a high-level summary of training datasets used for any generative AI system or service made available to Californians on or after January 1, 2022.

    Deadlineby_2026-01-01

  • DocumentationRole: developerCal. Civ. Code § 3111

    Address each statutory element in the dataset summary — sources or owners, how the data furthers the system's purpose, number and types of data points, copyright/trademark/patent or public-domain status, purchased-or-licensed status, presence of personal information or aggregate consumer information, any cleaning or modification, first-use dates, collection time period, and any use of synthetic data generation.

    Deadlineby_2026-01-01

  • TransparencyRole: developerCal. Civ. Code § 3110

    Refresh and re-post the public training-data summary before each subsequent public release or substantial modification of a covered generative AI system, so the disclosure stays current rather than ending at the initial January 1, 2026 deadline.

    Deadlinebefore_each_release

Related comparisons

Use the side-by-side comparisons to see how this law interacts with adjacent US AI laws and governance frameworks.

  • California SB 942 vs AB 2013

    Compare source-backed California AI law records and compliance categories.

Build a compliance program around these obligations

A single law is one input to a broader program. These guides show how to assign accountability, map every obligation to a control, and split developer-versus-deployer duties across the systems a team operates.

  • AI governance: building an AI compliance program

    The operating model — owners, committee, decision rights, lifecycle gates — that turns a law into an accountable, auditable program anchored to the NIST AI RMF GOVERN function.

  • AI compliance framework: the regulatory control map

    How to map each AI system to the laws it triggers, the controls that satisfy them, and the evidence that proves the controls operate.

  • Deployer vs developer obligations

    Which duties attach to building an AI system versus putting one into use — the split most state AI laws turn on.

Operationalize California Generative AI: Training Data Transparency compliance with OneTrust

partner link

Map obligations to controls, run impact assessments, and maintain audit-ready evidence in a single platform used by hundreds of regulated enterprises.

See OneTrust AI Governance →

Frequently asked questions

When does California Generative AI: Training Data Transparency take effect?

California Generative AI: Training Data Transparency has been effective since January 1, 2026.

What is the maximum penalty under California Generative AI: Training Data Transparency?

No fixed cap is specified; remedies follow the underlying enforcement framework.

Who must comply with California Generative AI: Training Data Transparency?

California Generative AI: Training Data Transparency applies to developer of AI systems within its jurisdictional scope.

Sources

Every fact above is sourced from the official primary source. Independent verification recommended before acting on the information.

  • Officialleginfo.legislature.ca.gov — Cal. Civ. Code §§ 3110–3111
  • leginfo.legislature.ca.gov
  • leginfo.legislature.ca.gov

Last reviewed July 27, 2026. Reviewed by the AI Compliance Atlas editorial process against primary sources. Source selection, retrieval dates, and update rules are documented in the Atlas methodology.

Legal disclaimer

This content is informational only and does not constitute legal advice. Laws change frequently and vary by jurisdiction. Consult qualified legal counsel before making compliance decisions. Information accuracy not guaranteed as of any specific date.

We may receive referral commissions from recommended compliance tools. Recommendations are based on product fit and not on commission size. Links marked “partner link” include a tracked redirect.