APP STORE August 31, 2026 · 4 min read

Apple's Updated Kids Category Rules: What Changes Before September Submission

Apple tightened its Kids Category guidelines ahead of iOS 26, reflecting new age-verification laws in the US, UK, and EU. Here's what changes — and what every developer targeting younger audiences must do before the fall review rush.

By the AppsOps news desk · August 31, 2026 · Original source ↗

With the September submission window opening and iPhone 17 launch reviews already filling Apple's queue, a quieter but significant update to the App Store Review Guidelines is catching developers off guard: Apple revised its Kids Category requirements ahead of iOS 26, tightening rules around age-gating, data collection, and third-party SDK use. If your app targets children — or sits in a category Apple might consider adjacent — here's what changed and what you need to do before you submit this fall.

Why Apple Is Tightening the Kids Category Now

Legislative pressure has been mounting globally. In the United States, updated federal proposals have expanded the definition of child-directed content beyond traditional age-13 cutoffs. The UK's Age Appropriate Design Code ("Children's Code") has been in force for several years and has generated enforcement actions against major platforms. The EU's Digital Services Act layered on further obligations for platforms with meaningful reach to younger users.

Apple's response has been to push accountability upstream to developers. Rather than gatekeeping at the platform level alone, the updated guidelines make it explicit that developers are responsible for ensuring their apps comply with applicable child-directed regulations in every territory they distribute to — and that Apple will reject apps that appear to target children while evading Kids Category restrictions through mis-categorization.

What's New in the Kids Category Rules

No third-party analytics or ad SDKs — this has long been the rule, but Apple has clarified that SDKs collecting device identifiers, even for non-advertising purposes (crash reporters that transmit IDFVs, for example), must be evaluated and potentially removed or replaced.
Age-neutral experiences for "mixed audience" subcategory — apps in the Ages 4+ subcategory must now demonstrate the experience works appropriately for younger users, not merely that adult-only content is blocked.
Stricter parental gate requirements — any in-app purchase flow or external link must sit behind an age-verification mechanism Apple considers sufficient. Generic "tap to confirm your age" prompts are no longer considered adequate.
Simplified subscription disclosure — auto-renewable subscriptions in Kids Category apps must now present pricing in plain language that Apple describes as "immediately understandable to the child's parent or guardian," with pricing shown upfront at the SKU level before any gate.

What This Means for Developers Submitting This Fall

The timing matters. Apple's App Review queue gets congested in the two weeks following the iPhone launch. Apps targeting the Kids Category — education tools, early learning apps, creative apps for children — that fail review during this window often miss the initial launch-window discovery boost entirely. A rejection mid-September can cost weeks of visibility at exactly the moment new iPhone owners are exploring the App Store.

Before you submit, run through this checklist:

Audit every third-party SDK against Apple's Kids Category prohibition on off-device device signals. Remove or replace anything that transmits identifiers.
Test your parental gate with someone unfamiliar with your app. Can they clearly identify what they're approving? Can a determined child bypass it in a few taps?
Review your subscription pricing flow end-to-end. Is the price clearly stated before the parental gate, in plain language? Does your disclosure hold up across your target territories?
Check your App Privacy nutrition labels. Kids Category apps face heightened scrutiny — if you recently added a new SDK or API, your label may need updating before submission.

Reports suggest Apple reviewers are also applying more scrutiny to apps outside the Kids Category that carry cartoon aesthetics, character-based UI, or school-subject content. The safe move: add your own age-gating proactively and document your design rationale in the App Review Notes field when submitting.

Territory-Specific Considerations

This is where it gets complex at scale. A Kids app shipping to 30+ territories faces different regulatory floors in each. What constitutes sufficient parental consent in the US may not satisfy the UK's Children's Code. Germany's requirements differ from Brazil's. If you're distributing broadly, you may need territory-specific variants of your privacy flows or age-gate mechanisms.

Managing that kind of per-territory variance in App Store Connect manually — pricing, availability, metadata — is exactly the problem AppsOps was built to help with. The territory management view and PPP pricing tools keep your multi-market setup clean; the localization cost calculator helps you model what a full territory rollout actually costs before you commit. If you're also revisiting your Kids app's description and keyword metadata to align with the new guidance, the AppsOps blog has deeper coverage of metadata strategy for the fall cycle.