IANAL, but as a layman, I don't think I agree with your article. But thanks for the links. I don't think the difference between hours and days is relevant, unl

IANAL, but as a layman, I don't think I agree with your article. But thanks for the links. I don't think the difference between hours and days is relevant, unless the law says that there's a difference. Setting user preferences, such as the language, is a matter of accessibility. I'd be hard-pressed to think of a better sample of “strictly required”. Setting user preferences, such as a “dark mode” toggle, wouldn't be any different from setting the browser or operating system's dark mode preference, a bit that web pages can always read. It's important to remember that ePrivacy isn't strictly about cookies, but about all client-side data that gets sent to the server. For example, in case you're doing analytics, fingerprinting via any other means except for cookies (e.g., user agent, HTTP referrer, IP, etc.) still counts under ePrivacy. As such, you can fingerprint users via “window.matchMedia('(prefers-color-scheme: dark)')”, and if you do that, then yes, you need a cookie banner. But not for doing what the user agent asked for. For analytics, indeed, you need a cookie banner. And while it's a concern of service providers to improve their service that I understand, it's not something that the user expects. And my personal problem is that the entire web ended up using Google Analytics. Such data ends up being shared with third parties, which is why it's good that it is opt-in. I do agree that businesses should consult lawyers (＾＾)ｂ