At some stage it might be worth having a default policy, when the community (meaning Drupal community rather than EU) has agreed on the key clauses. My first effort can be seen at http://www.clinicalneurophysiology.org.uk/cookies.
Quite difficult to know what should be included without knowing what each and every module is going to add to the cookies. Some modules probably set 3rd party modules, eg for Google analytics. I tried to keep my text very non-specific.

Comments

Miszel’s picture

Miszel commented
Status: Active » Postponed (maintainer needs more info)
Miszel’s picture

Miszel commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

This is now being addressed in the following feature request: http://drupal.org/node/1633706

I would appreciate your input there and I am closing this issue.

VinceW’s picture

VinceW commented
Status: Closed (duplicate) » Active

re-opened this ticket (see for reasoning #1633706: Providing an default information page for admins and a hook for developers #5

I think a default policy is a good thing to have. For this (and other compliance issues) I've created a new group at: http://groups.drupal.org/compliance (this group isn't public yet, since it has to be approved first)

On the other hand, untill there is community wide consensus about a policy, this module could create a default statement.

At the end it's the owner / webmaster of the site who is having the last call on it.

Miszel’s picture

Miszel commented
Status: Active » Closed (duplicate)

I am cleaning up the tickets queue. Please continue relevant discussion here:
http://drupal.org/node/1633706#comment-6414674