Risk
5/15/2013
11:52 AM
Dark Reading
Dark Reading
Products and Releases
50%
50%

Google's New Privacy Policy Display Violates California Privacy Protection Law, Is "Deceptive," Consumer Watchdog Tells Attorney General

Google has inserted another page between the home page and the privacy policy

SANTA MONICA, Calif., May 15, 2013 /PRNewswire-USNewswire/ -- A recent change in the way Google presents its privacy policy violates the California Online Privacy Protection Act (CalOPPA) and the policy is "fundamentally deceptive,"

Consumer Watchdog told Attorney General Kamala Harris.

"You have been a leader in the fight to protect Californians' privacy, a right that is enshrined in our State Constitution," wrote John M. Simpson, Consumer Watchdog's Privacy Project director, in a letter today to the attorney general.

"We ask that you continue this fight and take strong action against Google on both of these threats to our privacy."

Read Consumer Watchdog's letter here:

http://www.consumerwatchdog.org/resources/ltrharris051513.pdf

Previously, Google linked directly from its home page to Google's privacy policy, as is required by CalOPPA. Now Google has inserted another page between the home page and the privacy policy.

"The content of this page is designed to convey the impression that Google cares about security and privacy. However, it does not provide a meaningful explanation of how Google handles users' data," wrote Simpson. "In order to get to the privacy policy the user must click on yet another hyperlink. Google is clearly burying its privacy policy and offering distractions to users who are trying to reach the policy from Google's home page."

Even more troubling is what the privacy policy fails to make clear once you finally arrive at the privacy policy page, Consumer Watchdog said. Google's privacy policy is deceptive because of what it omits. The letter continued:

"Nowhere in the policy does Google explain that it gathers the users' data to amass ever more detailed information about them so it can maximize the amount it charges for ads. Users of Google's services are not its customers; they are its product. The information about users -- what they search for, what videos they view, how they use Google's services, how they behave online, etc. -- is what Google is using to sell ads. This is the basis of its business model. This is why our data is gathered, but Google has chosen to omit this crucial detail from its explanation of how it uses data in its privacy policy.

"Leaving out such an important point is in essence lying by omission. It is a fundamentally deceptive explanation of what Google is doing with our data and why it is doing it."

Google gives this explanation of why it gathers users data:

"We use the information we collect from all of our services to provide, maintain, protect and improve them, to develop new ones, and to protect Google and our users. We also use this information to offer you tailored content - like giving you more relevant search results and ads."

Here is the link to the page Google has inserted between the home page and the privacy policy: http://www.google.com/intl/en/policies/

Visit Consumer Watchdog at www.consumerwatchdog.org

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6501
Published: 2015-03-30
The default soap.wsdl_cache_dir setting in (1) php.ini-production and (2) php.ini-development in PHP through 5.6.7 specifies the /tmp directory, which makes it easier for local users to conduct WSDL injection attacks by creating a file under /tmp with a predictable filename that is used by the get_s...

CVE-2014-9652
Published: 2015-03-30
The mconvert function in softmagic.c in file before 5.21, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not properly handle a certain string-length field during a copy of a truncated version of a Pascal string, which might allow remote atta...

CVE-2014-9653
Published: 2015-03-30
readelf.c in file before 5.22, as used in the Fileinfo component in PHP before 5.4.37, 5.5.x before 5.5.21, and 5.6.x before 5.6.5, does not consider that pread calls sometimes read only a subset of the available data, which allows remote attackers to cause a denial of service (uninitialized memory ...

CVE-2014-9705
Published: 2015-03-30
Heap-based buffer overflow in the enchant_broker_request_dict function in ext/enchant/enchant.c in PHP before 5.4.38, 5.5.x before 5.5.22, and 5.6.x before 5.6.6 allows remote attackers to execute arbitrary code via vectors that trigger creation of multiple dictionaries.

CVE-2014-9709
Published: 2015-03-30
The GetCode_ function in gd_gif_in.c in GD 2.1.1 and earlier, as used in PHP before 5.5.21 and 5.6.x before 5.6.5, allows remote attackers to cause a denial of service (buffer over-read and application crash) via a crafted GIF image that is improperly handled by the gdImageCreateFromGif function.

Dark Reading Radio
Archived Dark Reading Radio
Good hackers--aka security researchers--are worried about the possible legal and professional ramifications of President Obama's new proposed crackdown on cyber criminals.