IAB TCF (Transparency and Consent Framework)
Qu'est-ce que IAB TCF (Transparency and Consent Framework) ?
IAB TCF (Transparency and Consent Framework)The Interactive Advertising Bureau Europe's framework for capturing, encoding, and propagating user consent for advertising and analytics data uses under GDPR — controversial, partly invalidated by Belgian DPA in 2022, then revised as TCF v2.2.
The Transparency and Consent Framework (TCF) is IAB Europe's industry-wide framework for representing GDPR-compliant consent for advertising and analytics in the open-web ad-tech ecosystem. A Consent Management Platform (CMP) presents the user with the standardized consent UI listing purposes (e.g. 'create profiles to personalise content', 'measure ad performance'), vendor counts, and legitimate-interest claims; the resulting consent string — a base64-encoded structure conforming to the TCF v2.x specification — is passed via the IAB OpenRTB bid request to every SSP, DSP, and ad-tech vendor in the chain, who are expected to honour the encoded purposes and vendor opt-ins. The Belgian Data Protection Authority ruled in February 2022 that the original TCF v2.0 was itself a GDPR violation (insufficient transparency, IAB Europe acting as joint controller for the consent string), kicking off a multi-year remediation that produced TCF v2.2 (May 2023) with cleaner purpose text, mandatory vendor counts, and explicit information sources. A separate IAB Tech Lab US Privacy String (`USP_v1`) handles U.S. state-law signals. From a security/AppSec perspective, the TCF string is a critical input that should be validated and not blindly trusted as user identity.
● Exemples
- 01
A publisher's CMP shows the TCF v2.2 consent UI to EU visitors, encodes the resulting choice into a TC string, and propagates it via OpenRTB to bidders.
- 02
An ad-tech vendor checks the TCF string on each request and refuses to process the bid request for purposes that the user has not opted into for that vendor.
● Questions fréquentes
Qu'est-ce que IAB TCF (Transparency and Consent Framework) ?
The Interactive Advertising Bureau Europe's framework for capturing, encoding, and propagating user consent for advertising and analytics data uses under GDPR — controversial, partly invalidated by Belgian DPA in 2022, then revised as TCF v2.2. Cette notion relève de la catégorie Confidentialité et protection des données en cybersécurité.
Que signifie IAB TCF (Transparency and Consent Framework) ?
The Interactive Advertising Bureau Europe's framework for capturing, encoding, and propagating user consent for advertising and analytics data uses under GDPR — controversial, partly invalidated by Belgian DPA in 2022, then revised as TCF v2.2.
Comment fonctionne IAB TCF (Transparency and Consent Framework) ?
The Transparency and Consent Framework (TCF) is IAB Europe's industry-wide framework for representing GDPR-compliant consent for advertising and analytics in the open-web ad-tech ecosystem. A Consent Management Platform (CMP) presents the user with the standardized consent UI listing purposes (e.g. 'create profiles to personalise content', 'measure ad performance'), vendor counts, and legitimate-interest claims; the resulting consent string — a base64-encoded structure conforming to the TCF v2.x specification — is passed via the IAB OpenRTB bid request to every SSP, DSP, and ad-tech vendor in the chain, who are expected to honour the encoded purposes and vendor opt-ins. The Belgian Data Protection Authority ruled in February 2022 that the original TCF v2.0 was itself a GDPR violation (insufficient transparency, IAB Europe acting as joint controller for the consent string), kicking off a multi-year remediation that produced TCF v2.2 (May 2023) with cleaner purpose text, mandatory vendor counts, and explicit information sources. A separate IAB Tech Lab US Privacy String (`USP_v1`) handles U.S. state-law signals. From a security/AppSec perspective, the TCF string is a critical input that should be validated and not blindly trusted as user identity.
Comment se défendre contre IAB TCF (Transparency and Consent Framework) ?
Les défenses contre IAB TCF (Transparency and Consent Framework) combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de IAB TCF (Transparency and Consent Framework) ?
Noms alternatifs courants : TCF, Transparency and Consent Framework, IAB TCF v2.2.
● Termes liés
- privacy№ 233
Gestion du consentement
Processus et outils permettant de recueillir, enregistrer, rafraîchir et appliquer les autorisations des utilisateurs pour le traitement des données personnelles et le dépôt de cookies, conformément à la loi.
- privacy№ 494
Global Privacy Control (GPC)
A browser-level signal — an HTTP header and a JavaScript property — by which a user expresses a 'do not sell or share' opt-out, given binding legal force in California (CCPA/CPRA) and Colorado (CPA) regulations.
- compliance№ 488
RGPD
Règlement général sur la protection des données de l'Union européenne, encadrant le traitement des données personnelles des personnes situées dans l'UE et l'EEE.
- privacy№ 1263
Cookie tiers
Cookie déposé par un domaine différent de celui affiché dans la barre du navigateur, historiquement utilisé pour pister les utilisateurs entre sites.
- privacy№ 914
Informations personnelles identifiables (PII)
Toute donnée permettant d'identifier une personne, seule ou combinée à d'autres informations, comme un nom, un identifiant ou un enregistrement biométrique.
- compliance№ 167
CCPA
California Consumer Privacy Act, loi américaine de l'État de Californie qui confère aux résidents californiens des droits sur leurs informations personnelles.
● Voir aussi
- № 299Dark Patterns