What is the cookieconsent_status cookie?
cookieconsent_status is an HTTP cookie created by the Cookie Consent JavaScript library (also known as CookieConsent.js, historically distributed in versions associated with Osano), embedded directly on a website to display a cookie acceptance banner.
It is set automatically by the consent script once the visitor makes a choice (accept, reject, or dismiss the banner), or in some configurations on first page load, before any interaction, depending on the site's setup.
What data it stores
The cookie typically stores a short text value indicating the consent state – for example allow, deny, or dismiss. The exact format can vary slightly between script versions and site configurations.
The data stays stored locally in the visitor's browser and is read by the site's script on each visit to decide whether the banner needs to be shown again. The cookie is not sent to any third-party servers of the provider; it is used exclusively by the JavaScript code running on the site's own domain.
What it is used for
The cookie's purpose is purely technical: it remembers the visitor's decision on the cookie banner so it isn't shown again on every page or visit. For the site owner, this cookie is what makes it practically possible to avoid repeatedly prompting for consent.
Its typical retention period is around 1 year, after which the visitor may be asked again.
Does it require consent?
In CookieFix's classification, cookieconsent_status falls under the strictly necessary category. Under the GDPR (Regulation 2016/679) and the ePrivacy Directive 2002/58/EC (transposed in Romania via Law 506/2004), strictly necessary cookies do not require prior consent, since their sole purpose is operating a service explicitly requested by the user – in this case, the consent mechanism itself.
- The site owner must still disclose this cookie in the cookie policy.
- Its function should not be made conditional on accepting the banner.
- Its purpose and retention period should be stated clearly, for transparency toward visitors and the ANSPDCP.
How to block or delete cookieconsent_status
A visitor can manually delete or block this cookie via browser settings (Chrome, Firefox, Edge, Safari – the site data/cookie management section), either individually or by clearing all cookies for that domain. Blocking it will make the consent banner reappear on every visit.
For site owners using a CMP like CookieFix, scripts belonging to categories that require consent (statistics, marketing, preferences) are automatically blocked until the visitor gives their consent; strictly necessary cookies like this one remain active so the consent system itself can function correctly.
Frequently asked questions
No. It's a technical cookie that only stores the visitor's choice on the cookie banner and is not used for advertising tracking.
No, since it's classified as strictly necessary, its basic function doesn't require prior consent under GDPR and ePrivacy, but it must still be disclosed in the cookie policy.
The consent banner will appear again on the next visit, since the site can no longer identify the previous choice.
Its typical lifespan is around 1 year, after which the browser removes it automatically and the visitor is prompted again.