Un-consenting [#1569478]

I have put this as a support request as it's something that should be considered.

As we know the module does not block cookies being set, but provides a way of presenting the user information on cookies, and allowing them to consent.

One thing whilst talking to the ICO, and reading the information on their site, it implies there should also be a way for a user to change their mind and withdraw consent.

If, or how this module could do such.....

Comments

Comment #1

Miszel commented 10 May 2012 at 13:08

Yes, that is a good point. I reckon that a website could provide a link (in the footer for example) that would take the visitor to a page that would explain to visitors how to clear cookies in various browsers. I don't think that there is more that the regulator will require.

I was thinking about providing such a page with the module that could be overridden if necessary.

What do you think?

Comment #2

Anonymous (not verified) commented 10 May 2012 at 14:15

On the sites I manage I have created a Cookie Policy page, which I guess could link to an unset option for the module, though would clicking the link set it again:) A provided page is a good idea, as it's already done for the user, as I suspect many will not consider it.

I have visited several UK websites in the last few day, none that provide a form of consent, just a page on cookie policy. So even just having a basic system such as this module should put us further down the food chain when it comes to non-compliance :) Now all we need to do is mention what our cookies do, though we could use a worst case scenario "they will track everything you do" :)

Comment #3

Miszel commented 17 June 2012 at 00:19

Status:

Active

» Closed (duplicate)

These issues are 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.

Comment #4

VinceW commented 18 June 2012 at 09:03

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 it makes sence if a visitor doesn't give consent any more this module provides a way for others to know this.

I think also it isn't the modules responsibility to block all cookies of other modules. I think it's the responsability of cookie setting modules to check wether they are allowed to set cookies. This module is only providing the users consent then.