security

Your Android Apps Are Leaking Your Location to Advertisers

An EFF investigation found ad SDKs in apps with 60 million downloads were sharing precise GPS coordinates with advertisers—without users' knowledge.

What the EFF Found in August 2026

In August 2026, the Electronic Frontier Foundation published findings from an investigation into advertising SDKs embedded in popular Android apps. The conclusion was direct: apps with a combined 60 million downloads were silently forwarding users’ precise GPS coordinates to advertising networks — every time an ad was served.

The four ad SDKs identified were BidMachine, InMobi, Verve’s HyBid, and Huawei’s Petal Ads. All four were capable of collecting and transmitting location data once an app had been granted location permission by the user.

The most striking finding: the app developers didn’t always know this was happening. The SDKs shipped with location-sharing enabled by default. Developers integrated the SDK for its advertising revenue features, unaware that it was also acting as a location data pipeline to advertising exchanges.

How the Data Flow Works

To understand the vulnerability, trace how location data actually moves through this system:

  1. A user downloads an app — a flashlight app, a weather app, a recipe finder, a game.
  2. The app asks for location permission. The user grants it, assuming the permission is for that app’s stated purpose.
  3. The app bundles an advertising SDK to display banner ads and generate revenue.
  4. When an ad is served, the SDK reads the device’s current GPS coordinates using the location permission the user granted.
  5. Those coordinates are packaged into the ad bid request and sent to advertising exchanges, where they are used to serve location-targeted ads and, in some cases, sold to data brokers.

The user sees a banner ad for a nearby restaurant. The advertising network now knows where they are, at what time, and — when cross-referenced with a persistent device ID — can build a pattern of that movement over time.

Location permission in Android is granted to the app, not to each piece of code inside the app. When you approve location access, you are — without knowing it — approving it for every SDK the app has bundled.

Some of those SDKs have no user interface, no privacy policy accessible from within the app, and no opt-out mechanism visible to the user. BidMachine’s opt-out, for instance, was buried in a separate developer compliance guide inaccessible to the people whose location was being collected.

Google Play’s Data Safety section is supposed to disclose what data an app collects. The EFF found that the sections for apps examined did not accurately describe the location sharing happening through embedded SDKs. These sections are self-reported by developers and are not independently audited by Google.

This creates a situation where:

  • You check the app’s Data Safety section: “no precise location collected.”
  • You read the app’s privacy policy: no mention of third-party location sharing.
  • The app is sharing your precise GPS coordinates with advertisers in real time.

All three statements can be simultaneously true, because the developer may genuinely not know what their bundled SDKs are doing with permissions the developer granted for a different purpose.

Who Receives the Location Data

When location is collected by an advertising SDK, it typically flows through multiple parties before reaching its final destination.

The advertising exchange

The SDK embeds location coordinates in each ad bid request sent to an exchange. Dozens of advertising networks may receive a bid request for a single ad impression, each of which now has a timestamped, precise location record tied to a device identifier.

Data brokers

Location data is among the most commercially valuable data types in the brokerage market. A persistent record of where a device travels over weeks and months can identify home address, workplace, places of worship, healthcare providers, and political activity. Data brokers package these location histories and sell them.

Analytics companies

Some SDKs send location to analytics services that build movement pattern profiles on behalf of third-party clients, including insurers, hedge funds, political campaigns, and marketing agencies. The downstream use of the data is often disclosed only at the level of “analytics purposes,” with no specifics about who ultimately purchases it.

Law enforcement

Location data purchased from brokers has been used by law enforcement agencies as a workaround for warrant requirements — acquiring commercially what legal process would require a court order to obtain. This practice has been documented in multiple investigative reports and is the subject of ongoing litigation.

State Laws That Now Restrict Geolocation Sales

Legislative action has followed investigations like the EFF’s. As of mid-2026, three US states have enacted laws that ban or restrict the sale of precise geolocation data:

California. The California Consumer Privacy Act, with subsequent amendments, creates a right to opt out of the sale of personal information, including precise geolocation.

