---
schema_version: "1"
id: f31a5248607daa713c471cefd22abca490a82d4f2964037bfbac2d90512aef7d
title: Customer Data Subject Rights in Data Transforms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_streaming_transform_data_subject_rights.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_streaming_transform_data_subject_rights.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e2caf8eaf9c448098dcc2932dc7e7d62adebd12f175aa6eae9a8ee560d4e94b0
description: A customer’s Data Subject Rights relate to the storage and use of their personal data. Data 360 offers tools to support Data Subject Rights in alignment with various data protection and privacy regulations.
products:
  - Data 360
release: "264"
---
# Customer Data Subject Rights in Data Transforms

A customer’s Data Subject Rights relate to the storage and use of their personal data. Data 360 offers tools to support Data Subject Rights in alignment with various data protection and privacy regulations.

Submit all Data Subject Rights requests using the Salesforce Consent API.

To ensure that Data Subject Rights are maintained, verify that all personal data is mapped to the Individual DMO.

The Consent API operates on all data stored in DLOs mapped to Individual. For example, in this diagram, DLO2 and DLO4 are mapped to the Individual and Contact Point Address DMOs. Contact Point Address has a relationship with Individual. Because DLO2 and DLO4 are directly or indirectly mapped to Individual DMO, the Consent API operates on these two DLOs.

Data lake objects DLO1, DLO3, DLO5, and DLO6 aren’t mapped to the Individual DMO or any of the Contact Point DMOs, so the Consent API doesn’t operate on these DLOs. You can remove personal data from these DLOs by deleting it from the data stream records.

Data stream-based deletions only apply to source DLOs. Streaming data transforms automatically transfer deletions to relevant target DLOs.

![Diagram shows where Consent API is applied between two related DLOs and two related DMOs.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/data_cloud/images/c360_a_streaming_transform_data_subject_rights.png)

#### See Also

- [_Salesforce Help_: Data Subject Rights](https://help.salesforce.com/s/articleView?id=data.c360_a_data_subject_rights.htm&release=264.0.0&type=5 "A customer’s data subject rights, such as those granted to them by the European Union’s General Data Protection Regulation (GDPR), relate to the storage and usage of their personal data. Data 360 offers tools to support your consumer’s data subject rights in alignment with various data protection and privacy regulations.")
- [_Salesforce Help_: Impact of Data Modeling on Data Subject Rights Requests](https://help.salesforce.com/s/articleView?id=data.c360_a_data_modeling_impact_on_dsr_requests.htm&release=264.0.0&type=5 "Learn more about how Data Modeling impacts your Data Subject Rights Requests in Data 360.")
- [_Salesforce Help_: Delete Data Stream Records](https://help.salesforce.com/s/articleView?id=data.c360_a_delete_data_stream_records.htm&release=264.0.0&type=5 "You can delete data ingested into Data 360. Your data stream must have an upsert refresh mode. The deletion process depends on the type of connector that you’re using.")