<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: New – Google Analytics on Library Web Site</title>
	<atom:link href="http://library.duke.edu/blogs/libraryhacks/2008/12/19/new-%e2%80%93-google-analytics-on-library-web-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://library.duke.edu/blogs/libraryhacks/2008/12/19/new-%e2%80%93-google-analytics-on-library-web-site/</link>
	<description>Tips and tools to save you time</description>
	<lastBuildDate>Thu, 19 Nov 2009 21:57:02 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul</title>
		<link>http://library.duke.edu/blogs/libraryhacks/2008/12/19/new-%e2%80%93-google-analytics-on-library-web-site/comment-page-1/#comment-104851</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 06 Feb 2009 01:06:05 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/libraryhacks/?p=2211#comment-104851</guid>
		<description>It looks like North Carolina&#039;s data privacy laws are looser than many states: http://ftp.legislature.state.nc.us/EnactedLegislation/Statutes/HTML/BySection/Chapter_125/GS_125-19.html.  Exception B1 looks open to ambiguous interpretation.

We examined Google Analytics&#039; EULA and noted that you&#039;re forbidden form reverse engineering the code, they can change it any time, and if it sits on a private/SSL page it can architecturally render the entire DOM contents visible to Google via javascript, effectively exposing research habits with a third party.</description>
		<content:encoded><![CDATA[<p>It looks like North Carolina&#8217;s data privacy laws are looser than many states: <a href="http://ftp.legislature.state.nc.us/EnactedLegislation/Statutes/HTML/BySection/Chapter_125/GS_125-19.html" rel="nofollow">http://ftp.legislature.state.nc.us/EnactedLegislation/Statutes/HTML/BySection/Chapter_125/GS_125-19.html</a>.  Exception B1 looks open to ambiguous interpretation.</p>
<p>We examined Google Analytics&#8217; EULA and noted that you&#8217;re forbidden form reverse engineering the code, they can change it any time, and if it sits on a private/SSL page it can architecturally render the entire DOM contents visible to Google via javascript, effectively exposing research habits with a third party.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bill</title>
		<link>http://library.duke.edu/blogs/libraryhacks/2008/12/19/new-%e2%80%93-google-analytics-on-library-web-site/comment-page-1/#comment-91121</link>
		<dc:creator>bill</dc:creator>
		<pubDate>Thu, 08 Jan 2009 16:35:06 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/libraryhacks/?p=2211#comment-91121</guid>
		<description>someday it would be interesting to try this.   It&#039;s not a task for you,  just would be fun to talk about sometime   :)</description>
		<content:encoded><![CDATA[<p>someday it would be interesting to try this.   It&#8217;s not a task for you,  just would be fun to talk about sometime   <img src='http://library.duke.edu/blogs/libraryhacks/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
