The legal ground under app store age verification laws is shifting again. Privacy World, a law firm blog, has published an updated version of its Q&A on the topic, saying it revised the original post to address legislative changes that affect both the substance and the effective dates of these laws. The published excerpt is brief, so it does not spell out every change. But the update is a useful signal: anyone relying on earlier summaries of these rules should double-check them.
Below is what we can say with confidence, based on the update and on publicly visible descriptions of the laws, and what readers can do about it.
What the Updated Laws Change
The headline from Privacy World is simple: the substance and the timing of the laws have both moved. That matters because a compliance date that was accurate a few months ago may no longer be. Requirements that apps and app stores were preparing for may also have been altered.
For context, search listings describing these laws say four states have enacted app store accountability measures. They name Texas, Louisiana, Alabama and Utah as states that will require app stores to obtain parental consent for minors' downloads. Those summaries also describe a shared age structure: under 13 is a child, 13 to 15 is a younger teen, 16 to 17 is an older teen, and 18 and over is an adult.
We have not independently confirmed the revised effective dates, so check the current text of each state law or the latest legal analysis before assuming a deadline. Separately, California's AB 1043 takes a different approach. Starting January 1, 2027, operating systems sold or distributed in California will need to ask users how old they are, as we covered in our report on California AB 1043 and the Linux exemption.
What Data Age Checks May Collect
This is the question most readers care about. The laws generally push responsibility onto app stores to establish or collect a user's age, then pass an age category to developers. A developer guide listed in search results says developers must check the age category and parental consent that Apple or Google shares, and tell the stores about significant changes to an app. Google's own developer support page says that in certain states stores must verify ages and share that information with developers.
That means the information at stake can include:
- Your age or age category, shared with apps you download.
- Parental consent records for minors' accounts.
- Whatever evidence a store uses to confirm age, which could include an ID or a face scan depending on the method it offers.
That last point is where privacy concerns concentrate. One advocacy piece in the search results argues that age verification mandates create a data breach target for bad actors seeking sensitive biometric and ID data. Apple's rollout of a selfie option is one example of a method in practice, covered in our iOS 27.2 selfie age verification explainer.
Which Devices and Apps Are Affected
Coverage depends on the law. The state app store laws focus on app stores and the developers who distribute through them, so the major mobile storefronts are the main targets. Apple has already published an update for apps distributed in Texas, which describes age assurance and parent or guardian consent for minors under 18 for downloads. Google has a support page on changes to Google Play for the upcoming bills.
Operating system rules like California's reach further, since they apply at the device software level rather than only inside a store. Because the Privacy World update says effective dates have changed, whether a particular app or device is covered today may differ by state and by date. If you or your family use an app that is distributed in several states, expect the experience to vary depending on where you are.
There is also an industry fight over who bears the risk. Apple and Google have reportedly been lobbying to strip liability provisions from age check bills, which could shape how much responsibility falls on stores versus developers.
Limiting Data Sharing and the Limits of VPNs
A common assumption is that a VPN can sidestep these checks. Be cautious. A VPN changes your apparent network location, but app store age checks are tied to your account, your device and the store you use. They are not simply based on your IP address. We have no evidence from the source material that a VPN reliably avoids these requirements, and using one to misrepresent your location could breach a service's terms. A VPN is still useful for protecting traffic on untrusted networks, but it is not an age verification workaround.
Better options focus on limiting what you hand over:
- Read the prompt before you verify. Check which method is offered and what the store says about retention.
- Choose the least invasive method available, if more than one exists.
- Review account settings for what age information is shared with apps.
- Keep family accounts accurate, since parental consent flows depend on them.
Some consumers may prefer verifying once instead of repeatedly. A Jumio survey reported by Biometric Update indicates most consumers would rather use a reusable digital ID than repeat facial age estimation.
What This Means For You
If you are an adult, expect more prompts asking you to confirm your age, and treat each one as a data-sharing decision. If you are a parent, expect consent requests tied to your child's downloads in states with these laws. If you build apps, the Privacy World update is a reminder to confirm current obligations and dates rather than relying on older guidance.
Takeaways
- Treat earlier summaries of app store age verification laws as potentially outdated, since substance and effective dates have changed.
- Verify deadlines against the current law text or recent legal analysis.
- Share the minimum age data required, and understand how the method you choose handles IDs or face scans.
- Do not count on a VPN to bypass age checks.
To weigh the tradeoffs, read our opinion piece on how app store age checks could expose every adult, then see how one platform is putting these rules into practice in our iOS 27.2 selfie verification explainer linked above.




