3 ms·
This is equivalent to setting a cookie with a hit count. It's still storing & submitting information, it's just not using a unique identifier (Which is pretty p
by luckylion 4y ago
This is equivalent to setting a cookie with a hit count. It's still storing & submitting information, it's just not using a unique identifier (Which is pretty privacy-respecting, I'm not saying it's a terrible thing or something).
I assume it will be treated as such, too. If you can use a cookie to do this without consent, this is fine too. If you can't then it's not. The same happens for local/session storage: it's cookie-equivalent.
- xyproto 4y agoThe user with the highest visit count will always be uniquely identifiable, though.
- not2b 4y agoOnly on the same day. Everything is reset the next day.
- jiveturkey 4y agoI don't follow how this is a problem. By that measure, any users behind a unique single IP (no IP pooling, no CGNAT, etc) will always be uniquely identifiable. And for IP there's much fewer steps to personally identify the user. The server necessarily sees the user IP.
- speedgoose 4y agoYes, the IP can be used to identify people. If you want to track users using their IP and respect GDPR, you need to get their consent first. The best is to not store them before you get consent. Having a temporary access log with a few IPs is probably fine. But keeping all your access logs forever for analytics purposes is not fine anymore.