Microsoft advances privacy-focused age checks in Windows 11 to support child safety and regulatory compliance

Microsoft is introducing deeper integration of age signals into Windows 11, enabling apps to determine user age groups without revealing personal details, aligning with global child-safety regulations and reducing data collection.

Microsoft is preparing to move age checks for Windows 11 deeper into the operating system, so apps can be told whether a signed-in user falls within an age band without being given a date of birth. The change is designed to help developers enforce child-safety rules, content limits and in-app purchase controls while collecting less personal data. According to Microsoft’s documentation, the new age APIs are intended to give apps the user’s age group and a separate verification status, rather than exact birth details.

The system exposes two main signals. One returns a broad age range, such as 10-12, 13-15, 16-17 or 18+. Another returns whether that age has been verified, with statuses including Verified, Unverified, OptedOut and TemporarilyUnavailable. Microsoft says the caller must first be registered with its Digital Safety platform, which is meant to stop arbitrary apps from querying the signal. The company also says the APIs are built to support compliance with child-safety regulation, rather than to create a universal identity system.

That timing reflects pressure well beyond Microsoft’s own platform. In the UK, Ofcom is pushing for age assurance that is technically accurate, robust and reliable under the Online Safety Act. In the EU, the European Commission has been steering services towards privacy-preserving proof of age, including a model that lets users confirm they are over 18 without disclosing unnecessary identity information. In the US, Microsoft’s move comes as states explore operating-system-level age-signal requirements, while the Federal Trade Commission has said it will not pursue certain COPPA-related enforcement actions when age-verification data is used only for age checks, kept only as long as necessary and properly secured.

Microsoft is not alone in this direction. Google Play already offers an Age Signals API with age ranges and sharing-status controls, while Apple’s Declared Age Range framework lets apps receive an age band that can be set or requested by parents and guardians in Family Sharing. All three approaches aim to reduce the need for individual apps to collect identity documents, payment data or other direct proof of age. The trade-off is that more trust shifts to the platform itself, and Microsoft has not fully detailed how an account’s age is established in every case.

For developers, Microsoft says the implementation is straightforward: an app calls the Windows user APIs, receives an age range or a null value, then decides how to gate content or features. The company says the functions are documented ahead of runtime support and will be enabled later. In the meantime, apps are expected to fall back to existing checks. Microsoft’s broader privacy settings in Windows still leave users able to manage features such as advertising identifiers, app-launch tracking and suggested content, but the new age signals show that the company wants age gating to become a platform feature rather than an app-by-app burden.