California Digital Age Assurance Act (AB 1043)
Requires operating system providers to collect a user age bracket at device setup and expose it to app developers through an API; effective 1 January 2027 with full compliance by 1 July 2027.
| Jurisdiction | California |
|---|---|
| Category | Privacy & Data Protection |
| Status | Upcoming |
| Effective date | |
| Latest development |
Analysis
The California Digital Age Assurance Act (AB 1043) is a California statute that requires operating system providers to collect a user’s age or age bracket at device account setup and expose a non-identifying age-bracket signal to app and online service developers, with obligations starting January 1, 2027 and full deployment requirements by July 1, 2027.California AB 1043 bill text (LegiScan) California Digital Age Assurance Act – overview Operating-System Age Verification Requirements – analysis California Age Verification Law tracker
Below is a structured, regulation-focused analysis.
Key Requirements
- Scope and covered entities
- AB 1043 creates a new title in the California Civil Code (Title 1.81.9, starting at Section 1798.500) governing “age verification signals: software applications and online services,” targeting operating system providers, app stores, and application/online service developers.California AB 1043 bill text (LegiScan) California Digital Age Assurance Act – overview
- The law is framed as a consumer protection measure to establish an age verification system for users of mobile devices and computers.California AB 1043 bill text (LegiScan) AB 1856 Assembly analysis referencing AB 1043
- Age collection at device/account setup
- Operating-system providers must, at account setup, present an accessible interface that asks the account holder to indicate the device user’s birth date, age, or both.Operating-System Age Verification Requirements – analysis California Digital Age Assurance Act – overview
- The law requires the system to derive a non-identifying “age bracket data” value from the provided information, rather than exposing exact birth date downstream.Operating-System Age Verification Requirements – analysis California Digital Age Assurance Act – overview
- Defined age brackets
- The statute establishes four age brackets for signaling to applications:
- Under 13
- 13 to under 16 (often referenced as 13–15)
- 16 to under 18 (often referenced as 16–17)
- 18 or olderCalifornia Digital Age Assurance Act – overview AB 1856 Assembly analysis referencing AB 1043 AllAboutCookies explainer on AB 1043
- Age signal transmission to apps and online services
- Operating systems and app stores must transmit the age-bracket signal to application developers and online services through an API when apps are downloaded and when they are launched.Operating-System Age Verification Requirements – analysis California Digital Age Assurance Act – overview
- Application developers are required to request and use that signal as a primary age indicator for compliance with other youth-protection laws (e.g., content restrictions, feature limits).California Children’s Privacy Laws summary – AB 1043 Operating-System Age Verification Requirements – analysis
- Non-identifying and privacy-oriented design
- The law defines “age bracket data” as nonpersonally identifiable information, explicitly intended to reduce direct exposure of birth date while still enabling age-based controls.Operating-System Age Verification Requirements – analysis California Children’s Privacy Laws summary – AB 1043
- The signal is designed to be real-time and non-identifying, transmitted as a categorical value rather than a full profile.Operating-System Age Verification Requirements – analysis California Digital Age Assurance Act – overview
- Effective dates and phased compliance
- Gov. Gavin Newsom signed AB 1043 into law on October 13, 2025.California Introduces New Age Verification Requirements – Hunton AllAboutCookies explainer on AB 1043
- The law’s core obligations for operating system providers and app stores are operative on January 1, 2027.California Age Verification Law tracker California Introduces New Age Verification Requirements – Hunton
- Existing devices must have the age-bracket interface and signaling added by July 1, 2027, creating a full-compliance deadline for deployed systems.California Age Verification Law tracker Operating-System Age Verification Requirements – analysis
- Enforcement and penalties
- AB 1043 provides for Attorney General–enforced civil penalties, commonly referenced as up to \$2,500 per affected child for negligent violations and \$7,500 for intentional violations, aligning with California’s pattern in child privacy statutes.California Children’s Privacy Laws summary – AB 1043 California Digital Age Assurance Act – overview
- Enforcement is expected to integrate with broader consumer protection and privacy enforcement mechanisms under the California Department of Justice and related agencies.California AB 1043 bill text (LegiScan) California OAG – Social Media Addiction Act page (context for child-protection enforcement)
Compliance Challenges
- Technical integration across diverse operating systems and app ecosystems
- Implementing a universal age-bracket API signal across large OS platforms (e.g., mobile, desktop, and embedded systems) is complex due to differing architecture, account models, and app store ecosystems.Operating-System Age Verification Requirements – analysis Techtimes article on AB 1043 and AB 1856 technical scope
- Analyses show concerns about coverage gaps for certain platforms (e.g., Linux distributions, non-traditional OS environments) and the need for exceptions or tailored implementations.Techtimes article on AB 1043 and AB 1856 technical scope AB 1856 Assembly analysis referencing AB 1043
- User experience and parental controls
- The Act relies on parents or account holders to configure age settings correctly, which can be undermined by misconfiguration, shared devices, or lack of understanding.AB 1856 Assembly analysis referencing AB 1043 AllAboutCookies explainer on AB 1043
- Privacy regulators and guidance documents on age assurance emphasize the difficulty of balancing frictionless user experience with robust age assurance, which is directly relevant to AB 1043 implementations.Assessing whether and how to use age assurance – regulator guidance California OAG SB 976 press release – parental consent and UX context
- Privacy, civil liberties, and risk of over-blocking
- Civil society organizations warn that mandatory age signaling at the OS level may expand age-gating and lead to over-blocking of lawful content and services for minors, raising free speech and privacy concerns.EFF analysis of AB 1043 California Age Verification Law tracker
- Commentaries underscore the risk that the age signal will be reused for broader surveillance or monetization, despite the non-identifying design, unless strong governance is enforced.EFF analysis of AB 1043 AllAboutCookies explainer on AB 1043
- Alignment with other child-protection and privacy laws
- OS providers and app developers must align AB 1043 implementation with other California youth-online-protection laws, such as SB 976 (Protecting Our Kids from Social Media Addiction Act) and related initiatives.California OAG – SB 976 page California DOJ press release on SB 976 regulations
- Industry analyses note the challenge of using the age-bracket signal consistently across multiple regulatory frameworks, including not-yet-finalized guidance and future e-safety standards.California Introduces New Age Verification Requirements – Hunton AB 1700 youth online protection bill synopsis
- Example challenges and cases
- Commentary on AB 1043 and its amendment bill AB 1856 highlights concrete concerns about compatibility with open-source OS ecosystems and browsers, including proposals to limit scope or clarify obligations.Techtimes article on AB 1856 and AB 1043 AB 1856 Assembly analysis referencing AB 1043
- Legal and privacy blogs illustrate scenarios where cross-border services must reconcile California age signals with federal COPPA obligations and other state laws, increasing compliance complexity.California Introduces New Age Verification Requirements – Hunton California Children’s Privacy Laws summary – AB 1043
Implementation Best Practices
These are practical, but organizations should always cross-check against legal counsel and official statutory language.
- Establish a structured age-bracket collection flow
- Design a setup flow that clearly informs users why age is being collected, how it will be used, and how it is categorized into brackets, in line with AB 1043’s definition of age bracket data.California AB 1043 bill text (LegiScan) Operating-System Age Verification Requirements – analysis
- Follow privacy regulators’ recommended practice to limit repeated age assurance prompts and minimize data collection, to maintain usability and privacy.Assessing whether and how to use age assurance – regulator guidance California OAG SB 976 page – youth protection design considerations
- Implement a robust age-bracket API and governance
- Create a documented, versioned API that exposes only the required age bracket classifications to apps and online services, with strong authentication and authorization for app access.Operating-System Age Verification Requirements – analysis California Introduces New Age Verification Requirements – Hunton
- Maintain internal governance policies restricting downstream use of the age signal to compliance and safety purposes, to mitigate misuse risks highlighted by civil liberties groups.EFF analysis of AB 1043 Assessing whether and how to use age assurance – regulator guidance
- Align with recognized privacy and child-protection frameworks
- Integrate AB 1043 implementation with privacy-by-design and data minimization principles commonly referenced in regulatory guidance on age assurance and youth online safety.Assessing whether and how to use age assurance – regulator guidance California OAG SB 976 page – minors’ protections
- Coordinate with emerging e-safety and youth online protection guidelines, such as those envisioned by California’s AB 1700 e-Safety Commission proposal, which would develop minimum age compliance guidelines and review age assurance technologies.AB 1700 youth online protection bill synopsis California DOJ press release on SB 976 regulations
- Tools, resources, and reference materials
- Use statutory text and official bill analyses for primary legal requirements:
- California AB 1043 bill text (LegiScan)
- AB 1856 Assembly analysis referencing AB 1043
- Consult specialized legal and technical commentaries for practical implementation:
- Operating-System Age Verification Requirements – technical/legal analysis
- California Introduces New Age Verification Requirements – Hunton
Recent Updates
- AB 1043 enactment and status
- AB 1043 was signed into law on October 13, 2025, as Chapter 675 of the 2025 statutes.California Introduces New Age Verification Requirements – Hunton AllAboutCookies explainer on AB 1043
- The law is enacted but not yet effective, with key obligations operative January 1, 2027, and deployment obligations for existing devices by July 1, 2027.California Age Verification Law tracker Operating-System Age Verification Requirements – analysis
- AB 1856 – amendment and expansion of the regime
- AB 1856 (Wicks) is an amendment bill referencing and building on AB 1043, further addressing California’s age verification system and expanding age-g
Recent developments
- — AB 1856, passed in late August 2026, amends the California Digital Age Assurance Act (AB 1043) to exempt open‑source operating systems like Linux from age‑verification obligations, while keeping major commercial platforms such as Windows, macOS, iOS, and Android fully in scope and reaffirming the January 1, 2027 implementation date for age prompts on new and existing devices.[9][1] (source)
- — The Electronic Frontier Foundation reports that California has stepped back from a proposed expansion of AB 1043’s age‑gating rules, but emphasizes that the core law—requiring operating systems and app stores to collect user ages, assign age brackets, and restrict young people’s access to lawful online speech and services—still goes into effect in January 2027.[6][13] (source)
- — EFF analyzes AB 1856 as a mixed development, noting that while it carves out open‑source software from AB 1043’s definition of “operating system provider,” it simultaneously broadens the age‑gating framework by reinforcing requirements for age‑bracketing systems across commercial platforms and potentially deepening compliance burdens and speech restrictions.[5][1] (source)
- — The Register reports that lawmakers are revising AB 1043 to add an open‑source carve‑out so that distributors of Linux and similar software are no longer treated as “operating system providers,” responding to concerns that the Digital Age Assurance Act would otherwise force community projects to build complex age‑verification infrastructure under penalty of fines.[1][12] (source)
- — A Russian‑language report highlights that AB 1043, effective January 1, 2027, will require operating system providers to integrate age‑tracking tools and a specialized API for age signals, warning that open‑source projects such as Debian and SteamOS initially faced significant compliance risks and fines of up to $7,500 per child before exemptions were advanced.[2][15] (source)
- — EFF’s March 2026 analysis argues that AB 1043’s requirement that operating systems and app stores create age‑bracketing systems, collect users’ birthdates or ages, and share age‑bracket signals with application developers will harm privacy and online freedoms for all users, not just minors, by normalizing age‑gated access to lawful services.[13][15] (source)
- — EFF also discusses industry and civil‑society reactions, noting that developers, privacy advocates, and digital rights groups are worried that AB 1043’s mandated age‑gating infrastructure will increase compliance costs, incentivize pervasive age data collection, and limit minors’ access to lawful information and services, prompting calls for exemptions and legislative revisions such as AB 1856.[13][5] (source)
- — Hackaday criticizes AB 1043 as a problematic attempt to add age verification to software, explaining that OS providers must implement an age‑selection interface during account setup, categorize users into four brackets (under 13, 13–15, 16–17, 18+), expose an API to app developers and app stores, and face penalties up to $7,500 per affected child for intentional violations.[15][8] (source)
- — Gigazine reports that AB 1043 will require operating systems to collect users’ age information at account setup and provide that data to applications via an API to protect minors online starting in January 2027, while also noting Governor Newsom’s caution and calls for reconsideration of the law despite having signed it in October 2025.[10][8] (source)
- — A technical commentary warns that AB 1043’s statewide age‑assurance framework, mandating age or date‑of‑birth declarations during OS account setup and an age‑bracket API for apps, could effectively regulate every command or application on Linux systems, raising broad concerns about privacy, implementation complexity, and unintended impacts on general‑purpose computing.[12][1] (source)
Related regulations
- California CPPA Regulations - ADMT, Risk Assessments and Cybersecurity Audits — California, Phased, effective 2026-01-01
- California Transparency in Frontier Artificial Intelligence Act (SB 53) — California, Active, effective 2026-01-01
- UK Data Protection Act 2018 — United Kingdom, Active
- Texas Data Privacy and Security Act (TDPSA) — Texas, Active, effective 2024-07-01
- General Data Protection Law (LGPD) — Brazil, Active, effective 2020-09-18
- COPPA (Children's Online Privacy Protection Act) — United States, Active
- Oregon Consumer Privacy Act (OCPA) — Oregon, Active, effective 2024-07-01
- Montana Consumer Data Privacy Act (MCDPA) — Montana, Active, effective 2024-10-01
Put it into practice
- Generate the policy: COPPA policy generator (generatepolicy.com)
- Buy the policy pack: Privacy Program Bundle (cyberpolicy.shop)
- Build it yourself: 2026 US Privacy Program Workbook (ciso.diy)
Browse all regulations · Compliance deadlines · Latest updates