Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Corporate & Regulatory

Cookie and tracking compliance under Russian law: what in-house counsel need to know

Elena Pavlova · June 2026 · 10 min read

Russian law imposes cookie consent, localisation, and Roskomnadzor duties on foreign-company sites. A step-by-step guide. Make an enquiry.

Unlike the EU's General Data Protection Regulation, which introduces a single cross-border consent framework for cookies and online tracking, Russian data protection law operates through several overlapping instruments — each with its own scope, supervisory authority, and enforcement mechanism. For in-house counsel managing a Russian-facing website or a Russian subsidiary's digital presence, this layered structure creates compliance obligations that are both broader and technically distinct from what GDPR experience would suggest. Understanding how cookie tracking compliance Russia requirements work in practice is the necessary starting point before any banner, consent flow, or data localisation project can be meaningfully scoped.

What to prepare before you begin: a compliance checklist

Before mapping obligations against your website's specific configuration, gather the following information. Each item shapes which requirements apply and which exemptions — if any — are available.

This checklist is a working tool, not an exhaustive compliance review. Your specific exposure will depend on the volume of Russian users, the nature of the data collected, and the technical architecture of your platforms.

If you need a preliminary assessment of your Russian cookie and tracking exposure — make an enquiry: info@vetrovpartners.com |

Step 1 — Determine whether Russian data protection law applies to your organisation

Russian data protection law — principally Federal Law No. 152-FZ on Personal Data — applies to any operator that processes the personal data of individuals located in Russia, regardless of the operator's country of establishment. This territorial reach broadly mirrors GDPR's extra-territorial logic, though the implementing requirements differ materially.

For cookie and tracking purposes, the key question is whether the identifiers your website collects — IP addresses, device fingerprints, advertising IDs, session tokens — qualify as personal data under Russian law. The prevailing regulatory interpretation holds that identifiers which can be used, alone or in combination, to single out an individual are treated as personal data. If your analytics or advertising stack collects such identifiers from Russian users, the law applies to you as an operator.

Foreign companies without a Russian legal entity are not exempt. The obligation attaches to the processing activity, not to corporate presence. In-house counsel should therefore assess applicability based on where users are located, not where the company is incorporated. For a detailed overview of the Federal Law 152-FZ personal data requirements that form the statutory foundation of these obligations, see our briefing at Federal Law 152-FZ: Personal Data Requirements for Foreign Companies.

Step 2 — Identify which cookies and trackers require consent and which do not

Not all cookies trigger the same obligations. Russian regulatory practice draws a functional distinction — broadly consistent with international norms — between cookies that are strictly necessary for the website to function and those that serve analytical, behavioural, or advertising purposes.

Strictly necessary cookies — session identifiers, load-balancing tokens, shopping cart state — generally do not require prior consent in Russian practice. By contrast, cookies that collect data about user behaviour, preferences, or identity for purposes beyond technical delivery are treated as requiring an informed, freely given, and specific consent before the tracking begins.

Third-party advertising and cross-site tracking scripts present the highest compliance risk. These typically involve data transfers to external processors, which introduces both the consent question and the data localisation question simultaneously. In-house counsel should instruct technical teams to produce a layered map: which scripts fire before consent is given, which fire on consent, and which are blocked entirely if consent is withheld.

Note: Roskomnadzor has intensified scrutiny of pre-consent script loading since late 2025. Websites where analytics or advertising scripts load before the user has interacted with a consent mechanism are at elevated risk of audit. The administrative consequences of unlawful processing include fines and, in cases of systemic violation, website blocking — a power that Roskomnadzor exercises with increasing frequency against non-compliant foreign-operated sites.

Step 3 — Implement consent collection that meets Russian requirements

A consent mechanism that satisfies GDPR will not automatically satisfy Russian law. The two regimes share underlying principles — consent must be informed, specific, and freely given — but differ in formal requirements.

Under Russian data protection law, consent to processing of personal data must be capable of being documented. This means the consent record must be stored and retrievable in a form that demonstrates what the user consented to, when, and on what terms. A standard GDPR-style cookie banner that records a boolean consent flag may not meet the Russian evidentiary standard unless the record also captures the version of the privacy notice presented at the time.

Practical requirements for a compliant Russian consent flow:

Present the consent request before any non-essential tracking script executes.Provide the privacy notice (or a summary linking to the full notice) in Russian. Notices available only in English do not satisfy the transparency obligation for Russian-speaking users.Offer genuine choice: a "Reject all" option must be as accessible as "Accept all." Pre-ticked boxes are not valid consent.Store a timestamped consent record tied to a session or user identifier, retaining it for the period during which you may be required to demonstrate compliance.Allow users to withdraw consent as easily as they gave it, and ensure that withdrawal takes effect promptly at the technical level.

For companies subject to both GDPR and Russian data protection law, a unified consent management platform can usually be configured to satisfy both regimes — but the Russian-language requirement and the evidentiary storage standard typically require configuration adjustments that are not part of a standard GDPR deployment.

For advice on configuring a consent management approach that satisfies both Russian and EU requirements — make an enquiry: info@vetrovpartners.com |

