App Store Age Verification: How Apple and Google Do It Now

App store age verification has quietly become mandatory rather than optional: Apple's App Store and Google Play are both now collecting an age signal for users before they can download or buy certain apps, driven by a wave of state and national laws rather than by either company's own initiative. Apple does it through a "Declared Age Range" that iPhone and iPad users (or their parents) set once in Settings; Google does it through a "Play Age Signals" check that developers can query at launch. Neither company asks for a birth date or ID by default, but in a growing list of places — Texas, Utah, Brazil, and soon the rest of the world — sharing an age band is no longer something a user can simply decline.

Why app stores suddenly need to know your age

For most of the App Store and Google Play's history, age checks meant a birth-date field at signup that nobody double-checked. That has changed because lawmakers decided the store, not just the individual app, should be the place where age gets established once and then shared downstream. Utah passed the first "App Store Accountability Act" in 2025, followed closely by Texas; both laws assign age-verification and parental-consent duties to the platform (Apple or Google) rather than to every individual app developer, on the theory that centralizing the check is both more reliable and less invasive than having thousands of apps separately demand ID or a credit card.

Apple and Google both resisted a version of this that would require government ID or facial scanning at the store level, and both ultimately shipped similar-looking solutions: an age range set once at the operating-system or account level, which individual apps can then request through an API, rather than a hard age verification that apps see directly.

Apple's Declared Age Range API, explained

Apple's mechanism is called Declared Age Range, and on the user-facing side it's the "Age Range for Apps" setting described in Apple's support documentation. Here's how the pieces fit together:

• A parent running Family Sharing sets a child or teen's age range directly, or an adult user can self-declare their own.
• Developers add the Declared Age Range entitlement in Xcode and call an API (requestAgeRange) with one or more age "gates," such as 13, 16 or 18.
• The system responds with a range (a lower and upper bound) and a declaration type — for example selfDeclared, guardianDeclared, or a stronger method such as governmentIDChecked or paymentChecked — rather than a specific birthday.
• Sharing is normally the user's choice, toggled per app or set to "Ask First," but Apple's support page notes that in some states, countries, or regions the age range is shared with developers by default, without an opt-out, to satisfy local law.

Apple requires iOS or iPadOS 26.2 or later for the full API; developer forum threads about building against Texas's law show the API returning a "not eligible" or "declined" response in plenty of real-world edge cases, so most developers are building a fail-safe path rather than assuming every call succeeds cleanly.

Google Play's Age Signals API, explained

Google's equivalent, the Play Age Signals API, is still labeled "beta" but is already live in several markets. According to Google's own documentation, it works in four steps: a developer requests access, requests a signal for a specific user, receives a response, and is then contractually bound to use that response only "to provide age-appropriate content and experiences in compliance with laws" — not for advertising, profiling, or analytics.

The age bands Google returns by default are 0–12, 13–15, 16–17, and 18+, though developers can request custom ranges for narrower use cases. Signals come from a mix of Family Link (for children whose parents manage their account) and adult self-reported sharing, and Google explicitly tells developers to pair an age-signal request with its separate Play Integrity API to make the result harder to spoof.

Google announced the global expansion plan in a July 29, 2026 Android Developers Blog post by Paul Feng, the company's VP of product management for Google Play: Brazil was already live, Australia and Canada would get it by mid-August 2026, and "every market" would have it by the end of 2026. The same policies that govern Android apps obtained outside Play are converging on a similar timeline — Google's own rules for registered third-party app stores and one-tap installs take effect within weeks of this age-signals push, part of the same broader push to tighten who can distribute apps to Android users and under what conditions.

The laws driving this: Texas, Utah and beyond

Three state laws are doing most of the work here, each built on a similar template: the app store verifies the account holder's age category, links minors' accounts to a verified parent, and requires parental consent before a minor downloads an app or buys something inside one.

• Utah SB 142 — the first in the nation — was signed into law in March 2025, and its app-store-provider and developer duties took effect May 6, 2026.
• Texas SB 2420, the "App Store Accountability Act," defines four age categories — child (under 13), younger teenager (13 to under 16), older teenager (16 to under 18), and adult (18+) — and requires app stores to verify age category, link minors to a parent account, obtain per-purchase parental consent, and share age/consent status with developers. Read the enrolled bill text for the full statutory language. It was originally set to take effect January 1, 2026.
• Louisiana and other states have introduced or passed similar bills on a rolling basis; Google's own documentation says simply that "updates for other US states' age verification bills will be provided in advance," which is a tell that more of this is coming rather than winding down.

