Roskomnadzor's 2027 cookie and tracking guidance affects every foreign company operating a Russian-facing website. Find out what changed. Make an enquiry.
Roskomnadzor, Russia's data protection and internet regulator, has issued formal guidance on cookie and tracking compliance under Russian law – a development that directly affects the legal position of foreign companies operating Russian-facing websites, digital services, and mobile applications. The guidance, published in early 2027, clarifies how the regulator interprets the collection and processing of behavioural tracking data in light of Federal Law No. 152-FZ on Personal Data, and signals a more structured enforcement posture toward cookie-based data processing than Russian regulatory practice has previously applied. For in-house counsel managing a Russian subsidiary or overseeing a Russian digital presence, this development warrants prompt review of existing consent architectures and data processing records.
The core shift in the Roskomnadzor guidance is one of classification and consent granularity. Under the prevailing regulatory approach before this guidance, cookies were treated inconsistently in Russian practice – sometimes characterised as personal data, sometimes not, depending on whether they could be linked to an identified or identifiable individual. The guidance resolves this ambiguity in the regulator's favour: where cookies or tracking technologies collect information that, alone or in combination with other data held by the operator, can identify a natural person, they constitute personal data within the meaning of the federal personal data framework.
The practical consequence is significant. Operators who previously relied on a generic website privacy policy to cover tracking activity will, under the guidance, be expected to obtain explicit, informed, and separately recorded consent for each category of tracking – including analytics cookies, advertising pixels, and third-party script loading. The guidance draws a distinction between strictly necessary technical cookies, which do not require separate consent, and non-essential tracking, which does. This mirrors the structural approach familiar to in-house counsel from European practice, but it operates within a distinct Russian legal framework and carries its own enforcement logic.
The guidance also addresses data localisation. Where tracking technologies transmit personal data outside Russia – to advertising networks, analytics platforms, or parent-company infrastructure located abroad – the localisation requirement under the personal data framework is engaged. Operators must be able to demonstrate that the initial collection and primary storage of such data occurs on servers located within Russia, before any cross-border transfer takes place. This obligation is not new, but the guidance applies it explicitly to the tracking context for the first time with regulatory specificity.
For in-house counsel reviewing your company's Russian website or digital product compliance position, this is a sound moment to reassess consent architecture and localisation records before a regulatory inquiry arises – make an enquiry: info@vetrovpartners.com |
The guidance applies to any operator – Russian or foreign – that processes personal data of individuals located in Russia through a website, application, or digital platform. For foreign companies, the scope is broadly construed: if the service is accessible in Russia, accepts Russian-language content, or is directed at a Russian audience, Roskomnadzor takes the position that the Russian personal data framework applies.
This means that the guidance is directly relevant to foreign parent companies whose Russian subsidiaries operate consumer-facing digital platforms, as well as to foreign companies that run Russian-language websites from abroad without a locally incorporated entity. The compliance question is the same in both cases: does the operator have in place a consent mechanism that meets the granularity standard set out in the guidance, and can it demonstrate that personal data collected through tracking is being localised and documented?
Foreign companies that have modelled their Russian cookie compliance on European GDPR practice will find that the frameworks partially converge on consent requirements, but diverge on localisation, documentation standards, and enforcement channels. A GDPR-compliant cookie banner does not, of itself, satisfy Russian law. The regulator's enforcement track record for cookie-specific violations has been limited to date, but the publication of structured guidance is a well-established precursor to audit activity in Russian regulatory practice. Companies that resolve their compliance position before an inquiry is opened are in a materially stronger position than those that address it in response to a formal request.
The immediate practical priority for in-house counsel is a structured review of the company's cookie and tracking inventory. This means identifying all cookies and tracking scripts deployed on Russian-facing digital properties, categorising them as technically necessary or non-essential, and mapping the data flows to determine whether personal data is being transmitted to servers outside Russia.
Where non-essential tracking is in use, the existing consent mechanism should be assessed against the guidance's requirements: consent must be freely given, specific, informed, and capable of being withdrawn without detriment to the user. A pre-ticked box or continued browsing does not constitute valid consent under the prevailing Russian regulatory interpretation.
Operators should also review their record-keeping. Roskomnadzor has the power to request documentation demonstrating that processing is lawful, and the ability to produce a clear processing register – covering the categories of data collected through tracking, the legal basis for each category, and the identity of any third-party processors receiving that data – is the operational foundation of a defensible compliance position.
For companies with localisation obligations, server configuration and data routing should be verified against the standard that initial collection and primary storage occur within Russia. Where this is not currently the case, legal and technical remediation should be scoped promptly.
Our firm's Data Protection practice regularly advises foreign companies on compliance with the Russian personal data framework, including consent architecture, localisation structuring, and regulatory correspondence with Roskomnadzor. For related reading on the broader framework, see our overview of cookie and tracking compliance under Russian law and our guide to Federal Law No. 152-FZ requirements for foreign companies.
If your organisation operates a Russian-facing digital service and has not yet reviewed its cookie compliance position in light of this guidance – make an enquiry: info@vetrovpartners.com |
Q: What specifically did Roskomnadzor's guidance change about cookie compliance in Russia?
A: The guidance formalises the regulator's position that cookies and tracking technologies which collect data capable of identifying a natural person constitute personal data under the Russian federal personal data framework. The key practical change is a requirement for granular, category-specific consent for non-essential tracking – separate from a general privacy policy acceptance. The guidance also explicitly applies the localisation obligation to tracking-based data flows for the first time, requiring that initial collection and primary storage occur on servers within Russia before any data is transferred abroad. Operators who previously relied on an omnibus privacy notice to cover all tracking activity will need to revise their consent architecture.
Q: Does this guidance apply to foreign companies that do not have a Russian legal entity?
A: Under the regulatory approach reflected in the guidance, the personal data framework applies to any operator processing personal data of individuals located in Russia, regardless of whether the operator is incorporated in Russia. A foreign company running a Russian-language website or directing digital services at a Russian audience is, in the regulator's view, subject to the framework – including the consent and localisation requirements now clarified by the guidance. The absence of a Russian subsidiary does not provide an exemption, though it does affect the practical enforcement mechanics available to Roskomnadzor. Foreign companies in this position should assess their exposure and compliance posture accordingly.
Q: What should in-house counsel prioritise immediately in response to this guidance?
A: The most actionable starting point is a cookie and tracking inventory for all Russian-facing digital properties. Counsel should identify which tracking technologies are in use, classify them as necessary or non-essential, and verify that non-essential tracking is covered by a compliant consent mechanism. The second priority is a data-flow audit to confirm whether personal data collected through tracking is being transferred outside Russia, and – if so – whether the localisation requirement is being met at the point of initial collection. Where gaps are identified, remediation should be scoped before a regulatory inquiry opens, since the ability to demonstrate a proactive compliance programme is relevant to how Roskomnadzor typically approaches enforcement discussions.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry