> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Form Privacy and UX Monitoring Profile View

> Use form privacy rules to mask, anonymize or exclude sensitive page content from monitoring.

Service
`Management`

Availability
2014.1 or later

**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:

* 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.

> [card] [Default Form Privacy Rules](#default-form-privacy-rules)
>
> Two rules added automatically

> [card] [Enable Form Privacy](#enable-form-privacy)
>
> Turn on during deployment

> [card] [Manage Form Privacy Rules](#manage-form-privacy-rules)
>
> Edit rules in Workspace

> [card] [Validate Form Privacy](#validate-form-privacy)
>
> Check replays for leaks

## 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:

```text theme={null}
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:

```text theme={null}
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

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

   ![UX Monitoring Profiles](https://mintcdn.com/germain-ux/8KX3c-GSSWR99tdN/images/main/form-privacy-and-ux-monitoring-profile-view/image-20260825-201527.png?fit=max\&auto=format\&n=8KX3c-GSSWR99tdN\&q=85\&s=bbb95cf8fe81bad73a3f5dabb2ce86e0)

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

![Form Privacy and UX Monitoring Profile View: Manage Form Privacy Rules](https://mintcdn.com/germain-ux/8KX3c-GSSWR99tdN/images/main/form-privacy-and-ux-monitoring-profile-view/image-20220719-090627.png?fit=max\&auto=format\&n=8KX3c-GSSWR99tdN\&q=85\&s=b7b242f89e0e1266fac59ebe63fd2adb)

### 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

**1. Go to GermainUX Workspace → Left Menu → Settings -> Germain -> Sessions**

**2. Open a session recorded after the privacy configuration was applied**

**3. Navigate to interactions involving the protected forms**

**4. 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:

* 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.

## Related Documentation

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

* [Data Privacy](https://docs.germainux.com/main/data-privacy.md)
* Compliance, Data Privacy and Security [Overview](https://docs.germainux.com/main/compliance-privacy-and-security.md)
* Data [Security](https://docs.germainux.com/main/data-security.md)
* [Cookie Consent and User Privacy](https://docs.germainux.com/main/cookie-consent.md)

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> 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.

> [card] 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.