Anonymize doesn't remove custom fields


Anonymize doesn’t remove custom fields that have been added to profile.

(Jeff Atwood) #2

What are your thoughts on this @gerhard?


The field has been added manually. Below a screenshot from customizer and the anonymized profile. (Normal Finnish locale.)

(Gerhard Schlager) #4

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.

(Sam Saffron) #5

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?

(Gerhard Schlager) #6

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.

(Gerhard Schlager) #7

Thanks for reporting this issue.


Will there be a fix that goes through alreazy anonymized accounts and removes values?

(Gerhard Schlager) #9

No, there are no plans to remove values from already anonymized accounts.

(Gerhard Schlager) #10

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.