Earlier quoted context omitted.
Unless your PII workflow is bonkers, you should be able to respond to those letters in mostly automated fashion. I mean, you do handle your data in mostly universal way, instead of randomly copying pieces of your database to random parties? Right?
How do you automate checking if person requesting the data is the person claims to be. How do you automate reading an email and giving meaningful response?
Publishers Haven't Realized How Big a Deal GDPR Is
401–410 of 468 posts
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#402IP adresses being protected as personal data has an interesting side effect. You can't be compliant under both EU GDPR and Turkish internet security laws (probably shared by a lot of oppressive and semi-oppressive regimes). That law states you have to keep the poster IP address of every post on the site and turn them over on court order. Obviously, as with every law in Turkey, the enforcement is very subjective (for…
> You can't be compliant under both EU GDPR and Turkish internet security laws [...] states you have to keep the poster IP address of every post on the site GDPR does have specific exemptions for holding/processing data per legal requirements.
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#403Earlier quoted context omitted.
> This should have been a brower-based implementation globally that every site must adhere to. This. if EU actually cared enough, they 'd go to the browser vendors to enforce some basic prompts on tracking and forms, and it would be better than gdpr because it would work for everyone from day 1. This law will bring a few more prompts and not much else (because most services can be provided with slight changes like ha…
Or the tech industry could decide that'd be useful to have and implement it. They could put it in a HTTP header with a nice name, maybe "do not track", and don't bother people activating that with tracking or prompts. Oh wait... How many websites are doing that? How many choose "let's bother our users" over respecting their stated preference?
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#404Earlier quoted context omitted.
> This should have been a brower-based implementation globally that every site must adhere to. This. if EU actually cared enough, they 'd go to the browser vendors to enforce some basic prompts on tracking and forms, and it would be better than gdpr because it would work for everyone from day 1. This law will bring a few more prompts and not much else (because most services can be provided with slight changes like ha…
Or the tech industry could decide that'd be useful to have and implement it. They could put it in a HTTP header with a nice name, maybe "do not track", and don't bother people activating that with tracking or prompts. Oh wait... How many websites are doing that? How many choose "let's bother our users" over respecting their stated preference?
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#405Earlier quoted context omitted.
> First it was the completely useless cookie notifications It was useless in the sense it was trying to play nice. It was a gentle call for the industry to self-regulate. The only problem with that law was how naïve it was. Go ahead and block the whole European IP range. See if we care.
You do care. Everytime some web service is US only there's endless ranting from Europeans about it.
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#406Re: Publishers Haven't Realized How Big a Deal GDPR Is
#407Earlier quoted context omitted.
> First it was the completely useless cookie notifications It was useless in the sense it was trying to play nice. It was a gentle call for the industry to self-regulate. The only problem with that law was how naïve it was. Go ahead and block the whole European IP range. See if we care.
You do care. Everytime some web service is US only there's endless ranting from Europeans about it.
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#408Earlier quoted context omitted.
Unfortunately even if you're already handling personal data responsibly, the GDPR still also requires that you be able to provide various documented policies to your regulator on demand, still contains lots of ambiguity about how far subject rights can go in practice, still imposes obligations to include lots of extra detail in privacy policies or otherwise provide lots of information and active warnings to data subj…
How about, “Our documented policy is to not collect personal information from users at all.” Assuming it’s true, wouldn’t that be compliant?
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#409Earlier quoted context omitted.
> That letter is likely only a problem when selectively used by a malicious actor against a small organization. Which is what is so annoying and economically destructive about regulations like these that are broadly applied to all companies, especially on the internet where single person companies are very popular. They are designed in a vindictive way against large companies like Facebook or major online retailers w…
> The western economic environment countinually gets more and more structured favouring large firms, encouraging large scale merging, which usually generates the type of large oligopoly companies who most often does the things that cause regulations to get created, then imposed on smaller firms. This is where socialism differs from communism - in socialism you have big privately owned companies, whereas in communism…
Re: Publishers Haven't Realized How Big a Deal GDPR Is
#410Earlier quoted context omitted.
GDPR also expands what is personal data to include things that are collected as a matter of course such as IP address. You likely have a reason to log that data but GDPR requires that you document it. Further it reaches into your business even if you aren’t trying to do business in the EU, as EU citizens can come to your site without your control. There is a lot to like with GDPR but it absolutely is expansive & easy…
Maybe these things shouldn’t be collected as a matter of course. Should web servers log client IP addresses by default? Why? Does my mail server need to log email addresses of incoming mail by default? “Logging all the things” as default behavior really needs to be a thing of the past. If anyone wants to get their feet wet in open source, there are thousands of high profile projects out there that could use a patch t…
Maybe, but logging useful things is reasonable. We investigate problems with our systems using server logs. We diagnose various security threats, fraud risks and ToS violations using server logs.
We're generally respectful of users' privacy, but we also have a legitimate interest in knowing how our systems are being used and preventing people from doing bad things with them. Those legitimate interests may take precedence over a visitor's right to privacy in some cases, in the same way that you can't tell a government to forget your criminal record or a bank to forget that you owe them money.