I’d be really keen to host a lemmy instance but just wondering with GDPR and everything, if there is anything else to consider outside of the technical setup and provisioning of hardware?

Lemmy is storing users data so is there any requirement to do anything GDPR wise?

Hope this is the right place for this - But seen a lot of posts interested in hosting their own lemmy instance, and this is an extension of that

  • chiisana@lemmy.chiisana.netEnglish
    1·
    1 year ago

    Question boils down to where is the boundary. Does an alias of your choosing, which uniquely identifies you across the fediverse personally identifiable? I think we all would say yes. Does then actions linked to that alias constitutes as personally identifiable? Well, in absence of the correlation of the ID, it is still technically possible to map out who this user is and what their interests and preferences are, so maybe yes? That’s a hard grey area to determine IMO.

    • poVoq@slrpnk.netEnglish
      2·
      1 year ago

      Indeed, but I think email addresses for email providers (but not everyone else) are handled differently by the GDPR as they are necessary for providing the email service. I think this is similar to how functional cookies do not require consent under the GDPR if they are only used to keep you logged into the site etc.

      • Daniel Jackson@lemmy.worldEnglish
        4·
        1 year ago

        The link I provided says that pseudonymous data can be used to hide personalized data.

        If you are a DPO, you can see the appeal and benefits of pseudonymization. It makes data identifiable if needed, but inaccessible to unauthorized users and allows data processors and data controllers to lower the risk of a potential data breach and safeguard personal data.

        GDPR requires you to take all appropriate technical and organizational measures to protect personal data, and pseudonymization can be an appropriate method of choice if you want to keep the data utility.

        The owner of lemmy.one can use tk338@lemmy.one to map it to an IP and/or email address. This becomes now personally identifiable data. But other instance owners can’t map it to any personalized data, so it is basically “anonymized data” for them.

        You just have to provide a way to either

        • To delete personally identifiable data
        • Unlink the personally identifiable data from the pseudonymized data on your local instance.

        Disclaimer, IANAL, YMMV, yaddy, yadda,…

        • tk338@lemmy.oneOPEnglish
          1·
          1 year ago

          Understood, missed that subtelty. The fact emails aren’t actually shared makes it very GDPR “friendly”