Kids App update was rejected by google play after using Yandex

[echogit]

After implementing Yandex ads on my app, I sent an update to google and got the reasons below.

Have anyone else being able to publish "Designed for Families" (DFF) app to Google Play using Yandex?

If that is not possible, it should be clearer on the documentation, I just spent at least 4 days of work doing this integration.

I declared on google play that my app doesn't collect or share any user information .

I also configured on the AndroidManifest.xml:

     <meta-data
          android:name="@string/yandex_mobileads_age_restricted_user"
          android:value="true" />

I read somewhere that it could be because of the "appmetrica" which is part of the yandex_mobileads package.

Is there any way to use yandex on a kids target app?

App Status: Rejected
Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Invalid Data safety form
We reviewed your app’s Data safety form in Play Console and found discrepancies between it and how the app collects and shares user data. All apps are required to complete an accurate Data safety form that discloses their data collection and sharing practices - this is required even if your app does not collect any user data.

We detected user data transmitted off device that you have not disclosed in your app’s Data safety form as user data collected.

You must ensure that your app’s Data safety section accurately reflects your app’s data collection, sharing, and handling practices. This includes data collected and handled through any third-party libraries or SDKs used in your app. When available, we’ve included details on SDKs that contain code similar to the code in your APK that may be sending user data off device. You can check if your app uses any of these SDKs, but note that this list of SDKs may not be exhaustive. You must review and account for all data collected and shared by your app.

Issue details

We found an issue in the following area(s):

Version code 57: Policy Declaration - Data Safety Section: Device Or Other IDs Data Type - Device Or Other IDs (some common examples may include Advertising ID, Android ID, IMEI, BSSID, MAC address)
About the Data safety section in Google Play User Data policy
Your app must be in compliance with this policy. If your app continues to be non-compliant, your app updates will be rejected and your app may face additional enforcement actions in the future.

Please make changes to align your app’s Data safety form with the app’s behavior. This can be done by either:

Updating your form in Play Console to declare collection of Data Types noted below; or
Removing unwanted functionality and attributable code that collects this user data from your app or libraries used in your app, and when applicable to deactivate all non-compliant APKs.
To deactivate non-compliant APKS, you can create a new release and upload a compliant APK to each track containing the non-compliant APKs.
Be sure to increment the APK version code. If using staged rollout, be sure to set the release to 100% rollout.

[mobile-ads-github]

Спасибо за Ваше обращение, для разбора создана задача с номером ADLIBGITHUB-6. Мы ознакомимся и вернемся с ответом как можно скорее, возможно запросим дополнительную информацию.

Thank you for your message, a task with the number ADLIBGITHUB-6 has been created for analysis. We will get acquainted and return with the answer as soon as possible, we may request additional information.