The Global Privacy Platform (GPP) is now complete and available for the industry. In this post, we’ll share with you all you need to know and cover any questions you may have regarding the new GPP.
What is GPP?
The GPP is one of a number of solutions created by IAB Tech Lab as part of the project Rearc initiative to assist the industry in overcoming the difficulties associated with dealing with various and evolving privacy laws worldwide.
Specifically, the GPP helps consolidate the handling of various consent signals from numerous worldwide privacy laws and enables user consent signals to be sent throughout the digital ad supply chain.
Additionally, iubenda supports Global Privacy Control (GPC). The GPP specs provide detail on the integration of current privacy signals into a single platform. This covers the common data types for encoding privacy strings, as well as methods for sending and receiving privacy strings.
💡 For further information, see the GPP Specification.
🗣 Did you know that iubenda’s CEO, Andrea Giannangelo, was one of the main collaborators who worked on the GPP?
We understand that managing privacy laws across numerous jurisdictions is challenging. That’s why iubenda is proud to announce Andrea’s involvement in the GPP, destined to grow into a key tool for navigating the intricacies of global privacy. Andrea held a crucial role in the development process, and he even presented the GPP when it was officially announced to the public at the IAB Tech Lab annual event in New York City.
What is supported by the GPP?
🚀 Currently, the GPP actively supports both the US Privacy and IAB Europe Transparency and Consent Framework (TCF) consent strings. Our Privacy Controls and Cookie Solution automatically detects and honors the GPC signal, so you don’t have to lift a finger!
In addition, we’ve incorporated support for US-specific privacy strings for Connecticut, Virginia, Colorado, and California as they have come into force. Furthermore, we plan to actively support the IAB Canada TCF consent string later this year.
💡 Be sure to bookmark this post! We’ll update it regularly throughout the year to keep you informed.
What about TCF v2.0?
TCF v2.0 specifications from IAB Europe are still accessible and supported.
Transparency & Consent String (TC String) and its encoding format are unchanged. TC string can be accessed via both the TCF-specific and GPP interfaces during the adoption process of the GPP.
💡IAB suggests that the industry adopt the GPP as it will serve as the main framework for future global user consent and preference signaling, especially for those who must take into account consent signaling across several jurisdictions.
How does this affect US Privacy Specifications?
Until now, the IAB CPRA (CCPA amendment) Compliance Framework has been supported by the US Privacy Specifications, which provided guidelines for managing data deletion requests and creating and transporting privacy strings.
👉 The state-specific privacy strings that take effect in 2023 will not be added to the US Privacy Specifications; instead, they will only be accessible through the GPP.
Since GPP will be the only platform that can support current and future privacy and consent management standards in the US, IAB urges the industry to move away from the US Privacy Specifications.
❓
What do I need to do?
For now, there’s nothing that you need to do.
As iubenda was directly involved in the creation of the framework, you can rest assured that we’ll keep you informed and that our solutions will seamlessly integrate with the GPP as it has with the TCF.