There's EU law that asserts that sites MUST have informed consent from their users before they can store or retrieve data on their devices. It's probably fair for Commons to expect those making a public site out of it to sort out other such legal requirements as privacy policies themselves, but really this is a code thing.
The helpful module http://drupal.org/project/cookiecontrol adds this and only for those countries where it's necessary.
In terms of a privacy policy, there's a great one at wordpress.com which I've been grateful for for a while, which they have under Creative Commons ShareAlike license with no outright stipulation to attribute it.
http://automattic.com/privacy/
Comments
Comment #1
lightsurge commentedHere's a good short and sweet snippet that explains what information should be provided:
http://www.ico.gov.uk/for_organisations/privacy_and_electronic_communica...
Comment #2
lightsurge commentedAs usual with this sort of legal morass it doesn't seem to be as black and white as that. It seems that cookies vital to a website's operation are exempt. So transactional/session cookies etc. Plus it's not just cookies but anything stored on the client, e.g. html5 localstorage.
First-party cookies for analytics and personalised content aren't technically exempt, but apparently at least the UK authorities have said there'd be no interest in regulatory action against websites using such 'minimally intrusive' cookies. Don't really know what that means, so we're breaking the law but only in a very minimal way *rolls eyes* lol
Okay so maybe they're saying 'use your common sense, you know when your website is forcing storage of data on a client that's either unnecessary, or necessary but which you're sharing so you don't know if it will be used improperly'. So that leaves anything third party really, which would be deemed 'moderately intrusive'. Google analytics, mollom, advertising etc etc
I think that's pretty difficult to audit until we have a release here and it's not worth adding another module until known it's absolutely necessary, so setting to postponed.
Comment #3
giorgio79 commentedAnother module http://drupal.org/project/eu-cookie-compliance
Comment #4
lightsurge commentedWell, perhaps this is relevant to keep active. The main alarm bells ring here when third party javascript is included which installs cookies, before a site has the chance to get implied or explicit consent, and that the site including the js has no control over the use of them. At least in the UK we have this notion of implied consent, and opinion that some cookies may be exempt, which might mean this is okay to use so long as there's a warning along the lines of 'if you continue to use this site we'll assume you're consenting to the use of cookies - see our policy to see what may be installed' i.e. the key being there existing a warning before such cookies are installed. But there are cases where it's difficult to guarantee this, or that really you should be getting explicit consent.
For example, there's an issue out which suggests a cookie-less sharethis button might be developed http://forums.sharethis.com/topic.php?id=78651 but not there yet. It might be okay if this button was cookie-less by its presence on a site, but installed cookies when you click it (since you have the opportunity to get consent) but might be questionable as it is.
So I'll put this back active since choices will be made on tools like social sharing buttons #1857354: Configure Social sharing links for default group content types
Comment #5
lightsurge commentedComment #6
achtonFor many of the reasons mentioned in #4, I'm trying to finish up a hook-based expansion of the EU Cookie Compliance module. It is meant to allow other modules to hook into the compliance popup, and fire client-side functionality upon various user actions, e.g. when he/she gives consent.
This way, any module developer can supply a patch or create a new module that "blocks" another module's cookies until such time as consent is given.
For instance, Google Analytics is blocked using the "ga-disable"-approach, and upon consent, the original tracking cookie is set so tracking of the landing page is not lost. Other modules and 3rd party libraries will have different ways of disabling/delaying cookies, but this approach should support them all when it is fully implemented.
As co-maintainer of the EUCC module, I'm willing to put in an extra effort, if Commons 3 needs to ship with these features.
Comment #7
lsolesen commentedThis should be added by the site owner as it is a EU thing.