• 17 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle


























  • My statement about it being up to those running instances is mean in terms of it’s up to them to read the legislation and come to a conclusion. If I were hosting an instance I’d certainly assume it applied, though I doubt there has been any case testing its implementation in this sort of situation.

    I can see someone starting a lawsuit against a standards incompliant server that ignores deletes and edits, though.

    I wonder if the first data breach will draw the attention of a regulator. We’re all using essentially alpha software, with no privacy notice, I doubt there are RoPAs or DPIAs, I doubt there is a DPO… all those things might upset someone like the ICO in the UK if a breach were to occur.

    Edit: saying that, I’m not sure any breach would even be reportable given what data is collected by Lemmy.


  • Wither GDPR applies to an individual instance will be up to those running the instance to decide.

    If you decide it does, then you need to do a few things. Number one is read up advice on compliance with GDPR.

    Being able to delete data alone doesn’t mean GDPR compliance. I’m thinking about the need for privacy notices on sign up, retention schedules for data, lawful basis of processing, records of processing activities… Data subjects have numerous rights, which apply depend on the lawful basis you’re processing under.

    I’d suggest that larger general instances might want to read up more urgently than smaller single focus “hobby” instances.

    edit: more I think about this, I think there is an moral responsibility for the developers to help those running instances comply. If GDPR does not apply to an instance, it is still good practice to allow uses to delete their data, etc… Also, art. 20 of GDPR is the right to portability. Interesting to see how this applies to fediverse platforms like Lemmy.