My Location the Next Google Privacy Controversy?
theodp writes "While Google boasts one of its Privacy Principles is making the collection of personal information transparent, even techies are left guessing about what's going on behind the scenes of certain products. The American Dictator points out that Google's Wi-Fi collection efforts don't stop with its Street View cars, offering up this explanation of Google's My Location: 'When you allow Google to "know your location," what you are really agreeing to is to send to Google's computers your Wi-Fi environment — not only the name of the Wi-Fi hotspot you are logged into, but also the names and signal strengths of every Wi-Fi hotspot around you. In other words, the same things that those Google Street View cars were sucking up as they drove by your house.' So, will changes in privacy attitude prompt changes in Latitude?"
This method of radio-location is not special or unusual in any way. If anything, it is rather common and not even innovative on google's part. Several firms have exited for _years_ which focus on location based services as determined by nearby hotspots. Also, Latitude is littered with warnings about the nature of the service, and the fact that your location information will be sent back to Google. Of course, this is even less interesting when you consider the fact that your cell phone carrier already knows all of this information all the time and always has, which nobody makes any fuss about whatsoever.
You mean that in order to use a service that uses your Wifi surroundings to determine your location, you have to send the service data about your Wifi surroundings? Holy shit!
Next, you'll tell me you have to send your private, personal *search terms* to Google to get search results - the horror!
That makes it public. Google is merely asking you to forward some public information to them. You may, if you wish, decline.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
People go to great pains to send a hundred mW throughout the air as far as it'll go, and are surprised when it does just that?
I'm on a volunteer ambulance squad; being a nerd I made a python script to scrape our crappy eDispatch provider's website for our dispatches and assemble them on a nice website. There was a big fight over password protecting this... despite the fact that we are going to great pains and expense to pump the very same information at about 50W. I ended up throwing a trivial password on it, until everybody forgot.
Point is, people don't seem to understand the 'broad' part of 'broadcast', and get annoyed that they don't have full control of the signals they emanate past their walls.
I have developed a truly marvelous proof of this comment, which this signature is too narrow to contain.
The recent privacy controversy was never about Google detecting and recording the names, unique IDs, and signal strength of local WiFi hotspots -- It was about Google mistakenly recording traffic, including unencrypted information that anyone could easily utilise.
In addition to that, there are only four ways to locate someone connected to the Internet:
- GeoIP which can perhaps pin you down to a city, perhaps even a town,
- WiFi triangulation which can pin you down to within a few metres
- Latency triangulation which is frankly uncompletely unworkable on something as complex as the internet
- IP->Postal Address Mapping (Read: ISP's database)
Obviously only two of these are workable for someone like Google and GoeIP is completely inaccurate. No ISP is going to give Google access to their address database.