GoogleのPlayストアに「プライバシー保護」年齢確認システムが導入Google's "privacy-preserving" age verification system is coming to the Play Store

Google is introducing a new age verification system for the Play Store that aims to confirm whether users meet age requirements without forcing them to hand over sensitive personal information. The approach matters because age checks have become a legal flashpoint worldwide, and many existing methods require users to upload government identification or submit to face scans, raising significant privacy concerns.

At the center of the rollout is a new application programming interface, or API, that developers can use to determine a user's age range. Rather than collecting documents or biometric data directly, the system relies on parents to set age ranges for their children through Family Link, Google's parental control service. When a child uses a device managed through Family Link, an app can query the API and receive a signal about the user's age bracket, which the app can then use to tailor its experience or restrict certain content.

Family Link, first launched several years ago, lets guardians create supervised Google accounts for children, approve app downloads, set screen time limits, and monitor activity. By tying age signals to information parents already provide when setting up these accounts, Google appears to be repurposing an existing framework rather than building an entirely new identity check from scratch. This design is likely intended to reduce the amount of new personal data flowing to app developers.

The privacy framing is central to how Google is positioning the feature. Traditional age assurance methods often demand that platforms or third parties collect and store identifying documents, creating databases that can be breached or misused. By passing along only an age range and keeping the underlying account details within Google's own system, the company argues the approach limits exposure of the individual data that a full identity verification would reveal. Whether the system delivers on that promise in practice will depend on implementation details and how developers handle the signals they receive.

The move arrives amid a broader regulatory push to keep minors away from age-inappropriate content and services. Several US states have passed laws requiring age verification for adult websites and, in some cases, social media, and lawmakers have debated placing more responsibility on app stores rather than individual apps. The UK's Online Safety Act and various European Union initiatives have similarly pressed platforms to introduce stronger age checks. App store operators, including Google and Apple, have faced growing pressure to serve as a first line of age assurance, since they sit at the point where software is distributed and often already know something about the account holder.

There are limitations worth noting. A system that relies on parents to set age ranges in Family Link primarily addresses accounts that are actively supervised. Adults and teenagers using unsupervised accounts would not be covered by that specific mechanism, so the API is likely one component of a wider set of age-assurance tools rather than a complete solution on its own. The accuracy of the age signal also depends on parents entering correct information, and children can potentially access unmanaged devices or accounts.

For developers, an API-based approach could simplify compliance by letting them request an age signal from Google instead of building or licensing their own verification systems. That could be particularly appealing for smaller studios that lack the resources to implement document scanning or third-party identity checks. It may also help standardize how age information is requested across the Android ecosystem, though adoption will depend on how many developers choose to integrate the API and how regulators view its reliability.

The announcement fits a pattern in which platform owners try to balance legal obligations, child-safety expectations, and user privacy simultaneously. Apple has outlined its own age-range sharing features that similarly aim to give developers a coarse age signal without exposing exact birth dates, suggesting the two dominant mobile platforms are converging on comparable models. As these systems mature, the key questions will likely center on how accurately they classify users, how transparently the data is handled, and whether regulators accept parent-set ranges as sufficient proof of age.