Requesting access to location in the background

Academy Logo

Free training.

Learn more well-nigh how you can minimize your utilise of device location and view examples of the device location declaration on the University for App Success.

Yous can now submit your app for feedback on location in the background access by completing the Location permissions announcement grade in Play Console.

Your app should not request access to location in the groundwork unless it's required. If your app requests admission to location in the background just it's not critical to the app'southward core functionality, you must remove it from your app and/or implement location admission in the foreground, such as when your app's activity is visible to users. You tin can observe details on policy compliant implementation below.

The post-obit video provides information nigh declaring permissions and providing in-app disclosures:

All apps that access location in the background will need to be approved or app updates may exist blocked and your app may be removed from Google Play.

About the process

First Apr 1, 2022, all apps must also post a privacy policy in the Google Play Console and inside the app itself.

When reviewing your app, we'll consider:

  • Does the feature deliver articulate value to the user?
    • Examples of feature categories that deliver pregnant user benefits include physical prophylactic, perceived safety, and wellness/fettle. Examples of feature categories that have minimal user benefit based on user location may include ads, analytics, personalization, entertainment, and convenience.
  • Would users look the app to admission their location in the groundwork?
  • Is the feature of import to the cadre purpose of the app?
  • Can you deliver the same experience without accessing location in the background?

Note: This list is not exhaustive, but intended to requite yous an thought of how your apps apply of location permissions may be reviewed and interpreted.

Core functionality is defined every bit the main purpose of the app. This may comprise a gear up of core features, which must all exist prominently documented and promoted in the app'south clarification. Without the core characteristic(s), the app is "cleaved" or rendered unusable.

Get blessing for your app's admission to location in the background

Earlier you start

You should complete these steps before you consummate the permissions announcement form to declare your app's admission to location in the groundwork. They'll help yous understand best practices for accessing location information, alternative options, and how you can brand location data access clearer to users.

Step 1: Review all-time practices for accessing location

Empathise requirements

Developers must meet the following requirements for accessing location data in their apps:

  • You should never request location permissions from users for the sole purpose of ad or analytics.
  • Groundwork location may but be used to provide features beneficial to the user and relevant to the cadre functionality of the app.
  • Apps designed specifically for children must comply with the Designed for Families policy.
    • Tip: Visit Google Play's Academy for App Success to better understand Google Play'south Families policies.

Review best practices

We encourage all developers to review the following best practices for accessing location data in their apps:

  • Review the background location access checklist to identify any potential access in your lawmaking. Remember that you are too responsible for ensuring all third-party SDKs or libraries that you use comply with our policies, including employ of location permissions. All app bundles or APKs across all active release tracks (including internal test, closed, and open tracks) are subject to review.
  • Minimize your use of location by using the minimum scope necessary to provide a characteristic (i.e., coarse instead of fine, foreground instead of background). Users should reasonably expect that the feature or service needs the level of location requested. For instance, we may refuse apps that request or access background location without adequate justification.
  • Review privacy all-time practices and ensure that yous take the proper disclosure and privacy policies in place.

Step ii: Consider alternatives to accessing location in the background

Apps are allowed to access location using foreground service (when the app just has foreground access, east.one thousand., "while in use") permission if the use has been initiated every bit a continuation of an in-app user-initiated activeness, and is terminated immediately after the intended use case of the user-initiated activity is completed by the application.

Access to location is considered in the foreground if it happens while the app is open up and visible to the user. If the user closes the app, or hits the home button to render to their main screen, and then the app'south access to location is considered in the background.

Location in the foreground examples

Below is a listing of potential features that can frequently be used with access to location in the foreground instead. Having these features does non hateful that your app will be automatically rejected. Still, if these features are the just reason your app requires access to location in the background, then the chances of rejection are college.

  • Propose nearby friends/players/connections to add simply when the user is in the app (excludes suggesting nearby friends/players/connections while the app is closed)
  • Personalized in-app content based on user location (i.east., music playlist for home, local news, etc.) without any notification/alarm/characteristic to user when the app is airtight
  • Restrict content to enforce region-based digital rights management
  • Commitment/service (for example, food, package, or ride) tracking on the user side (non driver)
  • Turn-past-plough navigation (not applicable if any functionality is done while the user is exterior the app, such as passive tracking of routes/steps, monitoring when a user starts or stops driving, etc.)
  • Accumulation user location data to show traffic patterns/high congestion points or map nearby internet speeds

Note that this is not an exhaustive list, and each app will be evaluated based on its declared cadre functionality. Still, if your app only has functionalities such equally those above that crave use of location in the background, please consider replacing location access in the background with access to location in the foreground instead.

Step 3: Brand access to location in the background clear to users

If y'all plan to use location in the background in your app, you should communicate this to users in the Google Play store listing via your app clarification, screenshots, and (if applicable) title or icon.

