Google has made plenty of news lately over concerns with how they handle user privacy. Now it looks like they may have been circumventing privacy settings in Apple’s Safari browser - on computers and iOS devices alike - in order to track users’ web browsing habits for the purposes of advertising.
Is real privacy even possible on the internet anymore? What do you do to protect yourself from online snooping from advertisers and marketers? Let us know in the comments.
According to a report by the Wall Street Journal Friday morning, Stanford researcher Jonathan Mayer discovered that Google and other advertising companies were employing a workaround that allowed third party cookies to be installed by tricking Safari into thinking that the user had submitted a form which allowed the advertisers to set a tracking cooking on the user’s browser. According to the Journal’s researchers, this behavior occurred in Safari both on iOS devices, and on computers (presumably both Windows and Mac versions of Safari). Here’s the Journal’s explanation of how the exploit works:
Google, however, insists that the Wall Street Journal is blowing the situation out of proportion. They say that the code in question was designed to allow certain features such as “Like” and “+1” buttons to function in Safari the way they do in other browsers (which allow third party cookies by default, unlike Safari). The workaround was only meant to apply to Google users who were signed in and allowed Google to show them personalized content. That the code allowed other advertisers to set their own cookies as well. Google says that once the Journal brought this to their attention, they disabled the code and began deleting the cookies.
In response to a request for comment, Google sent us the following statement from Rachel Whetstone, Senior Vice President, Communications and Public Policy:
The Journal mischaracterizes what happened and why. We used known Safari functionality to provide features that signed-in Google users had enabled. It’s important to stress that these advertising cookies do not collect personal information.
Unlike other major browsers, Apple’s Safari browser blocks third-party cookies by default. However, Safari enables many web features for its users that rely on third parties and third-party cookies, such as “Like” buttons. Last year, we began using this functionality 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.
To enable these features, we created a temporary communication link between Safari browsers and Google’s servers, so that we could ascertain whether Safari users were also signed into Google, and had opted for this type of personalization. But we designed this so that the information passing between the user’s Safari browser and Google’s servers was anonymous--effectively creating a barrier between their personal information and the web content they browse.
However, the Safari browser contained functionality that then enabled other Google advertising cookies to be set on the browser. We didn’t anticipate that this would happen, and we have now started removing these advertising cookies from Safari browsers. It’s important to stress that, just as on other browsers, these advertising cookies do not collect personal information.
A request for comment was also sent to Apple, but they have not yet responded. Business Insider, citing “an industry source who we believe understands Google’s perspective” suggests that Google’s intent was not malicious. Rather, they set out to solve a specific problem concerning their advertising business: Safari behaves differently than every other web browser, and that behavior impacts how Google’s ads work. The problem, this source suggests, is that the workaround was likely developed and implemented without thought toward how it would look from a public relations perspective.
Is it possible that Apple is partly to blame for making Safari function differently than other browsers? Should Apple bear any of the blame for the loophole that made Google’s workaround possible? Let us know in the comments.