> 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/download-tracker-policy.md).
# Download tracker policy
{% hint style="success" %}
**Access Type**: Data Manager - Editor
{% endhint %}
A tracker policy is a document that explains what tracking technologies (like cookies, pixels, or SDKs) a website or application uses, why they are used, and what choices end-users have to control or opt out of them. Once your organization's [tracker policy is configured](/data-manager/tracker-policy/configure-tracker-policy.md) you can download the file as a HTML or JSON file to add to your website or application.
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 **Edit** icon inline with the tracker policy name.
Navigate down the tracker policy configuration page and click **Download**.
Select the preferred format from the drop-down menu. Tracker policies can be downloaded as an HTML or JSON file.
The tracker policy will be downloaded onto your local machine in the specified format.
---
# 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.didomi.io/data-manager/tracker-policy/download-tracker-policy.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.
