Location history data in Google Maps will soon be stored on user devices
Google is shifting Maps’ location history from its servers to users’ devices, with optional encrypted cloud backup, prompting debate over whether the move is driven more by privacy concerns or by legal and storage pressures. Many welcome reduced exposure to government subpoenas and data breaches, but heavy users of the timeline feature worry about losing convenient cross-device access, web-based viewing, and long-term archives. The exchange also highlights broader concerns about pervasive location tracking, the “data as toxic waste” idea, and interest in self-hosted or alternative logging tools.
Data as “toxic waste” and regulatory risk
- Many compare user data to hazardous waste: valuable but dangerous to hold.
- Centralized location logs are seen as a liability under growing government surveillance, subpoenas, and cross-border legal demands.
- Some argue real reform will only come when executives face jail or existential fines for mishandling data.
- Others note that even if big players reduce collection, smaller offshore data brokers will continue to treat data as “gold.”
Feature loss vs. privacy gains
- A sizable group loves long-term location history as a personal “time machine” for:
- Remembering trips, restaurants, friends’ addresses, accident details, and tax / immigration records.
- Providing dates/locations for citizenship and residency applications.
- Several wish they could opt out of the change and keep full cloud-based history, even paying for it.
- Others welcome the move, saying they disabled history long ago over leak and surveillance fears.
- Some complain related Maps features degrade when tracking is disabled (e.g., easy “Home” navigation).
Local storage, backup, and end-to-end encryption
- The new model stores history on-device, with optional cloud backup that is claimed to be encrypted so even Google can’t read it.
- Multiple commenters highlight uncertainties:
- How multi-device sync and web timeline views will work.
- How data survives app reinstall, phone loss, or clearing app data.
- Whether the encryption is truly end-to-end or recoverable via account credentials.
- Some propose password-based client-side encryption as a general standard for cloud data; others point to existing Android/iOS backup approaches as examples.
Alternatives and self-hosting
- Several mention switching to self-hosted or third-party trackers (Traccar, OwnTracks, PhoneTrack, OSMAnd, GPX loggers, Arc, custom GPX apps) to keep data under personal control.
- Concerns include battery drain, OS-level background limits, and trust in Google’s underlying location services even when apps are “local.”
Google’s privacy image and motives
- Some see the change as a genuine privacy improvement; others think it’s primarily a way to reduce subpoena burden or storage cost.
- There is debate over Google’s broader privacy record, ad-driven tracking, and efforts like Web Environment Integrity and Manifest v3.