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.
Published: 2015-05-26 Multiple stack-based buffer overflows in Moxa VPort ActiveX SDK Plus before 2.8 allow remote attackers to insert assembly-code lines via vectors involving a regkey (1) set or (2) get command.
Published: 2015-05-26 The dissect_lbmr_pser function in epan/dissectors/packet-lbmr.c in the LBMR dissector in Wireshark 1.12.x before 1.12.5 does not reject a zero length, which allows remote attackers to cause a denial of service (infinite loop) via a crafted packet.
Published: 2015-05-26 The dissect_lbmr_pser function in epan/dissectors/packet-lbmr.c in the LBMR dissector in Wireshark 1.12.x before 1.12.5 does not properly track the current offset, which allows remote attackers to cause a denial of service (infinite loop) via a crafted packet.
Published: 2015-05-26 epan/dissectors/packet-websocket.c in the WebSocket dissector in Wireshark 1.12.x before 1.12.5 uses a recursive algorithm, which allows remote attackers to cause a denial of service (CPU consumption) via a crafted packet.
Published: 2015-05-26 epan/dissectors/packet-wcp.c in the WCP dissector in Wireshark 1.10.x before 1.10.14 and 1.12.x before 1.12.5 improperly refers to previously processed bytes, which allows remote attackers to cause a denial of service (application crash) via a crafted packet, a different vulnerability than CVE-2015-...
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.