Google Maps is free, and the price is that it remembers. Every search, every route, every restaurant tapped on a Friday night is recorded, and in principle can be found again. In practice, finding "that kebab place we went to during Ramadan" meant scrolling back through a chronological list that grows by a dozen entries a day.
A section spotted in the Android app, Your recent places, is the fix for that. But it arrived alongside a much larger change to the same data, and the two are worth reading together.
The small change: an index
The section carries four filters — Area, Category, Saved and Maps history. Area narrows to a neighbourhood or city; Category splits entries into Food & drink, Culture, Shopping, Sights and Hotels; Saved shows only places already on a list; Maps history is the old full timeline.
Each entry carries a bookmark icon and a three-dot menu with a delete option. So the kebab place becomes: Area, then Category, then done — and individual entries can be removed as easily as they can be browsed, which had not previously been true.
The large change: who holds the data
Separately, Google moved Timeline — formerly Location History — off its servers and onto the device. Visits and routes are now saved to a map on each phone rather than in the cloud, and the web version of Timeline was deprecated. The rollout ran gradually across Android and iOS.
Because losing a phone would otherwise mean losing the history, Google added an encrypted backup and device-transfer option: a copy can be uploaded to your Google account in a form Google cannot read.
Why that matters more than the filters
Here is the consequence that most coverage of either change left out.
While location history sat on Google's servers, it was subject to geofence warrants — court orders requiring the company to identify every device present near a given place at a given time. These are sometimes called reverse-location warrants, and the distinguishing feature is that they do not name a suspect. They ask which phones were in an area, and work backwards.
Google received very large numbers of them. With Timeline held on devices and the backup encrypted, the company no longer has the data to hand over. A warrant can still be served on an individual, but the bulk query against everyone who happened to be nearby no longer has anything to run against.
That is an unusually clean example of a privacy improvement achieved by architecture rather than by policy. Google did not promise to refuse these requests; it stopped being able to answer them. Promises change with management and jurisdiction. Not holding the data does not.
The trade-offs, stated honestly
Three, and they are real.
- You now own the risk. History on your phone is as safe as your phone. Lose it without having set up the encrypted backup and the record is gone; lose it unlocked and the record is someone else's.
- The web Timeline is gone. Reviewing years of history on a large screen is no longer possible, which was genuinely useful for expense claims and travel records.
- This covers Timeline, not everything. Web & App Activity — which records searches and places you tap, and is what feeds the new recent-places page — is a separate setting, usually on, and still server-side.
Which is the setting actually worth opening. On Android: profile picture → Your data in Maps → Web & App Activity, where auto-delete can be set to 3, 18 or 36 months. A recent-places page is useful precisely because something is recording everything; deciding how long that record survives is the other half of the feature.
Sources: Google's announcements; Android Authority; 9to5Google; The Hacker News; Android Police; and Prothom Alo's original report.
