GDPR and masked fields

Hi
Would it be possible to “enrich” relevant components (edit boxes, text area, grid cells/columns, …) with a masking/unmasking feature?
Rationale is that based on the GDPR and other privacy laws, more and more we need to hide data from user to respect privacy. It would be nice if we were able to have a checkbox/dropdown with default masking (example for emails th***@g***.com, for cards ****-4567) or a custom implementation to mask the data.
Next to it, we should have a button to show the unmasked data. This would need to be traced (so a callback of some sort so we can get the notification when a user has accessed the unmasked data).
We could also have a button at screen level that unmasks everything (and probably then batch the logging of masked fields access).
The data should not transit unmasked when displaying the fields - as one would say that nevertheless the data was accessible to the user.
I believe that in today’s privacy world that would be a very nice and useful feature to advertise.
FYI @krivopustov @mario

Hi Thierry,

Thanks for the idea.
Not sure it can be done in a generic way for all components without a major rework. Nevertheless it’s an interesting use case and we’ll try to show how it can be implemented at least for a particular screen. Adding to my to-do list :slight_smile:

3 Likes