I guess that could be in regards to user profiling.
Since no fedi platform aggregates user data like “user xy always upvotes topic a, therefore I will show him more on topic a via an algorithm”, or shows algorithmic advertisements, or sells user data for advertisements etc, I don’t think it’s relevant to GDPR at the moment.
Your instance has data covered by GDPR, but the data it sends to other instances is covered by the same exceptions as the data you send in a email. Without exceptions for legimitate interests it would be illegal to send an email from, say, mailbox to Gmail or Yandex Mail.
PII includes any information that can be used to link or correlate personal information. That includes usernames and account IDs. Every like/upvote contains that information, as well as a timestamp, indicating a unique account but also behaviour. The system doesn’t just share a list of names, it shares a list of names with a lot of context. Stuff like this is also why pseudonymisation isn’t sufficient to avoid GDPR obligations.
Usernames aren’t sensitive information, so you can handle it without too much special care (although you do need to ensure basic protection of login credentials against data leaks, for instance by encrypting databases as a minimum requirement). They are PII, though, which means you’re obligated to take some level of care and ensure that the information can be corrected or redacted everywhere.
The GDPR simply wasn’t written with something like the Fediverse in mind. My server knowing when your account upvoted what posts on a third server would be ridiculous if we’re talking about Twitter and Facebook, but it’s the core of vote counting on Lemmy.
GDPR doesn’t include things you choose to make public, otherwise no social media could show your posts or username to anyone. My only doubt about Lemmy and Mastodon is about DMs where people have a reasonable expectation that they are private but they are not.
Edit: and thinking about it, even DMs probably fall into the same exception as email.
That is wrong. GDPR of course covers public information. It simply does not force platforms to hide this kind of information. But transmission of these informations without user’s consent and especially sale of these informations could possibly be prohibited by a court referencing GDPR.
But simply transmitting it for the purposes of making the protocol work, falls under legimitate purposes, like sending an email to email server in China
Mastodon and Lemmy don’t actually share any data actually protected by GDPR, unless the users actively make it public (like using their real name).
Am I right in my understanding that if you run a federated Lemmy instance, you can see who has upvoted what, even on other instances?
Is that not something protected by GDPR?
I guess that could be in regards to user profiling.
Since no fedi platform aggregates user data like “user xy always upvotes topic a, therefore I will show him more on topic a via an algorithm”, or shows algorithmic advertisements, or sells user data for advertisements etc, I don’t think it’s relevant to GDPR at the moment.
No, things like your home address, your IP address, birth date, health conditions, religion, etc are PII.
Upvotes almost certainly falls into “legitimate purposes” since the data is required for moderation.
So, are you saying that Facebook holds basically no data covered by GDPR?
Your instance has data covered by GDPR, but the data it sends to other instances is covered by the same exceptions as the data you send in a email. Without exceptions for legimitate interests it would be illegal to send an email from, say, mailbox to Gmail or Yandex Mail.
PII includes any information that can be used to link or correlate personal information. That includes usernames and account IDs. Every like/upvote contains that information, as well as a timestamp, indicating a unique account but also behaviour. The system doesn’t just share a list of names, it shares a list of names with a lot of context. Stuff like this is also why pseudonymisation isn’t sufficient to avoid GDPR obligations.
Usernames aren’t sensitive information, so you can handle it without too much special care (although you do need to ensure basic protection of login credentials against data leaks, for instance by encrypting databases as a minimum requirement). They are PII, though, which means you’re obligated to take some level of care and ensure that the information can be corrected or redacted everywhere.
The GDPR simply wasn’t written with something like the Fediverse in mind. My server knowing when your account upvoted what posts on a third server would be ridiculous if we’re talking about Twitter and Facebook, but it’s the core of vote counting on Lemmy.
GDPR doesn’t include things you choose to make public, otherwise no social media could show your posts or username to anyone. My only doubt about Lemmy and Mastodon is about DMs where people have a reasonable expectation that they are private but they are not.
Edit: and thinking about it, even DMs probably fall into the same exception as email.
That is wrong. GDPR of course covers public information. It simply does not force platforms to hide this kind of information. But transmission of these informations without user’s consent and especially sale of these informations could possibly be prohibited by a court referencing GDPR.
But simply transmitting it for the purposes of making the protocol work, falls under legimitate purposes, like sending an email to email server in China
Absolutely.
But if a fedi software/instance decided to do something else with this public data, it could get legally problematic. That is the point I’m making.