Windows 11 Age Signals: Here's Exactly What Apps Will and Won't See About You

Windows 11 age signals are arriving, and they’ll let apps know your age bracket without ever learning your birthday. Microsoft is baking age verification directly into the operating system, which could quietly change how games, social apps, and media platforms treat you online.

According to Microsoft’s official documentation, the new 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 premise is straightforward: instead of every app collecting your date of birth, payment details, or third-party identity checks, Windows hands over a coarse age range plus a separate flag for whether that range was independently confirmed.

Here’s what actually changes, who can use it, and why Microsoft is moving on this now.

What Windows 11 age signals actually return

The core of the change is two new APIs that live in the Windows.System.User reference, both listed against Windows 11, version 24H2 and flagged as prerelease.

The first, GetUserAgeRangeAsync, asks one question: which age bracket does the signed-in user fall into? It returns one of five ranges, not a specific age.

Under 10 (0-9)
10-12
13-15
16-17
18+ (18 and above, using INT32_MAX as the upper limit)

A game or media app doesn’t need to know you’re exactly 14 years and 8 months old. It only needs to know whether you’re below a certain threshold, which is why Microsoft returns bands instead of a precise number.

The second API, GetAgeVerificationStatusAsync, answers a different question: was that age range independently confirmed? It can return one of five values — Verified, Unverified, OptedOut, TemporarilyUnavailable, or NotApplicable — indicating whether an identity provider actually checked the age.

Importantly, age range and age verification are separate signals. You can have an age range attached to your account that has never been verified, and an app can receive both values independently.

Who can actually read these signals

Not every app you install will be able to query your age. Microsoft says its Digital Safety platform validates the calling app’s identity before returning any meaningful value, and developers must register their app with that platform first.

In practice, this means the feature targets specific use cases: user-generated content, social features, in-app purchases, and mature-rated media. It isn’t a free-for-all where any random app can peek at your demographic.

Why Microsoft is moving now

The documentation frames these APIs as a way to help developers comply with child-safety regulations, and the regulatory pressure is global.

UK: Ofcom’s Online Safety Act requires age assurance to be technically robust and reliable. A July 2026 Use of Age Assurance Report explicitly rules out age inference for minimum-age enforcement, arguing it only works after a child has already used a service long enough to be inferred from.
EU: The European Commission favors privacy-preserving proof-of-age. Its “mini wallet” lets users prove they’re over 18 without handing over other identity data, and can adapt to other thresholds like 13+ or 65+.
U.S.: California’s Digital Age Assurance Act of 2026, introduced in August, would make operating system providers the primary source of age signals for apps and certain websites. It deliberately rules out requiring government ID or biometric scans.
FTC: A February 2026 COPPA policy statement said the FTC 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 do this

Microsoft isn’t the first to try OS-level age signals.

Google Play ships a beta Age Signals API returning default ranges of 0-12, 13-15, 16-17, and 18+, with custom ranges available. It adds a sharing-status layer — results can indicate signals are shared, not shared, or that verification is required — and its terms forbid developers from using the data for advertising, marketing, profiling, or analytics.

Apple takes a slightly different route with its Declared Age Range documentation, giving developers an age range based on the age gates an app requests. For children in Family Sharing, a parent can choose whether age information is always shared, never shared, or requested app by app, and Apple distinguishes self-declared or guardian-declared data from information confirmed via government ID or payment method.

How developers will use the signals

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

It can also call GetAgeVerificationStatusAsync() for the verification state. Right now, every call returns an unknown range and an unavailable status, so Microsoft instructs developers to fall back to their own age-gating logic until the APIs turn on.

Microsoft was explicit about timing. In the Windows SDK release notes, it wrote that these APIs “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.”

One caveat worth noting: the API doesn’t make Microsoft responsible for an app’s age restrictions. The developer still decides what to do with the signal — a limitation Apple also flags.

The privacy trade-off

If there were no OS-level signal, an app needing to distinguish children from adults would have to build its own age-assurance system, collecting dates of birth, identity documents, payment info, or even facial-age estimates. Microsoft’s approach aims to stop every app from collecting that data independently.

The trade-off is that trust shifts toward the platform. For Windows, that’s an awkward position, given the OS’s track record with user trust. The OS becomes the intermediary that determines or receives age-related information and decides exactly what an app is allowed to see.

Microsoft’s documentation confirms no birthday is returned and that the caller’s identity is validated — but it doesn’t spell out every method Microsoft might use to establish an account’s age in the first place.

What this means for you

For most users, the practical effect is subtle. You won’t be asked to hand over your birthday to individual apps and games, and mature-content gating should rely on a single, system-managed signal instead of a pile of third-party identity checks.

For parents, the age-range and verification flags give apps a more reliable way to enforce parental controls and COPPA-style restrictions without you typing in personal details.

The catch is that you don’t yet control how much Windows reveals — that depends on how the APIs and your account settings are wired up when they finally ship later this year.

How to get it

The signals aren’t available to end users yet. They’re prerelease documentation tied to Windows 11, version 24H2, and Microsoft says they’ll be enabled at runtime in a future release later this year.

Developers can start building against the documented APIs now, but should implement fallbacks for the “unknown range, unavailable status” responses the calls currently return. Regular users will see the feature arrive as part of a future Windows 11 update — there’s no separate download or opt-in to expect today.

Source: Windows Latest

Over to you: Would you feel more comfortable handing your age to Windows as a single platform signal, or to each app individually?