In a Support discussion titled Question About Anonymizing Users and GDPR, user Rubi asks whether Discourse’s anonymization process fully complies with GDPR, specifically regarding retention of IP addresses and emails, and whether anonymization can be reversed. elmuerte explains that anonymization changes usernames to anon#<random>, randomizes passwords, removes personal fields (name, avatar, bio, etc.), and optionally anonymizes IPs while replacing emails with <username>@anonymized.invalid. Reversal is “basically impossible,” though user traces may linger in posts. Rubi clarifies whether PMs are included — elmuerte confirms they are treated like posts, but notes GDPR compliance depends on local law and usage context, advising legal consultation. Heliosurge adds that partial recovery is technically possible by restoring old usernames and emails (though profile data remains lost), and suggests users review posts for sensitive content before anonymization. Rubi appreciates the insights, noting few deletion requests but seeking preparedness. JammyDodger recommends disabling Log anonymizer details in settings to avoid retaining original user data in staff logs — a tip Rubi plans to share with leadership. Overall, while Discourse’s anonymization aligns with GDPR’s Right to erasure in spirit, legal certainty requires jurisdiction-specific advice.
Hi,
I would like to ask if the following is true:
Anonymization meets GDPR requirements for removal of personal data. Once anonymized, no data remains in the Discourse server to identify who you are or about you.
Are the IP address and email of a user retained after anonymization?
Is a site admin able to reverse the anonymization process?
Thanks in advance,
Rubi
The code which does the anonymization:
It will:
anon#<random number><username>@anonymized.invalidAs the username is changed, Discourse will try to replace the username is all posts.
Reversal is basically impossible, but user information can remain in individual posts.
In this case, I assume emails includes/also means PMs?
From a legal perspective, can a user be told that the process of anonymizing is GDPR compliant or are the waters still muddy on this matter?
PM in discourse are just private discussions, they are posts with really limited visibility. They are anonymized in the same way as the more public posts.
The “invites and emails” I mentioned are the email messages send out by discourse for various actions. For example email notifications about reactions to followed discussions.
I am not a lawyer. But it is not that simple. In spirit this mechanism does conform to the guidelines of the Right to erasure from the GDPR, but the local implementing law might not agree.
It also depend a lot on how you use Discourse.
Further more, the amount of data being erased might violate some other laws which require this data to be kept.
If this is really a big concern, like with everything legal, you should contact a lawyer.
Mostly. I have been able to partially recover an account by renaming username back to what it was prior to being anonymized and reattaching the user email and reactivate account. Seems to keep original password. But all other things are gone, profile pic, birthday if entered. I had to explore this when I had a Moderator go off the rails.
It is a pain and not simple.The only thing is in posts where the user may have posted may have details in a post. Now if that was in a Personal message maybe not a big deal.
I believe the team has said though this is within gpdr compliance.
If a member requests to be anonymized likely good to ask them to scan their posts and if necessary flag them for deletion. Ie posts with uploaded pictures of the poster for example.
This is very useful to know!
Thankfully, we do not have many users requesting what they call “deletion” but since GDPR is or can be an issue I wanted to gather as much information as possible.
Oh, that is very nice!
Will definitely pass this information up the chain of command 
