Trending•June 26, 2026•8 min read

App Store Age Verification: What It Means for Developers and Stores

If you ship a mobile app, age verification is about to change for you in 2026. The shift is structural: instead of each app running its own age gate, the check is moving up to the app store and the operating system. The store verifies a user's age once, at the account level, then passes that age on to the apps the user installs.

We work with thousands of developers who distribute beyond Google Play, so a change this broad matters to us as well. Here's what's changing and what you'll need to do about it.

What app store age verification actually is

For years, each app handled age on its own — usually a self-declared birthday that nobody checked. The new model splits the job in two: the store verifies the user's age and collects parental consent where needed, then hands your app a signal. Your app reads that signal and adjusts what it shows. The goal is to keep age-inappropriate content and purchases away from minors. Developers don't have to build their own identity systems for it to work.

The signal is an age category, not an exact birthdate — under 13, 13–15, 16–17, or 18+ — which keeps the amount of personal data changing hands small. The store also tells your app whether the required parental consent is in place.

The laws driving the shift

A cluster of laws converged on app stores across 2025 and 2026. They differ in the details, but all push the same verify-at-the-store, act-in-the-app model:

• Texas (SB 2420, the App Store Accountability Act) had a statutory effective date of January 1, 2026, but a federal court preliminarily enjoined it in late December 2025. After the Fifth Circuit stayed that injunction, the law became enforceable — Apple applied age assurance to new Texas accounts from June 4, 2026, and Google began returning age signals for Texas accounts created after May 28, 2026. New accounts must confirm whether the user is 18 or older; minors join a family group, and a parent must consent to downloads and purchases.
• Utah, Louisiana, and California follow the same pattern. Utah's store and developer requirements land on May 6, 2026 (with enforcement from December 31, 2026), Louisiana applies from July 1, 2026, and California has enacted its own version.
• Brazil is already live. Under its Digital ECA framework, Apple switched on age controls there on February 24, 2026, blocking 18+ downloads on accounts not confirmed as adult, and Google's Play Age Signals API began returning signals for Brazilian users on March 17, 2026. Brazil also auto-classifies some content, such as apps with loot boxes, as 18+. It's a large market, so if you ship there your age ratings and consent handling need to be in place now.
• Asia is moving fast, and often through national law rather than store signals. Indonesia's PP Tunas began enforcement on March 28, 2026; Malaysia's under-16 social-media rules took effect June 1, 2026 with ID-based verification; and Vietnam's Decree 147 has required parental registration for under-16 accounts since late 2024. These put the duty on platforms directly, so the obligation may sit in your app rather than in a store API.
• Europe is close behind. The EU's age-verification blueprint became feature-ready in April 2026, and the Commission is urging member states to roll out an EU age-verification app by the end of 2026, tied to the Digital Services Act and the future EU Digital Identity Wallet. The UK's Online Safety Act and Australia's under-16 social media rules pull in the same direction.

All of them want the same two things: a dependable age check at the account level, and developers who act on the result.

Where age rules are live — and where they're coming

These rules are arriving market by market, the way Google's developer verification did. The table below sorts markets by status and flags how each one actually reaches you: some are app-store age signals you read through an API (US states, Brazil); others are national platform laws that put the duty on your app directly (Indonesia, Malaysia, Vietnam, Australia); and a few are adult-content rules aimed at pornographic services rather than ordinary apps (France, Italy). What you care about is whether a rule is live where your users are. Check the linked platform docs before trusting any single date; Texas alone has moved more than once.

Dates reflect platform rollouts and statutory effective dates as of June 2026 and can change with litigation or amendment. Rows for Japan and Denmark are based on government announcements rather than final statutes. Always confirm against the latest guidance from Apple, Google, and the relevant national regulator for your specific markets.

How this affects developers

