4 ms·

What's the point of adding such a massive cookie bar, supposedly for the GDRP, if there's no way to say no? If they don't need/want to be compliant, why have it

• TomK32 8y ago
  especially when you load the cookies and trackers before the showing the consent dialog :D
• kurtisc 8y ago
  I blocked it. I wonder if that counts as a yes.
• ojosilva 8y ago
  Funny, 5 minutes ago I've made this exact call in our website: remove the reject button. Unfortunately, and for the time being, we are not able to give users an alternative, no-cookie version of our website. And we didn't have a good place to send them to when Reject was clicked. history.back() appeared to be the best option but unreliable. So we first replaced it with the legalese equivalent of "close the tab/leave if you don't agree" but it looks like even that is assumed to be implicitly understood by the visitor, so TBH I'm not sure what's the best compromise between usability and compliance.
  • freehunter 8y ago
    Unfortunately I don't think "accept tracking or don't use the site" is in compliance with GDPR. There's some specific language in there about the site needing to be useable even if users don't give permissions to anything that's not 100% necessary for site functionality.