3 ms·
There is no guarantee that your first party tracker does not relay information to a third party via your web server. Furthermore, at least some of the data you
by chopin 8y ago
There is no guarantee that your first party tracker does not relay information to a third party via your web server. Furthermore, at least some of the data you list is considered personal information under GDPR. Block access if you want but do not collect personal data about me.
What I am hating most is that sites where I am willing to send money to (web shops) do these things and send data to ad net works too, no less.
- Klathmon 8y ago> There is no guarantee that your first party tracker does not relay information to a third party via your web server. You have no guarantees at all, but that information is always sent across, and in many cases must be sent to even make a request. You literally can't prevent an IP address from being "sent" because it's needed to route the information back to you. Sending an "Accept-Language" header lets a website be translated into multiple languages. And virtually 100% of my users want times and dates in their local time, not UTC. Just because it's potentially identifying information doesn't mean you can block it and pat yourself on the back as "stopping tracking". When you don't allow an IP address to be sent, you have just created a system where you can arbitrarily choose literally any request and block it under that rule. It's like making a law against breathing oxygen, then arresting anyone that you don't like for any reason because they are breaking at least that law.