Configure Privacy Exclusions
Hide sensitive values and elements
Data Field Exclusion
Protect fields across KPIs
Session Replay Exclusion
Mask DOM content in replays
Configure Privacy Exclusions
GermainUX provides configurable mechanisms for protecting sensitive information in analytics data and Session Replay recordings. Depending on the use case, a value or element can be:
These controls help prevent information such as usernames, email addresses, IP addresses, payment-card details, and sensitive form values from being exposed through GermainUX.
Privacy Rule Types
Data Field Exclusion
A Data Field Exclusion rule protects a field collected through one or more KPIs. The rule can:- Mask the field
- Anonymize its value
- Exclude it from collection
- Apply only to selected KPIs
- Preserve character length or whitespace when masking
- Apply protection only to content matching a regular expression
Create a Data Field Exclusion Rule
1
Go to GermainUX Workspace > Analytics > Data Privacy
2
Click +
3
Select Data Field Exclusion
4
Complete the configuration
5
Save the rule
Configuration Fields
Example: Mask a Username
The following configuration masksuser.name without preserving its original length or whitespace:
Mask a Username - GermainUX
Session Replay Exclusion
A Session Replay Exclusion rule protects sensitive HTML or DOM content from appearing in recorded sessions. Elements are selected using CSS selectors. Each matching element can then be masked, anonymized, or excluded.Create a Session Replay Exclusion Rule
1
Go to GermainUX Workspace > Analytics > Data Privacy
2
Click +
3
Select Session Replay Exclusion
4
Complete the configuration
5
Save the rule
Configuration Fields
Example: Exclude Payment-Card Fields
The following rule excludes input elements whoseautocomplete attribute begins with cc-:
This selector can match standardized payment fields such as card number, expiration date, and security-code inputs.
Exclude Payment-Card Fields - GermainUX
Validation Recommendations
After creating a rule:- Test it in a non-production environment.
- Confirm that it applies to every intended field or element.
- Verify that protected values do not appear in analytics or Session Replay.
- Test dynamic pages, embedded components, and single-page application navigation.
- Confirm that the selector or regular expression does not hide unrelated information.
- Repeat validation whenever the monitored application changes.
Get Help
Contact GermainUX Support
The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE.