Sep 4, 2009 at 10:21am ET by Greg Sterling
There is a much longer post to be written on Google’s privacy policies and its history of combatting or complying with government requests for information and those of third parties using the courts to get access to user data. But I’ll take two recent items to illustrate the complexity and potential contradictions here.
Google was just ordered to turn over the identity of some Gmail users pursuant to a defamation lawsuit between a Miami-based developer and a newspaper publication that tied the developer to government corruption in the Turks and Caicos Islands. According to an AP article:
Developer Cem Kinay of Miami accuses TCI Journal of causing “reputational damage and lost profits,” according to a civil complaint filed in California. A court order tells Google to turn over data that may help identify users of the newspaper’s account with Gmail, the Internet search company’s e-email service.
Google said in a statement to The Associated Press it is obligated to comply with “valid court orders,” but generally notifies users to give them time to challenge an order, as it did in this case.
This is legally identical to a recent case in which Google was ordered to reveal the identity of an anonymous blogger who was publicly insulting model Liskula Cohen. Ultimately the matter was dropped by Cohen. But it seems pretty clear that these sorts of defamation actions will continue and potentially even pick up steam. It’s also clear that Google will not get involved in defending against them or the idea of revealing user identities.
Stepping back, legal process often comes down to “reasonableness” and balancing competing interests. If someone is being defamed and it is causing damage the injured party does have the right to determine the identity of the person making defamatory claims and pursue an action. The process then determines whether the defendant is liable or not. The complicating factor is that judicial process is sometimes abused and sometimes “defamation” claims are used intimidate people and prevent speech or criticism; one could potentially put the first example above in that category (as the defendants claim).
Now I’ll turn to Google Books and Google’s recent statement about privacy and Books. On its public policy blog, Google says the following:
While Google Books has always been covered by the general Privacy Policy for all of Google’s services, we understand that the privacy of reading records is especially important to readers and libraries. We know that users want to understand how Google’s privacy practices apply to Books today, and what will happen after the settlement. To provide all users with a clear understanding of our practices, and in response to helpful comments about needing to be clearer about the Books product from the FTC and others, we wanted to highlight key provisions of the main Google Privacy Policy in the context of the Google Books service, as well as to describe privacy practices specific to the Google Books service. We’ve also described some privacy practices for services created by our proposed settlement agreement, which is currently awaiting court approval.
In its Google Books Privacy Policy Google says:
Without getting into a an arcane legal discussion here, Google is saying that it must comply with court orders but that it will protect users’ privacy and fight against disclosure of reading lists and user search queries. Google did something analogous in early 2006 when it was the only major search company to fight a Justice Department subpoena seeking search records, justified on that grounds that it was part of the enforcement of the 1998 Child Online Protection Act.
One could imagine the US government or some overzealous government agency trying to get access to reading lists or records to see who might be reading about terrorism or bomb-making or “communism” (even). In that latter context, think about how valuable Google Book Search queries and reading lists would have been, if they had existed in 1950, to someone like Senator Joseph McCarthy in seeking to root out “spies in our midst.” This is hyperbole on my part to make the point that the government might want to get access to this type of information, as it did with query logs in 2006.
Google is steadfastly saying that it will resist such efforts. But is there a double standard?
Where individual identity is an issue it has indicated it will reveal that information if there is a court order. But where broader search query logs are implicated it has fought or indicated it will fight (although that has been championed under the banner of individual privacy). I’m not trying to be a cynic here but I’m seeking to find a way to reconcile these potentially contradictory positions on user privacy.
Google, what say you?
Share, Bookmark & Discuss This Article
More:
Keep Updated: News Via Email | News Via RSS Feed | News Via Twitter
See more stories like this in the Members Library! Check out the Google: Legal, Legal: Privacy sections of the Members Library where this story is filed. Members also get access to exclusive video content, a members-only weekly & monthly newsletter, plus more. Check out all the benefits!
TOP STORIES
SEARCH NEWS BRIEFS
FEATURES & ANALYSIS
RECENT COMMENTS
Stay on top of all the search news with our daily summary, the SearchCap newsletter. View a sample ›
Search Engine Land produces SMX, the Search Marketing Expo conference series. SMX events deliver the most comprehensive educational and networking experiences - whether you're just starting in search marketing or you're a seasoned expert.
SMX Web Site » | SMX Difference » | SMX News »
Join us at an upcoming SMX event:
Learn more about search marketing with our free online webcasts and webinars from our sister site, Search Marketing Now. Upcoming online events include:
Featured sites from our Blogroll
Become a premium member today and receive:
Premium member since 06/2009
I could totally see Google having to fight the US government again, much like they did in 2006….much of this legal jargon is way over my head but this is interesting…thanks for the easy to understand summary!