The ACCESS_FINE_LOCATION Permission and What It Forces You to Disclose

Declaring ACCESS_FINE_LOCATION in your manifest doesn't just add a runtime permission prompt — it locks you into a specific Data Safety answer: "Location" must be marked as collected, and you'll be asked whether it's precise or approximate.

Here's the part that catches people: if a bundled SDK (commonly ad networks) also reads location for targeting, you now have two collection points to declare, potentially with different sharing purposes. Declaring only your own use and missing the SDK's is one of the most common causes of a data safety mismatch flag.

The fix

Fix: grep your manifest for every <uses-permission> line, then check each SDK's own privacy documentation for whether it independently accesses that same permission.

The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.

Keep going

Data Safety generator →

Turns these answers into a Play-ready CSV.

Data Safety guide →

The full method behind the checks.

Short, specific submission fixes.

Run this check on your own AAB

Free analysis, exports when you need them.

Start free See pricing