IAB TCF (Transparency and Consent Framework)
¿Qué es 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.
● Ejemplos
- 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.
● Preguntas frecuentes
¿Qué es 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. Pertenece a la categoría de Privacidad y protección de datos en ciberseguridad.
¿Qué significa 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.
¿Cómo funciona 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.
¿Cómo defenderse de IAB TCF (Transparency and Consent Framework)?
Las defensas contra IAB TCF (Transparency and Consent Framework) combinan habitualmente controles técnicos y prácticas operativas, como se detalla en la definición.
¿Cuáles son otros nombres para IAB TCF (Transparency and Consent Framework)?
Nombres alternativos comunes: TCF, Transparency and Consent Framework, IAB TCF v2.2.
● Términos relacionados
- privacy№ 233
Gestión del consentimiento
Procesos y herramientas que recopilan, registran, refrescan y aplican los permisos del usuario para tratar datos personales y emplear cookies conforme a la normativa de privacidad.
- 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
Reglamento General de Protección de Datos de la Unión Europea que regula el tratamiento de datos personales de personas en la UE y el EEE.
- privacy№ 1263
Cookie de terceros
Cookie creada por un dominio distinto al que aparece en la barra del navegador, usada históricamente para rastrear a los usuarios entre sitios.
- privacy№ 914
Información de Identificación Personal (PII)
Cualquier dato que permita identificar a una persona específica por sí solo o combinado con otra información, como nombres, identificadores o registros biométricos.
- compliance№ 167
CCPA
Ley de Privacidad del Consumidor de California, ley estatal de EE. UU. que otorga derechos a los residentes de California sobre su información personal.
● Véase también
- № 299Dark Patterns