Your Kid Now Needs Your OK To Download An App In Texas

Texas Senate Bill 2420, the App Store Accountability Act, requires app stores to determine whether a user is a minor and to get verified parental consent before that minor downloads an app, buys an app, or makes a purchase inside one.

It is the first law of its kind actually operating. Utah passed the first one, SB 142, in 2025, then delayed it to May 2027 and stripped out the attorney general's enforcement authority. Louisiana and Alabama passed versions too, both pushed to 2027.

Four states, one live.

The legal path was messy and is not finished. A federal judge blocked the Texas law in December 2025. The Fifth Circuit stayed that block in May 2026, finding Texas had shown a strong likelihood of winning. The Supreme Court declined to vacate that stay on July 6, 2026. The Fifth Circuit heard argument on the merits on August 4, 2026 and has not ruled.

Translation for a parent in the kitchen: the law is being enforced right now, and it might not be a year from now. Do not build your family's plan around the statute. Build it around the habit, because the habit outlives whatever the court decides.

If you are not in Texas, this still matters. The app stores did not build a Texas-only system. They built consent infrastructure and turned it on where required. That switch gets flipped in more places, probably soon.

Practically, an extra screen appears. Your kid taps download, the store checks the age category on the account, and if the account belongs to a minor, a request lands with you.

The part parents underestimate is the second half: in-app purchases. The $4.99 skin, the coin pack, the monthly subscription, the battle pass. Those used to happen in three seconds with a saved card and a fingerprint.

Now they generate a notification.

A lot of families are about to discover how many of those requests there actually are. That count is the real data. Eleven consent requests in a week is not a discipline problem. It is information about how the games your kid plays are built, and it is worth showing them the number.

The risk is that consent becomes a reflex. You are at work, the phone buzzes, you tap approve without looking, and you have taught your kid that the gate is theater. Worse than no gate, because now they have learned that a rule with a person behind it is not a real rule.

So the first decision is not what to allow. It is deciding in advance that you will not approve anything from a moving car, a meeting, or a checkout line.

Because the thing that makes digital money hard for children is that it does not feel like money.

A ten-year-old handing over a five dollar bill experiences a loss. They watch it leave. A ten-year-old tapping confirm on a $4.99 gem pack experiences nothing, because the payment is invisible, instant, and detached from any account they can see.

Research on kids and spending points the same direction: the pause does the teaching, not the lecture. The gap between wanting something and getting it is where a kid evaluates whether they want it.

Digital storefronts are designed to close that gap to zero, and it is not an accident.

What this law does, almost incidentally, is reintroduce the pause. Every purchase now has a person in the middle of it. That is an unusually good teaching tool and it will not last forever, so use it while it is here.

Make the pause do work. When a request comes in, do not just approve or deny. Send back one question. "What is this and what does it do?"

Half the time the answer is some version of "nothing, it just looks cool," and your kid hears themselves say it. That is worth more than anything you could have told them.

Set the rules once, in a calm moment, and put them somewhere both of you can see. Fighting request by request is exhausting for everyone and teaches nothing except that whoever is more persistent wins.

A structure that works for a lot of families:

Free apps get a light touch. A quick look at what it is and who else uses it. Approve or deny same day.

Paid apps and purchases come out of a budget. Your kid gets a monthly number, say $10 or $15, from their own income or an allocated allowance. Anything within budget is their call, and you approve it without argument even when you think it is a waste. That last part is hard and it is where the learning is.

Subscriptions get their own conversation. A recurring charge is a different decision from a one-time purchase, and most kids under fifteen have no intuition for what twelve months of $6.99 adds up to. Make them do the multiplication out loud. Eighty-three dollars surprises people.

Anything over budget waits 48 hours. Not denied. Waiting. Most of them evaporate.

Some families track this in a notes app, a whiteboard on the fridge, a shared spreadsheet, or a planning tool like Foundra Kids that keeps the budget and running total in one place. Any of those work. What matters is that the number is visible without asking you, because a budget you have to request the balance of is not really theirs.

This part almost nobody is discussing, and it matters if you have a kid who codes.

Age verification affects publishers too. A fourteen-year-old who wants to put something on an app store already had to work through an adult's developer account. The new consent infrastructure adds another layer of identity checking around minors on both sides of the store.

For a young builder this is annoying and also a real lesson, so name it as one. Distribution belongs to someone else. The store decides who can publish, who can buy, what the cut is, and what the rules are this year. Every founder learns this eventually, usually the hard way. A teenager who learns it at fourteen with a hobby project has learned it cheaply.

The response is the same at fourteen as at forty: do not let one channel be the only way people reach what you made. A browser version. A direct download. A mailing list of people who asked to hear from you. None of that needs anyone's approval.

If your kid is building something right now, ship the same thing two ways. It takes an afternoon and builds an instinct most adults do not have.

Four things, in order, and none of them take long.

Check the account age setting. A surprising number of kids' devices are registered to an adult birthdate, either because a parent set it up years ago or because the kid changed it. If the account says twenty-four, none of the protections apply and no requests reach you. Fix this first.

Look at last month's charges together. Not as an accusation. As data. Open the purchase history, add it up, let the number sit there. Most families land between mildly surprised and stunned.

Set the monthly number. Whatever you can live with. The amount matters far less than it being fixed, known, and theirs.

Agree on the 48-hour rule for anything above it. Write it down. Both of you.

That is the whole system. It survives a court ruling in either direction, it works in states where nothing passed, and it still works when your kid turns eighteen and the law stops applying. Which is the actual goal. The statute is temporary scaffolding around a habit you want permanent.

• Texas SB 2420 is the only app store age verification law currently being enforced. Utah, Louisiana, and Alabama have versions delayed to 2027.
• The Fifth Circuit heard the merits argument on August 4, 2026 and has not ruled. The law being enforced today may not be next year.
• Consent applies to downloads and in-app purchases, so the small recurring stuff now generates a request. Count those requests for a week before reacting.
• The value is the pause, not the permission. Reply to a request with one question rather than a yes or no.
• Set a fixed monthly digital budget, approve anything inside it without argument, and make anything above it wait 48 hours.
• Check that your kid's account uses their real birthdate. If it does not, none of this reaches you.
• For kids who build apps, the lesson is platform dependence. Ship a browser version alongside anything in a store.

Does this law apply outside Texas?

The statute applies to Texas residents. But the app stores built one consent system rather than a Texas-only one, so families in other states may see similar prompts as platforms roll out parental controls more broadly. Utah, Louisiana, and Alabama have passed their own versions with 2027 start dates.

Will this stop my kid from spending money on games?

Not by itself. It routes the decision through you, which helps a lot with impulse purchases and helps very little if you approve everything without looking. The gate works only if it is a real gate.

My teen says this is a privacy invasion. Are they wrong?

Not entirely, and it is worth taking seriously. Age verification requires collecting identity information, and privacy advocates have raised real objections about how that data is stored and who can see it. You can agree the concern is legitimate and still keep the household budget rule, because the budget rule is yours, not the state's.

What happens if the court strikes the law down?

The consent requirement would stop being mandatory in Texas, though app stores may keep the controls as an optional feature. Your household rules would be unaffected.

1. Loeb & Loeb: Children's Online Privacy in 2026, State App Store, Design Code and Social Media Laws
2. Recording Law: App Store Age Verification Laws, All 4 States Compared (2026)
3. Fortune: Social media companies are scrambling to verify minors online
4. Privacy World: App Store Age Verification Laws, Your Questions Answered
5. AVPA: US State Age Assurance Laws for Social Media