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

Landmark decision on data localisation obligations for foreign companies in Russia: what it means for foreign parties

Elena Pavlova · February 2026 · 7 min read

A Russian court has ruled on data localisation obligations affecting foreign companies storing personal data of Russian users. Make an enquiry.

Foreign companies that collect or process personal data of Russian users but store that data on servers outside Russia have long operated in a compliance grey zone. A recent Russian court decision has materially narrowed that grey zone. The ruling confirms that the data localisation obligations established under Russian personal data legislation apply to foreign entities engaging with Russian users, irrespective of where the company is incorporated or where its servers are physically located. For in-house counsel managing a Russian subsidiary, a Russian-facing digital product, or a regional data infrastructure that touches Russian users, the decision introduces a compliance standard that is no longer open to the structural interpretations that some companies had relied upon.

What were the proceedings about?

In a matter concluded in the past year, a foreign-incorporated company operating a digital service with a substantial Russian user base was brought before a Russian commercial court following an inspection by Roskomnadzor, Russia's data protection and telecommunications regulator. The legal question at the heart of the proceedings was whether the company's obligations under Russian personal data legislation — specifically the requirement to ensure that the recording, systematisation, accumulation, storage, clarification, and retrieval of personal data of Russian citizens is carried out using databases located on Russian territory — applied to a foreign entity that had not established a legal presence in Russia in the form of a registered subsidiary or branch.

The company argued that its operations fell outside the territorial scope of Russian data protection law on the basis that it had no Russian legal entity, no Russian employees in a formal employment relationship governed by Russian law, and no server infrastructure on Russian soil. Roskomnadzor maintained that the statutory localisation requirement is triggered by the fact of processing personal data of Russian citizens, not by the organisational form through which that processing occurs. The commercial court was asked to determine which position the legislation supported.

The matter also engaged a secondary question: whether the company's existing contractual arrangements — under which a Russian counterparty handled certain data processing steps on behalf of the foreign parent — satisfied the localisation requirement, or whether the obligation rested with the foreign entity as the data controller regardless of downstream processing arrangements.

What did the court decide?

The court found in favour of Roskomnadzor. It held that the data localisation obligations under Russian personal data legislation apply to any entity that determines the purposes and means of processing personal data of Russian citizens, regardless of whether that entity has a formal legal presence in Russia. The absence of a registered Russian subsidiary, branch, or representative office was not treated as a factor that could displace the statutory obligation. The court's reasoning focused on the purpose of the localisation requirement — ensuring that personal data of Russian citizens remains accessible to Russian supervisory authorities — and held that this purpose would be defeated if foreign entities without a Russian presence were exempt.

On the secondary question, the court rejected the argument that subcontracting certain processing steps to a Russian entity satisfied the controller's own localisation obligation. It distinguished between data processing arrangements entered into for operational reasons and the statutory duty of the data controller to ensure localisation. The contractual intermediary was treated as a processor, not as a substitute for the controller's compliance.

"This ruling closes an interpretive gap that a number of foreign companies had relied on — the assumption that the absence of a Russian legal entity insulates a foreign controller from Russian data localisation law. In practice, it does not." — Elena Pavlova, Associate, Vetrov & Partners

The court's reasoning is consistent with the trajectory of Roskomnadzor enforcement over the past several years, during which the regulator has increasingly asserted jurisdiction over foreign entities on the basis of the data subjects' location rather than the controller's place of incorporation. What distinguishes this decision is that the court articulated the jurisdictional basis explicitly, providing a reasoned framework that lower courts and the regulator itself are likely to apply in subsequent proceedings.

For in-house counsel assessing whether this ruling affects your company's current data infrastructure — make an enquiry: info@vetrovpartners.com |

What does this mean for foreign companies operating in Russia?

The practical implications of this decision fall into three areas.

First, the ruling establishes that organisational form does not determine regulatory exposure. Foreign companies that have deliberately avoided establishing a Russian legal presence — sometimes precisely to limit their exposure to Russian regulatory requirements — cannot rely on that structural choice to avoid the localisation obligation. If the company processes personal data of Russian citizens in connection with a service directed at the Russian market, the obligation applies.

Second, the decision affects how companies should evaluate their data processing chain. The court's treatment of the processor-controller distinction has direct consequences for foreign companies that have structured their Russian data operations through local partners, distributors, or cloud-service intermediaries. Those arrangements may satisfy operational requirements, but they do not discharge the controller's statutory localisation duty. In-house counsel managing these arrangements will need to assess whether the foreign parent entity — as the controller — independently satisfies the localisation requirement, not merely whether the downstream chain includes a Russian entity.

Third, the ruling carries heightened significance because non-compliance with Russian data localisation requirements can result in enforcement by Roskomnadzor that includes the blocking of access to the company's services within Russia, in addition to administrative penalties. For companies with active Russian user bases, service blocking is a commercially material consequence that operates on a faster timeline than conventional judicial enforcement. Under the current regulatory framework, penalties for repeated or persistent violations of localisation requirements have been substantially increased, and Roskomnadzor has demonstrated a consistent willingness to pursue foreign entities. For companies that have not yet completed a localisation compliance review, the window for addressing the structural issues identified in this ruling is narrowing.

For in-house counsel managing a Russian-facing digital product or regional data infrastructure, the relevant question is no longer whether the obligation exists in principle — this decision resolves that — but whether the company's current technical and contractual arrangements satisfy it in practice. That assessment requires a review of where data is recorded and stored at each stage of the processing lifecycle, not only at the point of collection.

If your company directs services at Russian users and has not completed a data localisation compliance review, the time to act is before a Roskomnadzor inspection, not after. Make an enquiry or contact the team directly on WhatsApp / Telegram at for an initial conversation.

Frequently asked questions

Q: What does this ruling change for foreign companies that process personal data of Russian citizens?

A: The ruling confirms — with explicit judicial reasoning — that the data localisation obligation under Russian personal data legislation applies to foreign controllers on the basis of where the data subjects are located, not where the controller is incorporated or where its servers sit. Previously, some foreign companies had taken the position that the absence of a Russian legal presence — no subsidiary, no branch, no registered office — placed them outside the territorial reach of the localisation requirement. This decision rejects that position. The immediate practical change is that foreign companies directing services at Russian users must assess their data storage infrastructure against the localisation standard regardless of their organisational form.

Q: What should foreign companies do in light of this decision?

A: The immediate priority for in-house counsel is a structured review of the company's data processing lifecycle — identifying at which stages personal data of Russian citizens is recorded, stored, and retrieved, and whether those stages occur on infrastructure located in Russia. Where they do not, the company faces regulatory exposure that this ruling has confirmed is real and enforceable. The review should also examine whether existing arrangements with Russian processing partners or cloud providers satisfy the controller's own localisation obligation, or whether the company itself needs to establish compliant storage infrastructure. Companies that have previously relied on organisational form as a shield against the localisation requirement should treat that position as no longer available. Early engagement with Russian data protection counsel is advisable before any Roskomnadzor inspection or enforcement notice crystallises the issue.

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