What is the _cc_id cookie?
_cc_id is CookieFix's own cookie, set by the consent widget (Consent Management Platform / CMP) installed on a website using the CookieFix service. It appears as soon as the visitor makes a choice in the cookie banner (accept, reject, or customize), or, depending on configuration, when the banner is first displayed.
It is a first-party HTTP cookie, set on the domain of the visited website, not on the cookiefix.ro domain.
What data it stores
_cc_id stores a unique identifier tied to the visitor's consent session, used to match the saved preferences (which cookie categories were accepted or rejected) to that visitor on subsequent visits.
The exact value format varies between installations and is not documented publicly in technical detail. Consent-related data is typically sent to CookieFix's infrastructure to generate the proof of consent (audit trail) required under GDPR.
What it is used for
The purpose of _cc_id is purely functional: it lets the CookieFix widget recognize a visitor who has already expressed a consent preference, so the banner doesn't reappear on every page or visit, until the cookie expires or the site's cookie policy changes.
For the site administrator, this cookie underpins the compliance mechanism itself — without it, the system could not track who has or hasn't given consent, making it impossible to honor the user's choice.
Does it require consent?
_cc_id is classified as strictly necessary (required for the website's basic functioning). Under Romania's Law 506/2004 (transposing the ePrivacy Directive) and ANSPDCP guidance, cookies strictly necessary to provide a service explicitly requested by the user — here, consent management — do not require prior consent.
The site administrator should still list it in the cookie policy, along with its purpose and duration, to meet GDPR's transparency requirements.
How to block or delete _cc_id
A visitor can delete or block _cc_id at any time from browser settings (Chrome, Firefox, Safari, Edge — per-site cookie management). Blocking it will cause the consent banner to reappear on every visit, since the site can no longer remember the previous choice.
Being strictly necessary, this cookie should not and normally cannot be auto-blocked by a CMP before consent, since it is itself the mechanism that records consent. CookieFix, as a consent platform, automatically blocks other scripts (statistics, marketing, preferences) until the visitor gives consent, but lets strictly necessary cookies like _cc_id function from the start.
Frequently asked questions
It's CookieFix's internal cookie that stores a visitor's consent choice on websites using the CookieFix banner.
No, it's classified as strictly necessary since it supports the consent management function itself, but it must be listed in the site's cookie policy.
Its typical duration is 1 year, after which it resets automatically if the visitor doesn't return to the site.
The consent banner will reappear on the next visit, since the site no longer has a record of the previous choice.