3 ms·
Cookie consent setting page stores 2 reasons for technical cookies: > Stores the information as to whether the user agrees to statistical analyzes or rejects t
by jve 6y ago
Cookie consent setting page stores 2 reasons for technical cookies:
> Stores the information as to whether the user agrees to statistical analyzes or rejects them
> Stores the information as to whether the user agrees to cookies or rejects them
As for what @capableweb said, did they update something or what? Before consenting to cookies I CAN actually open settings and... analytics cookie by default was disabled for me.
- dspillett 6y ago> analytics cookie by default was disabled for me I've noticed that a lot of permission boxes are disabled by default if you open the settings, but not otherwise. The optics are better that way: it makes any claim to care about your privacy look less dubious. It also catches people who go to settings and blindly click all the options to turn them off without reading the screen: they accidentally turn them on instead.
- Macha 6y agoIf these are just boolean flags, there's no GDPR consent required for these. If they're a user ID that is used to look up a database of GDPR consents, then they have PII and there's a need to have another valid reason under GDPR to store them. The issue is the flow to disable tracking cookies (maybe this is the right flow?): Step 1: Click Accept to be tracked or settings for details Step 2: Go to settings. Analytics is unticked. My understanding is clicking accept in the first page would still have granted permission. Step 3: Go back? Step 4: Click accept? Why is clicking accept going to have a different behaviour in step 4 than if I'd clicked it in step 1? I didn't change anything, just viewed settings. Is viewing settings the opt out? Is there no behaviour and then clicking accept on step 4 _does_ allow the tracking cookies? What was the point of the settings page? Yahoo's GDPR page has much of the same issues for me.