Microsoft is overhauling how Windows 11 handles child safety and account privacy by moving age verification directly into the operating system.

Usually, whenever an app or game on your PC needed to gate mature content, comply with child safety laws (like COPPA), or manage in-app transactions, it had to handle age verification, which meant asking for your date of birth, payment details, or third-party identity checks, or even the weak honor-system “I am 18+” checkbox.

Instead of you having to give this data, upcoming system-level APIs in Windows 11 will provide registered applications with your age range, such as 13-15 or 18+, and a status indicating whether your age has been independently verified.

The company says that this is to help developers adjust content, restrict features, and apply parental controls without forcing them to collect or store your birthday, as regulators across the UK, EU, and the U.S. push for stricter online age assurance laws.

What are Windows 11’s new age signals, and what will apps see?

First spotted by Windows Latest, Microsoft’s official age signals documentation states that “The Windows Age APIs provide a privacy-preserving mechanism for apps to determine the age group and age verified status of the signed-in user.”

The gist is that an app can ask two questions: what age bracket the user falls into, and whether that bracket was independently confirmed.

Apps don’t get your birthday. Microsoft says an age signal doesn’t directly expose the user’s age or date of birth. Instead, GetUserAgeRangeAsync returns one of five ranges.

The 18+ result uses INT32_MAX as the limit. A game or media app doesn’t need to know someone is exactly 14 years and 8 months old, only whether they fall below a threshold, and Microsoft’s range system adjusts it.

The second signal is to verify the age. Another API, GetAgeVerificationStatusAsync, can return Verified, Unverified, OptedOut, TemporarilyUnavailable, or NotApplicable, indicating whether the age was independently verified by the identity provider. It’s available to both first-party and third-party callers.

Of course, age range and age verification aren’t the same thing. Someone can have an age range attached to their account without it being verified.

Windows also checks who is asking

Microsoft says the Digital Safety platform validates the calling app’s identity before returning meaningful values, and apps must be registered with that platform first.

So, it’s not like every app you install on your PC can read your age signal. Its intended use cases are for things like user-generated content, social features, in-app purchases, and mature-rated media.

Why is Microsoft doing this now?

Microsoft’s documentation says the APIs help apps comply with child-safety regulations, and the regulatory push is much bigger than Windows.

UK: regulators want platforms to know who is a child. Ofcom requires age assurance to be highly effective in terms of technical accuracy, robustness, and reliability for its Online Safety Act. Its July 2026 Use of Age Assurance Report also rules out age inference for minimum-age enforcement, since it only works after a child has already used a service long enough to be inferred from.

EU: privacy-preserving proof of age is the preferred direction. The European Commission’s age verification approach avoids forcing services to collect unnecessary identity information. Its solution, called the mini wallet, lets users prove they’re over 18 without sharing anything else, and can adapt to other thresholds like 13+ or 65+.

U.S.: States are already pushing for operating-system-level mandates, led by California’s Digital Age Assurance Act of 2026 in August. It would make operating system providers the primary source of age signals for apps and certain websites. The bill isn’t a national ID card proposal, since it rules out requiring government ID or biometric scans.

Note that the FTC’s February 2026 COPPA policy statement said it would not pursue certain enforcement actions against age-verification data collection when the data is used only to determine age, isn’t retained longer than necessary, and is properly secured.

Google and Apple already have their own age signals

Google Play has an Age Signals API. Google’s Play Age Signals overview describes an API in beta returning default ranges of 0-12, 13-15, 16-17, and 18+, with custom ranges available too.

Google’s model adds a sharing-status layer; a result can indicate age signals are shared, not shared, or that verification is required, and in some U.S. states, users may need to verify age or set up supervision through Google Play. Google’s terms prohibit developers from using this data for advertising, marketing, profiling, or analytics.

Apple’s approach is slightly different. Apple’s Declared Age Range documentation gives developers an age range based on the age gates an app requests.

For children in Family Sharing, a parent or guardian can set whether age information is always shared, not shared, or requested app by app. Apple distinguishes self-declared or guardian-declared information from information confirmed through a government ID or payment method, and notes developers remain responsible for their own age restrictions.

How Windows developers will be able to use the age signal

Both GetUserAgeRangeAsync and GetAgeVerificationStatusAsync appear in the Windows.System.User API reference, along with the GetUserAgeRangeAsync page and the GetAgeVerificationStatusAsync page, both listed against Windows 11, version 24H2, and highlighted as prerelease information.

I checked the Windows SDK release notes and saw that Microsoft mentioned that these aren’t yet enabled at runtime, but will be enabled later this year:

“The age signal APIs (User.GetUserAgeRangeAsync, User.GetAgeVerificationStatusAsync, UserAgeRange, and UserAgeVerificationStatus) are documented ahead of availability. They aren’t enabled at runtime yet, and are planned to be turned on in a future release later this year.“

The developer workflow, per Microsoft’s implementation guide, is simple. The app gets the current user through User::GetDefault(), calls GetUserAgeRangeAsync(), and Windows returns the range or null, and the app makes its own content decision from there.

It can also call GetAgeVerificationStatusAsync() for verification state. Every call currently returns an unknown range and unavailable status, so the guide instructs developers to fall back to normal behavior or their own age-gating mechanism until the APIs turn on.

The API doesn’t mean Microsoft takes responsibility for every app’s age restrictions. The developer still decides what to do with the signal, which is a limitation that Apple also mentioned.

The privacy trade-off is more complicated, though

As you may have figured out by now, if we don’t have an OS-level signal, an app that needs to distinguish children from adults may have to build its own age-assurance system, collecting a date of birth, identity documents, payment information, facial-age estimates, or other evidence. Microsoft, along with other tech giants, is trying to avoid making every app collect this data itself.

The trade-off is that trust moves toward the platform, and unfortunately for Microsoft, Windows has very little of it. The OS becomes the intermediary that determines or receives age-related information and decides what signal an app is allowed to see.

Microsoft’s documentation confirms the API doesn’t return a birthday and that the caller’s identity gets validated, but it doesn’t explain every method Microsoft might use to establish an account’s age in the first place!

Windows is trying to make age verification a platform feature

Rest assured that Microsoft won’t give away your DOB to Windows. Redmond is building an operating-system-level age signal that returns age ranges and a separate verification status.

The UK wants more effective age assurance, the EU is building privacy-preserving proof-of-age infrastructure, the FTC is trying to reduce issues with age verification, and U.S. lawmakers are considering their own OS-based age-signal framework. Whether this ultimately improves privacy depends on what happens between the OS and the app, but if we compare it with giving every app your birthday or an identity document, an age-band signal clearly gives less information about you.

The post Windows 11 will start telling apps your age, but Microsoft says it won’t share your birthday appeared first on Windows Latest