Cookies and local storage

Review the table below for more information on cookies and/or local storage items that Didomi may store on end-user's devices:

Key	Status	Description
didomi_dcs	Active	The Didomi Consent String (DCS) didomi_dcs is an alternative to didomi_token as the mechanism used to store end-user consent. Allows your organization to not only support TCF vendors and purposes but also custom vendors and purposes, Authorized Technology Providers (ATPs), etc. in a single, lightweight, and privacy-compliant format. Click here for more information.
euconsent-v2	Active	Contains the IAB TCF consent string (TC String) and consent information for all the standard IAB vendors and purposes. Click here for the technical specification of the TC String. The TC string can be decoded using the TC String decoder.
didomi_token	Active	Consent information for custom purposes and vendors, as well as Didomi-specific information (e.g. user ID). The token can be decoded using a base64 decoder. Note: Token used specifically to store end-user consent related to GDPR. The data included in the token includes: 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
didomi_token_<regulation>	Active	Consent information for purposes and vendors for non-GDPR regulations supported by Didomi. The token can be decoded using a base64 decoder. For each regulation where the end-user's consent information is stored, the token will be suffixed with name of the regulation (e.g. didomi_token_cpra or didomi_token_tdpsa). Click here for more information on supported regulations. The data included in the token includes: 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 dns: Boolean value for if end-user has opted out of sale/share of data (only available for didomi_token_cpra) dnsd: Timestamp for when the opt-out notice was shown to the end-user (only available for didomi_token_cpra)