Apple allows some iOS apps to track user locations via lists of nearby SSIDs

Original Article ↗ Hacker News Discussion ↗

Apple’s iOS includes a Wi‑Fi hotspot API that can expose nearby SSIDs and MAC addresses, which in turn can be mapped to precise locations using large Wi‑Fi databases. Access to this API is gated by special Apple‑granted entitlements rather than user-visible permissions, and prominent “super‑apps” like WeChat and Alipay reportedly have this access, raising concerns that only large players can silently track users’ movements. Commenters debate whether this is an oversight or a structural issue with Apple’s closed ecosystem and incentives, contrasting it with Android’s more explicit location permissions and calling for clearer prompts, tighter controls, and greater transparency over app capabilities.

What the API Enables

  • Discussed API: NEHotspotHelper and related Wi‑Fi APIs expose nearby SSIDs/BSSIDs and can be used to infer location by matching against Wi‑Fi location databases.
  • Access is gated by a special entitlement granted by Apple, not by a normal user-facing permission.
  • Other paths to SSID info exist (e.g., via VPN profiles or specific Wi‑Fi configuration APIs), sometimes without explicit location permission.

Privacy, Consent, and Location Accuracy

  • Many see this as effectively a location API, since Wi‑Fi fingerprints can give street‑ or building‑level accuracy, often better than IP and sometimes comparable to GPS.
  • A minority argue Wi‑Fi gives only “coarse” or unreliable location; others rebut with examples (public Wi‑Fi databases, prior iOS behavior, indoor navigation, turn‑by‑turn without GPS).
  • Core concern: capability is not clearly surfaced to users, and may not be revocable except by uninstalling the app.

Apple’s Entitlement and Permission Model

  • Entitlements are granted by Apple after review; most commenters agree this stops “small spam apps” but not large players.
  • Unclear to readers whether this particular entitlement triggers any user prompt at all; Apple’s docs are seen as vague.
  • Several note a “three‑class” system: ordinary devs, “blessed” apps with special entitlements, and Apple’s own apps with de facto extra powers.

Trust in Apple vs Alternatives

  • One camp views this as another example that users don’t truly “own” iOS devices and must trust Apple’s choices.
  • Others accept Apple’s gatekeeping as the price for a stable, low‑maintenance “appliance” and still see it as safer than ad‑driven Android ecosystems.
  • Some argue open/OSS platforms allow better auditing and faster fixes; others counter that open platforms also rely on “pinky promises” and have worse malware problems.

Super‑Apps, Governments, and Power

  • Granting this entitlement to “super‑apps” like large Chinese payment/messaging apps is seen as especially worrying, given their centrality and potential state pressure.
  • Concentrating many functions (and permissions) in one app makes abuse harder to detect and avoids per‑feature user choice.

Mitigations and Requests

  • Suggestions include: tying SSID scanning explicitly to Location Services, adding clear user prompts (with “allow once/while using/never”), exposing entitlements in the UI, and listing requested permissions/entitlements in app store pages.
  • Users mention practical workarounds (DNS blockers, ad blockers, automations to disable Wi‑Fi), but note that Wi‑Fi/Bluetooth are difficult to fully disable on iOS and often re‑enable after updates.