Didomi Cookies: storage

Currently, we store two cookies: 

🍪 Didomi token (didomi_token) -- [Legacy]

This cookie contains consent information for custom purposes and vendors, as well as Didomi-specific information (user ID, for instance).

This is the data that this cookie contains: 

• • user_id: ID of the current user
  • created: date of the Didomi token creation
  • updated: last consent update date
  • vendors.enabled: list of custom vendors enabled on the consent legal basis
  • vendors.disabled: list of custom vendors disabled on the consent legal basis
  • purposes.enabled: list of custom purposes enabled on the consent legal basis
  • purposes.disabled: list of custom purposes disabled on the consent legal basis
  • vendors_li.enabled: list of custom vendors enabled on the legitimate interest legal basis
  • vendors_li.disabled: list of custom vendors disabled on the legitimate interest legal basis
  • purposes_li.enabled: list of custom purposes enabled on the legitimate interest legal basis
  • purposes_li.disabled: list of custom purposes disabled on the legitimate interest legal basis
  • version: TCF version used
    
    

Here is an example of the Didomi token:

eyJ1c2VyX2lkIjoiMTc4NDExNGMtZjhiMy02NTkwLWE2ZGYtYjlmYjI0MGJkZWE1IiwiY3JlYXRlZCI6IjIwMjEtMDMtMTdUMTY6NDY6MzIuMzQ0WiIsInVwZGF0ZWQiOiIyMDIxLTAzLTE3VDE2OjQ2OjMyLjM0NFoiLCJ2ZW5kb3JzIjp7ImVuYWJsZWQiOlsiYW1hem9uIiwiZ29vZ2xlIiwiYzpyZXNlYXV4c28tVkZlcEtyTFIiLCJjOnBhcnRlbmFpcmUtWDlTRFdrZzIiLCJjOnBlcnNvbm5hbGktWDNWY3h6UkQiLCJjOmdvb2dsZWFuYS1oN0tjM2U3WSIsImM6cHVibGljaXRlLXRGUkY0ZDM5Il19LCJwdXJwb3NlcyI6eyJlbmFibGVkIjpbInA0ZW05YThtIiwicGFydGVuYWlyZS1jQXNEZThqQyIsIkNMLVQxUmdtNyIsIk05TlJISmUzRyIsInE0emxKcWRjRCJdfSwidmVuZG9yc19saSI6eyJlbmFibGVkIjpbImdvb2dsZSJdfSwidmVyc2lvbiI6Mn0=

It can be decoded on this site: https://www.base64decode.org/

🍪 Didomi consent string (didomi_dcs)

The Didomi Consent String (DCS) is a new binary format that replaces the traditional didomi_token, typically stored in cookies or local storage. The DCS format is inspired by the IAB TCF and GPP strings and is designed to offer a smaller, more compact representation of user consent data. It is generated and consumed by the Didomi SDK and is designed to optimize performance and improve storage efficiency.

🍪 Consent string (euconsent-v2)

This cookie contains the IAB TCF consent string and consent information for all the standard IAB vendors and purposes.

📰 You can consult the technical specification provided by the IAB to see what it contains. 

Here is an example of the consent string: 

CPDNd-xPDNd-xAHABBENBRCgAP_AAAAAAAAAF5wAQF5gAAAGCQAQF5joAIC8ykAEBeZKACAvMVABAXmMgAgLzAAA.f_gAAAAAAAAA

It can be decoded on this site: http://iabtcf.com/#/decode

We also support shared cookies at the group (domain specific to your operations) or global level (consensu.org domain).