Publishing Status
Publishing status: Rejected
Your app has not been accepted into Google Play. This does not affect your existing app’s status on Google Play
Reasons of violation
Eligibility issues by versions
Version(s) Eligibility Issue
App Bundle:169
APK REQUIRES PROMINENT DISCLOSURE
The app is uploading users' Installed Application information to https://c-hzgt2.getui.com without a prominent disclosure. Prior to the collection and transmission, it must prominently highlight how the user data will be used, describe the type of data being collected and have the user provide affirmative consent for such use.
For further details on the valid prominent disclosure requirement, please review the “Prominent Disclosure & Consent Requirement” section under the User Data policy.
App Bundle:169
APK HAS A PRIVACY POLICY BUT IT IS NOT ADEQUATE
Privacy Policy in Play Console
The app is uploading users' Installed Application information to https://c-hzgt2.getui.com without disclosing it in the privacy policy in Play Console.
Next steps: Submit your app for another review
- Review the issues and any policy page(s) shown above.
Review best practices for prominent disclosure as guidelines for your prominent disclosure.
For the relevant policy requirements, refer to the "Prominent Disclosure and Consent Requirement" section in the User Data policy. - Make appropriate changes to your app, and be sure to address the issues identified above.
- Upon making the required changes, check if your app is compliant with the User Data policy and all other Developer Program Policies.
- For violations requiring APK/App Bundle level updates, deactivate the non-compliant version and upload a compliant version with an incremented version code.
In addition to your Production release, if you have other release types that you use for testing and/or quality assurance checks (for example, Internal test, Closed, Open), please make sure to update those tracks as well. - Sign in to Play Console, go to App bundle explorer and select the track with the policy issue (Internal / Closed / Open testing / Production). Click Manage track > Create new release.
If the release with the violating app bundles/APKs are in a draft state, discard the release.
Otherwise, add the policy-compliant version of app bundles/APKs.
Make sure that the non-compliant version is under the "Not included" section of this release.
Enter a release name and click Save. Once saved, click Review release, and then proceed to roll out the release to 100% and completely deactivate the non-compliant APK. - If the non-compliant versions are released to multiple tracks, repeat step 5 in each track.
If approved, your app will again be available with all installs, ratings, and reviews intact.
