---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Data privacy for inbound emails

# Data privacy for inbound emails {#ariaid-title1}

Release version: Brazil  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The inbound email channel enables organizations to discover and mask sensitive data in inbound emails through the Data Privacy framework. This replaces the previous approach which used Active Data Patterns with a centralized,
streamlined policy-based experience for managing sensitive data in emails.

The inbound email channel within the Data Privacy module that allows administrators to define and manage policies to detect and redact sensitive data in inbound emails and any associated inbound actions. This requires customers
to have the Sensitive Data Redaction for inbound emails plug-in installed on their instance.

## Migration of existing configurations {#inbound-email-channel-overview__section_configuration_migration}

For customers upgrading to Brazil with existing email redaction configurations:

* **Automatic migration:** Upon upgrade, existing email redaction configurations are automatically converted into email channel policies.
* **Pattern preservation:** Active data patterns used in the old plug-in are migrated to the new email channel policy.
* **Default policy:** If no active patterns exist, a default email policy is created with no patterns, allowing administrators to configure as needed.

Migration is transparent to end users as defined in the policy; masking continues seamlessly after the upgrade.

## Limitations and considerations {#inbound-email-channel-overview__section_limitations}

* **Pattern accuracy:** Sensitive data patterns may have false positives or false negatives depending on pattern specificity.
* **Email attachments:** Masking may not apply to sensitive data within email attachments; verify scope with your team.