Where Texas's law stands in court

Texas's law has had a bumpier legal road than Utah's. A federal district judge issued a preliminary injunction blocking SB 2420 on December 23, 2025, on First Amendment grounds, after industry groups sued. The Fifth Circuit Court of Appeals then stayed that injunction, allowing Texas to enforce the law while the underlying appeal continues, and the U.S. Supreme Court declined to intervene and block the stay. The practical result, as of this writing, is that SB 2420 is enforceable in Texas even though the courts haven't yet ruled on whether it's constitutional — which is exactly why both Apple and Google built age-signal systems that work today rather than waiting for a final verdict. Google's own compliance timeline (new Texas accounts after May 28, 2026) lines up with the date the Fifth Circuit's stay took hold.

Europe's approach: an app, not (yet) an app-store law

The EU has not passed an app-store-specific age-verification law comparable to Texas or Utah's. Instead, the European Commission has been pushing a different tool: a free, privacy-focused age-verification app that lets a person prove they meet an age threshold — for a website, platform, or store — without handing over their exact birthday or identity. The Commission's April 2026 recommendation urges every member state to have its own version live, either as a standalone app or folded into the EU Digital Identity Wallet, by the end of 2026.

Separately, a group of EU member states has floated the idea of a Europe-wide "digital age of majority" — a single age at which minors would no longer need parental permission to use certain online services — but as of late 2026 that remains a proposal working through discussion among member states, not adopted law, and officials have been candid that agreeing on one number across the bloc won't be simple. Don't expect Apple or Google to build EU-specific age-gating to match it until something is actually enacted.

What changes for parents

If you're the Family Sharing organizer on an iPhone, you can see and manage your child's declared age range in Settings, and choose whether apps always get it automatically or have to ask each time. On Android, the same control lives in Family Link. In practice this means less of the old pattern where a kid just typed in a fake birth year once at setup and every app treated them as an adult forever — the range can now be checked by individual apps every time it matters, and changing it is a parental action, not a one-time workaround. If you're also setting up a kid's first wearable alongside their phone, our comparison of two popular smartwatch options covers the parental-control features on each.

What changes for kids and teens

Teenagers get the most noticeable change: age bands like 13–15 and 16–17 are specific enough that an app can legally treat a 14-year-old differently from a 17-year-old, rather than lumping anyone under 18 into one bucket. In Texas and Utah specifically, a teen whose account is flagged as a minor will see parental-consent prompts before downloading new apps or making in-app purchases, and that consent is per-purchase rather than a single blanket approval a parent gives once and forgets about.

What changes for app developers

For developers, the headline change is that age handling moves from "ask the user and hope" to "query the platform and respond accordingly." That brings new obligations:

• Apps must handle multiple possible responses (shared, declined, not eligible, or an error) rather than assuming every user returns a clean answer.
• Under Texas law specifically, developers must assign and report their own age ratings to each store, and must honor whatever age-category and parental-consent data the store provides.
• Google explicitly restricts use of age-signal data to compliance and age-appropriate experiences — not ads, marketing, profiling, or analytics — and threatens API access and app removal for violations.
• Both platforms offer "safe harbor" style protection if a developer relies in good faith on the store's data and widely adopted industry standards, which matters because liability for getting age gating wrong (serving restricted content to a minor, or enforcing an in-app purchase without required consent) sits with both the store and the developer depending on the law.

Rollout timeline at a glance

What's next

None of this is finished rolling out. Google has explicitly said it's still building toward a worldwide launch of Age Signals, more US states are expected to pass their own version of Utah and Texas's laws, and the Texas case itself is still working through appeals even though the law is currently enforceable. On the EU side, the "digital age of majority" idea is still a proposal rather than a passed law, and the Commission's age-verification app depends on individual member states actually shipping it. The most likely near-term pattern: more countries and states get added to both companies' existing frameworks, rather than either Apple or Google building something fundamentally different from what's already live in Texas and Brazil today. Developers distributing on Android should also keep an eye on Google's separate app-store registration requirements, since age signals and sideloading rules are both tightening around the same time.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage