In 2006 an engineer working on an experimental WiFi project wrote a piece of code that sampled all categories of publicly broadcast WiFi data. A year later, when our mobile team started a project to collect basic WiFi network data like SSID information and MAC addresses using Google's Street View cars, they included that code in their software-although the project leaders did not want, and had no intention of using, payload data.
Mind you, this is publicly broadcast data. Anyone with the technical know-how can write software that will grab unprotected data traveling over WiFi networks. Even if the data is protected, there's plenty of free packet sniffing and encryption-cracking software to enable snooping.
Those suing Google are alleging privacy and wiretap law violations despite Google's claim that it didn't even know it had the data. You too could be guilty of this sort of wiretapping, if you've ever made a mobile call that was recorded on an answering machine and happened to capture the conversation of someone talking nearby.
Was any harm done? I doubt it. Even so, the legal fees and inevitable settlement will probably be disproportionate to any real damage. This is not like the company's Buzz launch fiasco, which arguably put some users at real risk from stalking ex-spouses and may have exposed confidential relationships.
The inadvertently gathered WiFi data apparently remained in Google's data centers, unused and inaccessible to the outside world.
Certainly Google should revise its policies so that it knows what its code does. But beyond that, this strikes me as a case of regulators and attorneys gone wild.
The Enterprise 2.0 Conference is the largest gathering for people ready to connect teams, and harness collective intelligence with social tools and 2.0 technologies. It happens in Boston, June 14-17. Find out more here.