CEO Eric Schmidt's remarks are being taken out of context, the company says.
"The context in which Eric answered this question was clear," said a Google spokesperson in an e-mailed statement. "He was talking about the US Patriot Act. The [CNBC] documentary later made clear the lengths to which Google goes to inform and empower users about privacy-related concerns, including creating a dashboard in which users can review and control data in their Google accounts."
Google has made, and continues to make privacy missteps, such as arguing last year that California law didn't require a privacy link on its home page and rolling out its Street View service around the world without enough outreach to communities and regulators.
In Italy, four Google executives face a possible jail sentence, if convicted, for failing to prevent a video depicting the bullying of a teen with Down Syndrome from being posted briefly on the Italian YouTube.
Google however is not the only company raked over the coals of privacy. Facebook this week, having apparently learned nothing from its Beacon fiasco, just asked its 350 million users to revisit their privacy settings while supporting settings that would share more rather than less information. And among other companies, there are even greater privacy problems.
If Google users care, they have not shown it in large numbers. The company continues to grow and thrive.
Google has repeatedly said that its business depends on user trust and has taken steps to enhance users' privacy, such as the Privacy Dashboard cited by Google's spokesperson.
Another such step was revealed earlier this week when Google VP of engineering Vic Gundotra said that this company had decided not to implement facial recognition for its Google Goggles service, which allows searchers to identify certain objects -- or apparently certain people -- by taking a picture of the object with a mobile phone. Gundotra said the company wants to understand the privacy implications more thoroughly.
Dark Reading Must Reads - September 25, 2014Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Published: 2014-09-29 The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.
Published: 2014-09-29 lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.
Published: 2014-09-29 Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
Published: 2014-09-29 bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.