Want to download an app? Google might ask for your ID first 🛑

Cliquez ici pour lire en français

Imagine this: you’re about to download an app on your Android phone—something you’ve done a thousand times before. But this time, Google stops you cold. “Prove you’re 18.” ID card. Selfie. Credit card. No other options. That’s the new reality on the Play Store, and it’s sparking serious conversations about online privacy.

Why now? Legal pressure is mounting 📜

Google isn’t doing this for fun. Several U.S. states—Texas, Utah, and Louisiana among them—have passed laws requiring app stores to verify users’ ages. The deadlines are coming fast: January 2026 for Texas, May for Utah, and July for Louisiana.

The stated goal? Protect minors from adult content. A noble idea on paper. In practice, it’s a lot messier. Even Google has raised concerns, warning that these laws could threaten user privacy by forcing companies to collect personally identifiable information.

The Play Store hosts more than 3.5 million apps. Sure, some are clearly for adults—dating apps, mature games, streaming platforms—but this new gatekeeping fundamentally changes our relationship with our phones.

How it works: four methods, zero privacy 🔐

Google offers four ways to verify your age:

• Upload a government-issued ID
• Take an AI-assisted selfie
• Verify through a refundable credit card charge
• Or use a third-party service like Verifymy.io

On paper, Verifymy.io sounds like the most privacy-friendly option. It doesn’t ask for biometrics or IDs—instead, it scans your email address to estimate your age based on where you’ve used it before. Clever? Maybe. Reliable? Not really.

If your email’s digital footprint is thin—or if you’re using a newer address—the system can’t make a call. And when that happens, you’re back to the invasive methods: ID, selfie, or card.

The big problem: false positives and shaky accuracy 🚨

Here’s where things get messy. Since YouTube rolled out age verification earlier this year, adult users have reported being mistakenly flagged as minors—forced to verify with sensitive data like selfies, credit cards, or passports.

Reddit and X are flooded with complaints from frustrated adults in their 30s and 40s who suddenly can’t access videos or apps without scanning their passport. Some even lost access to Google Search after failing the verification check—a chilling escalation.

AI-powered facial age estimation also raises fairness and accuracy concerns, especially across ethnic groups. Facial recognition algorithms have a well-documented history of bias.

Privacy: the real cost 🔓

Let’s be honest. Handing Google your ID, face, or credit card info just to download an app is a tough pill to swallow. Many users feel uneasy sharing such personal data with a company that already knows so much about them.

And their worries are justified:

• Data retention: How long will Google keep this information?
• Data leaks: No database is 100% secure.
• Data sharing: Utah’s law even requires app stores to share users’ age information with all developers—without parental consent or limits on how that data can be used.

Google has built a beta API called Play Age Signals to reduce how much data is passed to developers. Still, one question lingers: why should we have to choose between our apps and our privacy?

A messy rollout, a fragmented experience 🌍

The rollout isn’t uniform. Some users never see a verification prompt, while others are asked for full ID scans. Verification methods also vary by country—Verifymy.io isn’t even available everywhere.

That inconsistency makes for a confusing experience. Two users, same app, same platform—one downloads freely, the other is blocked unless they upload government ID.

The impossible trade-off 🤔

Here’s the paradox: no one wants 10-year-olds downloading explicit content. Protecting minors matters. But this approach feels like using a jackhammer to drive a nail.

Better options exist: robust parental controls, account-level checks instead of app-by-app barriers, and zero-knowledge proof systems that confirm age without exposing identity. Google is already exploring such privacy-preserving technologies, allowing users to prove they’re over 18 without revealing personal details like name or birthdate.

But for now, we’re stuck with a system that often misfires, collects sensitive data, and creates more friction than actual protection.

Between protection and surveillance ⚖️

The Play Store’s age verification rollout perfectly captures the tension of the digital age: how do we protect without surveilling? Secure without intruding?

Google’s hands are tied by new laws, and the company itself has expressed unease about what this means for privacy and user trust. But for users, it’s a lose-lose scenario: surrender personal data or lose access to legitimate apps.

The problem isn’t age verification itself—it’s the lack of a global, privacy-respecting standard that actually works. We deserve better than a system that locks out adults, over-collects data, and behaves differently depending on your ZIP code.

The technology to fix this already exists. The real question is: will we use it before this flawed system becomes the global norm?

What do you think?
Have you hit one of these age checks yet? Would you share your ID just to download an app—or is that a line you’ll never cross? Share your thoughts below. 👇