Historic data masking

When a customer or agent passes sensitive details during a messaging conversation, it’s important that the agent can view the information while handling the issue, but that the data will no longer be visible once the issue is resolved.

To facilitate this layer of security, sensitive data (such as credit card or social security numbers) is replaced with predefined masking characters before being stored in the Conversational Cloud Conversation History database (data is not masked in real time).

The data is masked based on predefined RegEx patterns and presented as masked throughout the historical data elements, widgets, and APIs, as soon as the conversation is closed.

Sensitive historical data masking is enabled by default for all Messaging accounts and used an out-of-the-box RegEx pattern for masking credit card patterns.

Brands can add additional RegEx patterns for masking additional sensitive data, such as SSN, email addresses, etc.

To configure additional RegEx patterns please contact your LP account team.