> 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/regulations-manager/frameworks/iab-tcf/processing-rules-for-iab-tcf-purposes.md).

# Processing rules for IAB TCF purposes

{% hint style="success" %}
**Access Type**: Regulations Manager - Editor
{% endhint %}

Processing rules are the legal bases that your organization sets for each combination of vendor and purpose. These rules govern whether the specified vendor can collect end-user data in pursuit of the purpose and whether end-user consent is required. In this article, we will cover the nuances of managing processing rules for IAB TCF purposes

* [Processing rules overview](#processing-rules-overview)
* [IAB TCF restrictions](#iab-tcf-restrictions)
* [Manage processing rules for IAB TCF purposes](#manage-processing-rules-for-iab-tcf-purposes)

To start, click **Regulations Manager** in the left-hand panel.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F8mHBFEasbCecBPmuE3Kh%2FScreenshot%202026-09-15%20at%207.21.21%E2%80%AFAM.png?alt=media&amp;token=a1e5ea20-451e-42c6-8322-459932ce64af" alt="" width="563"><figcaption></figcaption></figure>

Navigate to a regulation that uses vendor as a data collection scope on the subsequent list and click the edit icon inline with the regulation name.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FWHaCCcWQsiMviOreW6Td%2FScreenshot%202026-10-06%20at%2010.39.17%E2%80%AFAM.png?alt=media&amp;token=8bcc0b62-9a4a-4b1d-aa80-cbf5733e8745" alt="" width="563"><figcaption></figcaption></figure>

Select the **Vendors & Purposes**.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FGJMxikuVzkeeVaeqxrbb%2FScreenshot%202026-10-27%20at%207.19.17%E2%80%AFAM.png?alt=media&amp;token=f65b09f9-89ba-434a-89b8-a3218be7f64d" alt="" width="563"><figcaption></figcaption></figure>

***

### Processing rules overview

In the table below, review the possible processing rules your organization can utilize in the vendor x purpose matrix:

<table><thead><tr><th width="207">Processing rule</th><th>Description</th></tr></thead><tbody><tr><td>Allowed</td><td>Allow the vendor to process data for the specified purpose</td></tr><tr><td>Not Allowed</td><td>Do not allow the vendor to process data for the specified purpose</td></tr><tr><td>Opt-in</td><td>Only allow the selected purpose to be processed with consent as a processing rule for the specified vendor</td></tr><tr><td>Opt-out</td><td>Only allow the selected purpose to be processed with legitimate interest as a processing rule for the specified vendor</td></tr><tr><td>Not applicable</td><td>The vendor does not process end-user data for the purpose</td></tr></tbody></table>

### IAB TCF restrictions

When configuring processing rules for IAB vendors, your organization will want to keep the following rules in mind when:

<table data-header-hidden><thead><tr><th width="174"></th><th></th></tr></thead><tbody><tr><td>Purposes</td><td><p>For Purpose 1: Store and/or access information on a device, can only be <strong>Opt-in</strong> or <strong>Not applicable</strong></p><p></p><p>For Purpose 3-6, which are listed in order as:</p><ul><li>Purpose 3: Create profiles for personalised advertising</li><li>Purpose 4: Use profiles to select personalised advertising</li><li>Purpose 5: Create profiles to personalise content</li><li>Purpose 6: Use profiles to select personalised content</li></ul><p>processing rule for these purposes will always be <strong>Allowed</strong> or <strong>Not Allowed</strong></p></td></tr><tr><td>Special Purposes</td><td>No processing rules are available for IAB vendor special purposes</td></tr><tr><td>Features</td><td>No processing rules are available for IAB vendor features</td></tr><tr><td>Special Features</td><td>Declared legal basis for special features (always consent) cannot be restricted. Your organization can only apply <strong>Allowed</strong> or <strong>Not Allowed</strong></td></tr></tbody></table>

### Manage processing rules for IAB TCF purposes

The vendor x purpose matrix will populate with the default processing rules for IAB TCF purposes defined for the vendor in the data manager.  Review the table below for actions per vendor type

<table><thead><tr><th width="198">Vendor Type</th><th>Managing processing rules</th></tr></thead><tbody><tr><td>IAB</td><td>Any constraints coming from the Global Vendor List (GVL) is applied (Allow, Disallow, and restricted Opt-in/Opt-out options). Any IAB TCF purposes that are <strong>Not applicable</strong> are non-editable for the regulation.</td></tr><tr><td>Didomi</td><td>All processing rules set in the data manager for the vendor are non-editable. Additional IAB TCF purposes can be added, edited, or removed by configuring a processing rule.</td></tr><tr><td>Google ATP</td><td>All processing rules set in the data manager for the vendor are non-editable. Additional IAB TCF purposes can be added, edited, or removed by configuring a processing rule.</td></tr><tr><td>Custom</td><td>Can add, edit, or remove processing rule for IAB TCF purposes</td></tr></tbody></table>

If available, your organization can manage the processing rule for any vendor and IAB purpose combination by navigating to the appropriate cell in the matrix and using the provided drop-down menu to select a processing rule.

Any changes made will be inherent for the regulation only and will not impact the default settings of the vendor in your organization's data manager.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2F0EB9cQxYK0QIJRWGbmaM%2FScreenshot%202026-10-27%20at%207.14.36%E2%80%AFAM.png?alt=media&amp;token=351f99f6-6cf5-40ac-8da2-1f965c11d6c8" alt="" width="563"><figcaption></figcaption></figure>


---

# 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/regulations-manager/frameworks/iab-tcf/processing-rules-for-iab-tcf-purposes.md?ask=<question>&goal=<user_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.
