search

InteractiveAdvertisingBureau / GDPR-Transparency-and-Consent-Framework

Technical specifications for IAB Europe Transparency and Consent Framework that will help the digital advertising industry interpret and comply with EU rules on data protection and privacy - notably the General Data Protection Regulation (GDPR) that comes into effect on May 25, 2018.
860 stars 360 forks source link

Typo in Publisher Restrictions Section? #231

Closed mindblade closed 3 years ago

mindblade commented 4 years ago

Seems like there's a typo in "Publisher Restrictions Section" here - https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/IAB%20Tech%20Lab%20-%20Consent%20string%20and%20vendor%20list%20formats%20v2.md#the-core-string

Eg. if a vendor has Purpose 2 declared as Legitimate Interest but also declares that Purpose as flexible and this field is set to 1, they must then check for the “consent” signal in the VendorConsents section to make a determination on whether they have the legal basis for processing user personal data under that Purpose.

"VendorConsents" needs to be replaced with "PurposesConsent"?

tla-sirdata commented 3 years ago

In this example the vendor would normally check his signal in the "Vendor Legitimate Interest" section because it's the default legal basis he has declared. But as there's a publisher restriction set to 1 (require consent), the vendor must check his signal in the "Vendor Consent" section.

achimschloss commented 3 years ago

True - we added a more in depth guidance how to determine the presence of a legal basis in the vendor guidance - https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/TCF-Implementation-Guidelines.md#detlegalbasis

As a matter of fact they need to check both (purpose and vendor signal) after determining the applicable legal basis.