Permissions like location, contacts, or SMS need a clear, declared use case tied to core app functionality — Google reviews these more strictly than most other policy areas.
Why apps actually get flagged
Requesting a broad permission (e.g. background location) for a feature that could work with a narrower one is the most frequent trigger.
A real example
"Your app requests permissions that are not adequately declared or justified for its core functionality."
The short version, in more detail
Some Android permissions are considered sensitive, such as SMS, call logs, background location and broad file access. Google Play only allows them for apps whose core feature depends on them, and asks developers to submit a declaration that explains why. Apps that request more than they need, or that use these permissions for a feature that is not central, can be rejected or removed.
What this guideline covers
Permissions classed as sensitive, including SMS, call log, background location and all-files access.
The permissions declaration form in Play Console and the information it asks for.
The expectation that a sensitive permission supports the app's core functionality.
Permissions that arrive in the merged manifest from third-party libraries.
How and when permissions should be requested from users.
What usually triggers this rejection
The manifest lists a sensitive permission that the core feature does not need.
A library adds a permission to the merged manifest that the developer did not choose.
The permissions declaration form was not completed or does not match how the app works.
The app asks for access on first launch with no explanation or alternative.
Background location, SMS or call-log access is requested for a feature that could work without it.
How reviewers evaluate it
Google reads the declaration and compares it with what the app does.
It checks the merged manifest, not just the permissions the developer wrote.
It asks whether the permission is essential to the app's main purpose or only convenient.
A video or description demonstrating the feature may be requested.
Common misunderstandings
Not every permission needs a declaration. Only the sensitive categories do.
A permission in your build is not necessarily one you added. Dependencies can introduce them.
Being useful is not the same as being core. Play looks for the main purpose of the app.
Common questions
Why was I asked about a permission I never wrote into the manifest?
A dependency can add permissions to the merged manifest during the build.
What is the difference between foreground and background location?
Foreground access is while the app is in use. Background access continues when it is not, and has a stricter policy.
Do declarations expire?
Play can re-check them, so a declaration is tied to how the app behaves over time, not just at the first release.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.