Acoustic™ Experience Analytics (Tealeaf) client frameworks provide multiple security features to ensure that sensitive application and user data is safeguarded for transport or retained only in the client application.
Using controls that you can configure in each client framework, you can define the specific set of data that is blocked or masked from transport to Experience Analytics. Sensitive data that was cleansed through a client framework never reaches Experience Analytics, which ensures that your customer's interactions are secure.
- Masks can be expressed as explicit strings, replacements for character types, or custom functions.
- Extra security features.
As part of any implementation through Professional Services, data privacy is configured and applied for any data that is submitted from a monitored client application. Before you enable capture of client framework data, verify that privacy configuration was properly enabled and configured.
If you have questions about how to implement data privacy in UI Capture, contact Professional Services.
Data Masking and Blocking for Client Frameworks
Do not copy or transmit sensitive data when not necessary. To protect your users' privacy, do not log sensitive data like passwords and credit card numbers. You can see the format this sensitive data without seeing the data when troubleshooting. Removing the content of this information is called masking.
Step-based eventing simplifies and unifies event capture from all client frameworks and enhances performance. Because of changes in how the data is bundled, apply data privacy through the individual client frameworks, instead of using the Experience Analytics server methods for data privacy.
Any data that is masked or blocked by a Experience Analytics Client Framework is never available in Experience Analytics for processing, search, and reporting.
For data submitted from a client framework in JSON format, privacy must be applied by using the client framework's controls. Application of privacy controls to JSON-based data after it is submitted to Experience Analytics requires advanced abilities in Experience Analytics privacy controls and regular expression development.