GDPR/ Privacy / Data erasure policy: Allowing users to delete their own comments

Hello @Suvi Lehtovaara . Thank you for your idea. When deleting a user all his topics and replies are anonymized. Right now there is not a simple operation to delete all topics and replies from a user. It is however possible but a little time-consuming. In control, if you go to the user profile you can see all the topics and replies he created. Topics created can be deleted in bulk, however, deleting all replies requires manual action for each reply.

I'll leave this idea open to see if having a one-click solution is needed. 

Looks like we’re running into this same need. Privacy team would like users to be fully forgotten, not just anonomized. Perhaps this could be linked to the deletion of a user, which in turn results in all associated topics, articles, ideas, replies, likes, comments, etc. being removed from the system.

Messages being fully deleted from a community can really mess up discussions - they will be impossible to follow/read in a coherent way. If it's not a legal requirement I would be weary of hard deleting content based on the impact it can have on your wider community. 

Fully deleting messages from a community can indeed end up messing up the discussion - it is not something that we want from a community perspective.

But, the legal view is that a user has the right to be forgotten and that includes all the messages they’ve posted in the community. It can be argued that if the user is really active and shares a lot anonymisation would not necessarily be enough to wipe out all the traces of that users’ identity.

This is a tricky one!

Any updates or news on this idea?

This matter has come up again in our community and the legal view is quite clear - a user has the right to be forgotten and that includes all the messages they’ve posted in the community.

Even after five years or so, this idea is still very much relevant. Any updates? 😊

I agree that this is still relevant, so I am also wondering if there is an update. 

yes this is valid and we will continue to explore as it can be handled in backend. we will work on it find a better UX to bring it to user.