Snapchat Uses Apple's Age Range to Block Underage Users

In a significant move amidst ongoing debates about teen social media access and age verification, Snapchat is now utilizing Apple's "Age Range for Apps" feature to restrict underage users. This development could pave the way for a more universal and effective age-checking process across social media platforms, potentially shifting some of the responsibility from apps to app store providers.

Snapchat's New Age Verification System

Snapchat has confirmed it is integrating Apple's "Age Range for Apps" qualifiers to identify and block users who do not meet the minimum age requirements. This feature, available on Apple devices running iOS 16 or later, allows apps to receive an age range from the user's device, helping ensure age-appropriate experiences.

As per Snapchat's support page:

"On Apple devices running iOS 16 or later, Age Range for Apps shares your age range with apps to help keep experiences age-appropriate. If you are 13 or older, you can set this feature up yourself. If you are under a Family Sharing group, a parent or guardian will need to help manage your age range and related controls in Family Sharing settings."

Apple's "Age Range" process enables parents to share their child's age information and can require permission for app download requests based on these age brackets. These categories are derived from Apple's app age rating system, which was updated in February to offer more granular categorization, particularly for teen audiences.

How it Works for Snapchat Users

When users sign up for, log into, or open Snapchat, they may encounter a prompt to share their age range. Apple shares only the age range, not an exact birthday. If the shared age range meets Snapchat's minimum age requirements, access is granted. Conversely, if the age range falls below the local minimum, users will be unable to access the app.

Snapchat further notes that if users decline to share their age, and local regulations mandate age verification, they may be prompted to verify their age through k-ID. k-ID is a third-party age verification service for younger users, which Meta is also reportedly planning to use to confirm user ages.

This comprehensive approach provides Snapchat with a robust age-checking mechanism, verified by Apple and supported by a third-party tool, to more effectively detect and restrict underage users. Such systems are becoming increasingly crucial as more regions consider stricter laws on teen social media access and impose harsher penalties for violations.

The Broader Debate: App Stores vs. Platforms

This implementation by Snapchat resonates strongly with a long-standing argument put forth by companies like Meta. Meta has consistently called for Apple and Google to implement universal age-checking processes at the app store level. Currently, the onus largely falls on individual platforms to verify user ages and block younger users, leading to a fragmented landscape of varying effectiveness and placing platforms at risk of significant financial penalties for non-compliance.

Meta's proposal suggests that app store providers are better positioned to conduct these checks universally, applying them to all apps downloaded by a user, rather than requiring each app to implement its own system. Centralizing age verification at the download stage would ensure consistent standards across all applications. However, this would also mean that responsibility and potential penalties for violations would shift to Apple and Google, a burden neither company has been eager to assume.

Despite their success in avoiding this responsibility thus far, Snapchat's integration demonstrates that Apple possesses the capability to facilitate broader-scale age checking. While Apple might argue that its "Age Range" qualifiers are merely ranges and not compulsory (with parents opting into the process), this system highlights the potential for a more effective barrier to young user access.

If Apple were to make this process compulsory and implement broad-scale age checking at the download level, all social apps could be restricted for users under a certain age from a single entry point. While this wouldn't affect users who have already downloaded apps, it could offer a more universal and practical approach to app access restrictions for future users, simplifying management and implementation of age-based controls. As Meta has argued, implementing such blocks at the app store level makes logical sense, scaling restrictions under consistent parameters and lessening the burden on individual apps to develop similar measures.