Google Play · Background Location Permission

How to Fix Google Play Background Location Permission Rejection

Audit the exact AAB, move ineligible location access to foreground scope, or prove one indispensable background-location feature with a compliant declaration and video.

Policy-grounded recovery guideOfficial policy ↗
Have the rejection message open?Get a free diagnosis now. Upgrade to the complete $29 Fix Pack only if it is useful.
Analyze this rejection →

Direct answer

Start with the exact signed AAB and every active release track. If ACCESS_BACKGROUND_LOCATION—or equivalent background access through a service, SDK, job, geofence, or pending intent—is not indispensable to one prominently advertised core feature, remove it and use foreground, coarse, one-time, or user-initiated location instead. If the feature is eligible, declare one feature only, show a separate prominent disclosure before the permission flow, provide an accurate privacy policy and store listing, and record a short video of the exact release demonstrating the feature, disclosure, consent, permission grant, and resulting benefit. Deactivate every old noncompliant artifact. Upload a new AAB after any manifest, code, SDK, disclosure, permission-flow, or behavior change. Appeal only when the exact reviewed release already complies or Google evaluated a specific wrong artifact or fact.

Official sources checked

Match the wording in your rejection

“The feature does not meet the requirements to access location in the background”

Google does not consider the declared feature indispensable to the app's main purpose, significantly beneficial to users, reasonably expected, or impossible to deliver with foreground or narrower access.

“Prominent disclosure not found” or disclosure shown too late

The disclosure must appear inside the normal app flow before the runtime permission or settings grant, describe the background collection and its purpose clearly, and require affirmative user action.

“Submitted video does not demonstrate the declared feature”

The video must show the exact declared feature operating in the reviewed release, including the disclosure, consent, permission flow, and visible user benefit. A narrated slide deck or a different build is weak evidence.

“Invalid privacy policy”

The policy must be on an active non-editable web URL, identify the same app and developer entity as the listing, explain location collection and use, and be linked both in the app and on the store listing.

Google still detects background location after removal

A dependency, SDK, flavor, feature module, foreground service, job, geofence, pending intent, or older artifact on a production or test track may still access location while the app is not visible.

Several background-location features are listed in the declaration

Google asks developers to declare one feature for evaluation. Choose the strongest core feature and make the evidence specific to it rather than combining unrelated cases.

What this rejection usually means

A background-location rejection is normally a scope, eligibility, or evidence mismatch. Google evaluates more than the ACCESS_BACKGROUND_LOCATION line: it considers the actual runtime behavior, SDKs, services, jobs, geofences, pending intents, active artifacts, store listing, privacy policy, disclosure, permission sequence, and declaration video. The recovery decision is binary. Either redesign the feature so location is accessed only while the user is actively engaging with it, or prove that one background feature is indispensable to the app's prominently advertised main purpose and delivers a significant benefit users would reasonably expect. Documentation cannot rescue an ineligible data flow, and a compliant new build will not replace an old active artifact until the release configuration fully deactivates it.

Likely rejection signals

  • ACCESS_BACKGROUND_LOCATION appears in the merged manifest of the exact signed AAB
  • Location updates continue after the app is closed, the screen is off, or the user leaves the active feature
  • A foreground service keeps collecting after the user-initiated task has ended
  • Fused Location Provider, LocationManager, Geofencing, WorkManager, JobScheduler, AlarmManager, or a pending intent runs outside a visible user flow
  • An advertising, analytics, mapping, attribution, safety, or other third-party SDK accesses location in the background
  • The declared feature is optional, secondary, or can work through foreground, coarse, one-time, or user-selected location
  • The listing does not prominently explain the always-on location feature before installation
  • The disclosure is bundled into terms, privacy text, onboarding, or a system permission dialog instead of a separate just-in-time screen
  • The video omits the reviewed build, disclosure, consent, permission grant, or actual background behavior
  • A closed, open, internal, staged, or production track still serves an older noncompliant APK or bundle

