> For example, Google stores a snapshot of where you are when you merely open its Maps app.
Except in the case of using entirely offline map data, I don't know how the user can expect their location not to be revealed to the server in this case. To see the map, you have to have map data, and which data you pull is going to give a very strong hint of your location.
I guess you can distinguish between _a_ location (that you viewed) and _your_ location (that you definitely are at), but it's still an extremely strong hint that after a period of inactivity, the first location you load is probably the location where you are.
> To see the map, you have to have map data, and which data you pull is going to give a very strong hint of your location.
You are missing the point. While the location for which you fetch map data essentially reveals your current location, the request can be fulfilled without making a permanent record connecting that location to your Google account. The issue here is that when people turn off "Location History" in their privacy settings, they except Google not to store the location information to their Google account. But Google seems to be doing it anyway, unless you also disable "Web & App Activity".
Oh, I see. The article mentions https://myactivity.google.com/ but for some reason it didn't make it a hyperlink like it did with several other things. So I managed to not notice it.
Keep in mind that Apple also has a map application that also needs to know the user's whereabouts to give good information, but there's no issue because Apple does not need that data to be collected, stored, analyzed, aggregated, and sold. Google could simply send the map tiles requested then discard the request data from their servers as Apple appears to do.
Except in the case of using entirely offline map data, I don't know how the user can expect their location not to be revealed to the server in this case. To see the map, you have to have map data, and which data you pull is going to give a very strong hint of your location.
I guess you can distinguish between _a_ location (that you viewed) and _your_ location (that you definitely are at), but it's still an extremely strong hint that after a period of inactivity, the first location you load is probably the location where you are.