<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Connecticut removes restraining orders from court Web site</title>
	<link>http://pibuzz.com/2007/11/22/connecticut-removes-restraining-orders-from-court-web-site/</link>
	<description>Private Investigator | Public Records | Internet Search | Privacy | Reporting | Personal Information | Adoption | Genealogy |</description>
	<pubDate>Fri, 10 Oct 2008 23:52:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: InfoAdvocate &#187; Connecticut Takes Some Protection Order Info off the Web</title>
		<link>http://pibuzz.com/2007/11/22/connecticut-removes-restraining-orders-from-court-web-site/#comment-210493</link>
		<pubDate>Fri, 23 Nov 2007 19:52:35 +0000</pubDate>
		<guid>http://pibuzz.com/2007/11/22/connecticut-removes-restraining-orders-from-court-web-site/#comment-210493</guid>
					<description>[...] via PI Buzz I hear that the Connecticut court is removing some protection / restraining order information from its website.  Effective Monday, Dec. 3, 2007, and in accordance with federal law, information identifying a party protected by a restraining order will no longer be available through the civil/family look-up section of the Judicial Branch’s website. This federal prohibition does not extend to disclosable information in a file at a court clerk’s office. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] via PI Buzz I hear that the Connecticut court is removing some protection / restraining order information from its website.  Effective Monday, Dec. 3, 2007, and in accordance with federal law, information identifying a party protected by a restraining order will no longer be available through the civil/family look-up section of the Judicial Branch’s website. This federal prohibition does not extend to disclosable information in a file at a court clerk’s office. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
