Risk

3/9/2011
06:43 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Google Again Sued Over Gmail Content Scanning

The latest complaint argues Google's disclosures are inadequate because nobody reads lengthy legal documents.

Attorneys representing former Gmail user Kelly Michaels of Smith County, Texas, have sued Google, claiming that its Gmail service violates users' privacy by scanning e-mail messages to serve relevant ads.

This is not the first time Google has faced such a suit. Another Texas resident, Keith Dunbar, made similar claims in November, 2010. It's an issue Google has been dealing with since Gmail was introduced in 2004.

At Google's request, the Dunbar suit has been sealed. However, in a reply filed prior to the sealing of the case, Google's attorneys provide highlighted terms of service and the company's privacy policy as exhibits to show that users are informed about how Gmail operates.

Michaels's complaint takes the novel approach of arguing that while Google asks users to accept its terms of service, the company doesn't require that users actually understand what they're agreeing to. Such comprehension is all but impossible, the complaint suggests, because terms of service documents are difficult to read, if they're read at all.

The complaint bemoans how users who wish to read Google's Terms of Service have to scroll through a small text box with something like 92 paragraphs or visit a 15-page print-friendly version. Then there's a separate Program Policy and Privacy Policy, each on different Web pages, and the Privacy Policy includes some 55 external links.

"None of the multiple pages or links provides an opportunity for a user to inquire about the meaning of any of the terms used or negotiate the addition or deletion of the terms of the documents the user is supposed to be accepting," the complaint says, as if there were any Terms of Service documents that supported the addition or deletion of specific terms. That may happen in face-to-face contract negotiation but Web contracts have traditionally been take-it-or-leave-it affairs.

The complaint goes on to observe that no less than U.S. Supreme Court Chief Justice John Roberts "has admitted he doesn't usually read the 'fine print' that is a condition for accessing some Web sites."

It's widely known that people don't read lengthy documents online, particularly dry legalese. There's even Internet shorthand for the phenomenon: "TL; DR," which stands for "too long; didn't read."

Sadly for the plaintiff, there's no legal recognition of "TL; DR," even if companies like Google and Facebook recognize the problem. Both companies have acknowledged how difficult it is to read and understand lengthy privacy and terms of service documents, and have tried to make them less impenetrable.

Readability also recently surfaced in the ongoing legal battle between Microsoft and Apple over whether the term "App Store" can be trademarked. Microsoft argued that Apple's court filing should be rejected because it uses an impermissibly small font. However, that claim is based on specific rules for document presentation set forth by the court.

Eric Goldman, associate professor of law at Santa Clara University School of Law, characterized Dunbar v. Google last year as an "are-you-kidding-me? lawsuit" on his blog. He considers Michaels v. Google to be essentially the same.

"Both of these lawsuits feel like they should have been brought in 2004, not 2011," he wrote in an e-mail. "There is no additional merit to arguing the user agreement was 'TL; DR.'"

Goldman says that the most interesting thing about the case is its location, the Eastern District of Texas, a venue notorious in the past as a breeding ground for patent litigation.

"There have been some changes in patent litigation that may be reducing the amount of patent work taking place in that district," wrote Goldman. "Maybe some of those lawyers are going to repurpose into privacy plaintiff lawyers with their newly available time?"

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6487
PUBLISHED: 2019-01-18
TP-Link WDR Series devices through firmware v3 (such as TL-WDR5620 V3.0) are affected by command injection (after login) leading to remote code execution, because shell metacharacters can be included in the weather get_weather_observe citycode field.
CVE-2018-20735
PUBLISHED: 2019-01-17
** DISPUTED ** An issue was discovered in BMC PATROL Agent through 11.3.01. It was found that the PatrolCli application can allow for lateral movement and escalation of privilege inside a Windows Active Directory environment. It was found that by default the PatrolCli / PATROL Agent application only...
CVE-2019-0624
PUBLISHED: 2019-01-17
A spoofing vulnerability exists when a Skype for Business 2015 server does not properly sanitize a specially crafted request, aka "Skype for Business 2015 Spoofing Vulnerability." This affects Skype.
CVE-2019-0646
PUBLISHED: 2019-01-17
A Cross-site Scripting (XSS) vulnerability exists when Team Foundation Server does not properly sanitize user provided input, aka "Team Foundation Server Cross-site Scripting Vulnerability." This affects Team.
CVE-2019-0647
PUBLISHED: 2019-01-17
An information disclosure vulnerability exists when Team Foundation Server does not properly handle variables marked as secret, aka "Team Foundation Server Information Disclosure Vulnerability." This affects Team.