Impact of Data Modeling on Data Subject Rights Requests

Learn more about how Data Modeling impacts your Data Subject Rights Requests in Data 360.

Map all personal data stored in Data 360 to the Individual entity to ensure that it’s processed as part of any Data Subject Rights request.

You can map fields containing personal data to the Individual entity using a standard or custom attribute in Data 360. If you’re storing personal data in another standard or custom entity, create a relationship in the object data model between the field mapped to the customer identifier on that entity and the Individual ID field.

Example Northern Trail Outfitters ingests sales order data from Sales Cloud and stores it in the Sales Order entity in Data 360. This sales order data includes a field for customer email address, which is considered personal data. Northern Trail Outfitters creates a relationship in the object data model between a custom Customer Id attribute on the Sales Order entity and the Individual Id field.

Example Northern Trail Outfitters receives a request from Samantha Smith to delete her personal data. Northern Trail Outfitters finds Samantha's personal data on Individual Id 1234 in Data 360 and submits a data deletion request to the Consent API using that Individual Id. Because a relationship has been defined between a custom Customer ID attribute on the Sales Order entity and the Individual Id field, both entities are deleted as part of the data deletion request.