How to Construct a Website Privacy Statement
In Ireland 2012 you must provide a Privacy Statement on your website. The contents of the Privacy Statement are based on 2 sets of regulations:
- Data Protection Acts 1988 and 2003 (last amended 2012)
- ePrivacy Regulations 2011 (SI 336/2011) - the so-called "cookie law"
What are the laws about?
The Data Protection Acts 1988 and 2003
This law is about gaining consent for the collection and use of an individual's Personal Data. Your website's Privacy Statement must satisfy the principle that you collect and use Personal Data fairly.
ePrivacy Regulations 2011
This law is about gaining consent for the use of any technology that stores information on the end user's equipment. And that is what a Cookie does. Your website's Privacy Statement must clearly document the use and purpose of cookies on your website.
What needs to be in the Privacy Statement?
There is a good FAQ on the Data Protection Commissioner's website. I'll summarise here what the Data Protection Commissioner describes as the minimum requirement for compliance with the laws.
The Data Protection Commissioner's website has more information
Be sure to read the article on the Data Protection Commissioner's website to get comprehensive information about website Privacy Statements
What to say about the Cookies?
The truth is, right now, I'm not sure. I looked at the Data Protection Commissioner's own privacy statement for guidance. Here's what I found:
- dataprotection.ie uses cookies
- dataprotection.ie does not use any prominent/intrusive notices to gain consent for the use of cookies
- dataprotection.ie has ceased using Google Analytics since March 2011 (a popular free tracking service for collecting non personal visitor data which involves the use of cookies)
Img 1. Google Analytics not used on Data Protection Commissioners site since March 2011
Discussion
Have you ever read that the web is "a stateless protocol"? It's an important statement. It means that without using technologies like cookies we have no way of "remembering" things from one webpage to another.
The vast majority of cookies used on websites are for "remembering" things like - is the visitor logged in to a membership area? If so, we can show them a members only webpage. The cookies used for this type of functionality are called "session cookies", only used for the duration of the "session" (visit) and destroyed when the visit to our website is over.
But sometimes we need to set cookies that "persist" - like when you visit a site and choose your geographic location as Ireland. Next time you visit, you are auto-magically sent to the Irish site. That "remembering" is achieved by a persistent cookie that is not destroyed when the visit is over. It may be programmed to persist for weeks, or even months.
The legislators are specifically concerned about persistent cookies that track user behaviour. You may not even be aware that they're being used on your website when you employ third party advertising, analysis, social media functionality or visitor location targetting. It's not deliberate on your part - the company (Google, Yahoo, Bing, Facebook, Twitter, LinkedIn, YouTube etc etc) gives you some code to copy/paste into your website, and bingo, you've got the functionality you wanted. The legislators are well aware of the problem, and they know who they're really after. But in the meanwhile, the responsibility for these cookies is all yours...
Summary
There is insufficient guidance from the Irish regulations and our own Data Protection Commissioner on the matter of cookies.
The stand out phrases in the current legislation are consent for use of cookies, user friendly and current browser settings. So here's what I'm going to do about the cookies:
- Audit all the cookies in use on my site (using this Cookie Audit tool)
- List them out, describe the function of each
- Put it all into the Privacy Statement under a heading called "Cookies"
- Explain to visitors that their current browser settings imply consent for the use of cookies on my site
- Just to be sure (since I use third party cut/paste code for analytics, youtube etc) - put a notice on every page about the implied consent for the use of cookies with a link to the cookie section in the Privacy Statement
I hope I'm on the right track here, but all I've got is my own interpretation of the spirit of the law which is to inform visitors about what personal data we collect and process, and the technologies we make use of, like cookies, that they don't know about (and mostly we don't either).
Get to know and love your cookies
If you use a Content Management System (CMS) like Drupal, Wordpress, Joomla, etc there are going to be dozens of cookies in use that you didn't even know about. They're all there to help your website to function properly.