I suppose a scope for either could both potentially have their uses: Seeing if they are ID or Phone verified (or both!) could help confirm that a user is a genuine user.
On the topic of age-gating, following the recent release of 17+ Experiences, some Developers on the ClearlyDev platform have recently started publishing assets that could potentially require a game’s age-rating to be marked 17+.
If we can safely use a Roblox User’s Age Range - as could be returned by the oAuth2 Flow with a scope - we would be able to ensure that Roblox Content Policies are being upheld, even though they are off the Roblox Platform itself.
We could obviously integrate our own ID Verification system powered by a third-party provider, however as the number of users using our Roblox Authentication option increases, we think it could be beneficial if this data was returned by Roblox itself, as it is already proven to be viable data.