Anonymizing Personally Identifiable Information
Last updated
Last updated
Parloa provides robust features for anonymizing sensitive data, ensuring the privacy and security of personally identifiable information (PII). This process includes the anonymization of data such as names, birthdates, driver's licenses, addresses, IDs, phone numbers, emails, bank numbers, and other sensitive information.
Parloa uses industry-standard protocols to identify and manage PII data.
The anonymization of PII is currently applicable only to the Training screen. The feature is enabled by default for all projects and can be turned off using the toggle on the the screen.
Parloa replaces actual PII with augmented data to protect your privacy. For example:
Names are replaced with different names.
Birthdates are replaced with different dates.
All sensitive data is similarly replaced with realistic but fictitious information.
There is now an option to opt-in or out of anonymizing PII training data at Project level must you choose it. This can be done easily with the toggle option on the training screen. Once the toggle is turned off, the PII data will no longer be anonymized and replaced with fake realistic data.
Previously anonymized values will not be unanonymized. Once the feature is toggled off, the change takes effect for the future unassigned utterances.
The anonymized values are now highlighted with a different colour to bring transparency.
The values are highlighted provided the feature is enabled and only future PII Data will be highlighted once anonymised.
Past PII data, (even if anonymized) are not highlighted.
In the Training tab, when you click on one of the utterances in the table, the displayed utterance is anonymized to ensure privacy. When adding assigned utterances to an intent, the anonymized utterance will be assigned.
However, if you have permissions to Debug or Edit Project enabled for your role and you click on the utterance, the context of the conversation is displayed in a pane on the right. In this pane, the content remains as it was originally said, not anonymized.
To view the context sidebar of a conversation and access analytics data, the Debug permission must be enabled for the respective role.