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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configuring Data Privacy for Now Assist

# Configuring Data Privacy for Now Assist {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure a data privacy advanced configuration to de-identify personally identifiable information (PII) in generative AI applications.

## Before you begin

You must have the following applications installed on your instance:

* Data Privacy (Classic) \[com.glide.data_privacy\]
* Data Privacy \[sn_dp_store_app\]
* Data Discovery \[sn_data_discovery\]
* Data Discovery APIs\[com.glide.data_discovery\]

{#configure-now-assist-data-privacy__ul_vyy_d52_b2c}

These plugins should be installed automatically if you have the latest version of Generative AI Controller.

Role required: now_assist_data_privacy_admin

## Procedure

1. Navigate to AllData Privacy (Classic)Privacy Policy Advanced Configuration.  
   If you previously used the Sensitive Data Handler to help de-identify data for generative AI, you may already see a privacy policy configured. Your previously configured regular expressions have been migrated as part of your upgrade. If you already have a data policy for Now Assist, skip to step 6.
2. Select New.
3. Enter a name for the privacy policy.
4. In the Data Channel field, select the data channel to be used, see [Contextual based discovery](https://www.servicenow.com/docs/CqU_oVb_cAcv_VRey_XAoA "Use contextual based discovery to help discover sensitive data that does not follow fixed patterns.") for more information.

   | Channel | Description |
   | Data Kit | Data, which AI models are using for evaluation, is sanitized by discovering and de-identifying sensitive data. |
   | Data Extraction | Data is sanitized before being sent for model training |
   | Now Assist | Data is sanitized before being sent to GenAI Controller |
   |-|-|

   {#configure-now-assist-data-privacy__choicetable_ikl_yng_b2c}
5. Set Active to <kbd class="ph userinput">true</kbd>, then select Submit to create the policy advanced configuration.  
   Only one policy configuration for each data channel can be active at a time. To activate a new policy advanced configuration, you must set Active to <kbd class="ph userinput">false</kbd> for all other policy configurations on that data channel.
6. After you're redirected to the list of policy advanced configurations, open the record you created.  
   Open the existing record with the Now Assist data channel if one is already present.
7. To add a data pattern to de-identify, select Select Data Patterns.
8. **Optional:** To create your own data pattern, see [Configure Data Discovery patterns](https://www.servicenow.com/docs/_3R8tFN7qPmOtTewaibkHQ "Configure a Data Discovery pattern and review current patterns. A Data Discovery pattern defines the regular expression used to match data against a target table.").
9. Select your data patterns, then select Save.
{#configure-now-assist-data-privacy__steps_wyy_d52_b2c}

## Result

Data caught by the regular expressions selected in the data patterns is de-identified for generative AI applications.

*[\>]: and then