-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revoke consent after accepted #86
Comments
In my opinion, you should have a clear page about what cookies are and how your site uses them. An example of mine can be found here: https://www.rickvanlieshout.com/cookies. Smashing a "notice" in the user's face with info where and how to disable them is a bit... invasive if you ask me. I have the page above linked IN the cookiebar but it's also visible on every page (it's a link in the footer). My thoughts are basically as follows:
I make my cookie bar as easy to ignore as possible for user a, detailed enough for user b, and I can't do anything (nor want to) for user c. This, in my opinion, is as far as anyone should go. There's a certain responsibility on the users themselves as well. |
Thanks for your detailed reply. I was looking for a technical answer and I have received a global answer with which I agree. |
I'm adding the technical details for people stumbling upon this answer: you can provide a button which executes:
|
Hi, thanks for this plugin. In your experience, what do you think is the best way to revoke consent once it has already been accepted?
The text was updated successfully, but these errors were encountered: