{"id":2478,"date":"2025-08-15T09:01:00","date_gmt":"2025-08-15T07:01:00","guid":{"rendered":"https:\/\/blog.eprivacy.eu\/?p=2478"},"modified":"2025-08-15T09:01:00","modified_gmt":"2025-08-15T07:01:00","slug":"iab-tcf-version-2-3-2","status":"publish","type":"post","link":"https:\/\/blog.eprivacy.eu\/?p=2478","title":{"rendered":"IAB TCF Version 2.3"},"content":{"rendered":"\n<p>What? The IAB has published a minor update to the TCF guidelines. The change affects the\u00a0\u2018disclosed vendors\u2019\u00a0(disclosedVendors) section in the TC string.\u00a0\u2018Disclosed Vendors\u2019\u00a0refers to the vendors displayed to the user in the CMP. This information is now mandatory.<br>\u00a0<br>Why? The legal basis of\u00a0\u2018legitimate interest\u2019\u00a0for\u00a0\u2018special purposes\u2019\u00a0is to be strengthened. In our opinion, the IAB wants to use the mandatory disclosure to strengthen accountability and dispel doubts about the lawfulness of the processing. Since the IAB now itself relies on this legal basis for the processing of the TC string (\u2018special purpose 3\u2019), this is also essential for the IAB itself.<br>\u00a0<br>When?\u00a0<br>1) The updated technical specifications and the TCF JS Library were published on July 3, 2025.\u00a0<br>2) All participants are required to fully support the writing, reading, and processing of the \u2018Disclosed Vendors\u2019\u00a0section by February 28, 2026. After this date, any TC string without the \u2018Disclosed Vendors\u2019 section will be considered non-compliant with the TCF.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What? The IAB has published a minor update to the TCF guidelines. The change affects the\u00a0\u2018disclosed vendors\u2019\u00a0(disclosedVendors) section in the TC string.\u00a0\u2018Disclosed<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/blog.eprivacy.eu\/?p=2478\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2478"}],"collection":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2478"}],"version-history":[{"count":2,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2478\/revisions"}],"predecessor-version":[{"id":2480,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/2478\/revisions\/2480"}],"wp:attachment":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2478"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2478"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2478"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}