Starting on March 29, 2021, apps submitted to the Google Play Store must receive approval to access location in the background.
This is a good thing for end users, because it requires apps to follow privacy best practices and justify why they need to access location in the background.
But following privacy best practices and submitting a justification does require some effort on your part.
Google provides a number of resources that we'd recommend reading in full, including:
In this post, we share our own tips and best practices for getting approved based on our experience working with Radar customers.
If your app accesses location in the background, you will need to complete a location permissions declaration form in the Google Play Console when submitting your app.
The form requires you to:
When reviewing your submission, Google will consider:
While these criteria are subjective, they are relatively clear and easy to follow.
Importantly, you control all aspects of your submission, including:
As such, we recommend the following to maximize the likelihood that your app is approved:
If you fail to satisfy any of these criteria, your submission may be rejected.
A prominent disclosure shown to users before the runtime OS background permissions prompt that explicitly includes the phrases "location," "background," and "when the app is closed."
If your app targets Android 10 (API level 29) or higher and includes the ACCESS_BACKGROUND_LOCATION
permission in your manifest, you must submit for approval.
If your app targets API level 28 or lower (i.e., before the ACCESS_BACKGROUND_LOCATION
permission was introduced), includes the ACCESS_FINE_LOCATION
permission in your manifest, and uses location when the app is closed without starting a foreground service, you must submit for approval.
However, if your app does not include the ACCESS_BACKGROUND_LOCATION
permission and only uses location when the app is closed when starting a foreground service (e.g., during a curbside pickup, during a delivery, or during navigation), you DO NOT need to submit for approval.
Below is the Radar Toolkit video walkthrough that received approval from Google, including (1) a "core purpose" and feature of the app that requires background location, (2) the "prominent disclosure" that explicitly mentions "location" and "when the app is closed," and (3) the feature being activated from the background.
While features like location-based offers or reminders may seem to be in a gray area, and while Google's review criteria are subjective, the more you indicate that this is part of the "core purpose" of your app (i.e., why a user would download your app), and the more that this is part of your app description and branding, the stronger your case for getting approval.
Embrace this opportunity to follow privacy best practices and justify to your end users (and to Google) why background location helps you deliver impactful, valuable app experiences.
Location unlocks impactful app experiences, from curbside pickup and delivery tracking to location-based content and notifications, but permissions and app store requirements are always in flux. If you're looking for a partner to help you navigate these requirements, reach out to our team. We're here to help!
See what Radar’s location and geofencingsolutions can do for your business.