Updated August 2026 · Google's own help pages, the Play Age Signals documentation, Apple's developer material and the enrolled text of every state bill named here re-read on 18 August 2026
Email verification is our first choice because Google's help page, read 18 August 2026, says partner VerifyMy gets only your address and does not keep it. A selfie is our second because Google's help page, read 18 August 2026, says partner Private ID gets only a random identifier and deletes the photo. A credit card is our last easy choice because Google's help page, read 18 August 2026, says card data is retained for legal requirements. Data checked: 18 August 2026.
Google Play asks some people to prove their age before it will hand over an app. This page covers the five methods Google's own help page listed on 18 August 2026, what each one gives away and to whom, which US state laws have actually started, and what Google says happens if you do nothing. Every quotation below is linked to the page it came from.
Handing over the least
Google Account Help, section "Use an email address for age verification", partner named as VerifyMy · Google Account Help · read 18 August 2026
The route that asks for the least and explains itself the most. Google says it hands VerifyMy your email address and nothing else from your account, that VerifyMy checks where that address has been used before, and that it answers one question only. The catch sits in the same paragraph: your address is passed on again, to database partners Google does not name.
Skip it if the address is new or barely used, because Google describes the check as reviewing sites and apps where you have used it before. Choose it over the selfie when you would rather not have a photograph of your face processed at all.
No document, no card
Google Account Help, section "Use a selfie for age verification", partner named as Private ID · Google Account Help · read 18 August 2026
The only method where something biometric leaves the phone, and also the only one where Google says the company receiving it is told nothing about who you are. Google's own wording flags this part of the product as unfinished, and the terms you accept are somebody else's.
Skip it if you are not willing to have a biometric image processed by a company you did not choose. Choose it over the credit card because Google publishes a deletion sentence for the selfie and a retention sentence for the card.
No photo of anything
Google Account Help, sections "Use a credit card for age verification" and "How credit card verification works" · Google Account Help · read 18 August 2026
Nothing is uploaded and nothing is photographed, and Google is unusually plain that the money side is theatre: the card is checked, not charged. What the page also says, and what this page never mentioned before, is that this is the one method whose section states Google keeps the data.
Skip it if you would rather keep payment details out of the flow entirely. Choose it over a government ID because nothing is uploaded and no manual review stands behind it.
A wallet you already use
Google Account Help, section "Use a digital ID for age verification" · Google Account Help · read 18 August 2026
If your device wallet already holds a digital ID, this is the shortest path in the list: pick the ID, follow the wallet, done. It is also the method Google says least about. There is no retention sentence, no partner name and no issuer list, and there is a platform limit in Google's own words.
Skip it if you are verifying on anything that is not an Android device, because Google states that limit itself. Choose it over the ID upload because the document never leaves the wallet as an image file.
When the rest have failed
Google Account Help, sections "Use an ID for age verification" and "How ID age verification works" · Google Account Help · read 18 August 2026
The heaviest thing to hand over and the only one Google promises to delete. Read the promise closely, because it covers the image and not what is taken from it: the date of birth is saved to your payments profile and to your Google Account. A person may also read the document.
Skip it if any of the other four are offered to you, because this is the only one that puts a full identity document into the flow. Choose it over a selfie only when the lighter methods have failed, since this is the route Google says may go to manual review.
Where the law has actually started
The prompt is driven by law, and most of those laws are not running yet. Of the four US states that have passed an app store accountability act, one obligation date has arrived.
None of this is only American. Google says the Play Age Signals API "started returning age signals for users in Brazil for requirements under Digital ECA" on 17 March 2026, months before Texas (Play Age Signals overview, read 18 August 2026).
What Google actually says
Start with what is not there. Google's user help page describes five ways to verify and states no consequence at all for declining. This page used to say Google had warned of disruptions in getting apps; that sentence belongs to a news summary rather than to Google, and it has been removed.
What Google does document is the developer side, and it explains why the experience feels patchy. If you have not verified, the API reports your status as VERIFICATION_REQUIRED, which Google defines as meaning "the user's age is unknown and the user is in an applicable jurisdiction or region where age verification and age signals sharing is mandatory" (request age signals, read 18 August 2026). The same page carries something readers in covered states should know: "For eligible users in US states with laws requiring app stores to provide verified age information to developers, the in-app prompt is not triggered. Instead, users will be asked to verify or set up supervision when they visit the Play Store app."
More apps come into scope shortly. A policy preview dated 26 August 2026, read 18 August 2026, expands the age restricted content policy "to apply to anonymous chat and random chat apps".
One thing to be strict about. Every method Google documents begins inside the Play Store or a prompt on the device, never from a link in a message. Google does say it emails you when a manual review of an uploaded ID finishes, so a message can be genuine once you have started, but nothing legitimate asks you to begin by following a link. A current antivirus app is a reasonable backstop against pages that copy these screens.
What a parent approves
Children are not expected to verify themselves. Google says it "will use existing parental controls to facilitate download and purchase approvals for eligible supervised users", and that "Google Play will seek parental consent from parents of supervised users for downloads, purchases and significant changes in applicable U.S. states" (Play Console help, read 18 August 2026). Note the wording: Google says existing parental controls, and does not name Family Link in that sentence.
The reassurance parents want sits on a different page, and it is narrower than it looks. Google says "You or your child will still be able to see any apps and games you downloaded before you added content restrictions, even if they're outside of the rating you set", and in the very next sentence that "If your child's account is supervised with Family Link, you can block these apps on their Android devices" (content restrictions help, read 18 August 2026). Blocking takes "about 5 minutes, or once the device is connected to the internet", and Google warns that "Some apps can't be blocked because they're required for parent supervision settings to work" (Family Link help, read 18 August 2026).
One promise here is easy to over-read. Google says "Google Play will not revoke app access or disable the app based on significant change approvals". That is scoped by its own words to the significant change flow, and it is not a general guarantee about everything already installed. For controls beyond the built-in ones, our roundup of the best parental control apps for Android covers third-party tools.
What the app receives
The app you are installing never sees your date of birth. It receives a band and a source, through the Play Age Signals API, which Google labels beta on its own Play Console help page, read 18 August 2026. The default bands are "0-12, 13-15, 16-17, and 18+" and a developer can ask for custom ones (integration guide).
The field that says how your age was established is ageRangeSource, and its values are the only place all five methods appear together. TIER_C covers a user whose "age is assessed by using credit card, email address, selfie assessment, Government ID, or Tax ID", and TIER_D covers "a combination of Government ID and selfie assessment, or Digital ID" (response fields, read 18 August 2026).
Two things follow that this page previously had backwards. Google does not gate your content: it says "You are responsible for restricting access to any content or functionality in your app relating to significant changes based on the approval status you receive from the Play Age Signals API" (significant changes), and it orders nobody to adopt any of this: "It is your responsibility to determine how these laws apply to your app, and whether and how to use these features to meet your obligations." Even what counts as a significant change is the developer's call: "It is the developer's responsibility to decide what constitutes a significant change for their app."
Google against Google. The Play Console help page still describes apps receiving "age verification or supervision status", while the developer release notes for version 0.0.4, published in July 2026, say "userStatus is deprecated and no longer supported in version 0.0.4 or higher" and replaced by ageRangeSource and significantChangeStatus (release notes, read 18 August 2026). Both pages are Google's, both were live on 18 August 2026, and this page prints both rather than choosing between them.
For Texas, Google says the API "has started returning age signals for eligible users in Texas who created their accounts after May 28, 2026 as part of our compliance efforts for Texas SB2420" (overview, read 18 August 2026). That is a cutoff deciding whose accounts produce a signal, not a date when something switched on for everybody, and Google publishes no such switch-on date.
The same question, a different mechanism
Buying an iPhone does not get you out of this. Apple runs a parallel scheme, the Declared Age Range API, built to answer the same question with less data: "Rather than receiving an exact age, you receive age range bounds that correspond to your specified age gates." The developer picks the thresholds, up to three of them, each range at least two years wide.
What comes back depends on where you are. Apple says that when a child, or a parent or guardian, chooses to share, the API "will return the age band or age category, depending on legal requirements in the region", and that "In certain regions, where legally required, Apple uses age assurance methods to confirm an Apple Account holder's age" (Apple age assurance, read 18 August 2026). Apple's own Texas post is explicit that the brackets people quote are the statute's rather than the API's: the age category is "defined by Texas state law as under 13, 13-15, 16-17, or over 18" (Apple developer news, 4 November 2025).
Read Apple's dates against the statutes. Apple's post of 24 February 2026 tells developers to expect age categories for new accounts in Utah "as of May 6, 2026" and in Louisiana "as of July 1, 2026". Both dates have since been overtaken by the legislatures: Utah's duties moved to 6 May 2027, and Louisiana's 2025 act was repealed before it started. Apple's post was accurate when published and has not been updated, read 18 August 2026.
The same post carries a measure that is genuinely live and has nothing to do with US states: since 24 February 2026 Apple "will block users in Australia, Brazil, and Singapore from downloading apps rated 18+ unless they have been confirmed to be adults through reasonable methods."
Apple is also on the record against the law it is complying with. In a developer post of 8 October 2025 it wrote that it is "concerned that SB2420 impacts the privacy of users by requiring the collection of sensitive, personally identifiable information to download any app, even if a user simply wants to check the weather or sports scores." Neither company presents this as its own idea. If sideloading looks like the escape route, that ground is moving too: see what is changing for sideloading in 2026.
On Google's own help page, read 18 August 2026, the email check is described most tightly: Google says its partner VerifyMy is given your email address and no other account data, that VerifyMy does not keep the address or use it for anything else, and that the check answers only whether you are old enough. The selfie route comes next, because Google says its partner Private ID receives only a random account identifier and the photo is deleted once your age is estimated. The credit card section is the only one that says Google retains what you enter, to meet legal and regulatory requirements. Checked 18 August 2026.
No. Google's help page says the card check is an authorization request and not a charge, that you do not pay for an authorization, and separately that you will not be charged to verify your age. It does warn that a pending authorization may sit on your account for 1 to 14 business days depending on your bank, and tells you to contact the bank if it is still showing after 14 business days. Checked 18 August 2026.
Google plans for it on the page itself. If your age is not verified, it says you will get information on options to try again or to use a different verification method, and each method screen offers a route out to another one. Google publishes no accuracy figure for the estimate, so how often it misreads a face is not something anyone can quote from the source rather than guess. Checked 18 August 2026.
Texas was the only US state whose app store law had actually started as of 18 August 2026. Utah begins on 6 May 2027, Alabama on 1 January 2027 and Louisiana on 1 July 2027, on the enrolled text of each bill. Google says only that an eligible account identified as being in an applicable US state will be asked, in line with that state's effective legal date, and it names no other state. Age checks can still reach you for reasons that have nothing to do with US state law, including Brazil, where Google says signals began on 17 March 2026. Checked 18 August 2026.
No. Google says it will use existing parental controls to handle download and purchase approvals for eligible supervised users, and that it will seek parental consent for downloads, purchases and significant changes in applicable US states. Read the limit alongside it: Google says it will not revoke app access or disable an app based on significant change approvals, and that sentence covers that one flow rather than everything already installed. Checked 18 August 2026.
No. Apple runs its own Declared Age Range API, which returns an age band rather than an exact age, and Apple says whether you get a band or a legally defined category depends on the region. Apple has also blocked users in Australia, Brazil and Singapore from downloading apps rated 18 and over since 24 February 2026 unless they are confirmed adults. The requirement follows the law rather than the phone. Checked 18 August 2026.
Treat it as fake until you have checked. Every method Google documents starts inside the Play Store or a prompt on the device, never from a link in a text or an email. Google does say it will email you once a manual review of an uploaded ID is complete, so a message can be genuine after you started a check yourself, but nothing legitimate asks you to begin one by following a link. Checked 18 August 2026.
Checked 18 August 2026: the page was rebuilt against primary sources and the corrections are substantial. Google's help page lists five verification methods, not the four this page counted, and it names the partners: Private ID performs the selfie estimate and VerifyMy the email check, where this page had attached a single provider to the wrong one of the two. The sentence claiming Google says verification data is not turned into ad targeting is deleted outright: no Google page states it, and it was the most load-bearing unsourced claim here. In its place stand the statements Google does make, that an uploaded ID is deleted after the date of birth is verified while the date of birth itself is saved to the payments profile, and that card details are retained to meet legal and regulatory requirements. The claim that a temporary charge is refunded is gone, because Google charges nothing and never uses the word; the word debit is gone, because Google's page says credit card throughout. On the law, the assertion that the Fifth Circuit lifted the block is replaced by what the order says, that the injunctions are stayed pending appeal, with the Supreme Court's denial of 6 July 2026 added and the caution that no court has ruled on the merits. Utah switched nothing on in May 2026: its duties begin 6 May 2027, written ten times in the enrolled bill, with existing accounts around May 2028. Louisiana's 2025 act was repealed before it took effect rather than delayed. Alabama and California are added with their own dates, Kansas is removed because its bill died on the House calendar, and the claim that Google warned of disruptions in getting apps is withdrawn as a misattribution of a news summary. The Texas Tribune link now serves a different story than the sentence citing it described, so the court record is cited instead. A decision table, an "Our answer" capsule, a dated verification box and this changelog are new, and the anecdotal opening was cut to fund them.