Apple App Store Must Verify User Ages Under Texas Law, Supreme Court Rules

What You Need to Know
- Supreme Court declined to pause Texas app store age verification law; Apple must continue checking user ages.
- Texas law requires Apple to verify user age at store level before any download, purchase, or transaction.
- Apple opposed law, arguing age verification belongs with app developers, not at the store layer.
- Law applies to existing app use, extending scope beyond new downloads alone.
The Supreme Court has declined to pause Texas’s app store age verification law, meaning Apple must keep checking user ages and collecting parental consent for minors while the broader legal fight plays out in lower courts. The brief order offers no reasoning, which is standard for emergency stay denials, but the practical effect is immediate: the rules stay in force.
What makes this law unusual is its reach. Most age-related app regulations target the apps themselves. Texas placed the obligation on the app store layer instead, requiring Apple to verify whether an account holder is an adult before any download, purchase, or in-app transaction can proceed for a minor. The law also applies to existing app use, not just new downloads, which extends its scope considerably beyond what a simple storefront restriction would cover.
Why Apple Fought This at the Highest Level
Apple opposed the law directly enough that Tim Cook personally lobbied Texas Governor Greg Abbott against it. The company’s core objection is structural: it believes age verification belongs at the app level, not at the store level. Shifting that responsibility to Apple means the company becomes a gatekeeper for content decisions that individual developers have historically managed themselves.
That tension is not new. Apple has spent years adding parental controls and family-sharing features to the App Store, but those tools have always been opt-in tools for parents rather than mandatory verification checkpoints for all users. A law that requires the store itself to confirm ages before transactions complete is a fundamentally different kind of obligation.
What the Law Actually Requires From Apple
For users, the law applies to anyone creating a new Apple Account in Texas. Those users must confirm whether they are 18 or older, and Apple can verify some accounts automatically in certain cases. When age verification isn’t working as expected, the process can stall in ways that block purchases entirely.
Developers face a parallel set of new duties. Because app stores must now communicate age information downstream, developers need to understand the age range of their users and apply the appropriate safety rules inside their own apps. Apple has provided tools to help with this, though the compliance burden has effectively been split across the entire ecosystem rather than sitting with one party.
The Broader Legal Pattern Apple Is Navigating
This is the second time recently that a Supreme Court decision has touched Apple’s platform control in a meaningful way. The court’s role in Apple’s ongoing legal disputes over App Store rules has grown more consequential as regulators and legislators at both state and federal levels test the boundaries of what Apple can require from developers and users alike.
Texas’s approach may attract imitation. If the law survives its legal challenge, other states have a working template for pushing age verification obligations onto platforms rather than publishers. Apple would then face a patchwork of state-level requirements that could be difficult to reconcile with a single global App Store architecture.
For users in Texas, the practical reality is that creating a new Apple Account now involves an age confirmation step that did not exist before. If you already have an account, the immediate impact depends on how Apple interprets the law’s application to existing users, which remains an open question as the litigation continues. Adults who run into verification friction should check Settings and work through Apple’s verification flow rather than assuming a bug is responsible.
0 Comments