Features Pricing GDPR cookie banner Google Consent Mode v2 WordPress plugin Cookiebot alternative For Agencies GDPR ePrivacy About Contact
RO | EN
Start Free →
Necessary

viewed_cookie_policy Cookie (CookieYes) – What It Is & Does

viewed_cookie_policy is a strictly necessary cookie set by the CookieYes plugin to remember that a visitor has seen, and typically interacted with, the site's cookie consent banner. It is used solely to run the consent system, not for marketing or analytics.

Name
viewed_cookie_policy
Provider
CookieYes
Category
Necessary
Type
HTTP cookie
Lifetime
1 year
Consent
No, but it must be listed in the cookie policy

What is the viewed_cookie_policy cookie?

viewed_cookie_policy is an HTTP cookie set by CookieYes, a cookie consent plugin/service widely used on WordPress websites. It appears as soon as a visitor lands on a site running CookieYes, usually alongside the display of the consent banner.

Its purpose is purely technical: to record that the cookie policy banner has been shown and, depending on configuration, whether the visitor made a choice. It is part of the site's compliance infrastructure rather than its core content or features.

What data it stores

The cookie typically stores a simple boolean-type value (yes/no) indicating whether the cookie policy banner has been viewed or dismissed by the user. The exact format may vary slightly between CookieYes plugin versions.

The data stays stored locally in the visitor's browser under the domain of the site using CookieYes; it is not, as such, sent to third-party servers for profiling or advertising purposes.

What it is used for

For the site owner, this cookie prevents the consent banner from reappearing on every visit, giving visitors a smoother browsing experience. For CookieYes, it is the technical mechanism through which the plugin "remembers" the banner state for each visitor.

It has no role in traffic analytics, ad targeting, or cross-site tracking; its function is strictly limited to managing the display of the consent interface.

Does it require consent?

viewed_cookie_policy is generally classified as strictly necessary (needed for the consent system itself to function), so it does not require prior visitor consent under the ePrivacy Directive as transposed locally, or under GDPR.

  • It should still be explicitly listed in the site's cookie policy, along with its purpose, duration, and provider.
  • Site owners should check their CookieYes configuration, since related cookies (analytics, marketing) may require separate consent.
  • Correctly placing it in the "necessary" category in a CMP avoids mistakenly blocking the consent banner itself.

How to block or delete viewed_cookie_policy

A visitor can delete or block this cookie from browser settings (Chrome, Firefox, Edge, Safari), via a site's cookie preference panel, or by using private/incognito browsing. Deleting it will cause the consent banner to reappear on the next visit.

Because it is strictly necessary, a properly configured CMP such as CookieFix should not block this cookie before consent — only scripts from the statistics/marketing/preferences categories should be held back until the visitor makes a choice.

Frequently asked questions

No, it is a strictly necessary technical cookie used only to remember that the cookie banner was shown, with no tracking or advertising purpose.

No, since it is classified as strictly necessary for the consent system to work, it does not require prior consent, but it must still be disclosed in the cookie policy.

The CookieYes consent banner will reappear on the next visit, since the site no longer has a record that it was already shown.

Its typical duration is 1 year, though this can vary depending on the specific CookieYes plugin configuration on a given site.

Updated 7 September 2026 · Information comes from the provider’s public documentation and CookieFix scans; it is not legal advice.