All Roll Calls
Yes: 253 • No: 0
CaliforniaAB 10432025-2026 Regular SessionHouseWALLET
Privacy.
Sponsored By: Buffy Wicks (Democratic)
Signed by Governor
Your PRIA Score
Score Hidden
Personalized for You
How does this bill affect your finances?
Sign up for a PRIA Policy Scan to see your personalized alignment score for this bill and every other piece of legislation we track. We analyze your financial profile against policy provisions to show you exactly what matters to your wallet.
Bill Overview
Analyzed Economic Effects
5 provisions identified: 3 benefits, 1 costs, 1 mixed.
2027 deadlines for older devices and apps
Starting January 1, 2027, devices set up before that date must add an interface by July 1, 2027 to capture the user’s birth date or age. This lets the system send age-bracket signals to apps. For apps last updated on or after January 1, 2026 and downloaded before January 1, 2027, developers must request an age signal by July 1, 2027 if they have never asked for that user.
Platforms can't favor their own apps
Platforms must apply the same age-signal rules to their own apps as to third-party apps. They cannot use data collected to follow this law to compete with developers or to preference their own services. This nondiscrimination rule starts January 1, 2027.
Standard age checks for apps and devices
Beginning January 1, 2027, device operating systems must ask for a user’s birth date or age at account setup. They must give apps a real-time age bracket on request: under 13; 13–15; 16–17; or 18 and older. App developers must request the signal when the app is downloaded and opened. The signal counts as actual age knowledge across platforms and is the main age indicator unless the developer has clear, convincing proof otherwise. Platforms and developers may send or use only the minimum data needed and cannot share it for other purposes.
What this age-check law excludes
This law does not cover broadband internet access service, telecommunications service, or the delivery or use of a physical product. Providers, app stores, and developers are not liable when harm comes from someone who is not the user the age signal covers. These limits take effect January 1, 2027.
Attorney General can fine violators
Only the California Attorney General can sue for violations under this law. Companies face up to $2,500 per affected child for negligent violations and up to $7,500 per affected child for intentional violations. Courts can also issue injunctions. Providers that made a good faith effort to comply are not liable for an erroneous signal or for what a developer does with it. These enforcement rules start January 1, 2027.
Sponsors & Cosponsors
Sponsor
Buffy Wicks
Democratic • House
Cosponsors
Juan Alanis
Republican • House
Rebecca Bauer-Kahan
Democratic • House
Diane Dixon
Republican • House
John Harabedian
Democratic • House
Josh Hoover
Republican • House
Ash Kalra
Democratic • House
Josh Lowenthal
Democratic • House
Catherine Stefani
Democratic • House
Thomas Umberg
Democratic • Senate
Akilah Weber Pierson
Democratic • Senate
Roll Call Votes
House vote • 9/13/2025
Item 1000 — Assembly AFLOOR
Yes: 77 • No: 0
Senate vote • 9/12/2025
Item 58 — Senate SFLOOR
Yes: 38 • No: 0
legislature vote • 8/29/2025
Vote in CS61
Yes: 7 • No: 0
legislature vote • 8/18/2025
Vote in CS61
Yes: 7 • No: 0
legislature vote • 7/15/2025
Vote in CS53
Yes: 12 • No: 0
House vote • 6/2/2025
Item 393 — Assembly AFLOOR
Yes: 76 • No: 0
legislature vote • 5/23/2025
Vote in CX25
Yes: 11 • No: 0
legislature vote • 4/29/2025
Vote in CX13
Yes: 12 • No: 0
legislature vote • 4/22/2025
Vote in CX32
Yes: 13 • No: 0
Actions Timeline
Chaptered by Secretary of State - Chapter 675, Statutes of 2025.
10/13/2025SenateApproved by the Governor.
10/13/2025legislatureEnrolled and presented to the Governor at 3 p.m.
9/24/2025legislatureSenate amendments concurred in. To Engrossing and Enrolling. (Ayes 77. Noes 0. Page 3480.).
9/13/2025HouseAssembly Rule 63 suspended. (Page 3477.)
9/13/2025HouseJoint Rules 61(a)(14) and 51(a)(4) suspended. (Ayes 59. Noes 20. Page 3413.)
9/13/2025HouseIn Assembly. Concurrence in Senate amendments pending.
9/13/2025HouseRead third time. Passed. Ordered to the Assembly. (Ayes 38. Noes 0. Page 2996.).
9/12/2025SenateRead second time. Ordered to third reading.
9/8/2025SenateRead third time and amended. Ordered to second reading.
9/5/2025SenateRead second time. Ordered to third reading.
8/29/2025SenateFrom committee: Do pass. (Ayes 7. Noes 0.) (August 29).
8/29/2025SenateIn committee: Referred to suspense file.
8/18/2025SenateRead second time and amended. Re-referred to Com. on APPR.
7/23/2025SenateFrom committee: Amend, and do pass as amended and re-refer to Com. on APPR. (Ayes 12. Noes 0.) (July 15).
7/23/2025SenateReferred to Com. on JUD.
6/11/2025SenateIn Senate. Read first time. To Com. on RLS. for assignment.
6/3/2025SenateRead third time. Passed. Ordered to the Senate. (Ayes 76. Noes 0. Page 1914.)
6/2/2025HouseRead second time. Ordered to third reading.
5/27/2025HouseRead second time and amended. Ordered returned to second reading.
5/23/2025HouseFrom committee: Amend, and do pass as amended. (Ayes 11. Noes 0.) (May 23).
5/23/2025HouseAssembly Rule 63 suspended. (Ayes 51. Noes 16. Page 1644.)
5/23/2025HouseIn committee: Set, first hearing. Referred to APPR. suspense file.
5/7/2025HouseFrom committee: Do pass and re-refer to Com. on APPR. (Ayes 12. Noes 0.) (April 29). Re-referred to Com. on APPR.
4/30/2025HouseCoauthors revised.
4/30/2025House
Bill Text
Chaptered
10/13/2025
Enrolled
9/16/2025
Amended Senate
9/5/2025
Amended Senate
7/23/2025
Amended Assembly
5/23/2025
Amended Assembly
4/24/2025
Amended Assembly
3/28/2025
Introduced
2/20/2025