Oh the conspiracies!!!!
As a software developer, the explanation that Apple gave seems far more plausible than "they are tracking your every move".
It makes total sense to keep a cache of cell tower positions to speed up positioning through trilateration. It also makes sense for Apple to maintain this as a crowd-sourced database and download part of it to your phone. Further, it makes sense for a developer to make an arbitrary decision to say "let's make the cache size 2MB -- that's smaller than a single song". Finally, it makes sense for QA to miss this since the file is not readily visible through the user interface. A very good article on this is here.
I for one cannot remember a single iAd ever popping that was more appropriate based on my location (e.g.: a restaurant ad showing up when I was near a location for that restaurant chain). I seriously doubt that Apple cares where I have been for the past year -- especially with the huge degree of error that trilateration offers. But they definitely care about the crowd-sourced data to understand what regions iPhones are being used most heavily.
Certainly, if Apple wanted to record my personal position it would make MUCH MUCH MUCH more sense for their servers to simply record the query my phone makes to obtain the portion of the crowd-sourced database that my phone wants to cache. That query could easily include a more exact GPS position (i.e.: give me the part of the cache near this location). It could also include a phone identifier. Of course, a timestamp could be associated with the query. They could keep the information on their own servers where I would NEVER EVER see it and they could easily access it. Keeping it on my phone simply does not make sense if Apple really wanted this information -- it makes it easy for me to find and it is of less use to Apple that way.
I wonder if Google records my Wifi/GPS location on Google Maps or what locations I searched when using Google Maps. Hopefully, my identity is anonymized before the query is sent to Google for what part of the Maps database to pull down and cache. But again, it would be really easy for anybody to do this on the server side.
As a software developer, the explanation that Apple gave seems far more plausible than "they are tracking your every move".
It makes total sense to keep a cache of cell tower positions to speed up positioning through trilateration. It also makes sense for Apple to maintain this as a crowd-sourced database and download part of it to your phone. Further, it makes sense for a developer to make an arbitrary decision to say "let's make the cache size 2MB -- that's smaller than a single song". Finally, it makes sense for QA to miss this since the file is not readily visible through the user interface. A very good article on this is here.
I for one cannot remember a single iAd ever popping that was more appropriate based on my location (e.g.: a restaurant ad showing up when I was near a location for that restaurant chain). I seriously doubt that Apple cares where I have been for the past year -- especially with the huge degree of error that trilateration offers. But they definitely care about the crowd-sourced data to understand what regions iPhones are being used most heavily.
Certainly, if Apple wanted to record my personal position it would make MUCH MUCH MUCH more sense for their servers to simply record the query my phone makes to obtain the portion of the crowd-sourced database that my phone wants to cache. That query could easily include a more exact GPS position (i.e.: give me the part of the cache near this location). It could also include a phone identifier. Of course, a timestamp could be associated with the query. They could keep the information on their own servers where I would NEVER EVER see it and they could easily access it. Keeping it on my phone simply does not make sense if Apple really wanted this information -- it makes it easy for me to find and it is of less use to Apple that way.
I wonder if Google records my Wifi/GPS location on Google Maps or what locations I searched when using Google Maps. Hopefully, my identity is anonymized before the query is sent to Google for what part of the Maps database to pull down and cache. But again, it would be really easy for anybody to do this on the server side.