<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Google Voluntarily Reveals Bloggers EMail Address</title>
	<atom:link href="http://uneasysilence.com/archive/2007/11/12730/feed/" rel="self" type="application/rss+xml" />
	<link>http://uneasysilence.com/archive/2007/11/12730/</link>
	<description></description>
	<lastBuildDate>Sun, 22 Nov 2009 09:40:00 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike</title>
		<link>http://uneasysilence.com/archive/2007/11/12730/comment-page-1/#comment-400135</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 28 Nov 2007 19:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://uneasysilence.com/archive/2007/11/12730/#comment-400135</guid>
		<description>Yep.  The &quot;Read More&quot; site has issued an update/correction also.</description>
		<content:encoded><![CDATA[<p>Yep.  The &#8220;Read More&#8221; site has issued an update/correction also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://uneasysilence.com/archive/2007/11/12730/comment-page-1/#comment-400128</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 28 Nov 2007 16:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://uneasysilence.com/archive/2007/11/12730/#comment-400128</guid>
		<description>Uh.

Try reading &lt;a href=&quot;http://www.globes.co.il/serveen/globes/DocView.asp?did=1000279585&amp;fid=1725)&quot; rel=&quot;nofollow&quot;&gt;the primary news source&lt;/a&gt; rather than that alarmist blog post.

Google &lt;i&gt;was&lt;/i&gt; ordered to hand it over. A judge issued it and everything. And it&#039;s not like they just let this go by unopposed.</description>
		<content:encoded><![CDATA[<p>Uh.</p>
<p>Try reading <a href="http://www.globes.co.il/serveen/globes/DocView.asp?did=1000279585&amp;fid=1725)" rel="nofollow">the primary news source</a> rather than that alarmist blog post.</p>
<p>Google <i>was</i> ordered to hand it over. A judge issued it and everything. And it&#8217;s not like they just let this go by unopposed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MDPauley</title>
		<link>http://uneasysilence.com/archive/2007/11/12730/comment-page-1/#comment-400118</link>
		<dc:creator>MDPauley</dc:creator>
		<pubDate>Wed, 28 Nov 2007 15:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://uneasysilence.com/archive/2007/11/12730/#comment-400118</guid>
		<description>Update: We received email from Google regarding this story:

We wanted to let you know some facts about this case as we are concerned that the story on TechCrunch (like the one on Globes) is not accurate. 

1. Google’s approach to providing users’ personal data is clear – we only provide information to third parties (such as law enforcement agencies) when they have been through the proper legal process. This ensures that we are able both to protect the privacy of our users and act responsibly where people may have used Google’s products to break the law.

2. In terms of this case:
· Members of the Israeli Shaarei Tikva Council asked for an injunction against Google - requiring us to provide the IP address of a blogger who had allegedly defamed them;
· Google opposed the injunction. Amongst other things, we wanted to give the blogger a chance to explain in court why his or her IP address should not be disclosed to members of the council;
· On 18 November the court agreed that the blogger should be sent a notice (via the blog) inviting him/her to appear at a hearing on 25 November 2007;
· The blogger failed to appear at this hearing – in his/her absence, and having considered all the various arguments, the court ordered that the IP address (which it was holding) be provided to the members of the council.

3. Google approach to this case has been entirely consistent with the way it handles all third party requests for user data.

4. In terms of Blogger, we have clear terms and conditions, which users agree to when they sign up for the service. These make clear that:
· Certain types of content is against our rules;
· Violation of our terms of service may lead not only to the termination of the users’ account but also “state and federal penalties and other legal consequences”; and
· Google may investigate any violations to “comply with any applicable law, regulation, legal process or governmental request”.

In your comment to M Freitas you say “I’d note that Google voluntarily handed these details over, if the court had ordered them to do so, so be it but if they are serious about privacy they would have pushed it to that level, not just caved in at the first opportunity”. As you can see from the details above Google did oppose the injunction in court, we did not just cave in at the first opportunity and we did argue that the blogger in question should have the chance to make their case. But having considered all sides of the argument the judge ordered that the IP address be handed over.</description>
		<content:encoded><![CDATA[<p>Update: We received email from Google regarding this story:</p>
<p>We wanted to let you know some facts about this case as we are concerned that the story on TechCrunch (like the one on Globes) is not accurate. </p>
<p>1. Google’s approach to providing users’ personal data is clear – we only provide information to third parties (such as law enforcement agencies) when they have been through the proper legal process. This ensures that we are able both to protect the privacy of our users and act responsibly where people may have used Google’s products to break the law.</p>
<p>2. In terms of this case:<br />
· Members of the Israeli Shaarei Tikva Council asked for an injunction against Google &#8211; requiring us to provide the IP address of a blogger who had allegedly defamed them;<br />
· Google opposed the injunction. Amongst other things, we wanted to give the blogger a chance to explain in court why his or her IP address should not be disclosed to members of the council;<br />
· On 18 November the court agreed that the blogger should be sent a notice (via the blog) inviting him/her to appear at a hearing on 25 November 2007;<br />
· The blogger failed to appear at this hearing – in his/her absence, and having considered all the various arguments, the court ordered that the IP address (which it was holding) be provided to the members of the council.</p>
<p>3. Google approach to this case has been entirely consistent with the way it handles all third party requests for user data.</p>
<p>4. In terms of Blogger, we have clear terms and conditions, which users agree to when they sign up for the service. These make clear that:<br />
· Certain types of content is against our rules;<br />
· Violation of our terms of service may lead not only to the termination of the users’ account but also “state and federal penalties and other legal consequences”; and<br />
· Google may investigate any violations to “comply with any applicable law, regulation, legal process or governmental request”.</p>
<p>In your comment to M Freitas you say “I’d note that Google voluntarily handed these details over, if the court had ordered them to do so, so be it but if they are serious about privacy they would have pushed it to that level, not just caved in at the first opportunity”. As you can see from the details above Google did oppose the injunction in court, we did not just cave in at the first opportunity and we did argue that the blogger in question should have the chance to make their case. But having considered all sides of the argument the judge ordered that the IP address be handed over.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
