Android now stops you sharing your location in photos

Original Article ↗ Hacker News Discussion ↗

Android now strips GPS location (and often other EXIF metadata and original filenames) from photos shared via its native pickers and browsers, breaking workflows that rely on geotagged images for things like mapping, citizen science or photo organization. Supporters see this as a necessary privacy and safety safeguard, arguing most users have no idea they are exposing precise coordinates when uploading images. Critics counter that Google removed important functionality without clear communication or opt-in controls, and that a better design would allow explicit, per-site or per-action consent rather than forcing users to resort to USB transfers or native apps to preserve metadata.

Scope of the Change / What Actually Happens

  • Android’s scoped storage from Android 10 onward hides EXIF GPS data by default unless an app requests ACCESS_MEDIA_LOCATION and the user grants it.
  • Mobile browsers like Chrome and Firefox on Android do not request this permission, so any image selected via the system photo picker is delivered with GPS coordinates zeroed out.
  • Many share flows that use MediaStore URIs (including Bluetooth or QuickShare from gallery apps in some setups) also strip GPS; file managers using raw file access often do not.
  • The native Android photo picker also renames files (or hides originals) in ways that confuse users and some apps; Google classifies filename stripping as “intended behavior.”

Privacy and Safety Arguments (Pro Change)

  • Most users are unaware that photos contain precise location, timestamps, device details, etc.
  • Stripping EXIF on upload is seen as aligning with user expectations and reducing risks of stalking, doxxing, and inadvertent exposure (e.g., on mapping or social apps).
  • Some argue the OS should treat “my phone” as private and “browser / third‑party apps” as non‑private, enforcing data minimization by default.
  • Several commenters note similar behaviors on iOS and GrapheneOS and praise “maximum privacy by default,” especially for less technical users.

Criticism and Regressions (Against Change)

  • Power users and developers lose legitimate workflows: crowdsourcing (e.g., mapping, ecology), law‑enforcement documentation, photo organization, duplicate detection, and research projects.
  • Web apps cannot ask for EXIF GPS even with user consent; suggestions include HTML attributes or pickers with explicit “include location” toggles.
  • Some see this as turning general‑purpose phones into locked‑down appliances and as another unilateral, undocumented breaking change by a dominant platform.
  • Complaints extend to filename stripping and other “simplifying” changes (disallowed characters, hidden metadata), which break cross‑device sync and expert workflows.

Comparisons, Workarounds, and Broader Concerns

  • iOS reportedly allows per‑share control over including location; some wish Android copied this UI rather than hard‑stripping.
  • Workarounds mentioned: USB transfer, file managers, zipping files, alternative ROMs (e.g., GrapheneOS), or native apps that request the new permission.
  • Several note the irony that EXIF to websites is blocked while large platforms and data brokers still collect highly detailed location streams through other channels.