In case you didn't know, there are no sites without tracking cookies.
The poison slipped into your morning coffee is also less intrusive than the antidote shot into your arm with a syringe.
> In case you didn't know, there are no sites without tracking cookies.
And thanks to the GDPR, they might make a comeback now.
GDPR is here already and the solution chosen by websites is either the obnoxious banner or blocking Europe. No cookie-less I am afraid...
If a website is obnoxious about its GDPR compliancy, I just close it. Coincidentally, it has never happened on something I really needed (technical documentation, scientific journals, etc.)
I don't necessarily agree with how the GDPR was created, or maybe even why, but to say it's worse than the information tyranny being built in the world today? Pft.
You're confusing "harmful" and "visible".
HN doesn't set tracking cookies, for example. The only two cookies set are the cloudflare uid and a user login cookie, both of which are hardly meant for tracking.
Of course, if you use Google Analytics, you can't guarantee what Google is doing, so you'll need some banner to get consent before you can perform any analytics through GA (which means you need to disable GA until the user agrees, which barely any site does anyway).
If you can guarantee that the analytics won't produce or store personal data, you don't need to disable it or produce a banner.
Even if they did produce personal data, they very likely wouldn't need a banner. For processing personal data you merely need a lawful basis and documented processes, and asking consent is (intentionally) the least attractive lawful basis for using personal data. Consider for example the "legitimate interest" lawful basis:
> processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.
If you're using analytics to, say, optimise accessibility/usability of the site, then it should be fairly straight forward that the legitimate interest of both you and user (of improving the site) outweighs the "privacy harm" of processing that personal data. (Of course, using it for anything else will land you in hot water if you argue this).
Even a 3rd party data processor like Google Analytics would be fine, if they're 1) GDPR compliant and 2) you have a data processing agreement with the provider.
90% of websites who don't do shady things with your personal data should never require any banner or opt-in prompt. The fact that most of the web now does is incompetence, ignorance, intentional annoyance to provoke legislation change, or a mix of these.
There is no escape from GDPR... Bureaucracy at work.
And similar to ads, I expect automated tools to emerge that eliminate most GDPR banners by granting the minimum consent required (optionally alerting the relevant regulator if that's excessively broad) and then revoking it immediately afterwards.
You can't escape bureaucracy, but you can escape the lazy companies who can't think of a better way to deal with bureaucracy than pushing it onto the user.
Ghostery also doesn't report anything. :)
Sites without tracking cookies don't need to show a cookie banner.