Configuring Legitimate Interest for IAB TCF 2.2
The General Data Protection Regulation (GDPR) allows for data processing on the Legitimate Interest legal basis.
GDPR Article 6 Section 1f defines Legitimate Interest processing as when:
processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.
Within the IAB 2.2 framework Legitimate Interest can be used by registered IAB Vendors as a legal basis for processing data. This means that when the Vendor signs up for the IAB framework, they disclose which IAB 2.2 Purposes they will use for processing data and what legal basis they will use to process that data.
Their choices are Consent and Legitimate Interest. For Consent as a legal basis, the user must provide consent for that Purpose for the Vendor to be able to process data. When a Vendor chooses Legitimate Interest as a purpose of processing, the user does not need to consent for that purpose in order for the vendor to process data.
As a publisher, you may decide to you do not find this legal basis appropriate for a given vendor and therefore wish to prevent them from using Legitimate Interest as a legal basis.
If you decide to allow Vendors to use Legitimate Interest, you need to give the data subject the ability to dispute the Legitimate Interest legal basis of processing. In OneTrust, this is displayed to the end-user as a toggle, checkbox, or button.
You can review the IAB TCF 2.2 policies here.
You can also allow Legitimate Interest by individual vendor. For more information, see Managing the IAB TCF Global Vendor List.
You will also need to ensure that your implementation complies with IAB TCF 2.2 standards. To ensure that you are compliant, see IAB TCF 2.2 Policy Checklist & Custom Text Requirements.
|
Reason for Processing |
Consent |
Legitimate Interests |
|---|---|---|
|
Purpose 1 - Store and/or access information on a device |
Yes |
No |
|
Purpose 2 - Use limited data to select advertising |
Yes |
Yes |
|
Purpose 3 - Create profiles for personalised advertising |
Yes |
No |
|
Purpose 4 - Use profiles to select personalised advertising |
Yes |
No |
|
Purpose 5 - Create profiles to personalise content |
Yes |
No |
|
Purpose 6 - Use profiles to select personalised content |
Yes |
No |
|
Purpose 7 - Measure advertising performance |
Yes |
Yes |
|
Purpose 8 - Measure content performance |
Yes |
Yes |
|
Purpose 9 - Understand audiences through statistics or combinations of data from different sources |
Yes |
Yes |
|
Purpose 10 - Develop and improve services |
Yes |
Yes |
|
Purpose 11 - Use limited data to select content |
Yes |
Yes |
|
Special Purpose 1 - Ensure security, prevent fraud, and fix errors |
Notice Only |
Notice Only |
|
Special Purpose 2 - Deliver and present advertising and content |
Notice Only |
Notice Only |
|
Special Purpose 3 - Save and communicate privacy choices |
Notice Only |
Notice Only |
|
Feature 1 - Match and combine data from other data sources |
Notice Only |
Notice Only |
|
Feature 2 - Link different devices |
Notice Only |
Notice Only |
|
Feature 3 - Identify devices based on information transmitted automatically |
Notice Only |
Notice Only |
|
Special Feature 1 - Use precise geolocation data |
Yes |
No |
|
Special Feature 2 - Actively scan device characteristics for identification |
Yes |
No |
To configure Legitimate Interest
If you are overriding legal bases for all vendors, it could cause the Publisher Restrictions to enlarge the size of the eupubconsent-v2 cookie to a size that is incompatible with the browser. Disable any vendors to which you do not wish to signal consent or legitimate interest.