Back in 2009, Google CEO and now Executive Chairman Eric Schmidt, already under heavy fire for his company’s strategy to collect, store, and mine every shred of personal data out there, said on CNBC, “If you have something that you don’t want anyone to know, maybe you shouldn’t be doing it in the first place.”
It makes sense. Why worry about surveillance if you haven’t done anything wrong? This, in his unvarnished manner, is what he thinks about privacy. There is none. You don’t need it. You don’t want it. It’s not good for you. It just makes you appear guilty. It’s the philosophy under which police states operate.
Google has no compunction about reading emails of its Gmail users, browsing through user details in its social network services, tracking people throughout their searches, purchases, and reading patterns. It draws conclusions and combines it all with other data into a beautiful whole. For people with Android mobile devices, there is little Google doesn’t know.
Google isn’t the only data hog out there, and perhaps not even the one with the most intimate data – that would probably be Facebook – but it has some unique non-internet tools. Its Street View cars for example. They record visually what is going on in every neighborhood in the world – while also picking up wireless data from home or business networks. So when its new “privacy policy” took effect last year, it caused a lot of fretting. “Calling this a ‘privacy policy’ is Orwellian doublespeak,” lamented John Simpson of Consumer Watchdog. It should instead be called a “spy policy.” But the ruckus, like so many things, subsided after a few weeks.
But suddenly, Schmidt got all riled up about privacy issues of devices that Google doesn’t control through its software and that can access and record promising details of life: civilian drones. Including the toy-like “everyman” minidrones, such as multi-rotor helicopters. He wants them banned outright. And if they can’t be banned, he wants them regulated. To make his point, he dragged out an unfortunate example of a neighbor with an axe to grind:
“How would you feel if your neighbor went over and bought a commercial observation drone that they can launch from their back yard,” he said. “It just flies over your house all day. How would you feel about it?” He didn’t like that prospect. Not at all. “It’s got to be regulated,” he said, he whose company fights regulations wherever it encounters them. “It’s one thing for governments, who have some legitimacy in what they’re doing, but have other people doing it … It’s not going to happen.”
An unfortunate example because an insidious and at once funny Google moment of this type erupted in a village in France. A guy was urinating in his yard. We know he did; just then a Street View car drove by. Its camera, mounted on a rooftop post, could see over the closed gate and the perimeter enclosure and caught the hapless dude in flagrante delicto.
He didn’t know it at the time. And he didn’t know it when the scene appeared on Street View. His neighbors discovered the photo of him in his yard, relieving himself, face slightly blurred. It was only after he’d become the laughingstock of his village that he learned about it. Sure, in Schmidt’s surveillance-state words, he “shouldn’t be doing it in the first place.”
So the difference between a Street View car and a drone is one of degrees. One can only capture what’s visible from its elevated equipment; the other can fly. One is an essential part of its business model; the other should be banned? Why his sudden handwringing about privacy when it comes to drones? Especially since Google is plowing a fortune into cars that drive themselves – road-bound drones, so to speak. The next step would be devices that fly. The mapping and control software would by then be on the shelf.
In a couple of years, the FAA will take up the delicate matter of drones used by civilians and companies. Perhaps by then, Google Ventures will fund a company that is developing the latest and greatest unmanned multi-rotor helicopters the size of a briefcase to replace the awkward Street View cars. They’d take pictures of the insides of homes, to show what a neighborhood is really like, beyond the facades. Users would love it. Software will blur the faces of the people inside to guard their “privacy,” very helpful, as the hapless dude in France found out. And then Google will oppose vigorously any regulation that doesn’t suit it. Because Airborne Street View would be the next leap forward for Google – and Schmidt must already be fantasizing about it.
Here are some tricks I use to maintain privacy and security on the internet – written in my own manner so that even I can follow the instructions: Windows 7, Internet Explorer, Silverlight, Flash Player, & Java Privacy Settings and Cleanup.
April 16, 2013
Posted by aletho |
Civil Liberties, Full Spectrum Dominance, Timeless or most popular | Eric Schmidt, Google, googlestreetview, Privacy, streetview |
Leave a comment
Google bosses were informed their Street View cars would collect e-mails, names, addresses and other personal data from Wi-Fi users around the world, a government report shows. But the company insists the message didn’t get through.
Neither a mistake nor the work of an unauthorized engineer was behind Google’s massive harvesting of Wi-Fi communications that included e-mails, passwords and other sensitive personal information across three continents in 2007-2010, indicates the recent report filed by the US Federal Communications Commission (FCC).
The supervisors of the Street View program were well aware Google cars would go beyond photographing streetscapes. Or at least they should have been.
On Saturday, the web giant releases their own version of report – with employees’ names blacked out. An earlier version provided by the FCC had whole blocks of text blacked out.
The search giant said it wanted a more transparent version to be shown to the public as evidence that any wrongdoing by the company was inadvertent. Apparently, the company wants to avoid speculation over what could have been withheld from the initial release and thus limit any damage.
The report confirms Google’s engineer behind the data-collecting software voluntarily embarked on a project to gather personal e-mails and Web searches of potentially hundreds of millions of people. Identified as Engineer Doe, the individual declined to speak to the FCC, invoking Fifth Amendment rights, which protects citizens from being compelled to testify against themselves.
The design document prepared by Engineer Doe clearly shows his intention to collect payload data in addition to taking panoramic snapshots, as Google’s cars drove by. The private data would “be analyzed offline for use in other initiatives,” like finding how well Google’s other services are used, the document said.
Privacy consideration did come to his mind. “A typical concern might be that we are logging user traffic along with sufficient data to precisely triangulate their position at a given time, along with information about what they were doing,” the document says.
Engineer Doe decided that no harm will be done because Google’s data harvesters would not remain in the vicinity of any particular Wi-Fi user for “an extended period of time.” Nevertheless he added the following “to do” item: “Discuss privacy considerations with Product Counsel.”
“That never occurred,” the FCC report says.
The employee also “specifically told two engineers working on the project, including a senior manager, about collecting payload data.” It actually appears that at least seven Street View engineers had “wide access” to the plan to collect payload data back in 2007.
Engineer Doe’s code was used to collect some 200 gigabytes of payload data across the US between January 2008 and April 2010. Similar logging of private data happened across the world, which made Google the butt of investigations by respective authorities.
The report further cites a number of other people involved in the project as failing to recall knowing that collecting of payload data was happening at the time. Those include an engineer, whose job was reviewing Engineer Doe’s code line by line for bugs and a senior manager, who said he pre-approved the man’s document before it was written.
Following the investigation the FCC fined Google $25,000 for obstructing its investigation, including withholding an email, that openly discussed the engineer’s review of payload data with a senior manager on the Street view project.
It ruled that since the payload data collected was not encrypted, the act didn’t violate American wiretapping law, but said it has “significant factual questions” about why this ever happened.
Google denied stonewalling the probe and blamed the FCC for any delays.
April 30, 2012
Posted by aletho |
Civil Liberties, Deception, Timeless or most popular | FCC, Federal Communications Commission, Google, Google Street View, Personally identifiable information, streetview, United States, Wi-Fi |
Leave a comment
Aletho News
Aletho News 