Age Verification

Apple’s latest kid-safety update is “for families,” unless your family is a developer filling out paperwork. Then it’s for the form. Somewhere in App Store Connect, “social media” has become a selectable capability that determines how Time Allowances treats the app—because nothing says protection like turning your child’s feed into whichever bubble the questionnaire thinks is closest.

Here’s the human version: an app’s social-media capabilities—redistributing/amplifying/interacting with user-generated content through a feed—map to a “Social Media” content descriptor. After that, the app-time system can route that app into the Time Allowances “Social Media” grouping, and under-13 handling follows whatever Apple’s rules say to do next. Depending on the setup, that can mean disabling social-media experiences for under-13 users or using Apple’s Declared Age Range API to confirm age ranges. Parenting, but make it a deadline-driven scheduling boss fight.

And yes, Apple can tell the story as “parents get better tools.” But the mechanism is the opposite of what you’d want from a privacy promise: the outcome hinges on whether a developer clicked the right capability box—and whether their age-range declarations line up with what’s actually inside the app. That’s not magic parental empowerment; that’s compliance UI acting like a toll booth, where “agree” is the cart that rolls your assumptions straight into the platform’s sorting hat.

This is the part where the crowd goes “wait, really?” and Apple goes “Terms of Surrender, we’ve always been this way.” The joke is that the “agree” step doesn’t just take your lunch money—it takes your kids’ feed and labels it by the nearest form field. Privacy should protect humans; instead, it’s scheduled by checkbox.