No reasonable expectation of privacy in one's Google location data

Google’s Location History Changes & UX

  • Google is moving Location History storage from servers to user devices; optional cloud backup is end‑to‑end encrypted, off by default.
  • This effectively ends traditional geofence warrants using that dataset, which some see as a win driven by government overuse of warrants.
  • Several users value their Timeline history and fear losing years of data when changing phones; they find the migration dialogs confusing and poorly explained.
  • Backup enabling is described as unintuitive or buried, though others report it’s as simple as tapping a cloud icon in Timeline.

Privacy, Surveillance, and Law Enforcement

  • Many welcome reduced server‑side storage as limiting dragnet searches and potential future repression; concerns reference historical abuses of state power.
  • Others argue location data should be available for serious crime investigations and can exonerate suspects; question why “official law infrastructure” access is seen as bad.
  • Some contend law enforcement should remain costly and non‑automated to prevent scalable rights abuses; others seek “privacy‑first” designs that still aid policing.

Expectations of Privacy & Legal Framing

  • Discussion around the U.S. fourth amendment and “reasonable expectation of privacy”: once data is shared with a company, some argue legal protection weakens under third‑party doctrines.
  • Others push back, asserting that sharing data with a service for a feature does not equal consent for broad reuse or law‑enforcement dragnet access.
  • There is skepticism that users truly “opt in”: many may enable Location History unknowingly or feel coerced by feature lock‑outs.

Trust in Google and Ongoing Tracking

  • Some trust Google not to blatantly lie about disabling tracking due to legal and reputational risk.
  • Others cite multiple past privacy violations, weak regulatory enforcement, and the rarity/risk of whistleblowing as reasons to assume broader undisclosed tracking.
  • It’s noted that even with Location History off, other channels (cell carriers, apps, E911, cameras, data brokers) can still track movement.

Alternatives and Mitigations

  • Suggestions include using GrapheneOS, strict permission controls, turning off background access and radios, and using offline/OSS map apps.
  • Privacy‑focused location-history alternatives (like self‑hosted or “privacy‑first” apps) are mentioned.
  • Debate over whether iOS meaningfully improves privacy, given Apple’s own data relationships.