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

Russian Supreme Court clarification on cross-border data transfer restrictions from Russia

Elena Pavlova · October 2026 · 7 min read

Russia's Supreme Court clarified cross-border data transfer rules for foreign firms. What in-house counsel needs to act on. Make an enquiry.

Russian Supreme Court clarification on cross-border data transfer restrictions from Russia

When Russia's Supreme Court issues clarificatory guidance on a contested area of data protection law, the practical effects reach well beyond domestic entities. The cross-border data transfer rules under Federal Law No. 152-FZ — which govern how personal data collected in Russia may be transmitted to systems outside its borders — have long generated compliance uncertainty for foreign companies operating Russian subsidiaries, joint ventures, or data-processing arrangements. The clarification issued in the recent reporting period addresses several points on which Roskomnadzor enforcement and lower-court decisions had diverged, and the resulting picture is both more precise and, in certain respects, more demanding than what many compliance programmes currently reflect.

What did the Supreme Court clarify, and why does it matter?

Russian data protection legislation has, since the principal amendments that strengthened localisation requirements, required operators of personal data systems to notify Roskomnadzor before transferring personal data outside Russia's borders and to ensure that the receiving jurisdiction affords adequate protection. In practice, however, the notification and adequacy-assessment obligations were applied inconsistently: some operators treated the prior-notification requirement as a procedural formality satisfied by a one-time filing, while others read the legislation as imposing ongoing obligations that renewed with each materially new transfer arrangement.

The Supreme Court's clarification addresses this divergence directly. The prevailing judicial interpretation now holds that the prior-notification obligation attaches to each new category of data or new class of receiving party — not solely to the initial establishment of a cross-border transfer arrangement. Operators who implemented a single notification at the outset of their Russia data infrastructure and have since expanded the scope of data flows — adding new employee data categories, new customer data streams, or new third-party processors outside Russia — are likely operating under a compliance posture that no longer satisfies the interpreted standard.

A second point of clarification concerns the written assessment that operators must conduct of the adequacy of protection in the destination jurisdiction. The Court's guidance confirms that this assessment must be documented and retained, and that generic references to GDPR compliance in the receiving country do not, of themselves, constitute a sufficient adequacy determination under Russian law. This is a material point for multinational groups whose Russian entities transfer data to EU-based data processors: the fact that those processors operate under GDPR does not substitute for a Russia-specific assessment of the foreign jurisdiction's data protection framework.

Which foreign companies are most affected by these changes?

The entities most directly affected are those operating Russian legal entities — subsidiaries, representative offices, or branches — that transfer any category of personal data to group companies, shared services centres, or third-party processors located outside Russia. This captures a wide range of common operational arrangements: HR data transferred to a European or Asian payroll provider; customer data replicated to a global CRM platform hosted outside Russia; technical support data routed through a non-Russian shared-service facility.

EAEU member states retain a distinct position: data transfers within the Eurasian Economic Union are not subject to the cross-border transfer notification regime in the same way as transfers to third countries. Foreign groups that route Russian data through an EAEU-based intermediate entity — for example, through a Kazakhstan or Armenia affiliate — should confirm, in light of the Court's guidance, whether that routing genuinely insulates the arrangement from the notification requirement or whether the onward transfer from the EAEU entity to a non-EAEU destination re-engages the Russian rules.

Foreign companies that have not reviewed their data transfer arrangements since implementing the initial localisation measures required by the amendments that came into force in the prior legislative cycle face the most immediate exposure. Under the standard interpretation of the supervisory framework, Roskomnadzor may open an inspection on the basis of a complaint from a data subject, a regulatory trigger, or on its own initiative — and the absence of documented prior notifications for expanded transfer categories is among the items that inspection teams examine. Companies that cannot produce current, accurate notification filings and a documented adequacy assessment for each active cross-border transfer arrangement are exposed to the administrative consequences that the supervisory authority has the power to impose.

For in-house counsel whose Russian data infrastructure has not been reviewed since the prior legislative amendments — an updated gap analysis may identify material exposure before it becomes a supervisory matter. Make an enquiry: info@vetrovpartners.com |

What should in-house counsel do now?

The practical response to the Supreme Court's clarification falls into three stages. The first is a current-state mapping of all active cross-border data flows from the Russian legal entity: what categories of data are transferred, to which recipients, under what legal basis, and whether each transfer was individually notified to Roskomnadzor. For most multinational groups, this mapping will reveal flows that have evolved since the original notification — additional data categories, new processors, changed routing — that require supplementary filings.

The second stage is a documentation review of the adequacy assessments held on file for each destination jurisdiction. In light of the Court's confirmation that GDPR status in the receiving country is not a self-standing adequacy basis under Russian law, any assessment that simply cross-references GDPR compliance should be replaced with a documented analysis of the destination country's data protection framework by reference to the criteria under Russian legislation. This is a jurisdiction-specific exercise and cannot be discharged by reference to documents prepared for GDPR transfer-impact assessment purposes.

The third stage is confirming the EAEU routing position, where relevant. Groups that use EAEU affiliates as an intermediate step in their data architecture should obtain a specific legal opinion on whether that structure remains effective in light of the clarification. The Court's guidance does not directly address EAEU routing structures, which means the question remains one of legal interpretation — but it is a question that Roskomnadzor has the capacity to raise in an inspection context.

Foreign companies seeking a clearer view of how cross-border data transfer requirements under Russian law apply to their specific arrangements, or wishing to understand the full analytical framework for cross-border data transfer restrictions from Russia, will find detailed treatment in the related reading below. For a broader overview of the firm's work in this area, the Data Protection practice page sets out the scope of advice available to foreign-owned entities.

If your Russian entity's data transfer notifications have not been reviewed since the last legislative cycle — make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What specifically changed in how Russian courts now interpret the cross-border data transfer notification requirement?

A: The Supreme Court's clarification establishes that the prior-notification obligation is not discharged by a single, initial filing with Roskomnadzor. The prevailing interpretation now holds that notification must cover each new category of personal data and each new class of receiving party outside Russia. Operators who have expanded the scope of their data transfers since their original notification — by adding employee data categories, new customer datasets, or additional third-party processors — are required to file supplementary notifications. The practical effect for foreign-owned Russian entities is that a one-time compliance exercise carried out at the point of the original localisation amendments may no longer reflect the current position.

Q: Does GDPR compliance in the destination country satisfy the adequacy assessment requirement under Russian data protection law?

A: No. The Court's guidance confirms that GDPR status in the receiving jurisdiction does not, of itself, constitute a sufficient adequacy determination under Russian data protection legislation. Operators must conduct and retain a documented assessment of the destination country's data protection framework by reference to the criteria established under Russian law. This is a distinct and jurisdiction-specific exercise from the transfer impact assessments used under GDPR. For multinational groups transferring Russian personal data to EU-based processors, this means a separate Russia-law adequacy document is required for each destination jurisdiction — it cannot be derived from GDPR compliance records already held at group level.

Q: What action should foreign companies take in light of this clarification?

A: The immediate priorities are a mapping of all active cross-border data flows from the Russian legal entity, a review of existing Roskomnadzor notification filings to identify gaps where new data categories or recipients have been added without supplementary notification, and an assessment of whether the adequacy documentation held on file for each destination jurisdiction meets the standard confirmed by the Court. For groups using EAEU affiliates as intermediate data processors, a specific legal opinion on whether that routing arrangement remains effective under the clarified interpretation is advisable. Roskomnadzor has the capacity to examine notification records during an inspection, and the absence of current filings is among the items typically reviewed.

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