What does an app store age verification law mean for dating apps?
An app store age verification law makes Apple and Google check each account holder's age, and makes the app developer use the age category the store passes on. For a dating app, which must keep everyone under 18 out, the main work is rating the app correctly, reading the store's signal, blocking minors and telling the stores about significant changes.
Most are called App Store Accountability Acts. The stores do most of the work: they sort every account into one of four age categories and link a minor's account to a parent. Texas uses these categories:
| Category | Age |
|---|---|
| Child | Under 13 |
| Younger teenager | 13 to under 16 |
| Older teenager | 16 to under 18 |
| Adult | 18 or older |
The parental consent rules matter to apps that minors may use. A dating app's job is simpler: make sure the signal says "adult" before anyone signs up. These laws apply to apps. A dating website answers to other rules, set out in our guide to US dating regulations.
Which states have app store age verification laws in 2026?
Five states have passed laws that pass an age signal from the store or the device to app developers: Texas, Utah, Louisiana, Alabama and California. Only Texas is enforceable today.
| State | Law | Developer duties start | Enforced by | Status when we checked |
|---|---|---|---|---|
| Texas | SB 2420 | 1 January 2026 (enforceable since 4 June 2026) | Attorney general, as a deceptive trade practice | In force while the appeal continues |
| Utah | SB 142, amended by HB 498 | 6 May 2027 | Private claims by a harmed minor or their parent | Industry challenge withdrawn after the amendments |
| Louisiana | HB 570, amended by HB 977 | 1 July 2027 | Attorney general, up to $10,000 per violation after a 45-day cure period | No challenge reported |
| Alabama | HB 161 | 1 January 2027 | Attorney general, up to $7,500 per violation | Industry challenge filed, paused while rules are written |
| California | AB 1043, Digital Age Assurance Act | 1 January 2027 | Attorney general, up to $2,500 per affected child (negligent) or $7,500 (intentional) | No challenge reported |
California's law works differently. Operating system providers must ask for a birth date or age when a device is set up and pass on an age range, without verifying it. Developers must request the signal at download and launch, and are treated as knowing the age range it shows.
There is no federal law yet. A federal App Store Accountability Act cleared a House committee 26 to 23 in March 2026 without a floor vote, and the Senate version had not moved beyond committee.
What must a dating app developer do under these laws?
A developer must rate the app, request and use the store's age data, and give notice of significant changes. The Texas law sets out the duties most clearly:
- Age rating. Give the app and each in-app purchase an age rating, and tell each store what content drove it.
- Change notices. Tell each store before a significant change to your terms or privacy policy. Texas includes new types of personal data, a new age rating, new ways of making money and material changes to how the app works.
- Use the signal. Build a system that uses the store's data to check each account holder's age category and, for minors, whether a parent consented.
- Limit and delete. Use the data only to enforce age limits, meet the law and set safety features, then delete it once the check is done. Do not share it.
Utah adds timing rules from May 2027: request age data at download, at first launch of a pre-installed app and after a significant change, and ask again at most once every 12 months unless you suspect misuse. The substitute bill we read also lets a developer ask the stores to block minor accounts from downloading its app, which suits a dating app. Louisiana's amendments let a developer rely on the store's signal unless it knows its own data is more accurate.
For a dating app, that turns into a short checklist:
- Set the 18+ rating in every store and keep the answers current.
- Request the age signal at sign-up and first launch, and refuse sign-up for any category under 18.
- Never seek parental consent for a minor; block them instead.
- Keep your own age checks for web sign-ups and missing signals.
- Define what counts as a significant change, and notify the stores first.
- Delete the store's age data once the check is done, and record it.
Texas and Utah protect developers that relied in good faith on the store's data and otherwise complied. Keep records that show you did.
How do Apple's and Google's age signal tools work?
Both stores give developers an API that returns an age range rather than a date of birth.
Apple. Apple's notice of 3 June 2026 says new Apple Accounts in Texas became subject to SB 2420 on 4 June 2026. For account holders under 18, Apple checks age and asks a parent to consent to downloads, in-app purchases and significant changes. Apple asks developers to implement:
- the Declared Age Range API, to request a person's age category
- the Significant Change API in PermissionKit, to ask a parent to approve a significant change
- the age rating property in StoreKit
- App Store Server Notifications, which tell you when consent is withdrawn
Apple says the developer decides when a change is significant.
Google. The Play Age Signals API is in beta. Its default ranges are 0 to 12, 13 to 15, 16 to 17 and 18 and over. Google says version 0.0.6 will return responses for everyone from 11 December 2026. Google also says it does not mandate the use of these features and that each developer must decide whether and how the laws apply to its app.
Both change often, so read the current documentation before each release.
Where do the court challenges stand?
Texas is the only law to have reached the Supreme Court, and it is being enforced while the appeal runs. The other states have either delayed their laws or paused their cases.
- Texas. A federal judge in Austin blocked the law on 23 December 2025. The Fifth Circuit stayed that order in May and June 2026, and on 6 July 2026 the Supreme Court declined to reinstate it. The challengers, a student group and the Computer and Communications Industry Association (CCIA), argue that the law breaches the First Amendment. The appeal was heard on 4 August 2026 and a decision was still pending on 19 November 2026.
- Utah. CCIA sued in February 2026. HB 498, enacted on 18 March 2026, moved the start date to 6 May 2027 and removed the attorney general's power to enforce the law, and CCIA withdrew its case on 21 April 2026.
- Louisiana. The governor signed HB 977 on 15 May 2026, moving the start date from 1 July 2026 to 1 July 2027.
- Alabama. CCIA sued on 28 October 2026 and agreed with the attorney general to pause the case until the state adopts its age-verification rules. The attorney general asked for comments on those rules, with responses due on 8 January.
Any of these dates could move again, so check before you plan a release.
How do these laws sit beside the 18+ store ratings?
They sit on top of them. Store ratings decide who can download a dating app; the state laws add a legal duty to use the store's age data and give notice of changes.
| Rule | Who sets it | What it asks of a dating app |
|---|---|---|
| Apple age rating | Apple | Declare Dating and Relationships features, which gives a minimum 18+ rating. All apps must answer the new questions by 12 January 2027 |
| Google Play age-restricted policy | Apps whose core function is dating must use Play Console tools to block minors | |
| State app store laws | Texas, Utah, Louisiana, Alabama, California | Rate the app, use the store's age signal, notify significant changes, limit and delete the data |
Our guide to App Store and Google Play rules for dating apps covers the store side in detail, and our guide to age verification for dating covers how to check age beyond the store signal. If you collect face scans for age checks, state privacy laws apply too; see US privacy laws for dating.
Who handles this on a white label or managed dating app?
The developer has the duty, and on most managed and white label arrangements the app sits under your own store listing. That usually makes you the developer the law means, even if a provider writes the code.
DatingAPI, run by the same group as this site, rebuilds dating apps as native iOS and Android apps under your own store listing and runs ID and age checks, safety, moderation and releases. It suits brands that already have an audience. Before you rely on any provider, DatingAPI included, ask:
- Does the app call Apple's Declared Age Range API and Google's Play Age Signals API, and what happens when the signal shows a minor?
- Who decides what counts as a significant change, and who sends the notice to the stores?
- Where is the store's age data held, and when is it deleted?
- Who keeps the records you would need to claim the safe harbour?
See dating apps for how our group's app platform works.
This page is general information, not legal advice.
Questions
Do app store age verification laws apply to dating websites?
The Texas law applies to developers who make an app available through an app store, so a dating website is outside it. Websites still answer to other age and consumer rules, which our guide to US dating regulations covers.
Does a dating app need parental consent features?
Not if it keeps minors out completely. The consent duties matter when a minor is allowed to download or pay for an app, and a dating app should not let anyone under 18 in.
Can a dating app rely on the app store signal alone?
Texas protects a developer that relies in good faith on the store's age and consent data and otherwise complies. Many dating apps still run their own age checks as well, because the signal only covers app downloads and some signals are based on an age the account holder entered.
What counts as a significant change?
Texas lists new types of personal data collected, a change of age rating, new ways of making money and material changes to how the app works. Apple's notice says the developer is responsible for deciding when a change is significant.
Is there a federal app store age verification law?
Not yet. A federal App Store Accountability Act cleared a House committee in March 2026 but had no floor vote, and the Senate version had not moved beyond committee when we checked.
Sources
- Texas Legislature: SB 2420, enrolled text, checked 21 November 2026
- Utah Legislature: H.B. 498, Utah App Store Accountability Act Amendments (2nd substitute), checked 21 November 2026
- Louisiana Legislature: summary of Senate amendments to HB 570 (2025), checked 21 November 2026
- SCOTUSblog: Supreme Court allows Texas to enforce law requiring age verification and parental consent on apps, checked 21 November 2026
- Privacy World: App Store Age Verification Laws, Your Questions Answered (updated 19 November 2026), checked 21 November 2026
- Alston & Bird: Challenge to Utah's App Store Accountability Act voluntarily dismissed following statutory amendments, checked 21 November 2026
- Alston & Bird: Louisiana delays App Store Accountability effective date to July 2027, checked 21 November 2026
- Hunton: Alabama enacts App Store Accountability Act requiring age verification, checked 21 November 2026
- FOX10 News: Alabama AG asks for input on app store age-verification rules amid lawsuit, checked 21 November 2026
- Kelley Drye: FAQs on California's Digital Age Assurance Act, checked 21 November 2026
- Future of Privacy Forum: TX, UT, LA App Store Accountability Act comparison chart, checked 21 November 2026
- Apple Developer News: Update for apps distributed in Texas (3 June 2026), checked 21 November 2026
- Apple Developer News: Update on age requirements for apps distributed in Texas (23 December 2025), checked 21 November 2026
- Apple Developer News: New age rating content descriptors in App Store Connect, checked 21 November 2026
- Android Developers: Use Play Age Signals API (beta), checked 21 November 2026
- Google Play Console Help: Regional age-related protections on Play, checked 21 November 2026
- Google Play: Age-Restricted Content and Functionality policy, checked 21 November 2026
- DatingAPI, checked 21 November 2026
What changed
- : First published.