← Nesim Apps

Play Age Signals API and California AB 1043: What a Small Developer Must Do

By Nesim Razon, independent mobile developer · 2026-11-21

#Dev notes#Android

This is a developer’s reading of the law, not legal advice. California’s Digital Age Assurance Act, AB 1043, says that from 1 January 2027 a developer must request an age signal when an app is downloaded and launched, and Google’s Play Age Signals API is how an Android app asks for it. I read the text of the law and Google’s documentation. Here is what it says, what it does not say and what a small developer can do.

What the law requires of developers

The text defines a developer as the person who owns, maintains or controls an application, and an application as software a user can run on a computer, a phone or a similar device. I found no exemption for small developers or for games. The key sentence says a developer shall request a signal about a particular user from the operating system provider or a covered app store when the application is downloaded and launched.

The signal is an age bracket: under 13, 13 to under 16, 16 to under 18, or 18 and over. A developer that receives a signal is treated as knowing the age range of that user. It must treat the signal as the primary indicator of age unless it has clear and convincing information that the age is different.

Dates

Penalties and enforcement

A violation can bring an injunction and a civil penalty of up to 2,500 dollars per affected child for a negligent violation and up to 7,500 dollars per affected child for an intentional one. Only the California Attorney General can bring the action. Operating system providers and app stores that act in good faith are protected, while developers are not given that shield.

What the signal may be used for

Both the law and Google’s policy limit the use. The signal is for complying with the law and providing age-appropriate experiences. It must not be used for advertising, analytics, profiling or shared with third parties for other purposes. For an app that uses an ad network and analytics, that means keeping the age value away from both.

The Android API in outline

The flow has three steps. Optionally ask whether mandatory sharing applies to the user. Then request access, which returns one of three states: shared, not shared or verification required. If the state is shared, ask for the age signals, which return a lower and an upper age bound or nothing when the user does not share.

The new version of the API works worldwide and adds a method to tell if mandatory sharing applies. Check Google’s current documentation before you implement it, because the API is still marked beta.

Brazil

Google’s page for Brazil says the Digital ECA expects developers of apps aimed at children and teenagers, or likely to be used by them, to ingest age range data from app stores, and prohibits loot boxes in games for that audience. The same page presents the Age Signals API as a way to receive the data.

What I plan to do

My apps are small and mostly casual games. I plan to add the minimum call to the apps that have age limits first, keep the age value only inside the app, never send it to analytics or ads, and treat a missing signal as normal. If the text of the law is amended before 2027, I will revise this note.

Frequently asked questions

When does California AB 1043 apply to developers?

From 1 January 2027, when a developer must request an age signal after an app is downloaded and launched.

Is there an exemption for small developers?

I did not find one in the text of the law. Ask a lawyer if you need certainty.

What age groups does the signal return?

Under 13, 13 to under 16, 16 to under 18, and 18 and over.

Can I use the age signal for ads or analytics?

No. The law and Google’s policy limit it to compliance and age-appropriate experiences.

More from the blog