Pristine_Condition
Member
For those of you who don't know, the Wall Street Journal this week posted a story about Google and three smaller companies secretly circumventing Safari's default setting to block cookies that track users online activity.
Safari (the most popular OS X and iOS web browser) does allow advertisers to place a cookie if the user actually makes a choice and decides to click on the ad. This is the default setting for Safari.
Google used a technique that fooled Safari into thinking a user clicked on an ad when the user never did, and then placed a tracking cookie into Safari without the user's input.
This cookie could then be used to send encoded information to Google if the user used Google+ services. If the user had no Google+ info, the cookie would still be there, and if any other Google ads were "seen" by the browser in that session, other Google cookies, incluing Google's "Double-Click" tracking cookies could be added, again, totally without input from the user.
http://online.wsj.com/article/SB10001424052970204880404577225380456599176.html
Google did this despite language on Google's own privacy site that stated they wouldn't do anything of the kind, (that language has now disappeared from Google's site,) and a pledge from Google to the Federal Trade Commission that they would tell users the whole truth about tracking following them being called onto the carpet by the federal government after Google Buzz was exposed to have gaping privacy issues.
Here's some excerpts from an interview with the Stanford student (working on a PhD in CS and a law degree) who caught Google and the others with their hands in the "cookie jar." (Sorry for the miserable pun.):
Full interview, and more background info, here:
http://blogs.kqed.org/newsfix/2012/02/17/google-safari-spying/
Safari (the most popular OS X and iOS web browser) does allow advertisers to place a cookie if the user actually makes a choice and decides to click on the ad. This is the default setting for Safari.
Google used a technique that fooled Safari into thinking a user clicked on an ad when the user never did, and then placed a tracking cookie into Safari without the user's input.
This cookie could then be used to send encoded information to Google if the user used Google+ services. If the user had no Google+ info, the cookie would still be there, and if any other Google ads were "seen" by the browser in that session, other Google cookies, incluing Google's "Double-Click" tracking cookies could be added, again, totally without input from the user.
Wall Street Journal said:Google Inc. and other advertising companies have been bypassing the privacy settings of millions of people using Apple Inc.'s Web browser on their iPhones and computers-tracking the Web-browsing habits of people who intended for that kind of monitoring to be blocked.
The companies used special computer code that tricks Apple's Safari Web-browsing software into letting them monitor many users. Safari, the most widely used browser on mobile devices, is designed to block such tracking by default.
Google disabled its code after being contacted by The Wall Street Journal.
The Google code was spotted by Stanford researcher Jonathan Mayer and independently confirmed by a technical adviser to the Journal, Ashkan Soltani, who found that ads on 22 of the top 100 websites installed the Google tracking code on a test computer, and ads on 23 sites installed it on an iPhone browser.


http://online.wsj.com/article/SB10001424052970204880404577225380456599176.html
Google did this despite language on Google's own privacy site that stated they wouldn't do anything of the kind, (that language has now disappeared from Google's site,) and a pledge from Google to the Federal Trade Commission that they would tell users the whole truth about tracking following them being called onto the carpet by the federal government after Google Buzz was exposed to have gaping privacy issues.
Here's some excerpts from an interview with the Stanford student (working on a PhD in CS and a law degree) who caught Google and the others with their hands in the "cookie jar." (Sorry for the miserable pun.):
Joshua Johnson
How did you discover this particular cookie from Google?
Jonathan Mayer
We started by running ads of our own. We knew that this loophole existed, and to see which advertising networks had set cookies in Safari browsers we ran ads targeted to that browser's users. Then we we had some code that reported back whether the user had a cookie from each of a number of advertising networks.
The overwhelming majority of some 200,000 Safari browsers in our measurement sample, Google had set cookies on its DoubleClick domain -- that's its advertising domain. Around half of the users had cookies from a company called Vibrant Media. We also saw a number of cookies from a company called Media Innovation Group. These companies aren't nearly the size of Google.
Joshua Johnson
What was your reaction to these results?
Jonathan Mayer
I was a little bit skeptical at first; I ran it by several colleagues to get it verified. I also made sure to test with a bunch of different browsers to see if it was a Safari-specific thing. And we found that it was.
Joshua Johnson
What are the potential implications of these cookies?
Jonathan Mayer
They makes it really easy for Google to have a copy of your web-browsing history sitting on their server. One cookie is linked to your specific Google account. They use that to do social personalization of advertising. Google's response is that there's no personal information at play, which seems odd to me because we have this design document that Google sent us indicating this social-targeting cookie is supposed to have the user's Google account ID on it.
Google claims we mischaracterized what they're doing. When they're talking about mischaracterization, they've left the world of computer science and entered the world of spin. I've tried not to put too much stock in that statement.
And I certainly disagree with a few claims they made. They suggest what they did is okay because this was related to a social feature. [Note: Google said they began using the cookies to "enable features for signed-in Google users on Safari who had opted to see personalized ads and other content--such as the ability to +1 things that interest them."]
I don't think that's quite right. This was not a social feature purely for the user's benefit. It was a social feature on online ads for Google's benefit. It's not much of a stretch to imagine this was the tip of the iceberg in the social personalization of ads Google wanted to do. In fact the design document on this personal socialization feature has a couple of suggestions that the button on ads was just the starting point.
...
Joshua Johnson
Are there still some open questions around this issue?
Jonathan Mayer
I think the No. 1 question is how many users were caught up in this. It's quite possible we're talking about millions or even over 10 million people. Google hasn't suggested this was some sort of limited trial. It's quite possible we're talking about most iPhone owners in America who had their privacy undermined by Google.
Joshua Johnson
How can users gets rid of this cookie on their iPhones, iPads or desktops?
Jonathan Mayer
Google has said they're trying to go back and delete these cookies. And if you go into your Safari settings, you can clear out your DoubleClick cookies if you have them. And Google has stopped the practice and so have other companies.
That said, Google gave users the idea that if you were a Safari user, you didn't need to do anything. The default setting was enough. We know that was clearly not the case. They've since pulled that language; I think it's quite possible they're going to have a problem with the FTC for that possibly being a deceptive business practice.
Second, because they signed a deal with the FTC after the Google Buzz debacle, where they promised under possible sanction of money damages that they wouldnt misrepresent the extent to which users can control the information they're sharing with Google, I think this pretty plainly falls within that language they agreed to.
In my view, this is just another reason why it's time to build a technology that actually puts users in control over third-party web tracking. For a number of years there's been this phrasing among people who work on third-party web- tracking issues that there's an arms race or a cat-and-mouse game going on. And I think these research findings really reify that, quite possibly for millions of users.
So it's time to start thinking about how Google and other players in the online ad industry can work to provide users with a real choice. We've been working on a technology policy proposal called Do Not Track, intended to give users that choice. The World Wide Web Consortium has moved ahead and is trying to standardize it.
The Electronic Frontier Foundation has suggested that one way Google can try to make things right with its users would be to take the lead on Do Not Track, to go ahead and get it implemented in its Chrome browser. That's the only major browser that does not implement Do Not Track.
Full interview, and more background info, here:
http://blogs.kqed.org/newsfix/2012/02/17/google-safari-spying/