> Misconception: "If a user doesn't like cookies, they can just disable them in their browser." Wrong: Some cookies may be essential for proper functioning of w

> Misconception: "If a user doesn't like cookies, they can just disable them in their browser." Wrong: Some cookies may be essential for proper functioning of websites. We're very much splitting hairs here, but I think your "wrong" is a very subjective statement that's possible to argue with. A user can always disable cookies as it is their machine: this part of the statement is in fact true. The fact that a site may then break in unknown ways or might continue to function perfectly is an important detail, but it doesn't mean that people can't do it. There's some users that currently browse websites with JavaScript disabled by default, even though the modern web basically depends on it and even highly trafficked sites break in unexpected ways. > Browsers cannot technically propose any means to disable only non-essential cookies, that's outright impossible. The only entity capable of deciding if a cookie is essential or not is the website that sets the cookie. I'm not 100% sure if this is entirely accurate either now, or will be so in the near future. I'm not an expert in this field, but apparently there's a lot of research going into figuring out how to prevent tracking cookies from doing damage and extraneous API calls without breaking websites. Here's one example I've heard of. https://brave.com/privacy-updates/12-sugarcoat/ https://brave.com/privacy-updates/12-sugarcoat/