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
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: just wondering...Thanx
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.