Google will expand age checks on Android worldwide till the end of the year

Original Article ↗ Hacker News Discussion ↗

Google’s plan to roll out a Play Services “Age Signals” API worldwide, allowing apps to query a user’s age range, is framed as child protection and regulatory compliance but is widely viewed as a step toward deeper identification, surveillance, and platform lock‑in. Commenters argue that while age‑based safeguards and better parental controls are legitimate goals, tying them to government ID checks, centralized accounts, and app‑level enforcement risks eroding anonymity, strengthening corporate and state control over internet access, and normalizing intrusive verification for everyone, not just children.

Perceived Purpose and Motivations

  • Many commenters see the feature less as child protection and more as infrastructure for surveillance, identity binding, and platform lock‑in.
  • Others argue a simpler motive: Google complying with proliferating age‑regulation laws and protecting Play Store revenue by centralizing compliance.
  • A minority sees it as a pragmatic improvement over every app doing its own ID+selfie checks.

How the System Works and Design Critiques

  • API returns age ranges (e.g., 0–12, 13–15, 16–17, 18+) and can be configured via parental controls; apps can request ranges and, in some cases, trigger stronger verification (ID/selfie).
  • Critics note it’s tied to Google Play Services and accounts, not to AOSP/device alone, further entrenching Google.
  • Concern that today it’s optional and range‑based; tomorrow it could default to “locked” unless you complete KYC, as some claim already happens in parts of Google’s ecosystem and on other platforms.

Privacy, Surveillance, and Slippery Slope

  • Strong fear that “think of the children” is a pretext for:
    • Normalizing digital ID and ending anonymity.
    • Enabling government or corporate power to lock individuals out of devices and services.
    • Creating an “internet no‑fly list.”
  • Slippery‑slope examples cited: EU chat scanning, Apple UK moves, mandatory ID checks for porn, and city‑level surveillance cameras.

Parents vs. State vs. Market

  • One camp: parenting has failed at scale; only regulation can counter addictive algorithms and harmful content.
  • Counter‑camp: responsibility must remain with parents; government or platform taking over is inherently authoritarian and easily abused.
  • General distrust that corporations or random third‑party verifiers can handle sensitive IDs without abuse.

Alternative Proposals

  • Device‑level age or “child mode” set by parents at setup; apps and browsers read only a coarse flag, no external verification.
  • Content rating/metadata systems (PEGI‑like, HTTP headers) plus robust, interoperable parental controls, no age proof.
  • Government‑issued cryptographic attestations or ZK proofs that reveal “over X” but not identity; some argue even these will be misused or correlatable.

Broader Effects and Reactions

  • Concern about reinforcing big‑tech monopolies and mandatory accounts.
  • Some users discuss fleeing to de‑Googled ROMs (GrapheneOS, Lineage) or alternative platforms.
  • Several note that harms targeted (addiction, manipulation, scams) affect adults too; fixing those systemically might obviate age verification.