рдЖрдЧреЗрдЕрдЧрд▓реА рдЧрд╛рдЗрдб
рдХреИрд▓рд┐рдлрд╝реЛрд░реНрдирд┐рдпрд╛ рдПрдЖрдИ рдкрд╛рд░рджрд░реНрд╢рд┐рддрд╛ рдЕрдзрд┐рдирд┐рдпрдо (рдПрд╕рдмреА 942, рдПрдмреА 853 рджреНрд╡рд╛рд░рд╛ рд╕рдВрд╢реЛрдзрд┐рдд)
рд╕рдорд╛рдЬ
рд╕рдорд╛рдЬ рдЧрд╛рдЗрдб
California AB 2013 requires developers of covered generative AI systems and services to publish training-data documentation.
рдЗрд╕ рдЧрд╛рдЗрдб рдХреЛ рд╕реБрдиреЗрдВрдПрдЖрдИ-рдиреИрд░реЗрдЯреЗрдб ┬╖ ~3 min
The initial posting deadline was January 1, 2026; developers must also post before each later public release or substantial modification in scope. The law creates transparency duties but does not decide whether particular training uses are lawful.
AB 2013, the Generative Artificial Intelligence Training Data Transparency Act, was enacted in 2024. It requires a developer of a covered generative AI system or service made publicly available to Californians for use to post training-data documentation on its website. The initial posting deadline was January 1, 2026. For a covered system released on or after January 1, 2022, documentation must also be posted before each later public release or substantial modification. The documentation includes a high-level summary of training datasets and information about their sources or owners, purpose, approximate number and types of data points, and collection period. It must address whether datasets include copyrighted, trademarked, patented, personal, or aggregate consumer information; whether they were purchased or licensed; how the developer cleaned or processed them; when they were first used; and whether synthetic data generation was used. The definition of developer includes parties that substantially modify a system for public use. AB 2013 requires dataset-level information, not publication of the raw training corpus or source code. A disclosure does not grant copyright permission, decide fair use, or replace privacy obligations. The act includes exceptions, including systems used solely for security and integrity, systems whose sole purpose is aircraft operation in the national airspace, and systems developed for national-security, military, or defense purposes that are made available only to a federal entity. Read each exception against its exact statutory conditions. Maintain a training-data inventory linked to model versions, fine-tuning runs, synthetic-data generation, and release dates. Assign an owner to prepare and update the public documentation, review sensitive claims, and preserve evidence of what was posted for each covered release. Describe uncertainty rather than inventing dataset provenance. Check the enacted text and current California code for definitions, exceptions, and amendments.
A developer lists the sources or owners of training datasets and explains how the data were collected, processed, and used.
A model maker describes whether training included copyrighted, trademarked, or patented material, without claiming that disclosure settles permission questions.
A developer identifies whether personal information was included and whether synthetic data generation was used.
A system developed for national-security, military, or defense purposes is checked against the statutory condition that it be made available only to a federal entity.
AB 2013 is operative on a fixed timeline, and implementation choices may be clarified through amendments, enforcement, or litigation. Data pipelines and model versions continue to change, making stale disclosures a practical risk. Developers should monitor official California sources, preserve the dated disclosure in release records, and reassess coverage after substantial model changes. Training-data transparency should be coordinated with privacy, copyright, and contractual review. Retain dated copies of posted documentation and link them to model release records. Recheck the official code after amendments.
рдореБрдлрд╝реНрдд рдиреНрдпреВрдЬрд╝рд▓реЗрдЯрд░
рд╣рд░ рдХрд╛рд░реНрдпрджрд┐рд╡рд╕ рдХреА рд╕реБрдмрд╣ рддреАрди рд╕рддреНрдпрд╛рдкрд┐рдд рдПрдЖрдИ рдХрд╣рд╛рдирд┐рдпрд╛рдБ, рд╕рд╛рджреЗ рдЕрдВрдЧреНрд░реЗрдЬреА рдореЗрдВ рд▓рд┐рдЦреА рдЧрдИрдВред рд╣рдореЗрд╢рд╛ рдХреЗ рд▓рд┐рдП рдореБрдлрд╝реНрдд, рдХреЛрдИ рд╡рд┐рдЬреНрдЮрд╛рдкрди рдирд╣реАрдВред
рдкреНрд░рддреНрдпреЗрдХ рд╕рдкреНрддрд╛рд╣ рдХреЗ рджрд┐рди рдПрдХ рдИрдореЗрд▓. рдПрдХ рдХреНрд▓рд┐рдХ рдореЗрдВ рд╕рджрд╕реНрдпрддрд╛ рд╕рдорд╛рдкреНрдд рдХрд░реЗрдВ. рд╣рдо рдЖрдкрдХрд╛ рдкрддрд╛ рдХрднреА рдирд╣реАрдВ рдмреЗрдЪрддреЗ рдпрд╛ рд╕рд╛рдЭрд╛ рдирд╣реАрдВ рдХрд░рддреЗред
рд╕реНрд╡рдпрдВ рдХреА рдЬрд╛рдВрдЪ рдХрд░реЛ
рдкреНрд░рддреНрдпреЗрдХ рдЙрддреНрддрд░ рдкрд░ рддреНрд╡рд░рд┐рдд рдкреНрд░рддрд┐рдХреНрд░рд┐рдпрд╛, рдФрд░ рдкрд╛рдареНрдпрдХреНрд░рдо рдкрд╛рд╕ рдХрд░рдиреЗ рдХреЗ рдмрд╛рдж рдПрдХ рд╕рддреНрдпрд╛рдкрди рдпреЛрдЧреНрдп рдЖрдИрдбреА рдХреЗ рд╕рд╛рде рдПрдХ рд╕рд╛рдЭрд╛ рдХрд░рдиреЗ рдпреЛрдЧреНрдп рдкреНрд░рдорд╛рдгрдкрддреНрд░ред
рдирд┐рдГрд╢реБрд▓реНрдХ рдПрдЖрдИ рд╢рд┐рдХреНрд╖рд╛ рдХрд╛ рд╕рдорд░реНрдерди рдХрд░реЗрдВред AI Understanding рдПрдХ 501(c)(3) рдЧреИрд░-рд▓рд╛рднрдХрд╛рд░реА рд╕рдВрд╕реНрдерд╛ рд╣реИ - рдХреЛрдИ рд╡рд┐рдЬреНрдЮрд╛рдкрди рдирд╣реАрдВ, рдХреЛрдИ рдкреЗрд╡реЙрд▓ рдирд╣реАрдВред рджрд╛рди рдХрд░реЗрдВ
California AB 2013 requires developers of covered generative AI systems and services to publish training-data documentation. The initial posting deadline was January 1, 2026; developers must also post before each later public release or substantial modification in scope. The law creates transparency duties but does not decide whether particular training uses are lawful.
The statute defines developer broadly to include designing, coding, producing, or substantially modifying a system or service for public use.
The statute sets January 1, 2026 as the deadline for the required posting.
AB 2013 calls for documentation about datasets used in development, including source, collection, processing, and use information.
The transparency requirement does not resolve copyright permission or fair-use questions.
The statuteтАЩs scope includes systems released or substantially modified on or after January 1, 2022.
рд╕реАрдЦрддреЗ рд░рд╣реЛ
рдЗрд╕ рд╡рд┐рд╖рдп рдХреЗ рд▓рд┐рдП рдЕрдзрд┐рдХ рдорд╛рд░реНрдЧрджрд░реНрд╢рд┐рдХрд╛рдПрдБ рдЪреБрдиреА рдЧрдИрдВ
рдЖрдЧреЗрдЕрдЧрд▓реА рдЧрд╛рдЗрдб
рдХреИрд▓рд┐рдлрд╝реЛрд░реНрдирд┐рдпрд╛ рдПрдЖрдИ рдкрд╛рд░рджрд░реНрд╢рд┐рддрд╛ рдЕрдзрд┐рдирд┐рдпрдо (рдПрд╕рдмреА 942, рдПрдмреА 853 рджреНрд╡рд╛рд░рд╛ рд╕рдВрд╢реЛрдзрд┐рдд)
рд╕рдорд╛рдЬ