<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Michael Zimmer.org &#187; Cookies</title>
	<atom:link href="http://michaelzimmer.org/category/technology/cookies/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelzimmer.org</link>
	<description>information ethics : privacy : new media : values in design : 2.0</description>
	<lastBuildDate>Tue, 24 Jan 2012 20:33:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Data Privacy Day 2010: No More Cookies or Web bugs at MichaelZimmer.org</title>
		<link>http://michaelzimmer.org/2010/01/27/data-privacy-day-2010/</link>
		<comments>http://michaelzimmer.org/2010/01/27/data-privacy-day-2010/#comments</comments>
		<pubDate>Thu, 28 Jan 2010 05:08:08 +0000</pubDate>
		<dc:creator>Michael Zimmer</dc:creator>
				<category><![CDATA[Cookies]]></category>
		<category><![CDATA[Privacy]]></category>

		<guid isPermaLink="false">http://michaelzimmer.org/?p=1773</guid>
		<description><![CDATA[January 28, 2010 is Data Privacy Day. To celebrate, MichaelZimmer.org no longer uses any services that rely on web cookies or web bugs...]]></description>
			<content:encoded><![CDATA[<p>January 28, 2010 is <a href="http://dataprivacyday2010.org/" target="_blank">Data Privacy Day</a>:</p>
<blockquote><p>Data Privacy Day is an international celebration of the dignity of the individual expressed through personal information.  In this networked world, in which we are thoroughly digitized, with our identities, locations, actions, purchases, associations, movements, and histories stored as so many bits and bytes, we have to ask – who is collecting all of this – what are they doing with it  – with whom are they sharing it?  Most of all, individuals are asking ‘How can I protect my information from being misused?’  These are reasonable questions to ask – we should all want to know the answers.</p></blockquote>
<p>To celebrate, I&#8217;ve taken some steps to make MichaelZimmer.org even more privacy-friendly:</p>
<ul>
<li>I have replaced the commonly used <a href="http://sharethis.com/#STS=g4yp3p9n.no7" target="_blank">ShareThis</a> widget with <a href="http://blogplay.com/sociable-for-wordpress/" target="_blank">Sociable</a>. Both allow readers to easily post and share stories from my blog to various social networking sites, but Sociable does it <em>without</em> the use of <a href="http://en.wikipedia.org/wiki/HTTP_cookie" target="_blank">web cookies</a> or <a href="http://en.wikipedia.org/wiki/Web_bug" target="_blank">web bugs</a>. Sociable simply automatically creates the necessary links, that&#8217;s it. No one is tracking what you decide to share, or where you do it.</li>
<li>I have ended my use of <a href="http://www.statcounter.com/" target="_blank">StatCounter</a> for basic tracking and measurement of who visits this site, how they got here, and what they do while here. StatCounter&#8217;s <a href="http://www.statcounter.com/privacy.html" target="_blank">privacy policy</a> is pretty simple, but the service is dependent on a persistent cookie. While nearly everyone on the planet uses some kind of <a href="http://en.wikipedia.org/wiki/Web_analytics" target="_blank">web analytic tool</a> to track users, until I can find one that doesn&#8217;t rely on cookies or web bugs, I can live without it.</li>
<li>I&#8217;ve updated the site&#8217;s <a href="http://michaelzimmer.org/privacy-policy/" target="_blank">Privacy Policy</a> to reflect these changes (the old policy is <a href="http://michaelzimmer.org/privacy-policy/privacy-policy-old/" target="_blank">here</a>).</li>
</ul>
<p>You can validate these changes by installing the <a href="http://www.ghostery.com/" target="_blank">Ghostery</a> Firefox extension, which alerts you about the web bugs, ad networks and widgets on every page you visit. Nothing should appear when you visit <a href="http://michaelzimmer.org/" target="_blank">MichaelZimmer.org</a>, but you&#8217;ll be amazed to learn how other sites &amp; advertisers are tracking users.</p>
<p>Enjoy Data Privacy Day, and let me know what you&#8217;re doing to <a href="http://dataprivacyday2010.org/get-involved/" target="_blank">get involved</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelzimmer.org/2010/01/27/data-privacy-day-2010/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Google&#8217;s Cookie to have 2 Year Expiration (Because it is of little value after that time)</title>
		<link>http://michaelzimmer.org/2007/07/16/googles-cookie-to-have-2-year-expiration-because-it-is-of-little-value-after-that-time/</link>
		<comments>http://michaelzimmer.org/2007/07/16/googles-cookie-to-have-2-year-expiration-because-it-is-of-little-value-after-that-time/#comments</comments>
		<pubDate>Mon, 16 Jul 2007 18:05:36 +0000</pubDate>
		<dc:creator>Michael Zimmer</dc:creator>
				<category><![CDATA[Cookies]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Search privacy]]></category>

		<guid isPermaLink="false">http://michaelzimmer.org/2007/07/16/googles-cookie-to-have-2-year-expiration-because-it-is-of-little-value-after-that-time/</guid>
		<description><![CDATA[Google announced today they are changing the expiration date of their cookie from 2038 (the latest possible date) to a rolling 2 year period. Once put into action, users who visit Google today, for example, will receive a cookie that expires on July 16, 2009. If that user never visits a Google website again, that [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://googleblog.blogspot.com/2007/07/cookies-expiring-sooner-to-improve.html" target="_blank">Google announced today</a> they are changing the expiration date of their cookie from 2038 (the <a href="http://en.wikipedia.org/wiki/Year_2038_problem" target="_blank">latest possible date</a>) to a rolling 2 year period. Once put into action, users who visit Google today, for example, will receive a cookie that expires on July 16, 2009. If that user never visits a Google website again, that cookie will disappear after those 24 months.</p>
<p>Of course, if that user visits Google again tomorrow, the cookie will renew for a new 2-year period. So, users who visit Google daily (like many), will continue to receive cookies with a rolling 24-month expiration. In practice, then, regular users of Google will not really benefit from this policy change.</p>
<p>This sounds like a great policy shift in order to protect user privacy, but my hunch is that Google is willing to allow this change because they see little value in having cookies linking data beyond a 2 year window. Google uses cookies to help track individual users&#8217; search &amp; related activities in order to understand who that person is and provide personalized results (and, of course, advertisements). If a user searches for &#8220;Paris Hilton,&#8221; having tracking cookies helps Google know whether to provide results about hotels in the French capital or video clips of the celebrity debutante. Google can analyze previous searches associated with that cookie to predict what the user really wants to see. My hunch is that the brilliant data-mining minds at Google recognize that if someone hasn&#8217;t searched on Google in two years, their past history probably isn&#8217;t a good indicator of their current needs. So, if linking to two-year-old data isn&#8217;t all that valuable, they might as well just dump the cookie altogether. It doesn&#8217;t harm their data-mining needs &#8212; <em>and it&#8217;s good PR</em>.</p>
<p>Peter <span class="byline-author">Fleischer <a href="http://googleblog.blogspot.com/2007/07/cookies-expiring-sooner-to-improve.html" target="_blank">explains</a> this move as part of Google&#8217;s &#8220;</span>ongoing plan to continue innovating in the area of privacy to protect our users.&#8221; This is a good first step, but far from a complete solution. An easy way to take this announcement a step further would be for Google to announce that not only will the cookie on my computer expire after 24 months of non-use, but that they <em>will also remove any record associated with that cookie from their internal databases</em>. Such a policy would have a much greater impact on user privacy, since even if my cookie vanishes after 24-months, a record of all my activity remains on the servers in Mountain View.</p>
<p>(Thanks to <a href="http://chimprawk.blogspot.com/" target="_blank">Fred Stutzman</a> &#8212; <a href="http://www.oii.ox.ac.uk/teaching/sdp/Y2007.cfm" target="_blank">sitting in front of me</a> &#8212; for pointing this out to me before Bloglines did)</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelzimmer.org/2007/07/16/googles-cookie-to-have-2-year-expiration-because-it-is-of-little-value-after-that-time/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Tracking Web Users with ClickTale</title>
		<link>http://michaelzimmer.org/2006/07/12/401/</link>
		<comments>http://michaelzimmer.org/2006/07/12/401/#comments</comments>
		<pubDate>Wed, 12 Jul 2006 23:15:52 +0000</pubDate>
		<dc:creator>Michael Zimmer</dc:creator>
				<category><![CDATA[Cookies]]></category>
		<category><![CDATA[Data Aggregation]]></category>
		<category><![CDATA[Online Privacy]]></category>
		<category><![CDATA[ClickTale]]></category>

		<guid isPermaLink="false">http://michaelzimmer.org/2006/07/12/401/</guid>
		<description><![CDATA[Fellow PhD student Alice Marwick blogs about TechCrunch&#8217;s coverage of ClickTale, the latest in website surveillance tools: ClickTale shows you the full story: every mouse movement, every click and every scrolling action. By using ClickTale you will gain insights that will improve your website&#8217;s usability, enhance navigation, and increase effectiveness. Webmasters can add a small [...]]]></description>
			<content:encoded><![CDATA[<p>Fellow PhD student <a href="http://www.tiara.org/blog/?p=214">Alice Marwick</a> blogs about TechCrunch&#8217;s <a href="http://www.techcrunch.com/2006/07/11/watch-internet-users%e2%80%99-behaviour-with-clicktale/">coverage</a> of <a href="http://www.clicktale.com/">ClickTale</a>, the latest in website surveillance tools:</p>
<blockquote><p>ClickTale shows you the full story: every mouse movement, every click and every scrolling action. By using ClickTale you will gain insights that will improve your website&#8217;s usability, enhance navigation, and increase effectiveness.</p></blockquote>
<p>Webmasters can add a small piece of javascript code to their web pages which collects browsing data of all their visitors and transmits it to the ClickTale servers for processing &#038; reporting.</p>
<p>ClickTale <em>does not have a privacy policy</em>, but does offer this nugget in their <a href="http://www.clicktale.com/FAQ.html">FAQ</a>:</p>
<blockquote><p><em>How is user’s privacy affected?</em></p>
<p>ClickTale provides detailed information about users’ browsing behavior, so that usability of websites can be improved. ClickTale does not record any activity outside of the specific web page or outside the browser (no personal files recorded, no internet history, and no interactions with locally installed software). Also, ClickTale does not track users between websites. Inside the browser, no passwords are recorded.</p></blockquote>
<p>Rose-colored glasses, eh? No mention about what the folks at ClickTale do with the data themselves (it all is stored on their servers, afterall). No mention of whether users actually consent to such monitoring, or if they can do anything to prevent it.<br />
In the comments of the TechCrunch post, a representative of ClickTale makes this remark in reaction to others&#8217; privacy concerns:</p>
<blockquote><p>LOL. You might be surprised but most of the users are not concerned by this like you do. This is a personal preference and we respect that. There is an option to install a cookie that will disable the service for you (more on this in our soon to be released privacy policy), or you can use whatever tools that you are familiar with if you don’t like cookies.</p></blockquote>
<p>That&#8217;s real nice. Not only does ClickTale not have a privacy policy (&#8220;soon to be released&#8221;), they find privacy concerns laughable and a minority position. According to their moral compass, protecting one&#8217;s privacy is the burden of user, who must install a special web cookie or some other technical tool to block the service (which, of course, assumes they actually know the tracking service is in place).</p>
<p>I concur fully with Alice&#8217;s assessment:</p>
<blockquote><p>Again, privacy is reduced to a boutique concern of a small number of users. This is unbelievably irresponsible and I have no problem calling ClickTale out on that. There are plenty of ways they could require informed consent from users, but they know that marketers far prefer users <strong>not</strong> to know about tracking, because users will then opt out. These types of technologies should not be opt-out in the first place, and I am curious how this will fly in the EU where privacy rights are more strict than they are in the United States (which has some of the weakest privacy rights in the world).</p>
<p>&#8230;The argument “privacy is dead anyway” is a straw man. Privacy rights have diminished greatly in the United States because people don’t know that most privacy violations are going on, people don’t know what their rights are, and because the government has not legislated any sort of privacy protections. If these things changed, we could have a greater expectation of privacy. To say “there’s nothing we can do” ignores the fact that we are going to see more technologies like this which are increasingly intrusive and problematic.</p>
<p>My solution would be legislative, since neither marketers nor technology companies seem to be able to follow an internal code of ethics. Similar to anti-spam laws, technologies which track user data should a) notify the user and b) require consent to proceed. I also believe that tracking cookies (like DoubleClick) violate privacy, and this type of requirement would cover those as well.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://michaelzimmer.org/2006/07/12/401/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>CFP: Identity and Identification in a Networked World Graduate Student Symposium</title>
		<link>http://michaelzimmer.org/2006/05/19/cfp-identity-and-identification-in-a-networked-world-graduate-student-symposium/</link>
		<comments>http://michaelzimmer.org/2006/05/19/cfp-identity-and-identification-in-a-networked-world-graduate-student-symposium/#comments</comments>
		<pubDate>Fri, 19 May 2006 15:35:15 +0000</pubDate>
		<dc:creator>Michael Zimmer</dc:creator>
				<category><![CDATA[Conferences]]></category>
		<category><![CDATA[Cookies]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[Identity]]></category>
		<category><![CDATA[Identity 2.0]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[Law]]></category>
		<category><![CDATA[Online Privacy]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[RFID]]></category>
		<category><![CDATA[Spyware]]></category>
		<category><![CDATA[Surveillance]]></category>
		<category><![CDATA[Technology & Society]]></category>
		<category><![CDATA[Web 2.0]]></category>
		<category><![CDATA[IINW]]></category>

		<guid isPermaLink="false">http://michaelzimmer.org/2006/05/19/cfp-identity-and-identification-in-a-networked-world-graduate-student-symposium/</guid>
		<description><![CDATA[[I am one of the organizers the following graduate student symposium to be held this fall at NYU] CALL FOR PAPERS Identity and Identification in a Networked World: A Multidisciplinary Graduate Student Symposium When: September 29-30, 2006 Where: New York University Submission deadline: July 5, 2006 Increasingly, who we are is represented by key bits [...]]]></description>
			<content:encoded><![CDATA[<p><span style="font-style: italic">[I am one of the organizers the following graduate student symposium to be held this fall at NYU]</span></p>
<p>CALL FOR PAPERS</p>
<p><span style="font-weight: bold">Identity and Identification in a Networked World:</span><br />
A Multidisciplinary Graduate Student Symposium</p>
<p>When:        September 29-30, 2006<br />
Where:       New York University<br />
Submission deadline:   July 5, 2006</p>
<p>Increasingly, who we are is represented by key bits of information scattered throughout the data-intensive, networked world. Online and off, these core identifiers mediate our sense of self, social interactions, movements through space, and access to goods and services. There is much at stake in designing systems of identification and identity management, deciding who or what will be in control of them, and building in adequate protection for our bits of identity permeating the network.</p>
<p>The symposium will examine critical and controversial issues surrounding the socio-technical systems of identity, identifiability and identification. The goal is to showcase emerging scholarship of graduate students at the cutting edge of humanities, social sciences, artists, systems design &#038; engineering, philosophy, law, and policy to work towards a clearer understanding of these complex problems, and build foundations for future collaborative work.</p>
<p>In addition to presenting and discussing their work, students will have the opportunity to interact with prominent scholars and professionals related to their fields of interest. The symposium will feature a keynote talk by <a href="http://idtrail.org/content/view/42/43/">Ian Kerr</a>, Canada Research Chair in Ethics, Law &#038; Technology at the University of Ottawa.</p>
<p>Submission Information:</p>
<p>We invite submissions on the function of identity, identifiability and identification in the following general areas:</p>
<ul>
<li>Media &#038; communication: DRM systems, e-mail &#038; instant messaging, discussion forums</li>
</ul>
<ul>
<li>Online: Identity 2.0, web cookies, IP logging, firewalls, personal encryption</li>
</ul>
<ul>
<li>Social interaction: online social networks, blogging, meetups</li>
</ul>
<ul>
<li>Consumer culture: RFID product tags, reputational systems, commercial data aggregation</li>
</ul>
<ul>
<li>Mobility: electronic tolls, auto black boxes, RFID passports, SecureFlight, V-ID cards</li>
</ul>
<ul>
<li>Security: video surveillance, facial recognition, biometric identification systems, national ID cards</li>
</ul>
<p>Please submit abstracts, position pieces, demos or full papers for a 10-15 minute presentation to michael.zimmer@nyu.edu by July 5, 2006. Include contact and brief biographical information with your submission. Notification of submission acceptance will be given by July 17, 2006. Limited travel stipends will be available for presenters. Students in need of travel funds should indicate so with their submission.</p>
<p>Program chairs:</p>
<p>- Tim Schneider, JD Student, NYU School of Law<br />
- <a href="http://michaelzimmer.org/bio">Michael Zimmer</a>, PhD Candidate, Dept. of Culture &#038; Communication, NYU</p>
<p>Faculty advisor:</p>
<p>- <a href="http://www.nyu.edu/projects/nissenbaum/">Helen Nissenbaum</a>, Dept. of Culture &#038; Communication, NYU</p>
<p>Sponsors:</p>
<p>- Coordinating Council for Culture and Communications, Journalism, and Media Studies, New York University<br />
- <a href="http://steinhardt.nyu.edu/dcc/">Department of Culture and Communication</a>, New York University<br />
- <a href="http://www.law.nyu.edu/ili/">Information Law Institute</a>, New York University School of Law</p>
<p>(download PDF version <a target="_blank" href="http://michaelzimmer.org/docs/NYU_Identity_Symposium_CFP.pdf">here</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelzimmer.org/2006/05/19/cfp-identity-and-identification-in-a-networked-world-graduate-student-symposium/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Experimenting with a &#8220;StatCounter&#8221; counter on michaelzimmer.org</title>
		<link>http://michaelzimmer.org/2006/01/10/experimenting-with-a-statcounter-counter-on-michaelzimmerorg/</link>
		<comments>http://michaelzimmer.org/2006/01/10/experimenting-with-a-statcounter-counter-on-michaelzimmerorg/#comments</comments>
		<pubDate>Wed, 11 Jan 2006 04:09:38 +0000</pubDate>
		<dc:creator>Michael Zimmer</dc:creator>
				<category><![CDATA[Cookies]]></category>
		<category><![CDATA[Online Privacy]]></category>
		<category><![CDATA[Privacy]]></category>

		<guid isPermaLink="false">http://michaelzimmer.org/2006/01/10/experimenting-with-a-statcounter-counter-on-michaelzimmerorg/</guid>
		<description><![CDATA[To get a better sense of how michaelzimmer.org is being utilized, I have decided to experiment with a StatCounter counter. This was a difficult decision, being that StatCounter utilizes web cookies to help provide information about what IP addresses access this site and how. I&#8217;ve tried to address this concern in the official Privacy Policy [...]]]></description>
			<content:encoded><![CDATA[<p>To get a better sense of how michaelzimmer.org is being utilized, I have decided to experiment with a <a href="http://www.statcounter.com">StatCounter</a> counter.</p>
<p>This was a difficult decision, being that StatCounter utilizes <a href="http://en.wikipedia.org/wiki/HTTP_cookie">web cookies</a> to help provide information about what IP addresses access this site and how. I&#8217;ve tried to address this concern in the official <a href="http://michaelzimmer.org/privacy-policy/">Privacy Policy</a> for michaelzimmer.org:<br />
<blockquote>michaelzimmer.org strongly believes that you have the right to control the use of your personal information, and that your privacy must be respected.</p>
<p>michaelzimmer.org collects no personally identifiable information, but it does utilize <a href="http://www.statcounter.com/">StatCounter.com</a> [<a href="http://www.statcounter.com/privacy.html">privacy policy</a>] to help measure &#038; optimize usage of the site. The Statcounter service makes use of <a href="http://en.wikipedia.org/wiki/HTTP_cookie">cookies</a> to help determine things like (1) whether you are a new or returning visitor, (2) what web sites or search engines have been used to navigate to michaelzimmer.org, (3) the IP address of visitors, and (4) other information about your computer (resoultion, operating system, etc.) to help optimize the site&#8217;s performance. Such data is used only to get a general idea of the make-up of our visitors, and will not be stored, sold, aggregated or mined. [Lean how to block cookies <a href="http://www.jdrn.com/nacl/block.htm">here</a>.]</p>
<p>If you choose to participate in this blog by posting a comment to entries, you can decide whether or not you wish to leave information that could identify you to us and to others who access this site. If you choose to leave identifying information, it is collected and stored for the purpose of recognizing your contribution and enabling others to contact you directly. </p>
<p>Personal information that you provide to michaelzimmer.org will be used only for the purposes you have authorized. michaelzimmer.org does not sell, rent or lease personal data. We do not purchase or otherwise obtain data from other sources.</p>
<p>Any subpoena or attempts by government agencies or private sector organizations to gain access to any information that you give us will be vigorously challenged to the best of our abilities.</p>
</blockquote>
<p>I will quite understand if you decline to allow our cookies on your machine. I have read StatCounter&#8217;s privacy policy statement, and am comfortable with their assurances that they will not pass stats data to any third party, and with their anti-SPAM policy. My StatCounter account information is password protected, and I add my assurance that I will take such steps as I am able to ensure that it stays confidential (I have declined the option to allow others to access the stats data for michaelzimmer.org). </p>
<p>If I become concerned that too much identifiable data is being stored in the stats logs, I will take such steps as I can to reduce and/or dispose of it. If I get substantial feedback from you about data privacy concerns in this regard, I will consider cancelling my use of the StatCounter service.</p>
<p>I hope you find this acceptable; please let me know if you have any comments, questions or protests!</p>
<p>-michael zimmer</p>
]]></content:encoded>
			<wfw:commentRss>http://michaelzimmer.org/2006/01/10/experimenting-with-a-statcounter-counter-on-michaelzimmerorg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