Recovery plan

  1. Preserve the complete enforcement notice and record the package name, version code, target SDK, release track, review date, cited wording, declaration answers, video URL, privacy-policy URL, and reviewer attachments.
  2. Inspect the merged manifest inside the exact signed AAB and every relevant active artifact. Record ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION, ACCESS_BACKGROUND_LOCATION, location foreground-service types, SDK manifests, product flavors, dynamic features, and manifest-merger sources.
  3. Build a location-flow inventory. For every access, record the API or SDK, accuracy, trigger, screen state, service or job, sampling duration, recipient, retention, user benefit, denial behavior, and whether collection continues after the app is no longer visible.
  4. Apply the minimum-scope test. Use coarse instead of fine when sufficient, foreground instead of background whenever the feature can wait for a visible session, and one-time or location-button access for transactional requests. For apps targeting Android 17 or later, verify the current Play location-button and declaration requirements before shipping.
  5. Select one background feature only if it is indispensable to the app's main advertised purpose, provides a significant user benefit, is reasonably expected, and cannot deliver the same experience with foreground or narrower access. Remove background location if any gate fails.
  6. Audit every SDK and indirect execution path. Disable or replace libraries that collect location for advertising, analytics, convenience, or another undeclared purpose. Your app is responsible for SDK behavior included in the release.
  7. If removing background access, delete the permission and related code from every affected variant. Replace geofences, workers, jobs, alarms, background services, or pending intents with a foreground or user-initiated design and verify the final signed artifact.
  8. If retaining it, add a separate prominent disclosure immediately before the permission flow. State that location is collected when the app is closed or not in use, name the declared feature, explain why the data is needed, and require an affirmative action without making acceptance a precondition for unrelated features.
  9. Implement the platform-correct permission sequence. Request foreground access first. On Android 11 and later, use an educational UI before directing the user to Settings for background access, show the localized grant-option label when appropriate, and provide a clear decline path that leaves the rest of the app usable.
  10. Align the store listing, screenshots, Permissions Declaration Form, Data safety answers, privacy policy, in-app disclosure, review instructions, and runtime behavior. The privacy policy should identify the app and developer, explain collection, use, sharing, retention, and user controls, and be linked in the app and listing.
  11. Record a short clean-install video of the exact release. Show the declared feature from its normal entry point, the prominent disclosure, affirmative consent, foreground and background grant sequence, the app leaving the foreground, the feature continuing for the intended purpose, and the resulting visible benefit.
  12. Remove every older noncompliant APK or bundle from all active production and test releases. Confirm the compliant release is fully rolled out and the older artifacts appear as not included before requesting another policy review.
  13. Choose the recovery route: upload a new AAB after any manifest, SDK, code, service, UI, disclosure, privacy, or permission-flow change; resubmit a corrected declaration when only review evidence was incomplete; appeal only when the exact reviewed release already complies and Google relied on a specific verifiable mistake.

Evidence to prepare

  • Full rejection notice with package name, version code, target SDK, track, date, and exact finding
  • Merged-manifest output from the exact signed AAB showing all location permissions and service types
  • Inventory of production, staged, internal, closed, and open-track artifacts with noncompliant versions marked not included
  • Location-flow matrix covering API, trigger, visibility state, accuracy, duration, recipients, retention, denial, and revocation
  • One-feature core-purpose analysis explaining the significant user benefit and why foreground or narrower access cannot deliver it
  • SDK inventory and proof that advertising, analytics, attribution, and unrelated libraries do not collect background location
  • Screenshots and text of the just-in-time prominent disclosure, consent, educational UI, decline path, and system grant sequence
  • Current store listing, declaration form, Data safety answers, privacy policy, and reviewer instructions
  • Short clean-install video of the exact release with timestamps for disclosure, permission grant, background operation, and user-visible result
  • Before-and-after manifest, dependency, service, and code diff when background access is removed or narrowed

Appeal or fix first?

APPEAL / CLARIFY