In store-signal markets, you don't verify ages yourself — you read the signal the store gives you and adjust your app. The catch is the split the table makes: in a growing list of markets (Indonesia, Malaysia, Vietnam, the UK, Australia) the duty comes from national law and lands on your app directly, not through a store API. So the first step is knowing which model applies where your users are. After that, the work is:

• Read the age category for each user through the platform API and treat under-18 users differently wherever the law requires it.
• Check parental consent status before letting a minor access age-restricted features or make in-app purchases, and re-request consent after significant changes to your terms, privacy policy, or monetization.
• Assign accurate age ratings to your app and its in-app content. Texas, for instance, expects ratings in the under-13, 13–15, 16–17, and 18+ bands.
• Handle the age data responsibly: transmit it with industry-standard encryption, use it only for compliance, and delete it once it has served that purpose.

None of this is optional. These laws put developers on the hook for enforcement, not just stores, and some US states allow private lawsuits on top of that. Doing the work once, up front, costs a lot less than scrambling to retrofit it against a deadline.

The age APIs you'll integrate

Apple — Declared Age Range API

On iOS, iPadOS, and macOS, Apple's Declared Age Range API hands your app a user's age category, along with signals for whether age-related regulations apply, whether the user must share their range, and whether you need a parent's permission for significant updates. Apple is already sharing age categories for new accounts in Texas, Utah (from May 6, 2026), and Louisiana (from July 1, 2026), and enforcing 18+ download blocks in markets such as Australia, Brazil, and Singapore.

Google — Play Age Signals API

On Android, the Play Age Signals API (beta) returns a user's verification or supervision status and an age range, by default 0–12, 13–15, 16–17, and 18+, and lets you notify Google Play of changes that require fresh parental approval. Google began returning signals for users in Brazil on March 17, 2026 and for new Texas accounts created after May 28, 2026.

Google also offers the Android Credential Manager API, in beta for digital IDs, which can confirm a user's age from a digital ID in their wallet — sharing only an age signal, and only with the user's explicit permission. Both platforms work the same way here: the app learns the age band and nothing else.

What app stores need to assure

The heaviest obligations fall on the app store operator, and they reach any store that runs its own accounts and distributes apps, not just Apple and Google. A compliant store has to assure several things:

• Verify age at account creation using commercially reasonable methods, and assign the user to an age category rather than storing an exact birthdate.
• Obtain verifiable parental or guardian consent before a minor can download apps, make purchases, or transact.
• Share the age category and consent status with developers through a reliable API, so apps can react consistently.
• Surface age-appropriate content and honor age ratings, keeping restricted apps away from accounts that aren't eligible.
• Minimize and protect the data involved: collect only what's needed to establish an age band, secure it, and avoid using it for unrelated purposes.

In effect, the store becomes the age authority for the apps it carries. That's a real responsibility, and alternative stores have to take it as seriously as Apple and Google do.

What this means if you distribute with Aptoide

If you distribute with us, two parts are worth separating out. The first is yours to own: accurate age ratings, the platform age APIs, and parental consent handled in your own code — the same parts you'd own under Google's developer verification. No store can write that logic into your app for you.

The second is reach. A single Aptoide Connect integration puts your app on a network of partner stores with more than 250 million users worldwide, and those markets won't all switch on age rules at the same time. Get your age ratings and consent handling right once and it holds across the whole network, not one storefront at a time.

On our side, we handle the store-level part: age-appropriate gating, the standard age categories, and as little data as the job needs. None of that changes how open distribution works — you still decide where and how your app ships.

Get ahead of it

For all the regulatory noise, the developer to-do list is short and concrete: assign honest age ratings, wire up Apple's Declared Age Range or Google's Play Age Signals API, put minor-sensitive features behind parental consent, and handle the data carefully. Do that before your market's deadline and there's little left to do when it lands.

The references below go deeper on each platform's requirements and APIs.

References

• Apple's Declared Age Range documentation
• Google's Play Age Signals overview
• The European Commission's approach to age verification

Aptoide Connect Team

Unleash your Apps. Reach Millions

Share