Closed (fixed)
Project:
EU Cookie Compliance (GDPR Compliance)
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
21 May 2018 at 10:33 UTC
Updated:
23 Jul 2018 at 20:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
hass commentedD7 patch.
Comment #3
hass commentedComment #4
jonnyeom commentedQuestion guys,
Why should this default value be opt_in?
When would this default value be used?
Thanks,
Jonathan
Comment #5
svenryen commentedThanks, hass. This needs to be ported to D8.
@jonathan, this value is used to determine whether the module does "consent by default" (as is the recommended value pre-GDPR) or "consent only on affirmative action" (what it needs to be in order to comply with GDPR). It makes sense that the default is "opt_in".
Comment #6
jonnyeom commentedHmm,
So if GDPR requires "Consent only on affirmative action", wouldn't it makes sense to make the default be "opt_out" ?
Comment #7
svenryen commented@jonnyeom - "opt out" means that visitors will be tracked, presumably against their will, until they "opt out of tracking". The GDPR that comes into effect on May 25 demands that you should rather let the user "opt in" (that is NOT track them until they click a button to confirm they actually want to be tracked). Let me know if that was unclear :)
Comment #8
hass commentedWe should also change
Consent Storage Method. As you know you need to safe the consent and prove someone has confirmed. Everything else is no longer allowed if I understood it correctly. Why should someone configure it than? :-)Comment #9
svenryen commented@hass, I hesitate enabling consent storage by default. The storage method provided by the module is more a "proof of concept", and for busy sites it will be a bottle neck. Can we also handle that discussion in a separate issue?
Comment #10
hass commentedSure, let's move to another issue. I'm also concerned about possible database growth...
Comment #11
svenryen commentedDefinitely a full-fledged consent storage mechanism could have journaling and archival of past consents in text files, but it would be nice if those who need such a feature would gather some sponsorship from a client, and contribute their work back to the community as a patch or standalone module. This is why I made the consent storage a pluggable system.
The basic storage is good for a small blog (it's questionable though, why a blog would want - or need - to track users and handle private information), but definitely not a good choice for a busy newspaper or e-commerce site.
Comment #12
svenryen commentedNote that for now, we're not using 2.x. I'm changing the version to 1.x-dev. Feel free to revert if you object to this :)
Comment #14
svenryen commentedHere's the similar patch for 8.x.
Comment #16
svenryen commented