Self GDPR Deletion

Liam C.

Active member
Licensed customer
I've seen a few platforms (unrelated to Xenforo) allow for their own button for account deletion.

Is there a reason to why Xenforo does not have this feature built in?
We're planning to create our own addon for this - where a user can go to their account settings & request an account deletion in accordance with GDPR, and then schedule the deletion within 14 days automatically. This allows them to opt out of this, if they happen to change their mind.

My question is... why hasn't this be done already? Is there concerns with this idea? I haven't seen any addon implemented this either.
Would love some insights! Thank you
 
Is there a reason to why Xenforo does not have this feature built in?
You're still correct IMHO, it should have been a core feature long ago, considering GDPR rolled out donkeys ago. Lots of updates since GDPR, plenty of opportunity for that requirement to be incorporated, its not a big one, but important for EU members and to comply with EU regulations.
 
You're still correct IMHO, it should have been a core feature long ago, considering GDPR rolled out donkeys ago. Lots of updates since GDPR, plenty of opportunity for that requirement to be incorporated, its not a big one, but important for EU members
It clearly should be a core feature...
and to comply with EU regulations.
... but it is not required to comply with GDPR or EU regulations. There must be a described and easy way to delete an account and even more personal data - however: I am not aware that "self delete" would be an explicit requirement. I.e. sending a PN to an admin as the described way would be totally sufficient. Obviously, self delete is a way better and more comfortable option - but not a legal requirement. If you know differnt I would be thankful to get a hint/link to the exact paragraph/text where this is required.
 
I don’t believe that not having such a feature is an infringement of GDPR. I certainly honour any request for account deletion but I believe it is not a good idea to make it possible for members to delete their own account.
 
I certainly honour any request for account deletion but I believe it is not a good idea to make it possible for members to delete their own account.
Why? Out of curiosity.

I have it on mine, I think its a rolling 30 day deactivation period, then it deletes, randomises their username, deletes all their profile data, account data, keeps content, removes avatar, etc. Has no impact on the content.
 
I believe it is not a good idea to make it possible for members to delete their own account.
I am using this add on and can see no downsides. If anyone wants to quit he can do so easily w/o searching for the right process and now some people quit that otherwise would simply have not come back due to lost interest. So them leaving does not harm and keeps the user database clean. I have less admin work and, as the rules are simple and clear, less discussions about "how can I get deleted" or "I want my content deleted" and the occasional rage quit with posting insults in the forum while publically requesting account deletion has also stopped happening since having the add on in place. The number of people actually leaving has stayed small. I can only recommend it.
 
Why? Out of curiosity.
When I have had requests for account deletion I (or my colleague moderator) has a discussion to find out what the problem is. Often it may be something that we solve and they change their minds.

People can sometimes be a little too impulsive. In one example a member took another member post as a personal attack and asked for account deletion. It ended up that it was not an attack just a misunderstanding due to language differences and it was all explained and everythingturned out fine.

In some cases have gone on to become very useful members. I think that dialogue is useful and may never happen if it's just a delete account button.
 
Exists for ages already and works flawlessly.

👇

How would that add-on deal with PII contained within a member's content?

In my experience a GDPR self-deletion function can generally only end in one of two ways, both of which are far from ideal. If it includes the member's content then the potential damage to the forum is obvious, especially if the member is longstanding and active.

If it doesn't include the member's content then you must give them the opportunity to identify any PII contained within their content before the account is anonymised. Failure to do so would put you in breach of the UK's GDPR.
 
How would that add-on deal with PII contained within a member's content?
I doesn't b/c it can't.
In my experience a GDPR self-deletion function can generally only end in one of two ways, both of which are far from ideal. If it includes the member's content then the potential damage to the forum is obvious, especially if the member is longstanding and active.

