Re:How to track users for analytics in a privacy-first, cook...
by culturedsystems on Wednesday June 16, 2021 @07:54PM
(#27534807)
Note that you still need to get consent for the cookie in this case, as the cookie is being used for something which isn't strictly necessary to provide the service.
[ Parent
| on HN ]
Re:How to track users for analytics in a privacy-first, cook...
by CogitoCogito on Friday June 18, 2021 @03:05AM
(#27548048)
I think this is kind of interesting question actually. If this cookie is entirely separated from the rest of the experience (e.g. _never_ gets associated to a logged in cookie, or IP address, etc.), is it really tracking the user? It's more like tracking article association. I agree it's not strictly necessary to provide the service, but is it necessarily tracking users at all? Another similar approach would be to keep the clients IP address as a similar key, but in that case the IP address can often be used to (at least closely) identify the client, but if the UUID is randomly generated it's a bit different.
I mean my gut feeling is that you're correct, but I kind of wonder about this case.
edit: A cursory reading of this site makes me think you are correct:
Re:How to track users for analytics in a privacy-first, cook...
by xyzzy_plugh on Wednesday June 16, 2021 @08:16PM
(#27534940)
If the cookie is never used until a later date e.g. conversion, when the user clicks through an agreement, do you still need consent?
Edit: I honestly have no idea, I haven't read the regulations and I'm curious if any experts know. Seems sleazy regardless!
Re:How to track users for analytics in a privacy-first, cook...
by AstralStorm on Thursday June 17, 2021 @02:33AM
(#27536735)
What does it mean? Even a session cookie is used at a later date, e.g. 5 minutes later. The law does not specify minimum retention time.