The article can be viewed for free on their website and explains to other developers and agencies how Rye has complied with the EU Cookie Law
Cookies are delicious. So it’s understandable why ExpressionEngine likes to consume them: from remembering your last visit, tracking where you are, remembering your shopping cart or whether you’re logged in – they’re just handy.
However, where it starts to crumble (I’m not ditching this trail of puns – get used to it), is for sites that can’t get by without running cookie-less, and running on an “implied consent” basis simply doesn’t cut it.
It’s now pretty widely accepted that sites that need cookies to operate do not need opt-in for that functionality; probably the most common example of this is a shopping cart. So that’s all well and good, but what if your site also uses third-party cookies served up by Google Analytics, advertisements and even Twitter, Facebook and Google+ buttons? They are arguably non-essential, and because they’re third-party, implied consent may not be enough.
Here’s where there will be differing schools of thought. But for this article I’m going to make the argument that if we want cookies for other things such as Google Analytics, serving ads, A/B testing and the countless other things you may wish to do in EE, then we may as well have one single up-front message covering it all in one go.