Here are some suggestions on how to highlight use of location in the groundwork to users:

  • Provide a short clarification to signal "location" (for example, "observe anywhere" or "always know where").
  • Include an in-app screenshot that shows a map/user location or geotagged images.
  • If applicable, your app title or icon may likewise signal the location feature of your app.

Proclamation requirements

When completing the permissions declaration form, you'll also demand to complete the steps beneath and so Google can evaluate your app's access to location in the background.

Footstep 4: Provide a video demonstration

As part of the permissions announcement, you must provide a link to a short video that demonstrates the location-based characteristic in your app that requires access to location in the groundwork (while the app is not in use).

Yous tin can see an case of what this video sit-in should expect like below.

Encounter an example video demonstration

Video requirements

The video should demonstrate the groundwork location feature and the required steps to run into and enable this feature in-app. The video should show:

  • The feature being activated from the background
  • The prominent in-app disclosure dialog displayed to users (described beneath)
  • Runtime prompt

The recommended duration is 30 seconds or less. A YouTube link is the preferred video format, but Google Drive storage links to an mp4 or other common video file formats are as well supported.

Note:

  • If the feature does not have a user-facing interface when location in the groundwork is active, please annotation this in your declaration and demonstrate the feature or its impacts every bit much as possible in the video.
  • Ensure your video is made using an Android device.

Step 5: Provide prominent in-app disclosure

If your app accesses location in the background, you must provide an in-app disclosure of your data access, collection, use, and sharing.

You lot can see an example of an acceptable in-app disclosure below.

See an example of prominent in-app disclosure

In-app disclosure requirements

The in-app disclosure:

  • Must be within the app itself, not just in the app description or on a website;
  • Must be displayed in the normal usage of the app and not require the user to navigate into a menu or settings;
  • Must draw the information existence accessed or nerveless;
  • Must explain how the data volition be used and/or shared;
  • Cannot merely be placed in a privacy policy or terms of service; and
  • Cannot be included with other Disclosures unrelated to personal or sensitive data collection.
  • Does non need explicit consent such as an "have" or "I understand" granted by the user equally this is done in the runtime prompt that immediately follows; enabling the user to close or swipe abroad are acceptable means to drift out of the disclosure.

The language in the disclosure MUST include the following elements:

  1. The term "location"
  2. Indication that the nature of usage is in the background past using one of the following phrases "background"/"when the app is closed"/"always in use"/"when the app is not in use"
  3. A list of all the features that use location in the background
  4. If you extend permitted usage to ads, you must include the following: "used to provide ads/support advertising/support ads." (Choose the well-nigh accurate phrasing).

Recommended disclosure statement formats

To meet the policy requirements, it's recommended that you reference the following case formats. The 2nd case includes the use of location for ads .The employ of location data for ads purposes must be in compliance with the Use of Location Data for Ads policies. Choose the most relevant phrasing:

  • "[This app] collects location data to enable ["feature"], ["feature"], & ["feature"] even when the app is closed or not in apply."
  • "[This app] collects location data to enable ["feature"], ["feature"], & ["feature"] even when the app is closed or not in use and information technology is also used to support advertising."

    Case: "Fitness Funds collects location data to enable fitness tracking even when the app is closed or not in utilise."

The prominent disclosure may include other information to ensure compliance to policy requirements and clarity for users simply must at least include the above, where relevant.

Notation: If the feature does not have a user-facing interface when location in the background is active, please surface the prominent disclosure notification when the app is opened for the get-go time instead.

Privacy policy

Calculation a privacy policy to your app's shop listing helps provide transparency nigh how you treat sensitive user and device data. The privacy policy must, together with whatever in-app disclosures, comprehensively disclose how your app collects, uses, and shares user data, including the types of parties with whom it's shared. You lot should consult your ain legal representative to advise you lot of what is required.

  • Y'all must link to a privacy policy on your app's store list page and within your app.
  • Make sure your privacy policy is available on an active URL, references to your app, and specifically covers user privacy.
  • If your app uses location in the groundwork, your privacy policy must contain appropriate related disclosures, reference location information, and provide data about the app's usage of location data.
  • Ensure your privacy policy page is clearly labeled as such in the title or URL and within the trunk of the page.

Learn more

Frequently asked questions

Can I publish app updates while still working on Location compliance?

Prior to policy enforcement dates (January 18, 2022 for all new apps and March 29, 2022 for all existing apps), y'all may publish app updates without beingness compliant with Location policy.

To exercise this, re-submit (you lot can utilize the same Android App Package or APK and version), under "Declare sensitive location permission", select "No, this release does non come across the Location permission policy." This will allow you lot to publish app updates without doing through Location review while you lot're standing to work towards making your app compliant.

My app has multiple features that apply location in the groundwork. What should I do?

Y'all can merely declare one app feature that uses location in the background for review. If your app contains multiple features that are both core to the app'southward purpose and utilize location in the background, select the characteristic that provides the nearly significant benefit to the user.

