Blocks submissionGoogle Play

The in-app disclosure names the feature, the data, and that it happens in the background

The question Only when ACCESS_BACKGROUND_LOCATION is declared: from the app's own screens, is there a prominent disclosure, shown in normal use immediately before the location runtime prompt, that uses the word 'location', says the use happens in the background or when the app is closed, and lists every feature that uses background location? Google requires no separate accept tap; the runtime prompt that follows is the consent. Is the same disclosure in the app description and on the website? Name the screen and quote its text.

A person or a model answers it from the app's texts and screens; the answer is kept only while the facts it saw are unchanged.

Applies to every app

Checked from built, not yet uploaded, on a test track, submitted and in review, published

The rule, in our words

• Understanding location in the background permissions: Background location may be requested only for a feature that is core to the app's main purpose and gives users significant benefit (such as physical or perceived safety); requests solely for ads will be denied, location should never be requested solely for advertising or analytics, and location data may never be sold or shared to facilitate sale. The feature must be prominently described in the store listing. Approval goes through the Permissions Declaration Form in Play Console, declaring exactly one background-location feature, plus a video (recommended length 30 seconds or less) that must show the feature, the prominent disclosure and the runtime prompt. A prominent in-app disclosure dialog must appear in normal use before the location runtime prompt, must use the word "location", state that use is in the background or when the app is closed, list every feature using background location, and must also appear in the app description and website; no separate consent tap is needed because the runtime prompt that follows provides consent. A privacy policy that references location use must be available on an active non-PDF URL, linked both in the app and on the store listing. Without approval, updates may be blocked and the app removed.
• User Data: Be transparent about all user data handling and comply with applicable privacy law; you are responsible for third-party SDKs and AI integrations in the app. Personal and sensitive data (including device location) must be limited to app functionality the user reasonably expects, transmitted with modern cryptography such as HTTPS, requested via runtime permissions, and never sold. Where collection may not be expected (for example background collection), show a prominent in-app disclosure in the normal flow (not only in a policy, not bundled with unrelated text) describing the data and its use, immediately before any consent or runtime permission request; consent must be a clear affirmative action obtained before collection, and backing out or auto-dismissing messages do not count. If Google asks, you must within 2 weeks show evidence that an SDK collecting data by default meets these rules. Persistent device identifiers may not be linked to other personal data or resettable IDs except for telephony or enterprise device management. Every app needs an accurate Data safety section consistent with its privacy policy, and a privacy policy linked in Play Console and in the app, at a public non-PDF URL, labelled as such, naming the developer or app with a contact, and covering data types, sharing, security, retention and deletion. Apps with account creation must offer account deletion in-app and via a web link entered in Play Console, deleting all associated data (freezing does not count), with any retention disclosed. App Set ID may not be used for ads. EU/UK/Swiss personal data from Google must be handled under the Data Privacy Framework terms, with immediate notice to Google if you cannot comply.

Okkok never stores the stores' text. Each item above is our paraphrase, and the link is the page it rests on, verified unchanged by fingerprint on every run.

The other store

• Google adds the web-link requirement; Apple adds the ban on call/email/support-only flows and explicitly covers auto-created guest accounts. "Freezing does not count" (Google) equals "deactivating is insufficient" (Apple). partial
• Google names transport encryption; Apple says only "appropriate security measures". google-stricter
• Apple requires an on-screen or audible recording indicator; Google requires the disclosure dialog but no live indicator (except for stalkerware under the Malware policy). partial
• Google requires the policy URL to be public, non-PDF and to name the developer with a contact, and bans selling data; Apple requires consent even for anonymous data, requires the policy to confirm third parties give equal protection, and bans making paid features depend on granting data access. partial

Check your app

pip install git+https://github.com/petresandu-cloud/okkok
okkok audit path/to/app

The report names this rule as google.background-location-disclosure-wording and says what to do, who does it, where, and how it knows.