Colorado. The Colorado Privacy Act defines precise geolocation as sensitive data requiring opt-in consent for collection and use for advertising purposes.

Virginia. The Virginia Consumer Data Protection Act’s geolocation provision took effect July 1, 2026, making Virginia the most recent state to restrict this practice.

These laws give residents rights — the right to opt out of data sales, the right to request deletion — but enforcement is complaint-driven and involves significant lag. Data already collected and sold under prior policies is not automatically deleted by the passage of new law.

Outside the US, GDPR provides stronger theoretical protections: location data is personal data under GDPR, its processing requires a lawful basis, and “legitimate interest” cannot override individual rights for pure advertising purposes. Enforcement varies significantly by member state, and the ad tech industry has been slow to comply with GDPR interpretations from data protection authorities.

How to Protect Your Location on Android

Given the scale of the problem and the opt-in nature of Android 17’s location button improvements, practical protection requires active management.

Audit location permissions regularly

Go to Settings → Privacy → Permission Manager → Location. Review everything listed under “allow always” and “allow while using.” Revoke any permission for apps that don’t have an active, obvious need for your location right now. Many apps accumulate permissions that were granted once and never needed again.

Use “ask every time” for occasional-use apps

Android lets you set location to “ask every time” for apps that only occasionally need your position. This means the permission is granted for a single session and expires when you close the app. It prevents ad SDKs inside those apps from collecting location during subsequent sessions.

Be skeptical of free apps with advertising revenue models

Free apps often rely on ad SDKs to generate revenue. Those SDKs may be the very ones named in investigations like the EFF’s. A paid app with no advertising component has structurally different incentives around data collection.

Deny location permission when the reason isn’t obvious

A flashlight app has no legitimate reason to know your GPS coordinates. If an app asks for location and you cannot immediately explain why it needs it, deny the request. The app’s core function will work without it in most cases.

Switch to approximate location where precise isn’t necessary

For apps that only need a general region — a weather forecast, a local news aggregator — switch from precise to approximate location in the app’s permission settings. Approximate location is significantly less useful to advertisers at a fine-grained level.

Keep sensitive apps in a separate profile

Android supports multiple user profiles. Running apps that you don’t fully trust in a secondary profile, isolated from your primary accounts and storage, limits cross-referencing of location data with your identity and personal files.

Why Your Location History Is More Sensitive Than It Seems

Location data is not just about where you are. It’s about what can be inferred from where you’ve been.

A healthcare clinic. A domestic violence shelter. A bankruptcy attorney’s office. A specific place of worship. A political rally. These destinations carry meaning that goes well beyond geography. A location history that includes them can be used in employment screening, insurance underwriting, custody determinations, immigration proceedings, and government surveillance — depending on jurisdiction and the legal tools available.

The same phone that carries your location also carries your photos, your notes, your messages, and your personal files. When location data is combined with those other sources, it enables inferences that would not be possible from any single data point alone.

The Connection to Personal File Storage

Apps that hold your most personal files — photos, documents, memories — are not immune to the SDK problem. A cloud storage app, a notes app, a photo organizer that monetizes through advertising may bundle the same location-harvesting SDKs as the flashlight app. The fact that the app’s stated purpose is file storage doesn’t change what its bundled code does.

Choosing storage services with no advertising revenue model — and therefore no structural incentive to bundle location-harvesting SDKs — is a meaningful privacy choice. Services whose revenue comes from subscriptions, not from data, have less reason to embed code that collects data beyond what the app’s stated function requires.

The EFF report is not primarily a story about bad actors. Most of the developers whose apps were affected appear not to have known what their bundled SDKs were doing. It’s a story about a system designed to harvest location data at scale, invisibly, through code that developers treat as a revenue-sharing component without examining its full behavior.

The practical answer to a systemic problem is to choose services that don’t participate in the system. That means reading privacy policies, understanding revenue models, and treating location permission as the genuinely sensitive access right that it is.

Your memories deserve better than an ad platform.

Try daftei free →
← All posts