> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/data-manager/tracker-policy/delete-tracker-policy.md).
# Delete tracker policy
{% hint style="success" %}
**Access Type**: Data Manager - Editor
{% endhint %}
In this article, we will cover how your organization can delete an existing tracker policy that it has configured.
{% hint style="warning" %}
**Note**: A deleted tracker policy in the Didomi console will still be available on any website or app where your organization implemented the policy. In order to remove a tracker policy from these properties, your organization will need to remove the tracker policy from that website or application's source code.
{% endhint %}
Click **Data Manager** on the left-hand panel and select the **Trackers** tab on the subsequent page.
Click **Manage Tracker Policy**.
Navigate to a tracker policy on the subsequent list and click the **Delete** icon inline with the tracker policy name.
Confirm the decision to delete the tracker in the modal and click **Yes, delete**.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.didomi.io/data-manager/tracker-policy/delete-tracker-policy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
