I was thinking as an added feature to toolset and for the process of getting our websites closer to being GDPR compliant some of the fields that we create can have the option of pseudonymisation.
That what when we create contact forms etc that gather users personal data and gets stored as a type would be safe to do so.
Hello. Thank you for contacting the Toolset support.
As I understand - do you mean that, when someone save contact form you want to save that entry as new entry of CPT, basically you want to clone that entry to CPT?
There is a new European Law that will be live by the 20th of May and applies to all companies that serve to any European citizens.
It requires privacy protection to all EU citizens, otherwise, companies will be liable up to 20million euros or 4% of their Revenue.
One of the criteria of privacy protection is to make sure User stored is safe when stored, when i say user data this includes:
Name/Email/Address/IP address/ Personal ID any one of these data has to be stored and stored safely with the user's consent.
How does this effect Toolset:
A lot of toolset buyers use the CRED form as a contact form, in the contact form, they would usually request the user's name/email and store this data in a custom post type that they made through Types. By may 21st will be considered as heavily sensitive data and companies doing so will be liable for storing data in a non secure form.
My Suggestion:
Have an option for when you create a custom field to check whether you would like to pseudonymize (hash) that field's data into the database.
I am sure there will be a lot of use cases for this, it is a major law, it even effects any company that deals with any European citizen, the same way it will effect onthegosystems as I am a European customer using Toolset/WPML.
