Hi, I am working on an app intended to be a mobile version of a dating webstie. While compiling the age rating questionnaire, the app was rated improperly to what the actual content and intended use case is. The app does not display mature/violent/**** content of any sorts (including picture sharing between users, which are verified and must be approved by the website service before they can be shared at all - no **** content of sorts is allowed), and does not make any references to drugs, alcohol, and other option listed in the questionnaire (all answers are "NONE"). Thus, it scores a 4+ rating. However, the service provided through the app, and the use case, is clearly not intended for any young audience - and the service requires the audience to be 18 years of age, or older. Admittedly, you need to register an account with the website in order to use (log in) the app - which is where the age restriction actually comes in - but that's not a valid reason, in my opinion, to apply a 4+ rating. I would like not to "force hands" and report that the app displays any mature content or other such options. But it seems there is no option to manually apply a different age rating. How can I change the app rating such that it properly matches the intended use case? Google, for example, allows to select a different (higher) age range if the app qualifies for one of the low age categories. Is there any way to do this with iOS apps? If not, how should this age rating be interpreted at all?

Hi, The Expo SDK, in the managed workflow, includes an API bundle package that allows some internal APIs to access the IDFA. However, not every app will use the APIs that interact with the IDFA. Moreover, the IDFA is not exposed outside the internal APIs, there is no way to actually read the IDFA value directly and make use of it - only the internal APIs can do so, and only if you use such APIs. The new app store connect App Privacy requirements however, contains a few entries, that make it mandatory to indicate that you're using some data type for tracking and advertising purposes, only because - technically - the IDFA can be accessed by the app. While I understand the reason, I don't find it fair to indicate that an app is actually tracking the user. I am working on a number of apps with the Expo SDK, which do not have any intention of (and do not use any APIs for) tracking the user. Is there an option in this scenario in which we can indicate to app store connect that an app is not tracking the user, even if the Expo SDK has access to the IDFA? More information about IDFA in expo: docs.expo.io/distribution/app-stores/#ios-specific-guidelines forums.expo.io/t/getting-apple-idfa-and-android-equivalent/3175