How to Fix Google Play Permissions Declaration Rejection
Remove unnecessary sensitive permissions or prove core-functionality eligibility with an accurate declaration and review video.
What this rejection usually means
A sensitive-permission rejection usually means the requested access is not essential to the app's core functionality, the use case is not eligible, or the declaration and demonstration do not prove the actual production behavior.
Likely rejection signals
- Manifest includes sensitive permissions added by an SDK or old bundle
- Declared use case does not match the core user-facing feature
- Review video omits the permission-dependent flow
- Inactive testing tracks contain noncompliant bundles
Recovery plan
- Audit the merged manifest of every active bundle and track, including SDK-added permissions.
- Remove sensitive access that is optional, historical, or replaceable with a narrower system picker or API.
- Map each remaining permission to an eligible core-functionality use case.
- Complete the declaration accurately and provide a public review video showing the full permission-dependent flow.
- Deactivate obsolete noncompliant artifacts and retest the signed bundle.
Evidence to prepare
- Merged-manifest permission inventory
- Core-functionality explanation
- Accessible demonstration video
- Reviewer credentials and active-track inventory
Appeal or fix first?
Clarify when the permission is eligible, indispensable to the app's primary purpose, and fully demonstrated in the submitted declaration.
Fix first when the permission is unnecessary, SDK-inherited, replaceable, or unsupported by the declared core use case.
Reviewer response framework
Your response should be factual, short, and limited to the submitted build. Cover these points:
- Name each sensitive permission.
- Tie it to a user-visible core feature.
- State what was removed or narrowed.
- Provide a working review video and credentials.
Frequently asked questions
Can an SDK cause the rejection?
Yes. Permissions merged from libraries are part of your bundle and remain your responsibility.
Can I publish while the declaration is pending?
Sensitive-permission review can delay publication; removing ineligible permissions is often the fastest compliant path.
Need a rejection-specific plan?
Start with the free diagnosis. The $29 Fix Pack adds the prioritized remediation plan, evidence checklist, reviewer-ready reply, and preflight.
Source: Google Play permissions declaration guidance. Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.