What is the _cc_consent cookie?
_cc_consent is an HTTP cookie set by the CookieFix widget script on websites that use this consent management platform (CMP). It appears in a visitor's browser as soon as they interact with the cookie banner – for example by clicking a button such as "Accept", "Reject", or "Save preferences".
It is set by the CookieFix widget's JavaScript code, loaded on the site owner's domain, not by a third-party tracking domain.
What data it stores
The cookie stores the consent state expressed by the visitor (which cookie categories were accepted or rejected) and typically a timestamp of when the decision was made. The exact value format can vary depending on the CookieFix widget version.
The value is read by the JavaScript widget directly in the browser on each page load, to decide whether the banner needs to be shown again and which scripts are allowed to run. The data is generally not sent to third-party advertising servers.
What it is used for
The cookie's purpose is purely functional: it lets the site remember the visitor's choice so the consent banner isn't shown on every visit. It also helps the widget know which script categories (analytics, marketing, preferences) it is allowed to activate on the page.
For the site owner, this cookie is the technical element that makes it possible to record and enforce consent as required by law.
Does it require consent?
_cc_consent is classified as a strictly necessary cookie. Under the GDPR and the ePrivacy Directive (transposed in Romania via Law 506/2004), cookies that are strictly necessary for a service explicitly requested by the user – such as the consent mechanism itself – do not require prior visitor consent.
The site owner should still list this cookie in the site's cookie policy, along with its purpose and duration, for transparency and to allow the relevant data protection authority to verify compliance.
How to block or delete _cc_consent
A visitor can delete or block this cookie from browser settings (for example, the "Privacy and security" section in Chrome, Firefox, or Edge). Deleting it will make the consent banner reappear on the next visit.
- Manual deletion: from the browser's cookie settings, by searching for the visited site's domain.
- General blocking: via browser extensions that block first-party cookies, though this may affect the site's proper functioning.
Because it is strictly necessary, a CMP like CookieFix does not block this cookie before consent – it is the mechanism through which consent itself is collected and remembered. CookieFix instead automatically blocks third-party scripts (analytics, marketing) until the visitor has made a choice through this mechanism.
Frequently asked questions
No. It is classified as strictly necessary because it supports the consent mechanism itself, so it can be set without prior visitor consent.
The site will no longer know your previous choice, and the consent banner will appear again on your next visit.
The typical duration is 1 year, after which it expires automatically and needs to be reset by showing the banner again.
Yes. Even though it doesn't require consent, strictly necessary cookies must still be disclosed transparently, with their purpose and duration, in the cookie policy.