Data masking can be done at the organization level to prevent the exposure of sensitive data.

PII Data Masking

Admin users can enable PII data masking in Databricks and hide the PII data (including custom field and extended field data) of customers during the export of data from Databricks. Once the ETL is done, the data gets masked.

Perform the following steps to enable PII data masking:

1. From the Rizer UI home page, navigate to PII configs.
2. For the brands you want to enable PII data masking, click Configure.
   
3. Click Enable.

After enabling, when you export data, the PII fields are masked. Same steps can be followd to mask the PSI data.

4. To pause PII data masking, click Pause and to disable PII data masking, click Disable.

PSI Data Masking

When PSI data masking is enabled for a brand, PSI fields including custom and extended fields, are masked in the Databricks. In the Analytics database (read_api tables), they are displayed as a string of asterisks ("*").

Create a Jira ticket for the product support team to pause or disable masking.

📘

Note

To access unmasked PSI data, jobs must be run on admin_read_api tables, which are restricted to authorized Databricks users.