Summary
Google rejected the app because sensitive permissions are overbroad, poorly justified, or not supported by prominent disclosure and store forms.
Google Play App Review issue
Google Play sensitive permissions rejected
Google rejected the app because sensitive permissions are overbroad, poorly justified, or not supported by prominent disclosure and store forms.
google play sensitive permissions rejectedplay sensitive permissions rejectiongoogle play permission declaration rejected
Fix Google Play review issues before the next submission
Use LogicSpring to run a free precheck, regenerate the right policy or disclosure pack, and shorten the loop from rejection notice to resubmission.
What this means
Google expects sensitive permissions to be tightly scoped to a user-benefiting core feature.
The Play Console form, in-app disclosure, and policy all need to explain the same reason for access.
A valid technical implementation can still be rejected if the disclosure package is weak.
Common causes
- Location, media, contacts, accessibility, or background permissions are requested too early or too broadly.
- The prominent disclosure appears after the system prompt or is too vague to be meaningful.
- The declared permission use case differs across form, policy, and in-app copy.
Step-by-step fix
- Step 1
Remove every nonessential sensitive permission from the manifest and SDK tree.
- Step 2
Write a clear pre-permission disclosure shown before the system prompt.
- Step 3
Update policy and store forms so the same narrow use case appears everywhere.
What to update
- AndroidManifest
- Prominent disclosure UI
- Permission declaration forms
- Privacy Policy permission sections
How LogicSpring helps
- LogicSpring precheck reviews permissions, disclosures, and policy wording together before review.
- You can regenerate the policy sections that need to match permission forms instead of editing them in isolation.
- This is particularly useful for launch teams managing AI, camera, and location features across fast release cycles.
FAQ
Can I resubmit to Google Play without changing the binary?
Only for pure listing or form corrections. If the shipped build still requests the wrong permission, bundles the wrong SDK, or behaves inconsistently, resubmitting the same build is risky.
What evidence should I prepare before resubmitting?
Prepare the updated public policy URL, the exact store fields you changed, screenshots for permission or disclosure flows where relevant, and a short reviewer note explaining what changed and why it now matches the app.
Should the privacy policy, store form, and in-app disclosure all match?
Yes. Review teams compare these surfaces together. If one says you collect or disclose something and another says you do not, the mismatch itself often becomes the next rejection.