<?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: EU cookie law: 4 examples of sites already implementing it</title>
	<atom:link href="http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/</link>
	<description>Where to find Malcolm Coles, reviews, and tips on how to do things I couldn&#039;t do.</description>
	<lastBuildDate>Mon, 25 Mar 2013 16:22:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Steve Masters</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-30419</link>
		<dc:creator>Steve Masters</dc:creator>
		<pubDate>Wed, 02 May 2012 05:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-30419</guid>
		<description>The poster child for implementation should be the Information Commissioner&#039;s website because they are the enforcers for the UK. They have actually reduced their message length and visitors are asked to tick a box. 

It is woefully confusing though because it doesn&#039;t tell you what happens if you don&#039;t tick the box and continue to use the website, the privacy policy explains all the cookies in detail, even giving you links to privacy policies of third parties, but it doesn&#039;t let you selectively block cookies - only accept the cookies. 

In other words, the website of the body that is supposed to be showing people how to make the use of cookies more transparent for users is actually proving how impossible it is to do that.</description>
		<content:encoded><![CDATA[<p>The poster child for implementation should be the Information Commissioner's website because they are the enforcers for the UK. They have actually reduced their message length and visitors are asked to tick a box. </p>
<p>It is woefully confusing though because it doesn't tell you what happens if you don't tick the box and continue to use the website, the privacy policy explains all the cookies in detail, even giving you links to privacy policies of third parties, but it doesn't let you selectively block cookies - only accept the cookies. </p>
<p>In other words, the website of the body that is supposed to be showing people how to make the use of cookies more transparent for users is actually proving how impossible it is to do that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28914</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 04 Jul 2011 00:11:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28914</guid>
		<description>And someone will correct me to say that 3rd party cookies are used across multiple sites to give a higher level of information. This is the thing that should definately be blocked by the law in my mind.

The trouble we are going to have now with privacy is that the browser vendors are simply going to put the stats into their browser id. You have already ticked the box to say that you don&#039;t mind this. They already have your unique product key. They already know who you are.</description>
		<content:encoded><![CDATA[<p>And someone will correct me to say that 3rd party cookies are used across multiple sites to give a higher level of information. This is the thing that should definately be blocked by the law in my mind.</p>
<p>The trouble we are going to have now with privacy is that the browser vendors are simply going to put the stats into their browser id. You have already ticked the box to say that you don't mind this. They already have your unique product key. They already know who you are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28913</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Mon, 04 Jul 2011 00:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28913</guid>
		<description>&quot;1st party&quot;, &quot;3rd party&quot;, &quot;cookie&quot;.

We all get drawn into this.

Storing information on the terminal has security issues. Hmm. Not particularly interested.

I look at this and I see only a couple of things that are required by advertisers, businesses, etc, but might not be wanted by the end user:

1) The ability to identify the session
2) The ability to identify the computer (i.e. the returing session)

These are the two core things that are important to GA I think. 

Anything other than this should be illegal as far as general browsing goes. I can&#039;t see why the lawmakers can&#039;t define it simple rather that waffling with rubbish about storing things on terminals.</description>
		<content:encoded><![CDATA[<p>"1st party", "3rd party", "cookie".</p>
<p>We all get drawn into this.</p>
<p>Storing information on the terminal has security issues. Hmm. Not particularly interested.</p>
<p>I look at this and I see only a couple of things that are required by advertisers, businesses, etc, but might not be wanted by the end user:</p>
<p>1) The ability to identify the session<br />
2) The ability to identify the computer (i.e. the returing session)</p>
<p>These are the two core things that are important to GA I think. </p>
<p>Anything other than this should be illegal as far as general browsing goes. I can't see why the lawmakers can't define it simple rather that waffling with rubbish about storing things on terminals.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerry White</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28888</link>
		<dc:creator>Gerry White</dc:creator>
		<pubDate>Thu, 30 Jun 2011 15:34:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28888</guid>
		<description>Agreed - the risks of cookies etc.. is absolutely minimal compared with some of the other technologies such as Phorm, I actually don&#039;t mind a slightly personalised web and whilst I am pretty open about the fact I am straight (married), I know that some people do not want aspects of their politics, religion, medical searches and  sexuality available to other people. I don&#039;t think that cookies really carry this information to the extent that others think it does - Yes, using some clever tracking and Atlas for example, I could see Mark who bought a mobile from &quot;Mobile Store A&quot; also visited these other websites, and there is a lot of information about people who visit website 1 also visit website 2 but not 3 etc... My point really is that this law is unworkable and a tad ridiculous but if it is law we can&#039;t pick and choose which laws, or can we ? I think it is still a written law that taxi drivers in london should still have a bail of straw in their boot ....</description>
		<content:encoded><![CDATA[<p>Agreed - the risks of cookies etc.. is absolutely minimal compared with some of the other technologies such as Phorm, I actually don't mind a slightly personalised web and whilst I am pretty open about the fact I am straight (married), I know that some people do not want aspects of their politics, religion, medical searches and  sexuality available to other people. I don't think that cookies really carry this information to the extent that others think it does - Yes, using some clever tracking and Atlas for example, I could see Mark who bought a mobile from "Mobile Store A" also visited these other websites, and there is a lot of information about people who visit website 1 also visit website 2 but not 3 etc... My point really is that this law is unworkable and a tad ridiculous but if it is law we can't pick and choose which laws, or can we ? I think it is still a written law that taxi drivers in london should still have a bail of straw in their boot ....</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vicky Brock</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28887</link>
		<dc:creator>Vicky Brock</dc:creator>
		<pubDate>Thu, 30 Jun 2011 15:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28887</guid>
		<description>Google Analytics uses a 1st party, not a 3rd party cookie - meaning the cookie is issued from the website using GA, not by Google in a third party capacity.

Therefore it is the business, not Google, that issues the cookie from its own domain, the data cannot be altered or retrieved by any service on another domain. 

No personally identifiable information is captured (to attempt to do so would be in breach of GA&#039;s terms of service). The information stored on the terminal is available to view by the business and the end user alike - a recent one I picked up looks like this:

71233416.1306161650.5.3.utmcsr=google&#124;utmccn=(organic)&#124;utmcmd=organic&#124;utmctr=ico%20clarification%20on%20privacy%20guidelines

It tracks nothing about me personally, in this instance it just shows how I arrived at the ICO website - google, that it was organic (not paid) search and what specific search term I used to get there.  

My browser already lets me delete this or can even block my machine from accepting it in the first place, again at browser level.

Google Analytics does not store information the business does not have access to - the only information it captures that it does not let the business see is the visitor&#039;s IP address.  This provides a degree of regional context to the reporting, but is anonymised by Google.  This is the only piece of &quot;hidden&quot; information and as a GA user, I have no desire or need to see it.  IP can even be anonymised directly in markets or by businesses that require it, meaning Google doesn&#039;t hold the data either.

I think there is a lot of fear about the wrong thing here - on a scale of cookies, GA is about as benign as you get.  Given that this ruling came into to tackle suspect 3rd cookies exploited by behavioural targeters and cookie exchanges, I find it frustrating that the focus settles on an above board 1st party cookie that was never the target of the legislation - but simply got fudged into the guidelines.

Most of the privacy controls Nick mentions already exist at a browser and user access control level.  I am really not sure an individual online business should be expected to police a families web usage via cookies - surely this kind of control should be managed by the family at the device and browser level?</description>
		<content:encoded><![CDATA[<p>Google Analytics uses a 1st party, not a 3rd party cookie - meaning the cookie is issued from the website using GA, not by Google in a third party capacity.</p>
<p>Therefore it is the business, not Google, that issues the cookie from its own domain, the data cannot be altered or retrieved by any service on another domain. </p>
<p>No personally identifiable information is captured (to attempt to do so would be in breach of GA's terms of service). The information stored on the terminal is available to view by the business and the end user alike - a recent one I picked up looks like this:</p>
<p>71233416.1306161650.5.3.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=ico%20clarification%20on%20privacy%20guidelines</p>
<p>It tracks nothing about me personally, in this instance it just shows how I arrived at the ICO website - google, that it was organic (not paid) search and what specific search term I used to get there.  </p>
<p>My browser already lets me delete this or can even block my machine from accepting it in the first place, again at browser level.</p>
<p>Google Analytics does not store information the business does not have access to - the only information it captures that it does not let the business see is the visitor's IP address.  This provides a degree of regional context to the reporting, but is anonymised by Google.  This is the only piece of "hidden" information and as a GA user, I have no desire or need to see it.  IP can even be anonymised directly in markets or by businesses that require it, meaning Google doesn't hold the data either.</p>
<p>I think there is a lot of fear about the wrong thing here - on a scale of cookies, GA is about as benign as you get.  Given that this ruling came into to tackle suspect 3rd cookies exploited by behavioural targeters and cookie exchanges, I find it frustrating that the focus settles on an above board 1st party cookie that was never the target of the legislation - but simply got fudged into the guidelines.</p>
<p>Most of the privacy controls Nick mentions already exist at a browser and user access control level.  I am really not sure an individual online business should be expected to police a families web usage via cookies - surely this kind of control should be managed by the family at the device and browser level?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28885</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 30 Jun 2011 07:49:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28885</guid>
		<description>Also Google Analytics is a third party tool, and it is Google that is storing the information on the terminal (information that is not actually available to the site that deploys Analytics) - it is therefore possible to argue that it is Google that needs permission and Google that should be asking the question.

Traditionally however it is the overall responsibility of the publisher to ensure that all the components of the communication channel meet the necessary criteria.

So there we see another obvious point of non-compliance from the ICO. They use Twitter to publish information, and when I go to their Twitter pages I do not get asked anything about Cookies. So, going by their example on their own website (where they take responsibility for asking the question regarding Analytics) they either need to discontinue their use of Twitter or to ensure that their Twitter pages ask the question when I visit them.</description>
		<content:encoded><![CDATA[<p>Also Google Analytics is a third party tool, and it is Google that is storing the information on the terminal (information that is not actually available to the site that deploys Analytics) - it is therefore possible to argue that it is Google that needs permission and Google that should be asking the question.</p>
<p>Traditionally however it is the overall responsibility of the publisher to ensure that all the components of the communication channel meet the necessary criteria.</p>
<p>So there we see another obvious point of non-compliance from the ICO. They use Twitter to publish information, and when I go to their Twitter pages I do not get asked anything about Cookies. So, going by their example on their own website (where they take responsibility for asking the question regarding Analytics) they either need to discontinue their use of Twitter or to ensure that their Twitter pages ask the question when I visit them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28884</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 30 Jun 2011 06:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28884</guid>
		<description>Still waiting for a reply from them. In actual fact what they have currently done, and presumably what everone else is going to do in following their example, actually makes the situation far worse that it is at the moment. I am completely in favour of people having more control over their privacy, but consider that in a family household - where privacy is important - a computer could be shared by children as well. A child could visit a site and give wide ranging authority that the adults never know about because the question has not been asked again - there is no attempt made to determine the valididy of the terminal user to enter the contract. So I will definately be waiting for further clarification and maybe browser changes before applying this stupid and dangerous fix to any websites.</description>
		<content:encoded><![CDATA[<p>Still waiting for a reply from them. In actual fact what they have currently done, and presumably what everone else is going to do in following their example, actually makes the situation far worse that it is at the moment. I am completely in favour of people having more control over their privacy, but consider that in a family household - where privacy is important - a computer could be shared by children as well. A child could visit a site and give wide ranging authority that the adults never know about because the question has not been asked again - there is no attempt made to determine the valididy of the terminal user to enter the contract. So I will definately be waiting for further clarification and maybe browser changes before applying this stupid and dangerous fix to any websites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Malcolm Coles</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28882</link>
		<dc:creator>Malcolm Coles</dc:creator>
		<pubDate>Wed, 29 Jun 2011 22:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28882</guid>
		<description>Nick - what did they say in reply?!</description>
		<content:encoded><![CDATA[<p>Nick - what did they say in reply?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28881</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Wed, 29 Jun 2011 22:18:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28881</guid>
		<description>As I pointed out to ICO, their website is not compliant. The law clearly states that the user must have given consent, but there is no way of telling whether the same user is on the terminal equipment from one page to the next. For example I might be happy to give my consent, but my wife might then come on and use the site. She is not asked, but she might not want to give her consent. Since ICO have no way of telling if it is the same user from page to page then they (and all sites) should be asking the question every time on every single page they display.</description>
		<content:encoded><![CDATA[<p>As I pointed out to ICO, their website is not compliant. The law clearly states that the user must have given consent, but there is no way of telling whether the same user is on the terminal equipment from one page to the next. For example I might be happy to give my consent, but my wife might then come on and use the site. She is not asked, but she might not want to give her consent. Since ICO have no way of telling if it is the same user from page to page then they (and all sites) should be asking the question every time on every single page they display.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Heinakroon</title>
		<link>http://www.malcolmcoles.co.uk/blog/eu-cookie-law-examples-of-sites-already-implementing-it/#comment-28849</link>
		<dc:creator>Andreas Heinakroon</dc:creator>
		<pubDate>Mon, 27 Jun 2011 11:17:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.malcolmcoles.co.uk/blog/?p=6243#comment-28849</guid>
		<description>Wow, that&#039;s an impressive graph! And it is just what I feared would happen. Bye bye Google analytics.. :(</description>
		<content:encoded><![CDATA[<p>Wow, that's an impressive graph! And it is just what I feared would happen. Bye bye Google analytics.. <img src='http://www.malcolmcoles.co.uk/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
