Drive we are so privacy focused here. What is to prevent myself or anybody out there, from starting to report individual instances of GDPR and CCPA.
No lemmy insurances are complying with national privacy laws and nobody is talking about it at all.
Drive we are so privacy focused here. What is to prevent myself or anybody out there, from starting to report individual instances of GDPR and CCPA.
No lemmy insurances are complying with national privacy laws and nobody is talking about it at all.
In the UK a screen name is an identifier. See ICO here. I am in the UK. Therefore combined with other data being collected, e.g. IP. Lemmy and instances I interact with are handling personal data. If it is transferred between instances when I search or view content from one instance to another, there are GDPR implications.
Here is the information I have on your user ID as an operator of a remote instance.
1: Your username and home instance (and a separate link to your profile page on your home instance)
2: Your avatar
3: Your about info
4: Date/time of your last activity (but that I think will be the last time you were seen by my instance, interacting in a community I also have here), so not shared really.
I took a look at the json returned from your home instance, and again the info is profile page, username, information required for communication between instances with the only PII present being the username, the about and an icon and image.
Here’s why I’m going to say this isn’t likely to be a problem as such. This is the same as on reddit, if I look at a post a user makes I can click on the user and get access to this level of public information. Also under GDPR and DPA based on advice from the ICO data sharing isn’t forbidden, but the minimum required to fulfil the function of that sharing should be sent. I think the above data meets that. There isn’t information we don’t need to work a distributed network like this.
I think the point about making a privacy policy visible is a good one. It should make it clear how the network works, and what kind of information is shared with federated instances (and also available to the public, the user query is publicly available). But the data that is federated is the same as is publicly available.
Now I do feel like there’s the scope for a lot of manual work. For example, federation sometimes means that edits/deletes don’t make it. It can be caused by problems on both sides of the connection. So if you want all your data deleted. Sure I could delete all posts and your user info here. And even make requests to the home instances that they delete them too. But, some might remain on remote instances, and I don’t know who would be responsible for that. Some grey areas remain.
This is really interesting, thank you - I definitely agree there is grey areas and work to be done to ensure compliance as far as is possible!
It will be interesting to see how it all unpacks.
I agree, there is definitely work to be done regarding compliance.
If a screen name is an identifier doesn’t that make literally every social website or forum a potential breach? That seems a bit harsh
Not if they are compliant and handle the data correctly, but yes it is a minefield and pretty strict with potential huge fines for non compliance and breaches! I would not want to be in charge of trying to get it all straight for Lemmy!
Non-federated services keep data on their servers or share it with well-defined set of partners. This can be be done in accordance to GDPR. In fediverse that data is broadcasted to anybody who wants to listen (this make the network open). That is a big difference.
I hope you never send an e-mail overseas. Your e-mail provider would be in breach.
Just to be clear - I don’t think it is in breach but you have federated servers in various countries, some of which may be owned by entities that do business in the EU making copies of and forwarding messages that contain PII .
How would they be in breach?
You send the exact same kind of information when you send an email.
Username, host, and IP.
But e-mail is sent from one entity to another, through servers providing service for one or the other party. Most of Lemmy and Mastodon activities are publicly broadcasted and can be received and collected by any federated server.
Your email address (personal identifier) is right there in the from field. And in many cases, in the header there might be your IP address.
How is that a breach of GDPR?
Our point is, sharing the information required to make a network like this work is allowed provided you’re not sending information not required. If you right a post on a community that is shared the information about you (user id, avatar etc) is required to render that message on other federated instances. In the same way as when you send an email the from address is required so that people can reply to the email.
If we were sending IP addresses and data on your browsing preferences to other instances, there would be an argument because it is not required operate the federated network (although you know the corporate players are all justifying their sharing of exactly that data and more). But we don’t do that.
Thank you! Understand - I think the issue is there there is no documented policy on some instances, I don’t know how each instance handles / shares my data and what the retention policies etc are. I seem to remember there are more controls required depending on where the data is being transferred to. Anyway, that’s getting beyond what I am familiar with!
Yes, definitely and this has prompted me to write one up for mine. Even though right not it is just me, I am open to having around 100 active users on my instance. So this should be clear I think.
Awesome! I’m pretty sure there are some great websites with resources if you need it, although they likely come with a caveat they are not legal guidance :)