Vulnerabilities / Threats
9/3/2010
04:15 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Trims Privacy Policy

Moving to improve user privacy, Google has made it easier to understand the company's privacy policies and to find its privacy tools.




Slideshow: Top 10 Tech Newsmakers Of 2010
(click for larger image and for full photo gallery)
Google on Friday said that it has simplified its privacy policies in an effort to make them easier to understand and to operate with greater transparency.

The revised policies don't mark any change in the company's privacy practices. Rather, Google is updating its privacy policies to communicate more clearly and concisely -- the new main privacy policy has over 400 fewer words -- and to reflect the growing integration of Google's services.

Whether anyone will notice remains to be seen. Most Internet users do not read online privacy policies because they're "long, complicated and lawyerly," as Google associate general counsel Mike Yang concedes in a blog post. But the thought counts for something.

Yang says that Google is making two types of improvements. The first involves the deletion of 12 product-specific privacy policies, a consequence of service convergence. As an example, Yang notes that contacts are shared between services like Calendar, Docs, and Gmail. So it makes sense for these services to share a single privacy policy.

The second involves editing, specifically rewriting legalese in clear, readable prose, and omitting the obvious, like statements advising users that sites not owned by Google have their own privacy polices.

In conjunction with this new push for clarity, Google is expanding privacy articles in its Help Center.

The company has also created a new privacy tools page that assembles links to Google's various privacy tools in one place.

Google's updated privacy policy takes effect October 3, 2010.

Also on Friday, Google settled a privacy lawsuit filed in April over the February launch of Google Buzz, a social networking service that created controversy for exposing users' e-mail contacts.

The settlement recognizes changes to Buzz that Google made in response to the initial controversy as a good faith effort to address complaints. It also "...requires that Google undertake wider public education about the privacy aspects of Buzz" and "...provides for the creation of an $8.5 million Settlement Fund."

After deducting legal fees, the balance will be paid to various Internet privacy groups.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

CVE-2014-6132
Published: 2014-12-24
Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

CVE-2014-6153
Published: 2014-12-24
The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.