---
schema_version: "1"
id: 9e3e7f3b05ceddf82006775b3eb89b06bccb4aba46b64cd80fe57f9c7588e624
title: Delete Data with Privacy Requests
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/privacy_request_rtbf_create.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.privacy_request_rtbf_create.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 713bacde95f324681f0d4e4c34f8211506929301b2bdb533f733eeb92ef127bf
description: Fulfill Right to Be Forgotten (RTBF) requests from your customers using Privacy Requests. Find and delete relevant records in your Salesforce org and in Data 360.
products:
- Security
- Cross Cloud
release: "264"
---
# Delete Data with Privacy Requests
Fulfill Right to Be Forgotten (RTBF) requests from your customers using Privacy Requests. Find and delete relevant records in your Salesforce org and in Data 360.
### Required Editions
Available in: Lightning Experience
Available in: Developer, Enterprise, Performance, and Unlimited Editions. Requires the Privacy Center license.
User Permissions Needed
To create, edit, and run Privacy Requests:
Manage Privacy Center Policies
Note
As of October 14, 2025, Data Cloud has been rebranded to Data 360. During this transition, you may see references to Data Cloud in our application and documentation. While the name is new, the functionality and content remains unchanged.
Considerations for RTBF Privacy Requests:
- When you delete Data 360 records with Privacy Requests, Salesforce executes these actions using the [Consent API](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_consent_cdp_params.htm) in an asynchronous manner. It can take some time for Data 360 records to be deleted after you submit a request.
- Searching and processing Data 360 records can increase your Data Services Credit consumption. See [Billing Impact of Data Cloud–Powered Features](https://help.salesforce.com/s/articleView?id=data.c360_a_dc_billing_impact.htm&type=5&language=en_US).
To create and run an RTBF Privacy Request:
1. From the App Launcher, search for and select **Privacy Requests**.
2. Click **New Privacy Request**.
Note Depending on your settings, you may see both a **New** button and a **New Privacy Request** button. Use **New Privacy Request** to open a customized dialog that contains only the fields configured by your admin. The standard **New** button opens a default record dialog and can include fields that aren’t relevant to your privacy workflow. Optionally, ask your admin to hide the button you don’t use.
3. Enter search criteria for the data subject.
Note Admins can change the available search fields from Setup. See [Manage Privacy Request Settings](https://help.salesforce.com/s/articleView?id=xcloud.privacy_request_settings.htm&release=264.0.0&type=5 "Configure the search criteria and scope of Privacy Requests. Control which objects are scanned in your Salesforce org and in Data 360 when users execute searches.").
4. Click **Save**.
5. On the record page for your new Privacy Request, click **Search**.
Salesforce generates a list of matching records found in your org and in Data 360.
6. Choose how to process each record using the Record Handling picklist. The options are slightly different for records in your org versus in Data 360.
1. To delete a Data 360 record, select **Delete this Record**.
2. To delete a record in your org, select an available RTBF policy. This policy will be used to process the record at runtime. The picklist only shows RTBF policies that are active and that reference a matching object. Review [how to create RTBF policies](https://help.salesforce.com/s/articleView?id=xcloud.create_rtbf_policies.htm&release=264.0.0&type=5 "Honor individual customer requests to remove or mask sensitive data by creating Right to Be Forgotten policies.").
3. To maintain a record, select **Exclude Record from Request**. This option preserves the record with no modifications.
7. When you've chosen an action for all available records, click **Submit Requests**.
8. Review the request summary, and then click **Submit**.
9. To track the status of the request, click the **Related Requests** sub tab. Under Included Records, see details about the records targeted for deletion.
Note Keep in mind that records in your org are processed via Privacy Center job sessions, whereas Data 360 records are processed via Consent API requests sent to Data 360.