The Global Privacy Platform (GPP) String concept is a standardized format for representing privacy policies and consent choices. It is a machine-readable string that encodes the privacy practices of a website or application in a standardized way, allowing for easier and more efficient management of user consent.
Here's an example of what a GPP String might look like:
DBACNYA~CPonToAPonToABEACBENC7CoAP_AAH_AAAwII4Nf_X__b3_n-_7___t0eY1f9_7__-0zjhfdt-8N3f_X_L8X_2M7vF36tr4KuR4ku3bBIQdtHOncTUmx6olVrzPsbk2cr7NKJ7Pkmnsbe2dYGH9_n93T_ZKZ7___f__7___________________v____-_____9________________________________8EcGv_r__t7_z_f9___26PMav-_9___aZxwvu2_eG7v_r_l-L_7Gd3i79W18FXI8SXbtgkIO2jnTuJqTY9USq15n2NybOV9mlE9nyTT2NvbOsDD-_z-7p_slM9___v__9___________________3_____f____-________________________________-AAAA.YAAAAAAAAAAA~1---
The format of GPP String:
whatsInThisString~sectionOneEncodedValues~sectionFiveEncodedValues
Header section acting as a string “table of contents” followed by discrete sections of privacy signals.
Each section represents a unique privacy signal, usually a unique jurisdiction. Below are the supported discrete sections.
| Section ID | Client-side API Prefix | Description |
|---|---|---|
1 | tcfeuv1 | EU TCF v1 section (deprecated) |
2 | tcfeuv2 | EU TCF v2 |
3 | GPP Header section (REQUIRED) | |
4 | -- | GPP signal integrity section |
5 | tcfca | Canadian TCF |
6 | uspv1 | USPrivacy String |
7 | usnat | US - national section |
8 | usca | US - California section |
9 | usva | US - Virginia section |
10 | usco | US - Colorado section |
11 | usut | US - Utah section |
12 | usct | US - Connecticut section |
Find GPP API 1.1 at /docs/tutorials/iab-gpp
Find more information at https://www.iab.com/wp-content/uploads/2022/12/IABTechLab_MSPA_GPP_2022_12.pdf
Find IAB GPP Consent String Decoder at: GPP Decoder.