This is stupid. I’m not a lawyer. But I am a trained GDPR officer at my employer. I don’t work for our data protection office but I work with them all the time. And GDPR violations generally don’t involve the person whose rights have been infringed contacting a lawyer. They contact the Data Protection Commission in their country who pursue the case or don’t.
Let me explain to you (and my erstwhile debaters earlier in the thread) why GDPR is directly relevant to this action by Plex.
There are two possible angles to this: the Article 22 angle and the Article 5 angle.
Article 22
My interlocutors earlier in the thread seemed to want to claim two separate things that are likely contradictory:
- Plex weren’t blocking you personally.
- Plex weren’t using an automated process to carry out these blocks.
Article 22(1) reads as follows:
- The data subject shall have the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her or similarly significantly affects him or her.
Now, Plex has been anything but transparent in what it’s been doing here. They don’t even mention that Hetzner is the company in question and they don’t accuse anyone who got the email of being guilty of TOS violations. That lack of transparency is itself a likely violation under GDPR. But one can imagine that the process went something like this: Plex decides to block all Hetzner IPs. Someone writes a script to go through their customer base, pull out all the Hetzner IPs and send the same email to the account owner. It’s not clear that this meets the definition of “a decision based solely on automated processing,” but it’s not clear that it doesn’t either. It depends what counts as “the decision” and how you interpret “based solely on automated processing” (particularly the words “based on”). First, the decision to block all Hetzner IPs could have been entirely automated: the brief for the script might well have been “find out where TOS violations are likely, find the IP address blocks involved, write an email to any of our customers whose accounts serve from IP addresses in that block.” And all of that could have been automated.
“Decision” for the purposes of Article 22 is a decision to which a person is subject. What decision was I subject to in this case? It wasn’t the decision to block Hetzner. I wasn’t subject to that: Hetzner was. It was the decision to block my IP because it’s hosted by Hetzner. That’s the decision I was subject to. Was that decision based solely on automated processing? I’d say it’s very likely it was.
If it was “based solely on automated processing” then it’s clearly prohibited under Article 22. And I’ve previously linked to some ancillary documentation to GDPR (the WP29 document) that makes clear that this is something that is prohibited outright, not a right that those adversely affected have to claim.
But let’s say it wasn’t totally automated and that humans made the decision based on judgement, etc. Then we have to consider:
Article 5
The first two paragraphs of Article 5 say this:
Personal data shall be:
- processed lawfully, fairly and in a transparent manner in relation to the data subject (‘lawfulness, fairness and transparency’);
- collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes; further processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes shall, in accordance with Article 89(1), not be considered to be incompatible with the initial purposes (‘purpose limitation’);
There is no question that IP addresses count as “personal data” under the definition provided in Article 4 of GDPR. Plex itself also includes “IP addresses” in what it calls “personal data” in its Privacy Policy.
Now, there has been very little “transparency” or “fairness” in relation to those of us whose IP addresses are going to be blocked. Fairness? We are blocked not for having violated the TOS but because others are suspected of violating them. Transparency? We have no idea which providers are blocked (no hosting provider is named in the email), what the process was by which the decision was made to block these IPs, how it was carried out, etc.
So that’s pretty clearly not in compliance. And if you look at Articles 12-21 of GDPR, it becomes a lot more egregious.
Article 12: " The controller shall take appropriate measures to provide any information referred to in Articles 13 and 14 and any communication under Articles 15 to 22 and 34 relating to processing to the data subject in a concise, transparent, intelligible and easily accessible form,"
and
“The controller shall facilitate the exercise of data subject rights under Articles 15 to 22.”
Article 13: " Where personal data relating to a data subject are collected from the data subject, the controller shall, at the time when personal data are obtained, provide the data subject with all of the following information:
- the identity and the contact details of the controller and, where applicable, of the controller’s representative;
- the contact details of the data protection officer, where applicable;
- the purposes of the processing for which the personal data are intended as well as the legal basis for the processing;"
There’s a lot more listed and Plex has done, essentially, none of it.
And this is where the non-compliance with and flouting of GDPR become pretty flagrant. Plex is supposed to have a list of purposes for which they process personal data. And they do:
- To provide the Services
- To improve and enhance the Services
- Product development
- To respond to your requests
- To consider your application for a job
- To communicate with you about Plex (as permitted by applicable law)
- To personalize marketing, advertising, recommendations, and other content and experiences delivered or offered to you through the Services (as permitted by applicable law)
- To facilitate your payment for any products and services we sell
But they are also supposed to provide, under Article 6 the legal basis for that processing. There are only 6 legal bases for processing and Plex haven’t provided any of them. Worse, the purpose for which the personal data was collected in this instance (to block the IPs of those Plex customers using a hosting service that Plex regards as suspicious) figures nowhere in the list of purposes in Plex’s privacy policy. Indeed, it’s incompatible with those purposes (Article 5(2)): if your purpose, for example is “to provide the service,” blocking a customer’s ability to avail himself of the service is not a compatible purpose.
So the situation is, they are using the personal data of those affected customers for a purpose that they have not listed among the purposes for which they collect/process such data; they have not provided any legal basis either for the original purposes or for this new purpose; and they haven’t done any of this in a transparent manner or complied with the GDPR requirements that they provide data subjects with processes to uphold their right of access to the data (Article 15), their right to object (Article 21), their right to rectification of erroneous data (Article 16), etc.
So Plex is not only not in compliance with GDPR in general, but that non-compliance exacerbates and enables the violations of EU data subjects’ rights in this particular case.