Why You Can't Just Block EU Visitors, EU Customers, or Any EU Traffic Under GDPR

Re:Why You Can't Just Block EU Visitors, EU Customers, or An... by MatthewWilkes on Sunday May 27, 2018 @02:55PM (#17168476)

Fair point. Pretty much all of my data protection work recently has been with sites that can identify the person, sorry, I let thay context affect what I said.

That said, doesn't this assume the user has a dynamic IP address? You can't easily tell a dynamic from a static, so wouldn't you have to plan for the worst?

[ Parent | on HN ]

Re:Why You Can't Just Block EU Visitors, EU Customers, or An... by joshuamorton on Sunday May 27, 2018 @03:12PM (#17168566)

Maybe, but firewalling an IP range doesn't actually require logging the specific ips. I don't think gdpr has any teeth for information that isn't actually stored.

[ Parent | on HN ]

Re:Why You Can't Just Block EU Visitors, EU Customers, or An... by reitanqild on Sunday May 27, 2018 @03:40PM (#17168732)

> I don't think gdpr has any teeth for information that isn't actually stored.

But if it 1. isn't stored && 2 there is a good reason (e g. be able to block attacks) && 3. it isn't abused for any other illegal reason then I think they are fine, no extra consent needed to store the IP address temporarily.

But then the law has already been followed.

Edit: also I wouldn't expect anyone outside of IT to care if something is "stored" in RAM or on disk. Kn this case that might be a good thing.

[ Parent | on HN ]