Google Play location data for ads policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Apps using permission-based device location in advertising.

You can’t request device location solely to serve ads. If an app legitimately uses location for a current feature and also uses it for advertising, Google requires clear disclosure and compliant handling.

What to check

Identify the feature that needs location independently of advertising. Inspect SDK access, precision, background collection, and what users are told before sharing.

Review the privacy policy for the advertising use and links to relevant ad-network privacy policies. A generic statement that you collect location may not describe the actual advertising purpose.

How to address the rejection

Remove location permission if ads are its only purpose. For allowed feature use, limit access to the necessary scope and comply with prominent disclosure and consent requirements where applicable.

Test permission denial and confirm that advertising SDKs don’t obtain location through another path. Explain the core feature, the advertising data flow, and the changes made. Also check Location permissions for the underlying access requirements.

Messages this guide can help with

Location data for ads; Location data for ads policy violation; Location data for ads rejection; Location data for ads denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access