> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/administration/data-deletion-requests.md). # Data deletion requests You can ask Chord to delete the data it holds about a customer. This is useful for privacy requests, compliance requirements and customer opt-outs. You submit and track each request in Chord, and you don't need engineering help. ## Submit a request 1. Go to **Chord CDP** > **Data Deletion Requests**. 2. Select **New Data Deletion Request**. 3. Enter the details that identify the customer. The customer's email address is required. 4. Submit the request. Chord reviews each request and confirms when the deletion is complete. ## What Chord deletes Chord deletes the customer-level data it stores for that customer. This covers all environments that Chord manages, both production and staging. ## What Chord doesn't delete Chord can't delete data that lives outside Chord. This includes: * Downstream destinations, such as email and SMS platforms, ad networks and analytics tools. * Data warehouses and BI tools that your team manages. * Other third-party platforms connected to Chord. * Exports made before the deletion. To remove data from these systems, send the request to each destination or provider directly. ## Timeline Deletion can take up to 30 business days from the day you submit the request. Chord processes requests in the order it receives them. ## Track a request The **Data Deletion Requests** page lists every request you have submitted. For each one you can see its status (Submitted, In Progress or Completed) and its details. ## Good to know * You can submit as many requests as you need. * You can't reverse a request once processing has started. * For bulk deletions or special compliance needs, email . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/administration/data-deletion-requests.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.