Re:Degoogle: Alternatives to Google products, privacy tips, ...
by hspotorno on Wednesday March 02, 2022 @11:35AM
(#30529232)
Nice! We have made a Google Analytics alternative (getinsights.io) which is not linked there. Servers are still in the US unfortunately, although none of the data from the analytics is sent there. I'll create a PR to add it as an alternative if that's okay.
[ Parent
| on HN ]
Re:Degoogle: Alternatives to Google products, privacy tips, ...
by XCSme on Wednesday March 02, 2022 @05:39PM
(#30534336)
> Insights doesn't use any cookies, so there is no need to put a banner.
Doesn't sending requests from users PC to your 3rd party server require consent as it sends the IP address of the visitor?
Re:Degoogle: Alternatives to Google products, privacy tips, ...
by faeranne on Monday March 07, 2022 @01:30AM
(#30584778)
Does it? I would assume that means every single online interaction needs a consent banner, since sending a request over TCP includes, by it's nature, your IP address. I never dug too deep into GDPR or the like, since my own websites are all for personal use, and I'm not in charge of any of that stuff for work.
I kinda assumed that demanding consent before sending a user's IP would be technically impossible, given that you have to send it as part of the first request, before even being able to ask for permission? Ok, time to research this.
Re:Degoogle: Alternatives to Google products, privacy tips, ...
by XCSme on Monday March 07, 2022 @09:10AM
(#30587975)
I wrote a short blog post about this: https://www.uxwizz.com/blog/self-hosted-analytics-gdpr-frien...
This quote from the GDPR law is more relevant to your question:
> If the controller has the legal option to oblige the provider to hand over additional information which enable him to identify the user behind the IP address, this is also personal data. In addition, one must note that personal data need not be objective.
Re:Degoogle: Alternatives to Google products, privacy tips, ...
by faeranne on Monday March 07, 2022 @01:36AM
(#30584812)
I keep forgetting that part of GDPR is the storage aspect. Unless it goes in a log (though it usually does,) it's not counted. A technical argument could be made that going into memory is storage, but at that point the above issue comes full force, so arguing it doesn't seem to make any sense.