Publishing status: Rejected - Google APK HAS A PRIVACY POLICY BUT IT IS NOT ADEQUATE
Budget: $30 – $250 USD
APK HAS A PRIVACY POLICY BUT IT IS NOT ADEQUATE
Privacy Policy in Play Distributed App
Your app is uploading users' Social Account information to https://www.afrotradegroup.com without posting a privacy policy in Play Distributed App.
PK HAS A PROMINENT DISCLOSURE BUT THE DISCLOSURE IS NOT ADEQUATE
Your app is uploading users' Social Account information to https://www.afrotradegroup.com without an adequate disclosure.
For further details on the valid prominent disclosure requirement, please review the “Prominent Disclosure & Consent Requirement” section under the User Data policy.
Next steps: Submit your app for another review
1. Review the issues and any policy page(s) shown above.
For issues related to Privacy Policy and Prominent Disclosure, refer to the “Privacy Policy” and “Prominent Disclosure & Consent Requirement” sections in the User Data policy. Additionally, for further guidance on prominent disclosure, review best practices for prominent disclosure.
2. Make appropriate changes to your app, and be sure to address the issues identified above.
3. Upon making the required changes, check if your app is compliant with all Developer Program Policies.
4. For violations requiring APK/App Bundle level updates, deactivate the noncompliant 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 required changes and update those tracks as well.
5. For creating a new release, 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.
6. If the noncompliant 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.
Privacy Policy in Play Distributed App
Your app is uploading users' Social Account information to https://www.afrotradegroup.com without posting a privacy policy in Play Distributed App.
PK HAS A PROMINENT DISCLOSURE BUT THE DISCLOSURE IS NOT ADEQUATE
Your app is uploading users' Social Account information to https://www.afrotradegroup.com without an adequate disclosure.
For further details on the valid prominent disclosure requirement, please review the “Prominent Disclosure & Consent Requirement” section under the User Data policy.
Next steps: Submit your app for another review
1. Review the issues and any policy page(s) shown above.
For issues related to Privacy Policy and Prominent Disclosure, refer to the “Privacy Policy” and “Prominent Disclosure & Consent Requirement” sections in the User Data policy. Additionally, for further guidance on prominent disclosure, review best practices for prominent disclosure.
2. Make appropriate changes to your app, and be sure to address the issues identified above.
3. Upon making the required changes, check if your app is compliant with all Developer Program Policies.
4. For violations requiring APK/App Bundle level updates, deactivate the noncompliant 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 required changes and update those tracks as well.
5. For creating a new release, 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.
6. If the noncompliant 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.