You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since data anonymization is just a way to make data unrecognizable, we should introduce a way so the gem does it by default for a set of chosen attributes.
class User
def anonymization_definitions
[firstname, lastname, email]
end
end
user = User.new(firstname: 'John', lastname: 'Doe', email: '[email protected]')
user.save
John's has used the service for quite long time and was happy with it but for some reason, he no longer needs it. He decides to delete his account and therefore the service provider needs to anonymize its data.
Customizable anonymzation values should still be allowed from the standpoint of the service providers. They may want to exposed those anonymized data to their customers in different way than <record.id>_anonymized
The text was updated successfully, but these errors were encountered:
Since data anonymization is just a way to make data unrecognizable, we should introduce a way so the gem does it by default for a set of chosen attributes.
John's has used the service for quite long time and was happy with it but for some reason, he no longer needs it. He decides to delete his account and therefore the service provider needs to anonymize its data.
Customizable anonymzation values should still be allowed from the standpoint of the service providers. They may want to exposed those anonymized data to their customers in different way than
<record.id>_anonymized
The text was updated successfully, but these errors were encountered: