What is the _ym_visorc cookie?
_ym_visorc is an HTTP cookie associated with Yandex Metrica, the web analytics service developed by Yandex. It is used by Metrica's Webvisor feature, which records visitor on-page behavior (mouse movements, clicks, scrolling) for later playback and analysis.
The cookie appears as soon as the Yandex Metrica script executes on the page, typically when the site loads, provided the site owner has enabled Webvisor in their Metrica account. It is set on the website's own domain (first-party cookie).
What data it stores
The cookie generally stores a technical identifier tied to the current browsing session, used to link recorded behavioral data (clicks, scrolling, movement) to that session within the Webvisor interface. The exact value format is not publicly documented by Yandex and may vary.
Data collected through this cookie is sent to Yandex Metrica's servers, which may process it outside the European Economic Area — a point that raises additional considerations regarding international transfers of personal data.
What it is used for
For Yandex, the cookie supports Webvisor's core function: visually reconstructing browsing sessions to analyze user experience. For the website operator, these recordings help identify usability issues, points where visitors abandon a form, or page areas that draw the most attention.
It is not used for targeted advertising, but strictly for statistical and behavioral traffic analysis.
Does it require consent?
- Category: statistics (analytics)
- Requires consent? Yes – under the ePrivacy Directive (transposed in Romania via Law 506/2004) and GDPR, analytics cookies are not strictly necessary and therefore cannot be set before the visitor gives explicit consent.
- What the site operator should do: list the cookie in the cookie policy, place it under the "statistics" category in the consent banner, and check the legal basis for any data transfer to Yandex, informing visitors accordingly.
How to block or delete _ym_visorc
A visitor can manually delete or block this cookie via browser privacy settings (e.g., the "Privacy and security" section in Chrome, Firefox, or Edge), or use script-blocking extensions targeting analytics tools. Given its short 30-minute lifespan, the cookie expires quickly anyway if the visitor is inactive.
For site operators, the correct approach is to automatically block the Yandex Metrica script until consent is obtained. A CMP such as CookieFix can prevent the Webvisor script from loading before the visitor accepts the "statistics" category, avoiding non-compliant cookie placement.
Frequently asked questions
It's not harmful in a technical sense, but it is privacy-sensitive because it supports recording visitor behavior on the page (session replay). That's why it's classified as a statistics cookie requiring consent.
The short lifespan reflects its technical purpose: linking behavioral data to the current browsing session rather than tracking the visitor long-term.
Yes, any analytics cookie active on a site, including Yandex Metrica's, must be clearly disclosed in the cookie policy with its provider, purpose, and duration.
Yes, if the Webvisor feature is disabled in the Yandex Metrica account, this specific cookie will not be set, though other Metrica cookies may still remain active for basic statistics.