Step 4 — Address data localisation requirements for tracking data

Russia's data localisation rule requires that the personal data of Russian citizens be initially recorded, systematised, accumulated, stored, clarified, and retrieved using databases located on servers in the Russian Federation. This obligation applies to tracking data when that data constitutes or contains personal data of Russian users.

For in-house counsel, the localisation question is frequently the most technically and commercially demanding element of Russian cookie compliance. Several configurations raise particular concerns:

Cloud-based analytics platforms that route Russian user data through infrastructure outside Russia may not satisfy the localisation requirement, even if the provider offers contractual assurances about data handling. The prevailing regulatory and enforcement position is that the initial processing must occur on Russian-territory infrastructure, not merely that a copy is stored there subsequently.

Cross-border data transfers to advertising networks and data management platforms present a related issue. Where tracking data flows to third-party recipients outside Russia, the transfer must be justified under one of the permitted grounds — typically, documented consent that specifically covers cross-border transfer, or an agreement meeting the standard content requirements.

Roskomnadzor maintains a register of non-compliant operators and has used website blocking as an enforcement tool. Foreign companies with significant Russian user bases should assess whether their current infrastructure configuration exposes them to localisation non-compliance before a regulatory enquiry or audit is initiated. Our Data Protection practice covers the full range of advisory services available to companies navigating this requirement.

Step 5 — Notify Roskomnadzor and maintain ongoing compliance records

Operators who process personal data in Russia — including through cookies and tracking technologies — are generally required to notify Roskomnadzor before commencing processing. The notification must describe the categories of data processed, the purposes and legal bases, the retention periods, the data subjects, and the cross-border transfer arrangements.

Maintaining the notification as a live document is as important as the initial filing. Material changes to your processing activities — adding a new analytics tool, expanding to a new advertising network, or changing your data storage provider — may each require an updated notification.

Ongoing record-keeping obligations include:

Maintaining an internal record of processing activities that covers cookie and tracking operations specifically.Retaining consent records for the period for which you may be required to demonstrate compliance — in practice, this is typically aligned with the retention period of the data to which consent relates, plus a reasonable additional buffer.Documenting the legal basis for each category of processing, including any cross-border transfers.Conducting periodic reviews of third-party scripts to confirm that no new trackers have been introduced without a corresponding update to the privacy notice and, where required, a new notification to Roskomnadzor.

For in-house counsel managing multiple jurisdictions, the Roskomnadzor notification requirement is a procedural step with practical consequences: late or absent notifications have been used as the basis for audit initiation. The Federal Tax Service has also issued guidance on cookie-related data obligations relevant to commercial platforms — see our update at Federal Tax Service Guidance on Cookie Obligations for current regulatory developments. Companies with regulatory or licensing obligations in adjacent areas should also consider how tracking compliance intersects with requirements under Regulatory and Licensing frameworks.

For matters where prior non-compliance has already occurred, early remediation and voluntary disclosure to Roskomnadzor — before a formal audit commences — can meaningfully affect the outcome. Our Matters Hub contains anonymised references to prior data protection mandates where the firm has assisted companies in this position.

If you are assessing a prior gap in Roskomnadzor notification compliance — discuss your matter in confidence: info@vetrovpartners.com |

Frequently asked questions

Q: How long does the Roskomnadzor notification process take, and can we operate our website before it is complete?

A: The notification itself is submitted electronically and does not involve a waiting period for approval — it is a declaration rather than a licence. However, processing activities that are notifiable must not commence before the notification is submitted. In practice, companies that are already operating and have not yet filed are in a position of technical non-compliance from the point at which the obligation arose. Remediation in that position typically involves submitting the notification promptly, updating internal records, and — where processing has involved cross-border transfers without a documented legal basis — reviewing whether voluntary disclosure to Roskomnadzor is appropriate. Timelines for completing the notification itself are typically short (days to a few weeks) if the required information has been gathered in advance.

Q: What documents does a foreign company need in order to comply with Russian cookie consent requirements?

A: The core documents are a privacy policy available in Russian that covers cookie and tracking processing specifically; a consent record system capable of storing timestamped evidence of each user's consent choice; an internal record of processing activities covering all cookie and tracker categories; and any cross-border data transfer documentation required where tracking data is shared with recipients outside Russia. For companies subject to both GDPR and Russian law, many of these documents can be adapted from existing GDPR documentation, but Russian-language versions and the evidentiary storage requirements typically require additional configuration rather than direct translation.

Q: What happens if our website is found to be non-compliant with Russian data protection requirements?

A: The range of regulatory responses available to Roskomnadzor includes issuing a compliance order requiring remediation within a specified period, imposing administrative fines, initiating a formal audit, and — for systemic or repeated violations — adding the operator to the register of violators and blocking the website for Russian users. The practical significance of website blocking varies by business model, but for companies with material Russian user bases or e-commerce operations, it represents a material commercial risk. Companies that identify a compliance gap and remediate proactively — before a regulatory enquiry is received — are, in the prevailing enforcement practice, in a meaningfully better position than those who address the issue only after an inspection begins.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry