Microsoft is set to transform the landscape of child safety and account privacy within Windows 11 by integrating age verification directly into the operating system. Traditionally, when applications or games required age verification to manage access to mature content or comply with child safety regulations, users were often asked to provide sensitive information such as their date of birth or payment details. This process frequently relied on the honor system, with users simply checking a box to indicate they were over 18.
With the introduction of upcoming system-level APIs, Windows 11 will allow registered applications to access users’ age ranges—such as 13-15 or 18+—without disclosing their actual birthdays. This initiative aims to assist developers in tailoring content, restricting features, and implementing parental controls while adhering to the growing demands for stricter online age assurance laws across regions like the UK, EU, and the U.S.
What are Windows 11’s new age signals, and what will apps see?
According to Microsoft’s documentation, the new age signals provide a privacy-preserving mechanism for applications to ascertain the age group and verification status of users. Essentially, an app can inquire about two key aspects: the user’s age bracket and whether that bracket has been independently confirmed.
Apps don’t get your birthday. The age signal does not reveal a user’s exact age or date of birth. Instead, the GetUserAgeRangeAsync function returns one of five defined ranges:
| Windows signal | Range |
|---|---|
| Under 10 | 0-9 |
| 10-12 | 10-12 |
| 13-15 | 13-15 |
| 16-17 | 16-17 |
| 18+ | 18 and above |
The 18+ designation uses INT32_MAX as a threshold, allowing applications to ascertain whether a user meets a minimum age requirement without needing precise details about their age. Furthermore, another API, GetAgeVerificationStatusAsync, can indicate whether the age was independently verified, offering statuses such as Verified, Unverified, OptedOut, TemporarilyUnavailable, or NotApplicable. This functionality is accessible to both first-party and third-party applications.
Windows also checks who is asking
To ensure security, Microsoft’s Digital Safety platform validates the identity of the calling app before providing any age-related information. Consequently, not every application installed on a user’s PC will have access to these age signals. The primary use cases for this data include user-generated content, social features, in-app purchases, and mature-rated media.
Why is Microsoft doing this now?
Microsoft’s initiative aligns with a broader regulatory push for enhanced child safety measures. In the UK, Ofcom is advocating for robust age assurance mechanisms as part of its Online Safety Act, which emphasizes the need for technical accuracy and reliability. Meanwhile, the European Commission is promoting privacy-preserving proof of age, allowing users to verify their age without disclosing unnecessary personal information.
In the U.S., states are moving toward operating-system-level mandates for age verification, exemplified by California’s Digital Age Assurance Act of 2026. This legislation positions operating system providers as the primary source of age signals for applications and websites, steering clear of proposals that would require government IDs or biometric scans.
Google and Apple already have their own age signals
In the realm of age verification, both Google and Apple have established their own systems. Google Play features an Age Signals API that returns default age ranges and allows for custom ranges, while also incorporating a sharing-status layer that indicates whether age signals are shared or require verification. Apple’s approach, on the other hand, offers developers an age range based on the age gates requested by an app, with options for parents to control the sharing of age information.
How Windows developers will be able to use the age signal
Developers will find both GetUserAgeRangeAsync and GetAgeVerificationStatusAsync within the Windows.System.User API reference. Although these features are documented, they are not yet enabled for runtime use, with plans for activation later this year. The implementation guide outlines a straightforward workflow, allowing apps to retrieve the current user and determine their age range or verification status, thereby enabling informed content decisions.
The privacy trade-off is more complicated, though
While the introduction of OS-level age signals aims to alleviate the burden on individual applications to collect sensitive data, it also shifts the responsibility of trust toward the platform itself. Microsoft’s documentation assures users that their birthdays will remain confidential, but the specifics of how age is initially determined remain somewhat ambiguous.
Windows is trying to make age verification a platform feature
In essence, Microsoft is striving to establish a comprehensive operating-system-level age signal that conveys age ranges and verification statuses without compromising user privacy. As regulatory bodies push for more effective age assurance, the success of this initiative will hinge on the interplay between the operating system and applications. Ultimately, by providing a less intrusive alternative to sharing personal information, Microsoft is paving the way for a more secure digital environment.
