Best Practices for Tracking Data Privacy
Keep these best practices in mind when storing certain data privacy preferences in data privacy records based on the Individual object.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: all editions, including partner and customer community users. |
Encrypting Personal Data
The Name field in data privacy records is personal data. Salesforce Shield customers can use Shield to encrypt this field. If you’ve added custom fields that contain personal data, consider encrypting them.
Helping Your Users Decode Individual
After you add the Individual field to your page layouts, consider renaming the field to something meaningful for your users. (Example: Manage data privacy or Track customer consent)
Keeping Renamed Contacts, Leads, and Person Accounts Consistent with Data Privacy Record Names
Renaming a contact, lead, or person account doesn’t update any corresponding privacy data. To keep the name of data privacy records up to date, write an Apex trigger.
Converting Leads to Existing Contacts
When you convert a lead, you can decide which data privacy record you maintain between the converted lead and the contact.
| To Maintain the Data Privacy Record From the | You Need To |
|---|---|
| Contact | Sit back and do nothing. |
| Lead | Edit the contact’s IndividualId to replace the ID with the one from the converted lead. If your contact doesn’t include the ID before the conversion, the conversion process populates the field from the converted lead. |
Creating Community Users from Contacts with Associated Data Privacy Records
To create a new community member from a contact record, first disable Don’t Process and Forget this Individual in the associated data privacy record.
