After Wednesday’s revelation that
iPhones have been storing location data since iOS 4.0, now it’s time for the fallout. Sen. Al Franken, D-Minn., was concerned enough about it to send Apple a letter, asking how and why this happened.
In the letter (
full text here), Franken wants to know why Apple collected and compiled this data, why it wasn’t encrypted, whether it’s compiled on laptops, how it’s generated, how frequently the location data is recorded, how precise it is, who’s using the data and why consumers weren’t told about it.
Adding to this congressional inquiry was Rep. Ed Markey, D-Mass., who is co-chairman of the House Bipartisan Privacy Caucus. He wrote his own letter to Apple, asking “Is it an iPhone or an iTrack? Apple needs to safeguard the personal location information to ensure that an iPhone doesn’t become an iTrack.”
Why did Apple do this? Respected Apple watcher John Gruber writes in his
Daring Fireball blog that he doesn’t have a definitive answer, but says he has some insider information about the location tracking on the iPhone, calling it “an oversight” on the part of Apple:
“…my little-birdie-informed understanding is that consolidated.db acts as a cache for location data, and that historical data should be getting culled but isn’t, either due to a bug or, more likely, an oversight. I.e. someone wrote the code to cache location data but never wrote code to cull non-recent entries from the cache, so that a database that’s meant to serve as a cache of your recent location data is instead a persistent log of your location history. I’d wager this gets fixed in the next iOS update.”