You are here:
Considerations for Privacy Center Data Retention
When you process Salesforce records with Data Management or Right to Be Forgotten policies, you can also copy the records to an external data store for retention. Review these guidelines and limitations when implementing data retention with Privacy Center.
Required Editions
| Available in: Developer, Enterprise, Performance, and Unlimited Editions. Requires the Privacy Center license. |
This topic applies to Privacy Center on the Salesforce platform, released in Winter ‘24. For the managed-package version of Privacy Center that uses Heroku for retention, see Legacy Privacy Center: Satisfy Customer Requests and Data Privacy Laws.
How to Configure Data Retention
The data retention setup is available when you add an object to a Data Management or Right to Be Forgotten policy. You can select retention options after applying mask or deletion rules to the object’s records. For detailed instructions, see Retain Records on an Object.
Feature Availability
Certain Salesforce instances don’t support data retention. If your instance is listed here, skip the data retention setup by selecting Do Not Copy in the policy configuration flow. Otherwise, errors occur when your policy executes. To find out your org instance, go to Company Information in Setup, or contact your account executive.
Data retention is unsupported in:
- South Korea: kor* instances
- Indonesia: idn* instances
- Brazil: bra* instances
- Middle East: are* instances
Data retention isn’t available in Government Cloud.
Limitations
Newline and tab characters in long
or rich text fields are transformed during the record retention process. Newline characters
become \n or \r, and
tab characters become \t. As a result, any line breaks or tab spaces found in the original
records aren't present in the retained copies.
If your policy includes a formula field with an invalid formula, data retention fails, and the job session can't complete. Either correct the formula field or remove it from your policy, and then rerun the policy.
Retention Stores
Your Salesforce org creates a data retention store automatically when executing a data retention job for the first time. Alternatively, you can create a new production org data retention store manually from the Privacy Center app Data Stores tab. Retention stores are built on Hyperforce infrastructure and are maintained in the same region as your Salesforce org.
While you can create only one data retention store for each production org, you can create multiple sandbox data stores for development and testing. Production data stores have storage volume limits, while sandbox data stores have no storage limit. If you already have a data retention store associated with your production org, you can create a sandbox store directly from your production org's UI. From the Data Stores tab, click Create Sandbox Store. Your sandbox store appears as a new row in the list view.
To delete the data retention store that’s associated with your production org, contact Salesforce Customer Support. To view records in your retention store, use the Salesforce Connect adaptor for Privacy Center.
Data Encryption
Privacy Center retention data is stored in the nearest Hyperforce region to your org instance and is fully integrated and compliant with Salesforce’s security and data classification policies. All data transfers use the TLS 1.3 security protocol, and data is encrypted at rest using the AES-256 algorithm. Your retained data never leaves the Salesforce trust boundary.
