AB 412 California Assembly · 2025-2026 Regular Session

Generative artificial intelligence: training data: copyrighted materials.

Summary
Existing federal law, through copyright, provides authors of original works of authorship, as defined, with certain rights and protections. Existing federal law generally gives the owner of the copyright the right to reproduce the work in copies or phonorecords and the right to distribute copies or phonorecords of the work to the public. Existing federal law provides that sound recordings fixed before February 15, 1972, are not subject to copyright but are subject to similar rights and protections under the Classics Protection and Access Act. Existing law requires, before each time that a generative artificial intelligence system or service, as defined, or a substantial modification to a generative artificial intelligence system or service, released on or after January 1, 2022, is made available to Californians for use, regardless of whether the terms of that use include compensation, a developer of the system or service to post on the developer's internet website documentation, as specified, regarding the data used to train the generative artificial intelligence system or service. This bill would require a developer of a generative artificial intelligence model to make available on its internet website a mechanism allowing a rights owner to request information about the developer's use of the rights owner's covered materials that would allow the rights owner to provide the developer with, among other things, registration, preregistration, or index numbers for one or more covered materials. The bill would require a developer to document and retain any requests received from rights owners for a specified time period. The bill would, subject to specified exceptions, require a developer to, within 30 days of receiving that request from the rights owner, assess whether the developer used the rights owner's covered materials to develop the model and provide the rights owner with a list of covered materials, as specified. The bill would provide that each day following the 30-day period that a developer fails to provide a rights owner with that information constitutes a discrete violation. The bill would authorize a rights owner who complies with specified requirements for submitting a request that is not provided with information according to these provisions to bring, subject to a certain notice and cure opportunity, a civil action against the developer for specified relief. The bill would provide that its requirements do not apply to a model that meets certain criteria, including, among other things, being trained exclusively using data the developer makes publicly available at no cost to users. The bill would provide that it does not impose liability on a telecommunications service, information service, or cable service provider, as specified. The bill would define various terms for these purposes.
Bill status passed 3 of 5 stages cleared
Introduction
Feb 2025
Committee Review
Aug 2026
Assembly Passage
May 2025
Senate Passage
Governor
Introduced Feb 4, 2025 Last action Aug 13, 2026
Maddy AI version diff · 10 comparisons

What changed between versions

05/28/26 - Amended Senate 06/11/26 - Amended Senate · 7 edits · Jun 11, 2026
MODERATE
The June 11 Senate amendment to AB 412 makes several substantive changes: it narrows the definition of 'developer' to only those making GenAI models available for 'reasonably foreseeable commercial use' (rather than any use), adds detailed technical standards for how developers must assess whether a rights owner's materials are in their training data, adds a prohibition on requiring rights owners to submit copies of their materials in training-ready form, and removes the January 1, 2026 compliance deadline from the existing law description. These changes both narrow who is covered by the bill and strengthen the assessment obligations for those who are covered.
SCOPE

The definition of 'developer' was narrowed. Previously it covered any entity that makes a GenAI model available to Californians for use. Now it only covers entities making the model available for 'reasonably foreseeable commercial use,' excluding purely noncommercial or personal-use distributions.

REQUIREMENT

New detailed standards were added for how developers must conduct their assessment of whether a rights owner's materials are in their training data. The assessment must be designed to identify exact or substantially similar copies, be robust to minor variations (format changes, cropping, resizing, excerpting), be appropriate to the material format, be applied to all reasonably relevant datasets and records, and be conducted in good faith with a manner reasonably calculated to produce accurate results.

A new provision was added stating that a rights owner shall not be required to transmit a copy of a covered material in a form suitable for training, fine-tuning, or otherwise developing a GenAI model to the developer in order to receive information about the developer's use of covered materials.

A new documentation and retention requirement was added: developers must document and retain any requests received from rights owners for as long as they use the model commercially in California or make it available for reasonably foreseeable commercial use, whichever is longer, plus five years.

TIMELINE

The existing law description previously stated that documentation was required 'on or before January 1, 2026, and before each time thereafter.' The specific January 1, 2026 deadline was removed, leaving only the requirement to document before each time the system is made available.

DEFINITION

