GrapheneOS refuses to comply with new age verification laws for operating system

Privacy rebels or virtue signalers? GrapheneOS says “no IDs,” internet explodes

TLDR: GrapheneOS says it won’t add age checks at setup, even as Brazil and California move to require them. Commenters split: some hail a bold pro-privacy stand, others call it virtue signaling—especially with a Motorola phone on the way that may force real-world compliance or restricted sales.

GrapheneOS just planted a privacy flag: no age checks, no accounts, no IDs—period. The internet lit up like a comment-section bonfire. Team Free-Phone cheered the stance as a win for anonymity, linking the project’s defiant Mastodon post. Team “Think of the Children” fired back that it’s empty posturing unless phones ship with it preinstalled. Cue the popcorn.

The timing is spicy: Brazil’s new law threatens massive fines (up to about $9.5M per violation), California’s 2027 law forces operating systems to ask your age at setup and share it with app stores via a real-time pipeline, and Colorado is lining up too. Critics say the rules build surveillance with a paper-thin gate—self-reported birthdays—so the memes flowed: the classic “I was born in 1900” age check is back in rotation. One commenter even pitched “malicious compliance”: let people type a random birthday and call it a day. Another called the whole move “virtue signaling,” since GrapheneOS doesn’t sell phones right now.

Then came the twist: GrapheneOS is pairing with Motorola, eyeing a 2027 device. The thread immediately asked the obvious—how does a privacy absolutist OS square with global rules? Meanwhile, comparisons to other rebels (like calculator firmware DB48X and Brazil-banning MidnightBSD) turned this into a full-blown culture-war episode over age-gates, jurisdiction, and where the line between safety and surveillance actually sits.

Key Points

  • GrapheneOS stated it will not implement age verification at setup, prioritizing privacy even if it limits regional device sales.
  • Brazil’s Digital ECA (Law 15.211) took effect March 17, imposing fines up to R$50 million per violation for OS noncompliance.
  • California’s AB-1043 (effective Jan 1, 2027) requires OS providers to collect user age/date of birth at setup and share it via a real-time API; penalties are enforced by the state attorney general.
  • Colorado’s SB26-051 passed the state senate with similar age-verification requirements for operating systems.
  • Motorola and GrapheneOS formed a partnership to ship GrapheneOS on future Motorola devices by 2027, which may necessitate regional compliance or restricted sales.

Hottest takes

"How's that gonna pan out with Motorola?" — echelon_musk
"Seems like a pure virtue signaling" — Svoka
"Let the user enter a random birth date" — OutOfHere
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.