Google Play location permissions policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps requesting approximate, precise, foreground, or background location.
Google looks at how much location access the feature actually needs. Request the narrowest scope, stop when the purpose ends, and don’t collect location solely for advertising or analytics.
Match scope to the task
Could approximate location or foreground-only access complete the feature? We’d test those options before asserting that precise or background access is essential. Background use needs a beneficial core purpose and the background-location requirements.
Correct the access lifecycle
Ask in context and respect refusal. Location use through a foreground service under foreground permission must continue a user-initiated action and stop when that action’s intended use finishes. A persistent service isn’t permission for unrelated tracking.
Test starting, ending, denying, and leaving the feature. Inspect actual requests and SDK use. Give Google the task, scope, and evidence that collection stops appropriately. Children’s apps have additional restrictions under the Families policy.
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: Location permissions Checked 22 September 2026