Age verification that once affected only social apps like Instagram and Discord is now being rolled into the operating systems that run our devices. What began as a gate at the app level is becoming a gate at the point where you first set up a computer or phone.
If you use Windows, macOS, or a smartphone in an affected state, this change matters. Setting up a new device could soon require entering your birthdate before you can complete any other configuration steps, and that age information may be shared with apps you install afterward. This shifts where and how age data is collected, and it changes who controls the first interaction between users and their devices.
It Started With Apps. Now It’s Your Whole Computer.
California’s Digital Age Assurance Act, signed into law in 2025, mandates that every operating system sold or used in the state collect a user’s age at account setup beginning January 1, 2027. The law instructs systems to sort users into four distinct brackets: under 13, 13 to 15, 16 to 17, and 18 or older. That bracketed result is intended to be passed to any app that requests age information, which means age-based restrictions or content filtering can be applied more broadly and consistently across software ecosystems.
Other states are moving in the same direction. Colorado and Illinois have enacted similar requirements, and New York is considering legislation that would follow a comparable approach. Penalties for noncompliance are notable: companies that fail to follow these rules can face fines, with higher amounts assessed if violations appear intentional rather than accidental. Those consequences create a strong incentive for platform makers and device vendors to implement age-gating at the operating system level.
Apple has already piloted aspects of this approach in other markets: the company enabled age checks for iPhone users in the UK, for example, where skipping the prompt can cause an account to be treated as a minor’s and trigger additional content restrictions, such as blurred images and tightened filters. That deployment offered a preview of how system-level age controls can affect everyday device use.
Privacy Groups Call It a Step Too Far
The idea of moving age verification into the operating system has drawn pushback from privacy and civil liberties groups. The Electronic Frontier Foundation and other organizations argue that system-level age checks can create barriers to accessing information online, particularly for households where multiple people of different ages share a single device. When account setup requires a birthdate entry up front, the device itself becomes the point of enforcement rather than the individual apps, reducing users’ choice over which services enforce age limits and how.
There is also a practical honesty problem. Many of the new laws do not require a government-issued ID, facial recognition, or any other independent proof of age; they rely on the user entering a birthdate at setup. That means someone can provide false information and bypass restrictions, which weakens the intended protection for minors while still centralizing the collection of sensitive age data. Centralized collection raises concerns about how long that data is stored, who it is shared with, and how securely it is handled.
Age gates used to be confined to individual websites and apps—places people could avoid or opt out of when they chose. Now the gate is moving to the device itself, the one thing nearly everyone touches daily. For users in California, Colorado, or Illinois, expect to see a birthdate prompt the next time you set up a new computer or phone. Even where laws are not yet finalized, the trend toward OS-level verification is gaining momentum and could influence device setup flows more broadly.
For consumers, this development means thinking ahead about the devices you buy and where you live. It also suggests a shift in responsibility: platform vendors will need to design account setup experiences that are clear about how age data is used and shared, while policymakers and privacy advocates will continue debating the trade-offs between protecting minors and preserving open access to information. In the short term, if you are setting up a new device in an affected state, be prepared to enter a birthdate and to consider how that information will influence subsequent app behavior and privacy settings.