I'm adding a cookie banner to my app and genuinely wondering if clicking 'Deny' on these banners does anything meaningful. Are cookies already loaded in the background, and is this just a gesture to make us feel good? Are we actually complying with GDPR standards, or are we just slapping a banner on our sites and hoping nobody notices until we get a scary email?
5 Answers
In theory, clicking 'Deny' should mean no tracking cookies would load. If your implementation is done right, it will block those scripts until the 'Accept' button is hit. You can even test it in Chrome Dev Tools to see what happens with cookies when you make your choice.
Exactly, just make sure to choose a comprehensive solution.
By law, clicking 'Deny' is supposed to prevent tracking, but it really depends on how the site is set up. For my clients, we make sure all third-party scripts only run if the user allows cookies, which sometimes frustrates clients who heard differently from previous developers. Still, it's about doing the right thing even if nobody checks on it regularly.
True, I heard the UK regulator mainly checks the top 1,000 sites, so a lot might slip through the cracks. But it's better to play it safe!
Gotcha! It's tough to lose that data in analytics, but better safe than sorry.
Yeah, clicking 'Deny' really should do something. Suppose it doesn't. In that case, that's a big legal issue, especially if you're operating under GDPR where user privacy is vital and violations can cost you a lot.
Totally agree! You really need to respect user choices.
Right? It's shocking how many sites ignore these rules just to keep tracking.
Some cookie banners do function correctly, saving your choice in a cookie. But cookies considered necessary for the service can be added without consent. It's all about how the site operator implements it.
But who decides what's necessary? I mean, can all of them argue they're essential for their business?
I feel like every site's cookie banner has a different level of effectiveness. It really can break a website if the consent question goes unanswered, especially for embedded content like videos. It's definitely more than a useless button!
Exactly, it's all about how it's implemented.
Sounds about right! Some websites even stop functioning if you deny consent.
Makes sense! So if we're using a solid cookie consent library, it should help with tracking all third-party services?