3 ms·
Don't slurp up data worldwide, then. If you don't do that, you're fine. If you do business you'd better know the law of your target audience, isn't it?
by chopin 9y ago
Don't slurp up data worldwide, then. If you don't do that, you're fine. If you do business you'd better know the law of your target audience, isn't it?
- kasey_junk 9y agoHow does one avoid people making web requests originating in Europe from reaching your servers else where? The obvious answer is by geographically identifying them by IP. Which GDPR makes pains to point out is personal data.
- chopin 9y agoSo you don't store data from that IP? How is this a problem? And that's perfectly compliant with the GDPR. It seems you can't be bothered to not store data.
- kasey_junk 9y agoYou don’t see the humor (at least) of a privacy regulation requiring me to learn more about the consumers hitting the site? Previously they were so private I knew nothing but an IP. Now I’m instrumenting my systems with geo lookup databases which usually also include much more fine grained data (such as home/business) than that. In any case, your original point was to just not interact with those people, which requires active filtering and isn’t the same thing as saying ‘just don’t watch that tv show’ in that it demands actions on my part due to behaviors and preferences on someone else’s.
- chopin 9y agoThere is no active filtering required if you don't store anything. I don't understand why this is so hard to grasp. You can learn as much as you want as long as you don't store it or provide that information to a third party. I believe our industry has too long gotten away with a "store everything" mentality. I have zero sympathy for web sites which slurp up everything from their visitors.