Appeal or request clarification when the exact reviewed AAB does not access background location, Google evaluated an obsolete or inactive artifact, or the release already has one eligible core feature with minimum scope, a compliant disclosure and permission sequence, accurate privacy materials, and a complete video. Identify the factual error precisely and attach release-specific evidence; do not argue only that other apps use background location.

FIX BEFORE RESUBMITTING

Fix and upload a new AAB when background location is unnecessary, secondary, unexpected, used by an SDK, replaceable with foreground or narrower access, collected after the task ends, disclosed incorrectly, requested in the wrong sequence, or still present in an active old artifact. Correct the declaration and video as well, but do not treat documentation as a substitute for changing an ineligible data flow.

Choose the next action

What you can verifyRecommended path
The feature needs location only while a screen is visible or for one user-requested transactionRemove background access and use foreground, coarse, one-time, or the Android location button where applicable. Keep the request limited to the session and user action.
A user starts navigation, fitness tracking, or another bounded task and a foreground service continues itUse foreground access only if the service is a continuation of that in-app user action, remains visible through the required notification, and stops immediately when the task finishes. If the behavior is equivalent to background access, the background-location policy still applies.
Continuous family safety, geofencing, or an IoT automation is the app's indispensable main featureRetain the minimum scope only after verifying eligibility. Declare one feature, align the listing and privacy materials, implement the disclosure and permission sequence, and submit release-specific video evidence.
Location supports advertising, analytics, convenience, personalization, or an SDK rather than the main featureRemove the background path and the contributing permission or SDK configuration. A better declaration cannot make a secondary or prohibited purpose eligible.
The exact reviewed release is already compliant but the notice names the wrong version, track, permission, or featureClarify or appeal with the signed-artifact manifest, active-track inventory, declaration, disclosure screenshots, privacy policy, and timestamped video tied to the factual error.

Reviewer response framework

Your response should be factual, short, and limited to the submitted build. Cover these points:

  1. Identify the package name, version code, target SDK, track, declared feature, and exact policy finding.
  2. State whether background access was removed, narrowed, or retained for one indispensable core feature.
  3. For removal, name the replacement foreground or one-time flow and attach the signed-artifact manifest plus active-track evidence.
  4. For retained access, provide the minimum-scope analysis, disclosure text, permission sequence, privacy-policy link, declaration answers, and exact video timestamps.
  5. Ask for review of the corrected release or reconsideration of the documented factual error without claiming guaranteed approval.

Frequently asked questions

Does a foreground service avoid the background location policy?

Not automatically. Google says a location foreground service must continue an in-app user action and stop when that task ends. If its behavior is equivalent to background location, the background-location requirements still apply.

Can analytics or advertising justify background location?

No. Google says location permissions must not be requested solely for advertising or analytics. Remove that collection and any SDK configuration that causes it.

What must the declaration video show?

Show the exact release and declared feature from its normal entry point, the prominent disclosure, affirmative consent, permission-grant sequence, intended operation after the app leaves the foreground, and the visible user benefit.

Why is Play still detecting background location after I removed the permission?

Inspect SDKs, services, workers, jobs, geofences, pending intents, the merged manifest, and all active release tracks. An older APK, dependency, flavor, or equivalent background behavior can keep the policy finding active.

What changes for Android 17 location requests?

Google has announced minimum-scope requirements for apps targeting Android 17, including the location button for one-time or infrequent requests and a declaration to justify ACCESS_FINE_LOCATION when coarse or button-based access is insufficient. Verify the current deadline and policy before shipping.

Should I appeal or resubmit?

Resubmit a new AAB after any manifest, SDK, code, service, UI, disclosure, privacy, or permission-flow change. Appeal only when the exact reviewed release already complies or Google relied on a specific wrong artifact or fact.

Need a rejection-specific plan?

Start with the free diagnosis. The $29 Fix Pack adds the prioritized remediation plan, evidence checklist, reviewer-ready reply, and preflight.

Analyze my rejection

Source: Google Play — Understanding location in the background permissions. Platform policies change. Verify the official rule before submitting. Resubmit AI provides technical and editorial decision support, not an approval guarantee or legal advice.