Form Privacy and UX Monitoring Profile View

Form Privacy provides predefined rules that protect information entered into HTML forms from appearing in Session Replay recordings.

These rules can mask, anonymize, or exclude sensitive DOM content such as:

Item
Payment-card information
Email addresses
Personal information
Free-text responses
Other user-entered form values

Form Privacy controls what is captured in Session Replay. It is separate from Data Field Exclusion, which protects fields collected as analytics data.

📃 Default Form Privacy Rules

When Form Privacy is enabled, GermainUX adds two default rules to the applicable UX Monitoring Profile:

Rule	Purpose
Form Privacy Mask	Masks the content of supported form elements.
Form Privacy Exclude	Excludes selected controls from the recording.

🔍 Elements Masked by Default

The default masking rule applies to elements such as:

input,
textarea,
select,
option,
datalist,
[contenteditable],
input[autocomplete^="cc-"]

This includes form inputs, free-text areas, selection controls, editable content, and standardized payment-card fields.

🚫 Elements Excluded by Default

The default exclusion rule applies to controls such as:

input[type="checkbox"],
input[type="radio"]

Excluded elements are omitted from the Session Replay capture according to the configured rule.

Default rules should be reviewed against the structure and privacy requirements of each monitored application. Custom components may require additional CSS selectors.

⚙️ Enable Form Privacy

Form Privacy can be enabled during the initial deployment of a UX Monitoring Profile.

After deployment, its rules can be reviewed and managed from the GermainUX Workspace.

🛠 Manage Form Privacy Rules

Go to GermainUX Workspace -> Left Menu → Settings → Analytics -> UX Monitoring Profiles.

UX Monitoring Profiles - GermainUX
Search for the applicable profile—for example, reactjs2.
Select the profile to open its configuration.
Scroll to Session Replay Exclusions.
Locate the default rules:
- Form Privacy Mask
- Form Privacy Exclude
Select a rule to edit, update, or disable it.
Save the UX Monitoring Profile.

🚀 Available Actions

Action	Description
Edit	Change the selector, privacy-control type, or advanced settings.
Add	Create a rule for additional application-specific elements.
Disable	Stop applying a rule when it is not appropriate for the monitored application.
Update	Modify a rule after the monitored application or its DOM structure changes.

✅ Validate Form Privacy

After configuring Form Privacy, review Session Replay recordings to confirm that the rules protect the intended information.

👀 Review Recorded Sessions

Go to GermainUX Workspace → Left Menu → Settings -> Germain -> Sessions.
Open a session recorded after the privacy configuration was applied.
Navigate to interactions involving the protected forms.
Confirm that sensitive values are handled according to the configured rules.

Privacy control	Expected result
Mask	The original value is replaced with characters such as `***`.
Anonymize	The original value is replaced with an anonymized representation.
Exclude	The selected content is not captured or displayed in the replay.

💡 Validation Recommendations

Test the rules against:

Area
Every sensitive form and workflow
Dynamically created fields
Single-page application navigation
Custom input components
Embedded content
Payment and authentication workflows
Mobile and responsive layouts

Repeat validation whenever the application, UX Monitoring Profile, or privacy configuration changes.

When sensitive information is not required for monitoring, use Exclude so the value does not enter the Session Replay data pipeline.

This page focuses specifically on form protection within Session Replay. Related capabilities are documented separately:

Document
Data Privacy
Compliance, Data Privacy and Security Overview
Data Security
Cookie Consent and User Privacy

Service: Management

Feature Availability: 2020.1 or later