Normally I'd be inclined to agree, but this isn't the first instance where Google employs these types of tactics. There was the other issue with the Google StreetView where they employed rather objectionable means to mine their data.
The Streetview code was caused by a single person and the later Google programmers didn't know about it.
However, the background is more interesting than I thought. Apparently the guy who wrote the original code was quite famous as one of the first "war-driving" experts in Silicon Valley. That is, he was a hacker who helped invent the idea of drive-by WiFi logging, locating and hacking.
So when Google needed someone good at logging WiFi locations, they hired this guy. Of course, he brought with him a lot of the code that he'd spent much time on... including the automatic collection of user data. Later he left, and his code library ended up being used in the cars.
Upshot: never hire hackers without auditing their code
There is a precedent emerging and that suggests to me we should be cautious to think it is always rogue programmers who are to blame. Accountability must become a consideration, if not now, certainly by the next time.
You're right about the accountability.
Google's power and its Achille's Heel are the same thing: engineers rule there, with comparatively little oversight.
While I applaud treating adults as adults and giving them huge responsibility, there also need to be firm rules in place to avoid trouble.
The trouble is, many programmers cannot discern that using clever code can be the equivalent of "doing evil", or that it might have huge consequences if found out. It's just clever code to them.