---
schema_version: "1"
id: 8899314fcec22846f1e1547bb23126e41293cf0d3591e2d4f5508021c92901ad
title: Impact of Data Modeling on Data Subject Rights Requests
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_data_modeling_impact_on_dsr_requests.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_data_modeling_impact_on_dsr_requests.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 556fe794c39848f2e5b12052b16d73599a12cdda9f7c4fd314c051c18ada74c9
description: Learn more about how Data Modeling impacts your Data Subject Rights Requests in Data 360.
products:
  - Data 360
release: "264"
---
# 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_example.png)

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.

![NTO example of a Data subject rights request](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/impactdatamodeling_example.png)

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_example.png)

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.

#### See Also

- [_Salesforce Developer_: Use the Consent API with Data 360](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_consent_cdp_params.htm)
- [_Salesforce Help_: Customer 360 Data Model: Individual and Contact Points](https://help.salesforce.com/s/articleView?id=data.c360_a_cloud_information_model_individual_and_contact_points.htm&release=264.0.0&type=5 "When using the Customer 360 Data Model, Data 360 prepares a list of Salesforce-published objects, fields, metadata, and relationships to ensure consistency across applications and business processes. Individual and contact point objects are important concepts for successful and complete data streams.")
- [_Salesforce Help_: Data Model Objects](https://help.salesforce.com/s/articleView?id=data.c360_a_data_model_objects.htm&release=264.0.0&type=5 "Create, view, and manage data model objects (DMOs). DMOs are fundamental to Data 360. Familiarize yourself with the definitions, concepts, and resources related to DMOs before creating or working with them.")