Google Play background location policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps accessing location when the user isn't actively using the relevant app screen.
Background location needs more than a convenient implementation. Google limits it to a feature beneficial to the user and central to the app’s purpose, with a convincing need for that level of access.
Demonstrate the core task
Write down what fails if location stops when the app leaves the foreground. We’d test a foreground-only design first. Check the listing, permission declaration, and in-app explanation against the actual task.
Explain before collecting
Meet the prominent disclosure and consent requirements and Google’s linked background-location review instructions. Request the minimum scope and remove unused background permissions from the bundle. A background SDK needs the same scrutiny as your own code.
Test opt-in, refusal, stopping the feature, and returning to the app. Provide the requested review evidence showing the feature and disclosure. If a foreground service is appropriate, follow its user-initiation and stopping conditions; changing the service label doesn’t justify otherwise unnecessary tracking.
Messages this guide can help with
Background location; Background location policy violation; Background location rejection; Background location denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Background location Checked 22 September 2026