why are you calling it an analytics platform when it isn't one?
How we built a GDPR-compliant website analytics platform without using cookies
51–60 of 129 posts
Re: How we built a GDPR-compliant website analytics platform without using cookies
#52Earlier quoted context omitted.
There's certainly nothing wrong with that. But this sounds a little defensive. And if you're going to promote the "Community Edition"/open-source nature of the codebase, this should probably be made more clear to your users/contributors. (Maybe it is made clear and I'm just not seeing it, though - this is my first time hearing about this product).
I think the defensiveness comes when people put comments such as "I'm a little concerned by the lag in publishing this update". I've never spoken like this in my life to an OS contributor and I use open-source software every day. We're working hard to get the software OS but we were originally planning on keeping the codebases separate (since they were different languages). We only recently pivoted on this after spea…
You know, I do wonder why people talk like that these days. I cannot recall a time when it was acceptable and I certainly wouldn't do it myself. But these snide comments are so common on OSS thèse days.
Re: How we built a GDPR-compliant website analytics platform without using cookies
#53This is very weak reasoning, because you cannot identify an individual by IP either. This project looks like trying to exploit loopholes. The idea behind GDPR is to make sure companies log only data they need. This project looks into logging the data but without expressing why this is even necessary. Therefore I don't think this is compliant with GDPR.
Re: How we built a GDPR-compliant website analytics platform without using cookies
#54Re: How we built a GDPR-compliant website analytics platform without using cookies
#55This is very weak reasoning, because you cannot identify an individual by IP either. This project looks like trying to exploit loopholes. The idea behind GDPR is to make sure companies log only data they need. This project looks into logging the data but without expressing why this is even necessary. Therefore I don't think this is compliant with GDPR.
GDPR is for protection of personal data and we store no personal data. Please take a read of this: https://usefathom.com/data/
Re: How we built a GDPR-compliant website analytics platform without using cookies
#56I am not sure what exactly they did here. How do they persist the hash between requests? My guess is they use localStorage and sending the hash to their servers with each request. So we are talking about a mechanism that’s just like a cookie. As long as they don’t have any PII and can’t figure out who the user was, then I think the GDPR gives them an exception. But “without cookies” claim is dubious!
It's a session long affair, rather than a persistent affair, with 30 minutes apparently the arbitrary cut-off for a session.
Re: How we built a GDPR-compliant website analytics platform without using cookies
#57At first glance this appears to be a well thought out solution. It will never be able to give you some of the stuff that GA can give you but that is by design. The problem that I see is that as long as GA is able to claim they are GDPR compliant there will be very few websites that will see this as a necessity and so adoption will be relatively low. But, and this is just an idea, one of the things that company could do is to proudly present a 'zero retention' button or logo assuming they do not have other trackers on their pages. That way it might become a distinguishing factor for the adopters and that might drive further adoption.
Thanks for building this, I will promote it.
Re: How we built a GDPR-compliant website analytics platform without using cookies
#58At first glance this appears to be a well thought out solution. It will never be able to give you some of the stuff that GA can give you but that is by design. The problem that I see is that as long as GA is able to claim they are GDPR compliant there will be very few websites that will see this as a necessity and so adoption will be relatively low. But, and this is just an idea, one of the things that company could…
A fantastic idea. We've recently designed a button for websites to show users that they care but I really love this idea of a 'zero retention' button :)
Re: How we built a GDPR-compliant website analytics platform without using cookies
#59> Tracking page views alone, without visits, is completely useless and means that you won’t have insight into how many people visit your site / pages each day.
What's the difference between a page view and a visit?
Re: How we built a GDPR-compliant website analytics platform without using cookies
#60> Tracking page views alone, without visits, is completely useless and means that you won’t have insight into how many people visit your site / pages each day. What's the difference between a page view and a visit?
If I came onto your website and refreshed one of your pages 500 times, that would count as 500 page views but only 1 visit.