Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #154705

Many ad SDKs share locations

Show all headers | View raw

| An investigation by the Electronic Frontier Foundation (EFF) reveals
| that many mobile advertising SDKs automatically collect and share
| users' precise location data by default the moment an app is granted
| system-level location permissions. Because mobile operating systems
| lack SDK-specific permission controls, giving a trusted app (like a
| weather tracker or fitness app) permission to view a location inhe-
| rently gives that same data to any embedded third-party ad libraries.
| 
| Many developers are entirely unaware of this backend behavior. The
| data quickly moves through Real-Time Bidding (RTB) advertising systems
| straight into the hands of commercial location data brokers.
| 
| Why This Happens
| 
| Invasive Default Settings   Several major ad networks configure
| their SDKs to actively look for and transmit location coordinates 
| automatically without requiring explicit opt-ins from the developer.
| 
| Financial Incentives   Ad networks actively reward developers with
| higher monetization rates or payouts if precise location sharing is
| active.
| 
| Deceptive Documentation   SDK guides often use dark patterns, unclear
| language, or omit the exact extent of their background data harves-
| ting.
| 
| Key Harms of Leaked Location Data
| 
| This is not just about serving creepy, hyper-local ads. Aggregated
| location histories from data brokers have been actively weaponized,
| bought, or leaked for severe real-world harms:
| 
| - Government intelligence tracking and law enforcement investigations
|   without warrants.
| 
| - Global digital spying tools and targeted cyber surveillance.
| 
| - Tracking political union organizers and military personnel.
| 
| - Targeted harassment, outing individuals, and massive data broker
|   database breaches.

  Lines marked with "| " come from my editing, where I start by writing
  prompts for the chatbot and then edit the generated texts and format
  them for USENET.

Back to comp.mobile.android | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Many ad SDKs share locations ram@zedat.fu-berlin.de (Stefan Ram) - 2026-08-05 21:06 +0000
  Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-05 13:56 -0800
    Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-05 15:17 -0800
  Re: Many ad SDKs share locations "R.Wieser" <address@is.invalid> - 2026-08-06 09:16 +0200
    Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-06 07:55 -0800
  Re: Many ad SDKs share locations Arno Welzel <usenet@arnowelzel.de> - 2026-08-07 16:09 +0200
    Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-07 18:51 -0800
      Re: Many ad SDKs share locations Arno Welzel <usenet@arnowelzel.de> - 2026-08-09 11:18 +0200
        Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-15 09:05 -0800
          Re: Many ad SDKs share locations "Carlos E. R." <robin_listas@es.invalid> - 2026-08-15 19:30 +0200
            Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-15 10:37 -0800
          Re: Many ad SDKs share locations Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-16 09:28 +0100
            Re: Many ad SDKs share locations Maria Sophia <mariasophia@comprehension.com> - 2026-08-16 10:26 -0800

csiph-web