Anonymization
Anonymization replaces or removes a record's identifying fields instead of deleting the entire record. Some integrations support anonymizing data on a Deletion request as an alternative to a full deletion, and others rely on anonymization because their API can only update records, not delete them. Anonymization is specific to processing Privacy Requests in Request Manager and has no effect on other DataGrail products, such as Live Data Map or Consent.
Anonymization happens during the Active: Pending Delete phase of the Deletion Request Lifecycle, alongside standard deletion.
Configuring anonymization is not self-serve for most integrations. To enable or customize anonymization for a supported integration, contact support@datagrail.io.
Supported Integrations
DataGrail integrations support anonymization in one of three ways, described below. If you don't see an integration listed, contact support@datagrail.io to confirm whether it supports anonymization.
Configurable Anonymization
For these integrations, DataGrail can configure custom anonymization rules for specific fields to fit your requirements:
- Salesforce
- Salesforce Order Management
- Salesforce Service Cloud
- Greenhouse
- RainFocus
- HR Cloud
- Oracle Opera Cloud (profile data only)
- PowerReviews
Automatic Anonymization
These integrations always anonymize data using DataGrail's standard rules, and require no configuration:
- Adyen
- AfterShip
- AnswerHub
- BigMarker
- Clutch
- CommonRoom
- Oracle NetSuite
- ProfitWell
- Sendoso
- Skilljar
- Splash
- Xero
Hybrid Deletion And Anonymization
These integrations delete some records and anonymize others — for example, anonymizing a record when deletion isn't possible or would remove data your organization needs to retain:
Related Reading
For more on how anonymization fits into the deletion process, see:
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.