The Problem With “Allow While Using App”
For years, Android’s location permission model offered three choices: always, while using the app, or deny. The “while using” option sounded reassuring. In practice, it meant any moment the app was technically open — in the background, between taps, seconds after you put your phone down.
Ad SDKs embedded inside apps exploited this gap. An EFF investigation published in August 2026 found that four major advertising SDKs — BidMachine, InMobi, Verve’s HyBid, and Huawei’s Petal Ads — were collecting and transmitting precise GPS coordinates through apps that had location permission. Apps with a combined 60 million downloads were silently forwarding location data to advertisers every time an ad was served, regardless of whether the user was actively engaged.
The developers didn’t always know. The SDKs shipped with location-sharing enabled by default.
What Android 17 Actually Introduces
Android 17 adds a new mechanism called the location button. Instead of granting permanent location access, users tap the button in an app’s UI to share their exact position once, at that moment, in the foreground.
The location button functions like a temporary pass:
- It grants precise location access only while the app is visible and active.
- Once the user switches away, the access expires automatically.
- Apps cannot silently re-request location in the background.
- The permission does not persist after the session ends.
This is a meaningful structural change. Ad SDKs that previously collected location continuously through a background process can no longer do so if the app uses the location button pattern.
Android 17 also refines the algorithm behind approximate location. When a user grants approximate rather than precise access — an option introduced in Android 12 — the new version narrows the inaccuracy radius, making the approximate result genuinely less informative to advertisers at a fine-grained level.
What It Does Not Fix
Android 17’s location button is opt-in for developers, not mandatory. Apps that rely on the older “while using” grant can still request it. The new button pattern only applies when developers choose to build it in.
Pre-existing apps are unaffected. An app built before Android 17’s release that already holds a “while using” location permission keeps working exactly as before, unless the developer updates it.
Background location is a separate tier. Apps that justify background location access — navigation, delivery tracking, fitness logging — can still apply for that permission level. The button does not replace that.
Third-party SDKs remain opaque. Unless Google mandates disclosure at the SDK level — something not yet required — users have no way to know which SDKs inside an app receive their location data. You can grant location to an app and implicitly grant it to every SDK bundled inside, including ones designed specifically to harvest location for advertising.
The SDK Problem That Hasn’t Gone Away
The structural issue the EFF identified is not fully resolved by Android 17’s location button. The problem isn’t just how location is collected; it’s that granting location to an app means granting it to every SDK bundled inside.
Those SDKs can have their own data pipelines, their own servers, and their own opt-out mechanisms buried in compliance documents most users will never find. BidMachine, one of the SDKs in the EFF report, listed in its Google Play Data Safety section that it did not collect precise location — while the technical reality was the opposite.
Virginia became the third US state to ban the sale of precise geolocation data in July 2026, joining California and Colorado. But enforcement is complaint-driven and slow. The data already collected under prior policies is not automatically deleted.
How to Limit Location Exposure on Your Android Device
Given that Android 17’s improvements are developer-opt-in, practical protection remains largely manual.
Audit existing permissions
Go to Settings → Privacy → Permission Manager → Location. Review every app listed under “allow always” and “allow while using.” Revoke any permission for apps that don’t have an obvious, active need for your location.
Prefer “ask every time” for occasional-use apps
Android lets you require an explicit prompt each time an app wants location access. For apps you use infrequently — a restaurant finder, a weather app, a shopping app — set location to “ask every time.” The permission doesn’t persist between sessions.
Check Data Safety sections critically
The EFF found that these sections can misstate what SDKs actually do. They are self-reported by developers, not audited by Google. Treat them as a starting point, not a guarantee.
Use approximate location where precise isn’t necessary
For apps that only need a general region — a weather forecast, a local news app — switch from “precise” to “approximate” location in permission settings. Android 17’s refined approximate algorithm makes this a more meaningful restriction than it was on earlier versions.
Separate your location-sensitive activities
If you use navigation apps heavily, consider using a dedicated device or profile where you are not logged into the same accounts that hold your photos, files, and personal data. Location data is most dangerous when it can be cross-referenced with identity.
Why This Matters Beyond Maps
Location data is more revealing than most people realize. A year of precise location records can identify your home, your workplace, your doctor’s office, your place of worship, your children’s school, and patterns in your daily movement that reveal health conditions, relationship status, and political activity.
When that data is collected by an ad SDK, it often flows into data brokers who bundle it with other sources and sell it to employers, insurers, law enforcement agencies, and political campaigns.
A photo storage app, a notes app, a file manager — apps that have no obvious reason to need your location — can still embed ad SDKs that do. The app holding your most personal files might be quietly broadcasting your physical location to parties you will never identify.
The most reliable mitigation for sensitive files and memories is keeping them in services with no advertising business model — and therefore no SDK incentive to collect location data at all.
What to look for in any app
Before granting location permission to any app, ask:
- Does this app’s core function require my location?
- Does this app have an advertising business model that might bundle data-hungry SDKs?
- What does the privacy policy say about third-party data sharing?
- Has the privacy policy changed in the past year?
If the answers point toward an advertising-driven app with vague third-party sharing language, the safest approach is to deny location and see whether the app still does what you downloaded it for. Most will.
The Bigger Picture
Android 17’s location button is a genuine improvement. It gives users a meaningful way to grant one-time location access for specific tasks without creating a persistent surveillance window for background processes. The approximate location algorithm refinement adds a layer of real protection for users who grant approximate access.
But it is an improvement to a system that has been leaking precise location data at scale for years. The SDKs identified in the August 2026 EFF report exist across a large portion of the Android app ecosystem. The developers that bundle them often don’t know what they’re enabling, and the users who install those apps have no practical way to find out.
Until SDK-level permission grants are required — meaning each SDK inside an app must independently request and be granted permission — the structural gap remains. Android 17 narrows it. It does not close it.