The definitions section was renumbered (AI definition moved from subsection (b) to (a), covered material from (c) to (b), rights owner from (d) to (c)), and the 'covered material' definition was cleaned up to remove a stray reference to 'Title 17 of the United States Code.'

TECHNICAL

Section numbering was reorganized throughout: old Section 3118 (request limits) became 3116.5, old Section 3119 (civil action) became 3117, and old Section 3119.5 (exemptions) became 3117.5. Cross-references were updated accordingly.

Floor votes · Assembly May 12, 2025

How they voted

4516
Passed · 17 other
Total votes 78
May 12, 2025
D Democratic59
45 Yea 14
76% Yea
R Republican19
16 Nay 3
84% Nay
Vote distribution
All Yea All Nay Mixed No data
Full legislative history

Actions timeline

Total actions
32
Key actions
9
Committee
14
Amendments
13
Aug 13, 2026
Upper · Passed
In committee: Held under submission.
upper
Aug 3, 2026
Committee
In committee: Referred to APPR. suspense file.
upper
Jun 30, 2026
Upper · Passed
Read second time and amended. Re-referred to Com. on APPR.
upper
Jun 29, 2026
Introduced
From committee: Amend, and do pass as amended and re-refer to Com. on APPR. (Ayes 12. Noes 0.) (June 23).
upper
Jun 11, 2026
Upper · Passed
Read second time and amended. Re-referred to Com. on JUD.
upper
Jun 10, 2026
Introduced
From committee: Amend, and do pass as amended and re-refer to Com. on JUD. (Ayes 6. Noes 2.) (June 8).
upper
May 28, 2026
Introduced
From committee chair, with author's amendments: Amend, and re-refer to committee. Read second time, amended, and re-referred to Com. on P., D.T., & C.P.
upper
May 6, 2026
Committee
Re-referred to Coms. on P., D.T., & C.P., JUD., and APPR.
upper
Apr 27, 2026
Committee
Re-referred to Com. on RLS.
upper
Jul 9, 2025
Upper · Passed
In committee: Set, first hearing. Hearing canceled at the request of author.
upper
May 21, 2025
Committee
Referred to Coms. on JUD. and APPR.
upper
May 12, 2025
Lower · Passed
Read third time. Passed. Ordered to the Senate. (Ayes 45. Noes 16. Page 1517.)
lower
May 7, 2025
Lower · Passed
Read second time and amended. Ordered returned to second reading.
lower
May 6, 2025
Introduced
From committee: Amend, and do pass as amended. (Ayes 9. Noes 1.) (May 6).
lower
Apr 29, 2025
Committee
Re-referred to Com. on JUD.
lower
Apr 28, 2025
Introduced
From committee chair, with author's amendments: Amend, and re-refer to Com. on JUD. Read second time and amended.
lower
Apr 22, 2025
Committee
Re-referred to Com. on JUD.
lower
Apr 21, 2025
Introduced
From committee chair, with author's amendments: Amend, and re-refer to Com. on JUD. Read second time and amended.
lower
Mar 28, 2025
Lower · Passed
In committee: Hearing postponed by committee.
lower
Mar 24, 2025
Committee
Re-referred to Com. on JUD.
lower
Mar 20, 2025
Lower · Passed
Read second time and amended.
lower
Mar 19, 2025
Introduced
From committee: Amend, and do pass as amended and re-refer to Com. on JUD. (Ayes 10. Noes 3.) (March 18).
lower
Mar 11, 2025
Committee
Re-referred to Com. on P. & C.P.
lower
Mar 10, 2025
Introduced
From committee chair, with author's amendments: Amend, and re-refer to Com. on P. & C.P. Read second time and amended.
lower
Feb 26, 2025
Committee
Re-referred to Com. on P. & C.P.
lower
Feb 25, 2025
Introduced
From committee chair, with author's amendments: Amend, and re-refer to Com. on P. & C.P. Read second time and amended.
lower
Feb 18, 2025
Committee
Referred to Coms. on P. & C.P. and JUD.
lower
Feb 5, 2025
Lower · Passed
From printer. May be heard in committee March 7.
lower
1 primary · 1 co-sponsor

Sponsors