Anonymize doesn’t remove custom fields that have been added to profile.
4 Likes
The field has been added manually. Below a screenshot from customizer and the anonymized profile. (Normal Finnish locale.)
1 Like
I guess it’s a good idea to always remove those values. We should assume that they contain some kind of identifying information.
Adding it to my list.
7 Likes
Shouldn’t plugins implement an “on anoymize” for cases like this, maybe they store stuff that needs to go away in plugin store or a custom table.
Also, some custom fields may be private, do we want to anonymize them?
2 Likes
Plugins should handle the user_anonymized event, if they need to do some cleanup. I don’t plan on removing them automatically.
But removing values of User Fields defined in admin/customize/user_fields makes sense.
6 Likes
Thanks for reporting this issue.
https://github.com/discourse/discourse/commit/797cbf8653f9b8c75e38695d9abc7654a631eea7
4 Likes
Will there be a fix that goes through alreazy anonymized accounts and removes values?
No, there are no plans to remove values from already anonymized accounts.
2 Likes
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.