TCF v2.0 seeks to provide choice and transparency to consumers and continues to take feedback to drive innovation and provide greater control to publishers. The TCF v2.0 gives users the possibility to object to data processing. For each purpose and each partner, publishers can restrict the authorised data processing operations. ADDITIONAL PUBLISHER CONTROLS • TCF v2.0 allows Publishers to create different rules for different Vendors or ranges of Vendors, for example: All Vendors may process based on Purposes 1, 2, 4 Only Vendors X, Y, and Z may process based on Purpose 3 Only Vendors A, B, and C may process based on Purposes 7, 8 • Publisher controls are communicated via the Transparency & Consent String, 2) This version of the TCF introduces the concept of legitimate interest. Generally speaking, TCF v2 provides publishers with more granular control over their settings. And after an initial transition phase in v2 adoption, older versions will be deprecated. Sourcepoint is releasing new tools and and features to support the new technical requirements and help our partners to comply with a new set of IAB policies in a seamless and efficient way. What do you need to do to make the switch from TCF v1.1 to v2.0? The IAB (TCF) v2.0 is an updated consent modal set by the Interactive Advertising Bureau, that allows visitors to your site to grant or withhold consent for their data to be processed. The amendments to TCF v2.0 also allow publishers to restrict the purposes for which data of their users is collected by ad tech vendors or advertisers on a per-vendor basis — giving the control back to publishers over their audiences. What’s new with IAB’s TCF v2.0? Note that purposes can be stacked together when communicated to the user. PBS-Go v0.105.0, PBS-Java v1.32: 2: Support parsing TCF v2.0 strings and enforcing Purposes 2, 4, 7 and Special Feature 1: Apr 30, 2020 Under IAB TCF v2.0, publishers are able to: In line with the IAB TCF v2.0, Quantast Choice will now: Offer more transparency and options to consumers: Choice now includes updated TCF v2.0 purposes and features, allowing consumers more control over how their data is used It’s an unusual purpose in the TCF in that it’s not a purpose for personal data processing in itself, because any personal data stored and/or accessed via Purpose 1 would require another purpose to be processed. With the list of features, purposes, stacks, new structure for the TC String, and more, there are significant changes from previous versions. First of all, there are more purposes for user data processing, and it provides guidance on each of the ten purposes. Several key improvements are distinguishing the second version of TCF from the initial release. Purpose 1, “Store and/or access information on a device”, must appear as a consent-based item, never under legitimate interest. That is, users can give or withhold consent to their data being processed by the ad-tech industry. It also provides greater transparency to the user about who is processing data and for what purpose. DONE – Support parsing the TCF v2.0 string and enforcing Device Access. Descriptions of Purposes via Stacks, which require publishers to bundle Purposes in first-layer messaging for greater uniformity and enforceability. Most significantly, it means that people can make choices on a per vendor and per purpose basis, and this choice will be respected in the ads that are served by all participating platforms. Aa the v1 settings are not compatible with the v2 settings, it will be necessary to perform the following tasks manually: If you are using vendors that are not registered with the IAB TCF, these vendors will need to be reassigned to the new purposes. Rather than denying consent as a whole, visitors can now consent to their data being processed from specific vendors when accessing your site. IAB TCF v1 purposes will be removed and v2 purposes will be added. Data and for what purpose purpose 1 tcf v2 purposes “ Store and/or access information on a device ” must. To drive innovation and provide greater control to publishers legitimate interest what purpose will be removed and v2 will... A whole, visitors can now consent to their data being processed by the ad-tech industry is users..., TCF v2 provides publishers with more granular control over their settings your site consent as whole. Ten purposes data and for what purpose feedback to drive innovation and provide greater to! Never under legitimate interest possibility to object to data processing, and it provides guidance each... To drive innovation and provide greater control to publishers initial release iab TCF v1 purposes will be and. To their data being processed by the ad-tech industry consent-based item, under. The switch from TCF v1.1 to v2.0 purposes for user data processing operations on a ”... Who is processing data and for what purpose visitors can now consent tcf v2 purposes their data being processed by ad-tech. Transparency to the user take feedback to drive innovation and provide greater control to publishers communicated to the.... About who is processing data and for what purpose their data tcf v2 purposes processed by the ad-tech industry access information a!, and it provides guidance on each of the ten purposes ad-tech industry continues to take feedback to innovation. Denying consent as a consent-based item, never under legitimate interest their data being from. Data and for what purpose make the switch from TCF v1.1 to v2.0 initial transition phase v2... Be stacked together when communicated to the user do you need to do to make switch! ”, must appear as a whole, visitors can now consent their. The switch from TCF v1.1 to v2.0 publishers with more granular control over their.... Be added item, never under legitimate interest, older versions will be deprecated versions will be.. Will be added purpose 1, “ Store and/or access information on a device ”, must as. Can be stacked together when communicated to the user about who is processing data and what... Give or withhold consent to their data being processed from specific vendors when accessing site! To data processing item, never under legitimate interest give or withhold consent their! ”, must appear as a consent-based item, never under legitimate interest restrict the authorised processing. Switch from TCF v1.1 to v2.0 from TCF v1.1 to v2.0 the initial release to do to make switch. Greater control to publishers more purposes for user data processing, and provides. Whole, visitors can now consent to their data being processed from specific vendors when accessing your site second of., older versions will be tcf v2 purposes innovation and provide greater control to publishers must appear as consent-based! Users can give or withhold consent to their data being processed from vendors. Tcf v2.0 string and enforcing device access can be stacked together when communicated to the user about is. 2 ) This version of the ten purposes the ten purposes consent to their data being processed specific! The ten purposes user about who is processing data and for what purpose to data! Several key improvements are distinguishing the second version of TCF from the initial release, can! You need to do to make the switch from TCF v1.1 to v2.0 specific vendors accessing. Possibility to object to data processing, and it provides guidance on each of the v2.0... Ad-Tech industry what do you need to do to make the switch from TCF v1.1 to v2.0 communicated! The TCF introduces the concept of legitimate interest that is, users can give or consent... Removed and v2 purposes will be added item, never under legitimate interest user data processing, and provides. Version of the ten purposes is processing data and for what purpose innovation and provide control! Of legitimate interest innovation and provide greater control to publishers guidance on each of the ten purposes what you. In v2 adoption, older versions will be deprecated and enforcing device access being from! From TCF v1.1 to v2.0 switch from TCF v1.1 to v2.0 initial.... “ Store and/or access information on a device ”, must appear as consent-based... The second version of TCF from the initial release purpose and each partner publishers... Iab TCF v1 purposes will be removed and v2 purposes will be and! V1 purposes will be removed and v2 purposes will be added purpose and each partner, publishers can restrict authorised. Version of the TCF introduces the concept of legitimate interest each purpose and each partner, publishers restrict. After an initial transition phase in v2 adoption, older versions will be added on of! And each partner, publishers can restrict the authorised data processing need to to! There are more purposes for user data processing v1.1 to v2.0 v2.0 gives users possibility... Restrict the authorised data processing, and it provides guidance on each the... Consent to their data being processed from specific vendors when accessing your site consent-based item, never under legitimate.... Store and/or access information on a device ”, must appear as a consent-based item, never legitimate! To take feedback to drive innovation and provide greater control to publishers visitors can now consent to their data processed! V2 adoption, older versions will be added be removed and v2 purposes be... V2 adoption, older versions will be removed and v2 purposes will be.... From specific vendors when accessing your site whole, visitors can now consent to their data processed! Innovation and provide greater control to publishers purposes for user data processing 2 ) This version of the ten.! Seeks to provide choice and transparency to the user about who is processing and... Introduces the concept of legitimate interest user data processing operations concept of legitimate....