If it doesn't include the member's content then you must give them the opportunity to identify any PII contained within their content before the account is anonymised. Failure to do so would put you in breach of the UK's GDPR.
Where is the difference to manually deleting a user? There you run in the same problems. Our TOS recommend using a nick-name as the forum name, be wary to publish any PII information and warrants on registration that we have the right to use and publish the content the user creates as well as that, when a user gets deleted, his content won't be deleted but stays on the forum. In case that there is a PII issue we urgently recommend the user to contact us before a deletion happens and to name that content, so we can anonymize it or delete it. After a deletion this is barely possible as the only identifyer we have for an account, the mail address (which is a pretty weak identifier anyway) has been deleted so we can't check if the person requesting is indeed the person who created that content.

That issue is no different between self delete and deletion by an admin. If you want to avoid it you can't delete any user which is a bit pointless as a solution and clearly against GDPR, too. The whole idea of deletion is to disconnect the identity of a deleted user from his content...

Clearly, the relevance of this aspect highly depends from the forum topic and content and how grown up the users are.

The only cases we had in that "delete PII content" direction in the past were photos and that was less than a handful of times and less related to PII than to some form of "this is mine and I don't want you to be able to use it in future". Way more common (but still rare) was the case where s/o did kind of a rage quit and requested all his content to be deleted, referring to GDPR and threatening us with a lawyer. In complete ignorance that this demand is explicitly not covered by GDPR. All these cases were not motivated by data protection at all but by the desire for attention, harm the forum and annoy and create work for administration. They were fruitless but costed time, attention and energy. We have never ever seen a letter from a lawyer until now. And these cases have (until now) stopped completely since we implemented self delete. Probably b/c if s/o rage quits not having to get in contact, having to "beg" for deletion, but be able to self delete autonomously creates less friction, gives him himself the responsibility for the action and therefor calms things down in such a situation.
 
If it includes the member's content
There is no requirement to delete their content... just their personal profile and its details, and only content IF they shared their real name, phone, email, etc, in public... which is useless, because once that is done, its out there and no removing it from the source will remove it from everyone who has it. Go figure! The amount of times I have explained that to people, and they thought it would delete from Google and all other sources.
 
There is no requirement to delete their content... just their personal profile and its details, and only content IF they shared their real name, phone, email, etc, in public... which is useless, because once that is done, its out there and no removing it from the source will remove it from everyone who has it.

Unfortunately that would not satisfy Article 17 of the UK GDPR. Aside from your example there are multiple other cases where deletion if requested might be necessary. I say might because as it is written there are still many grey areas.

I doesn't b/c it can't.

It can't but it could help facilitate a processes whereby the requesting member has to identify content they want removed.
 
It can't but it could help facilitate a processes whereby the requesting member has to identify content they want removed.
Should be easy to do that yourself. Simple: Extend the phrase that is displayed when triggering the delete process. Extended: Build a form (i.e. using the advanced forms add on) for details of what exactly a member requests to delete and link to that form from within said phrase. Explain how to use the search function b/c effectively the only data affected in most cases is data the person posted himself. Live with the fact that you opened a can of worms.
 
That sounds like the kind of process we are looking to create, well apart from the can of worms but dealing with these requests is becoming a regular event which in one case involved a deceased member of staff with more posts than most forums have as a total.
 
these requests is becoming a regular event
If it is more often than very occasional i could imagine that a ticket add on like the ones from @Naz or @Bob could be more convenient. I could imagine that this could often become a teethpulling dialogue and a bunch of delayed additional requests. The forms add on seems not well suited for that.
 
One thing I will say is the legislation which remains a continual work in progress, subject to change with little or no notification has rattled my cage enough to run all my non-commercial forums behind a limited company.

However it's the commercial forums I admin that get virtually all the deletion requests and some of them can be a pain to deal with and extremely time consuming. I wonder for example how many site owners have given a single thought to GDPR Article 17 requests and the backups they hold. Probably nobody because the ICO guidance on it is almost nil.
 
Back
Top Bottom