> 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/vendors/remove-purpose-from-vendor.md). # Remove purpose from vendor {% hint style="success" %} **Access Type**: Data Manager - Editor {% endhint %} A [purpose](/data-manager/purposes.md) describes the reason your organization or its vendors is collecting the end-user's data and how your organization processes that data. In this article, we will cover the following: * [Purpose removal overview](#purpose-removal-overview) * [Remove purpose from vendor](#remove-purpose-from-vendor) *** ### Purpose removal overview The ability to remove purposes from a vendor depends on factors such as the vendor type and purpose type being removed. Refer to the matrix below for more information
Vendor typeIAB purposesGlobal purposesCustom purposes
IAB vendorIAB purposes are predefined and managed by the IAB TCF framework and cannot be removed. If your organization has added any additional IAB purposes other than what was predefined for the vendor then these can be removed.

Note: Publisher restrictions are available via the consent notice settings to enforce any organizational restrictions you my require. Click here for more information.		✅✅
Google ATP vendorIAB purposes are predefined and managed by the IAB TCF framework and cannot be removed. If your organization has added any additional IAB purposes other than what was predefined for the vendor then these can be removed.

Note: Publisher restrictions are available via the consent notice settings to enforce any organizational restrictions you my require. Click here for more information.		✅✅
Global vendor✅✅✅
Custom vendor✅✅✅
### Remove purpose from vendor Click **Data Manager** in the left-hand panel and select the **Vendors** tab on the subsequent page.
Navigate to a vendor on the subsequent list and click **Edit** inline with the vendor name.
Use the respective **opt-in purposes** or **opt-out purposes** drop-down menu and deselect the purpose that should be removed from a vendor. {% hint style="info" %} Purposes that cannot be removed from the vendor will have the purpose name muted to grey. {% endhint %}
Click **Save** when finished. The purpose will be removed from the vendor. --- # 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/vendors/remove-purpose-from-vendor.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.