For case, a social networking app that uses location in the background to notify users of nearby offers and to let users to continuously share their location with friends. The friend sharing characteristic should exist used on your permission proclamation equally it delivers more user benefit (connexion/utility) than the location-contextual ads (convenience/personalization).

Google Play will establish location in the background eligibility based upon review of the primary app feature you lot declare; even so approval is contingent upon using location in the background is granted at the app level. It is your responsibility to ensure that any other features that may use location in the background are policy compliant. This includes meeting requirements pertaining to prominent user-facing in-app disclosure, as described in the "Prominent disclosure" department above.

Where practice I find the proclamation?

The Location permissions declaration grade volition be bachelor in Play Console on September 30, 2020. Y'all can detect the form here manually past going to the App Content page, clicking Start under "Sensitive App Permissions," so clicking Start under "Location Permissions."

If you're seeing prompts for other forms such as App Access Rights or Authorization Announcement Grade, please complete these start every bit they're required steps in preparing your app for review in Play Console. Go to Ready your app for review for detailed instructions.

If you do not see the declaration prompt in Console, please ostend that y'all are using one of the sensitive location permissions co-ordinate to the target SDK level of your app:

  • If your app bundle or APK targets Android ten or newer (SDK level 29 or higher) and contains ACCESS_BACKGROUND_LOCATION permission in the manifest, y'all volition be directed to complete details on location usage
  • If your app bundle or APK targets Android 9 or older (SDK level 28 or lower) and contains either ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION, you will need to indicate your intention to access location in the background and then you will and then be directed to complete details on location usage.

What if I have an old APK with Location permissions and can't make code changes?

If you have former APKs with Location permissions and you are no longer able to make lawmaking changes to these APKs y'all may apply for a policy exception.

In order to qualify for the exception, you lot must come across ALL of the following requirements:

  • You must declare the specific APK(s) for which you would like an exception.
  • The APKs requesting an exception must take been published before January ane, 2019.
  • You must have alternative APKs served to users on Android Oreo (API Level 26) or higher, and these must exist compliant with the Location permission policy.
  • The APKs requesting an exception must represent a very pocket-size pct (no more than than low single-digit %) of your total install base of operations.

Google Play will review the asking and grant exceptions on a case past instance basis. Alternatively, you may choose to unpublish the violating APKs to exist compliant with the Location permissions policy.

What inputs will I demand to provide in the proclamation?

The Location announcement asks you to provide inputs to the following questions:

  1. App purpose: What is the main purpose of your app?
  2. Location access: Why does your app need access to location in the background?
    1. Tell us about 1 location-based feature in your app that requires access to location in the background, and explain why it tin can't be implemented without this access. The feature should exist related to the master purpose of your app. Approving will be granted for your entire app, not just for this single characteristic.
    2. Delight annotation that we can only evaluate one feature at a time and inclusion of multiple features will upshot in the rejection of your app.
  3. Video instructions: Provide a link to a short video which shows the feature yous've described above being used in your app. The video should include the prominent disclosure dialog that is shown to users. Recommended thirty seconds or shorter.

Is permission approval perpetual and when exercise I need to update?

It is the developer's responsibleness to ensure that apps that are canonical for Groundwork Location usage remain compliant in all future submissions. App updates will be reviewed in accord with Play policies; material changes to your app may impact your app's approval for Groundwork Location and result in additional reviews. If in that location is a change in app characteristic using Background Location, please submit a new Declaration form and it will exist reviewed appropriately.

How practice I remove location in the groundwork?

If you accept adamant that your app does not crave location in the groundwork, complete the following steps to remove background usage and achieve compliance. Please annotation that you lot volition demand to submit your app for review if the post-obit permissions are used in any app bundles or APKs, including non-production tracks. You can find a listing of impacted app bundles or APKs in Play Console on the App content page (Policy > App content > Sensitive App Permissions > Show Summary):

  • If you lot previously had any non-compliant app bundles or APKs accessing background location, make sure the not-compliant versions are not in any of your current releases, even if you exercise not use sure tracks.
    • Open the App bundle explorer page (Release > App package explorer) to check whether a certain version is active.
    • When submitting a new app bundle APK to supplant the previous, not-compliant app package or APK, delight make sure the non-compliant app parcel or APK is nether the "Non included" section before rolling out the new release.
      • For further guidance, see the "Not included" section in the Prepare and roll out a release article.
    • Ensure that any new, compliant release is rolled out to 100% and completely deactivates non-compliant app bundles or APKs.

If you are nonetheless facing issues after examining your code paths and restricting usage to foreground purposes just, please review whatsoever tertiary-party SDKs used in the app that may be accessing location in the background.

Related content

  • Learn more about declaring permissions in Play Console
  • Larn more nigh building location-aware apps on the Android Developers site
  • Acquire more than about permissions on the Android Developers site
  • Learn more nearly permissions workflow on the Android Developers site
  • Learn more than about privacy all-time practices on the Android Developers site
  • Read our User Information policy

Was this helpful?

How can we ameliorate it?