Since then the documentation has been updated and now the property is consistent with being available for exactly iOS 26.2+. Also there is a paragraph, related to its availability for macOS: In macOS, isEligibleForAgeFeatures returns false because the system doesn’t require Age Assurance for the person or device. However, you can still call requestAgeRange in macOS to get the declared age range. Thus we shouldn't use this property in macOS at all, which is rather inconvenient.

@DTS Engineer thanks for your reply! Though most of the info is clear, I find some insights worth additional clarifying: based on your reply, is it correct that as of now there is no requirement to implement Declared Age Range API for macOS apps? based on your reply, is it correct that this policy applies ** only to the new** Apple Accounts, created in TX after Jan 1st 2026 (as well as UT, LA, after their respective deadline dates)?