> 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/iab-special-features.md).

# IAB special features

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

In the IAB Europe Transparency and Consent Framework (TCF), special features are data-processing activities that carry higher privacy risk than ordinary purposes. They are always a separate category from purposes and end-users must explicitly opt in to them, and vendors can not rely on legitimate interest as a legal basis. In this article, we will cover:

* [IAB special feature overview](#iab-special-feature-overview)
* [Manage special feature processing rule](#manage-special-feature-processing-rule)

***

### IAB special features overview

The IAB has designated the following as special features and require explicit end-user opt-in for data-processing:

<table><thead><tr><th width="307.86663818359375">Special Feature</th><th>Description</th></tr></thead><tbody><tr><td>Use precise geolocation data</td><td>With your acceptance, your precise location (within a radius of less than 500 metres) may be used in support of the purposes explained in this notice.</td></tr><tr><td>Identify devices based on information actively requested</td><td>With your acceptance, certain characteristics specific to your device might be requested and used to distinguish it from other devices (such as the installed fonts or plugins, the resolution of your screen) in support of the purposes explained in this notice.</td></tr></tbody></table>

### Manage special feature processing rule

When a vendor registers with the IAB they declare any use special features in the [IAB Global Vendor List (GVL)](/regulations-manager/frameworks/iab-tcf.md#global-vendor-list). Didomi will use these declarations to populate the vendor x purpose matrix.&#x20;

For IAB special features, the following processing rules are possible:

<table><thead><tr><th width="207">Processing rule</th><th>Description</th></tr></thead><tbody><tr><td>Opt-in</td><td>Only allow the selected special feature to be processed with consent as a processing rule for the specified vendor.<br><br>If the vendor has declared the use of a special feature in the GVL, Didomi will set the default processing rule for the special feature as opt-in.  This processing rule is coming directly from the vendor's GVL declaration.</td></tr><tr><td>Allowed</td><td>Allow the vendor to process data for the specified special feature. <br><br>The special feature will still require end-user opt-in for the vendor to process data related to the special feature. </td></tr><tr><td>Not Allowed</td><td>Do not allow the vendor to process data for the specified special feature.</td></tr><tr><td>Not applicable</td><td>The vendor does not process end-user data for the special feature.</td></tr></tbody></table>

To view/edit the processing rule for a special purpose, 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 has IAB TCF enabled on the 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%2FrsuGHRuRYSesBrp6a0ZW%2FScreenshot%202026-10-07%20at%208.43.34%E2%80%AFAM.png?alt=media&amp;token=3964561d-26d7-4f1b-98f0-1c72e96bdda1" alt="" width="563"><figcaption></figcaption></figure>

Select **Vendors & Purposes** on the subsequent page.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FJ4NLBk3Ku5bApQajhQMo%2FScreenshot%202026-10-08%20at%2012.54.06%E2%80%AFPM.png?alt=media&amp;token=c98aaa35-1bf0-45d4-af41-0b224794711c" alt="" width="563"><figcaption></figcaption></figure>

Navigate to the special feature column in the vendor x purpose matrix. Each cell in the column indicates the processing rule for the special feature per vendor.&#x20;

Select the cell inline with a particular vendor to view/edit the processing rule for the special feature

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FOMxiSlqVLybYoTVKBpNh%2FScreenshot_2026-10-08_at_1_14_14%E2%80%AFPM.jpg?alt=media&amp;token=8bd5e1ba-d4a6-4233-ac01-82d810f0d511" 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/iab-special-features.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.