# TCF v2.2 amendments - September 2024 On March 7, 2024, the Court of Justice of the European Union (CJEU) issued a judgement in a case involving IAB Europe and the Belgian Data Protection Authority (APD). The court clarified that Transparency and Consent (TC) Strings may be considered personal data under certain conditions, particularly if they can be linked with other identifiable data points, thereby enabling the identification of an individual with reasonable effort. In response to the CJEU's reasoning, the Transparency & Consent Framework (TCF) Steering Group approved a new iteration of the IAB TCF Framework (v2.2), incorporating three new amendments. These changes aim to assist online ecosystem participants in adhering to the ePrivacy Directive and GDPR requirements as expected by regulators. This updated version is based on measures proposed in the “action plan” submitted to and approved by the Belgian Data Protection Authority (APD). The plan ensures compliance with the finding that TC Strings may qualify as personal data under the GDPR, thus necessitating a legal basis for their processing. In this article, we will cover the following: * [Amendments](#amendments) * [Timeline](#timeline) * [Didomi updates and changes](#didomi-updates-and-changes) {% hint style="info" %} For more information on the CJEU decision regarding IAB Europe’s Transparency and Consent Framework (TCF), please refer to our [dedicated blog article](https://blog.didomi.io/cjeu-decision-iab-europes-tcf-march-2024 ). {% endhint %} *** ### Amendments The three new amendments added as part of TCF v2.2 are: * [Inclusion Special Purpose 3](#inclusion-of-special-purpose-3) * [New second layer UI requirement for CMPs](#new-secondary-layer-ui-requirement-for-cmps) * [Policies versioning](#policies-versioning) #### Inclusion of Special Purpose 3 A new special purpose, titled "**Save and Communicate Privacy Choices**" has been added to the TCF purposes taxonomy as Special Purpose 3, as outlined in [IAB policies](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/#headline-524-18959). This purpose is specifically designed to address the processing of TC Strings to verify the consent and/or objection status of a vendor and/or purpose, ensuring end-users' privacy choices are respected. Vendors can declare this purpose at the registration level, provided they have conducted and documented a legitimate interest assessment (LIA) that demonstrates the end-users’ interests and fundamental rights do not outweigh the legitimate interests pursued. | **Impact on UI notice** | **Impact on consent** | **Impact on console** | | -------------------------------------------------------------------------------------------------- | --------------------- | --------------------- | | New Special Purpose displayed when at least one IAB vendor included in the notice has declared it. | None | None | #### New secondary layer UI requirement for CMPs TCF policies describe in [Section D. c. VII](https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/#headline-2055-18959): *"c. When providing transparency about Purposes, Special Purposes, Features, Special Features and Vendors in connection with a legitimate interest for the same, a single secondary layer must be provided that allows the user to (...) VII. review where applicable the storage and access information relating to the CMP’s recording of Signals, including the maximum device storage duration."* CMPs should, at a minimum, **disclose on the secondary layer of their UIs how the TC String is stored and the duration for which it is stored on the end-user's device**. According to [IAB recommendation](https://iabeurope.eu/tcf-faqs/), Didomi will address this requirement by including a dedicated section at the bottom of the second layer of the consent notice. The new section called "About the storage of your choices" will list the cookies added by Didomi to collect consent and their maximum duration. {% hint style="info" %} This new section will only be displayed when TCF is enabled. {% endhint %} The names of the cookies will be retrieved dynamically based on the actual configuration (whether default names or custom names). | **Impact on UI notice** | **Impact on consent** | **Impact on console** | | ---------------------------------------------------- | --------------------- | --------------------- | | New section displayed in layer 2 when TCF is enabled | None | None | #### Policies versioning The Policies version has been incremented from 4.0.a to 5.0, and this change must be reflected in the TC Strings. Starting 4 October 2024, new TC Strings must be created under policies version 5.0. TC Strings created under policies version 4 before this date **will remain valid**. | **Impact on UI notice** | **Impact on consent** | **Impact on console** | | ----------------------- | ----------------------------------------------------- | --------------------- | | None | Policies version changed from 4.0 to 5.0 in TC string | None | ### Timeline The timeline for the migration to TCF v2.2 is as follows: | **Date** | **Milestone** | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | July 3rd, 2024 | Deadline for Vendors to update their GVL registration | | July 4th, 2024 | Availability of Special Purpose 3 in the IAB TCF [Global Vendor List](https://vendor-list.consensu.org/v3/vendor-list.json) (GVL) and [corresponding translations](https://register.consensu.org/Translation) as of Thursday July 4, 2024. | | Mid July 2024 | Didomi delivery to support the new amendments for both Web and Mobile SDKs | | October 4th, 2024 | Deadline for CMPs to implement the new policies and for publishers to deploy it | ### Didomi updates and changes The new Policies do not require CMPs to resurface the Framework UIs. That is, there is **no need to re-collect consent or re-publish the notice**. | | **Amendment** | **Impact on UI notice** | **Impact on consent** | **Impact on console** | | ------ | ------------------------------------------- | -------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | --------------------- | | **#1** | Inclusion of Special Purpose 3 | New Special Purpose displayed when at least one IAB vendor added in the notice vendors declared it | None | None | | **#2** | New secondary layer UI requirement for CMPs | New sentence displayed in layer 2 when TCF is enabled | None | None | | **#3** | Policies versioning | None | Policies version changed from 4.0 to 5.0 in TC string | None | {% tabs %} {% tab title="Web SDK" %} The changes will be reflected automatically in your consent notice and no further action is required by your organization. {% endtab %} {% tab title="Mobile SDKs" %} New SDK versions were released to support the new amendments. The minimum required versions are the following: * Android and Android TV - `2.9.0` * iOS and tvOS - `2.10.0` * Unity - `2.5.0` * Flutter - `2.6.0` * React native - `2.6.0` Your organization has to **upgrade its apps** with the last version of the SDK **before October 4th**. {% hint style="danger" %} If your organization does not migrate its apps to a version supporting the latest amendments by October 4th, Didomi will disable the TCF integration for those appa. {% endhint %} {% endtab %} {% endtabs %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.didomi.io/releases-and-announcements/announcements/tcf-v2.2-amendments-september-2024.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.