Live data from Hacker News

How we built a GDPR-compliant website analytics platform without using cookies

usefathom.com

11–20 of 129 posts

Re: How we built a GDPR-compliant website analytics platform without using cookies

#11

I think the GDPR was enacted into law not to prevent cookies, but to prevent collecting data on regular people. This seems to circumvent the technicalities of the law but not the spirit. The risk is that they enact a new law that puts even further restrictions on website operators. I'm not sure this is a good idea.

[deleted]

Re: How we built a GDPR-compliant website analytics platform without using cookies

#12

I think the GDPR was enacted into law not to prevent cookies, but to prevent collecting data on regular people. This seems to circumvent the technicalities of the law but not the spirit. The risk is that they enact a new law that puts even further restrictions on website operators. I'm not sure this is a good idea.

Thanks for the concern here. We are GDPR compliant (and may be exempt from it). See here: https://usefathom.com/data/

Re: How we built a GDPR-compliant website analytics platform without using cookies

#13

Earlier quoted context omitted.

https://crypto.stackexchange.com/a/47810

Based on the blog - anyone who shares a IP address (such as inside a company network) would effectively look the same.

And given most companies run managed browsers on managed systems, the user agent is going to collide too

Re: How we built a GDPR-compliant website analytics platform without using cookies

#15

Earlier quoted context omitted.

https://crypto.stackexchange.com/a/47810

Based on the blog - anyone who shares a IP address (such as inside a company network) would effectively look the same.

Indeed. This is one of the limitations to our approach. We're thinking of ways to workaround it. Please shout if you have any ideas ;)

Re: How we built a GDPR-compliant website analytics platform without using cookies

#16
Most schemes of this kind are just more complicated cookies that people hope will avoid the GDPR provisions by dint of being obfuscated.

What the article is discussing looks (at first brush) to be a sensible way of aggregating users up-front before it hits the database, rather than later. So no personal data is stored.

Does this meet the requirements for a site to avoid notifying users under the GDPR? I have no idea.

Even with the best of intentions, if you use a service like this then you are relying on them a) doing what they claim, and b) not screwing up (by leaving logs around, etc).

If I use this service and data from my users gets leaked by Fathom, who gets blamed? The users were on my site, so I guess it is I that gets fined. Maybe the risk is worth it, maybe it isn't.

Re: How we built a GDPR-compliant website analytics platform without using cookies

#17

Most schemes of this kind are just more complicated cookies that people hope will avoid the GDPR provisions by dint of being obfuscated. What the article is discussing looks (at first brush) to be a sensible way of aggregating users up-front before it hits the database, rather than later. So no personal data is stored. Does this meet the requirements for a site to avoid notifying users under the GDPR? I have no idea.…

>If I use this service and data from my users gets leaked by Fathom, who gets blamed? The users were on my site, so I guess it is I that gets fined.

fathom would get fined

Re: How we built a GDPR-compliant website analytics platform without using cookies

#18

Most schemes of this kind are just more complicated cookies that people hope will avoid the GDPR provisions by dint of being obfuscated. What the article is discussing looks (at first brush) to be a sensible way of aggregating users up-front before it hits the database, rather than later. So no personal data is stored. Does this meet the requirements for a site to avoid notifying users under the GDPR? I have no idea.…

The GDPR (and other data privacy legislation) uses the concept of a "data controller" and a "data processor". Data controllers use a variety of data processors to deliver a service to their users.

If you ran a SAAS and used Fathom analytics, a SMTP email provider (to send password resets), a newsletter provider (for your monthly newsletter), a blog host etc. each of those would be data processors as you (the SAAS) are making the determination of where user data is going on the backend.

As a data controller, it's your responsibility to make sure that each of those services you are using is handling the data in an appropriate and safe way.

As to who gets fined if there is a data breach: the answer is likely nobody. I say this because it's not like you have a credit card on file and breach automatically means a fine. What really matters is what actions you're taking before and after a breach.

- As a data controller did you notify your users with no undue delay?

- As a data processor did you notify the SAAS with no undue delay?

- Did you identify the source of the breach? Did you take steps to remedy it?

For almost all these privacy regulations if you:

1. Take steps to protect user data/privacy like https, encryption etc.

2. Provide a mechanism to allow users to make data requests for their own identifying data

3. Notify users if there's a data breach

You would be in compliance.

Re: How we built a GDPR-compliant website analytics platform without using cookies

#20

Looks decent, but pricing is insanely high for the extremely limited set of stats.

Totally fair, as that's an opinion :) Luckily our customers are happy with the price, and other folks use the open-source (100% free) version. Cheers!

I actually think your prices are pretty reasonable for business use, but I wonder if you've considered a "personal" plan of, say, $6/month for up to 10k hits, non-commercial use only.

I've been looking for a privacy-first tracker for some personal sites for a while, but nobody is offering pricing that makes sense at the lower end.

Post reply on HN