Google Maps is killing Timeline for Web

Original Article ↗ Hacker News Discussion ↗

Google is phasing out web access to its Maps Timeline feature and moving location history storage to individual devices, framing the change as a privacy and security improvement. Commenters are split between welcoming reduced centralised tracking—especially in light of geofence warrants and data subpoenas—and lamenting the loss of a powerful, desktop-friendly tool for recalling trips, tracking mileage, and querying their own historical movements. The change also fuels wider concerns about Google’s tendency to deprecate popular services, the opacity of its data retention practices, and the lack of robust, user-controlled alternatives for long-term location logging.

Overall user reaction

  • Many commenters are upset; Timeline on web was heavily used for:
    • Remembering places from trips and past years.
    • Reconstructing purchases, holidays, and work-related mileage/tax logs.
    • Browsing life history on a large screen instead of a phone.
  • Some say this is the first Google “kill” that personally hurts them.
  • A minority welcome the change if it truly means less server-side storage.

Privacy, “on-device” model, and data retention

  • Google frames the shift as “more private, on-device, per-device.”
  • Skeptics argue:
    • Google still harvests/infer location for ads, Photos, etc., so privacy gain is limited.
    • It may be “privacy from the user” (less visibility/export) rather than from Google.
  • Supporters counter:
    • If precise, unified location history is no longer stored in the cloud, that’s a real improvement.
    • Location is particularly sensitive; keeping exhaustive server-side logs is risky.
  • It remains unclear whether Google will truly stop retaining equivalent location data in other backends.

Law enforcement, liability, and regulation

  • Several comments suggest a key driver is avoiding:
    • Geofence warrants and bulk law-enforcement requests.
    • Long-term liability of holding years of detailed location trails.
  • Others note the article doesn’t clearly guarantee deletion, only the end of web access.
  • Some discuss GDPR/right-to-be-forgotten tensions, but legal applicability and enforcement are viewed as uncertain.

Data export, migration, and lock-in

  • Users rush to Google Takeout; some report:
    • Raw Location History exports (e.g., GPX) have been restricted for about a year.
    • Current exports may be JSON with limited format choices.
  • Concern that:
    • Historical data may become effectively unexportable.
    • Device-bound histories complicate switching phones, platforms, or using multiple devices.
  • One commenter reports the new on-device Timeline offers JSON export, but others note older data is hard/impossible to fully retrieve.

Alternatives and self-hosted options

  • Suggested replacements include OwnTracks, Traccar, uLogger, and custom GPS logging setups, often self-hosted.
  • Users note tradeoffs:
    • Higher battery usage, lower resolution, or weaker semantic “place snapping” compared to Google.
    • Complexity of running servers, app-store hurdles, and device power-management issues.

Why Google kills features

  • Theories include:
    • Cost cutting, degrowth, and infrastructure churn making understaffed features hard to maintain.
    • Privacy/liability concerns outweighing value of the feature.
    • Strategic refocus away from non-core, low-revenue offerings.