• dan@upvote.au
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 months ago

    This field needs to be checked everywhere the account is used.

    Usually something like this would be enforced once in a centralized location (in the data layer / domain model), rather than at every call site.

    for the automatic removal after x amount of days

    This gets tricky because in many jurisdictions, you need to ensure that you don’t just delete the user, but also any data associated with the user (data they created, data collected about them, data provided by third-parties, etc). The fan-out logic can get pretty complex :)

    • x00z@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      Usually something like this would be enforced once in a centralized location (in the data layer / domain model), rather than at every call site.

      True. Although not every endpoint is the same, nor is every website or service.

      This gets tricky because in many jurisdictions, you need to ensure that you don’t just delete the user, but also any data associated with the user

      GDPR specifically mentions user identifiable data. I don’t know about others.