They know where you texted last summer and where you ate last night, thanks to location data on your smartphone. Who else are Google and Apple sharing your data with?

InfoWorld|Apr 22, 2011

Today's smartphones are amazing devices. They let you check your email, surf the Web, watch YouTube, make video calls, or play Angry Birds from virtually anywhere. You can use one to find a four-star Italian restaurant within three blocks of your current location that's offering a 20 percent discount if you place an order in the next 30 minutes.

Sometimes, when the wind is right and a cell tower is within visible range, they even let you make calls.

[ Want to cash in on your IT experiences? InfoWorld is looking for stories of an amazing or amusing IT adventure, lesson learned, or tales from the trenches. Send your story to offtherecord@infoworld.com. If we publish it, we'll keep you anonymous and send you a $50 American Express gift cheque. ]

While you're doing all of that, they're watching you, scribbling down your location, and storing that information invisibly for an indefinite period of time. It's kind of like having an imaginary friend following you at all times -- one with a really large bank account.

In a letter to U.S. Senator Ed Markey last year, Apple admitted to collecting cell tower and open Wi-Fi data anonymously to improve its location-based services. It has yet to comment about why it stores this data locally in an unencrypted file, however.

The big question, of course, is why Apple is storing this information. I don't have a definitive answer, but the best at least somewhat-informed theory I've heard 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.

Well, maybe, but it would be nice to hear this from a somewhat more informed source -- like, directly from Apple.