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

Russian Supreme Court clarification on data localisation requirements under Russian law

Kristina Kornouhova · January 2026 · 8 min read

Russia's Supreme Court has clarified data localisation obligations for foreign companies. What in-house counsel needs to act on now. Make an enquiry.

Following the Supreme Court of the Russian Federation's clarification on the application of data localisation requirements under Russian law, foreign companies maintaining databases of Russian users now face a more precisely defined compliance framework than at any point since Federal Law No. 152-FZ was amended to introduce mandatory local storage. The clarification, issued in the period leading up to January 2026, resolves several interpretive ambiguities that had persisted across lower-court decisions and Roskomnadzor enforcement practice – including which categories of personal data trigger the localisation obligation, how the requirement interacts with data transferred outside Russia for processing, and what documentation standard regulators expect from foreign entities. For in-house counsel managing a Russian subsidiary or a cross-border data flow touching Russian individuals, this development marks a material shift in the risk calculus that should be revisited now.

What the Supreme Court clarified – and what it changed

The core of the clarification concerns the scope of the localisation obligation under Russian personal data legislation. Prior to this ruling, a division had emerged in lower-court practice: some courts applied the localisation requirement narrowly, limiting it to databases in which a Russian citizen's personal data was first collected and stored; others applied a broader reading that captured any processing activity involving Russian individuals' data, irrespective of where the originating database sat. Roskomnadzor's enforcement actions had tended toward the broader interpretation, creating a gap between what regulated entities understood the law to require and what the regulator was actually pursuing.

The Supreme Court's clarification aligns the judicial position with the regulator's broader reading. Localisation applies where the operator – whether Russian-incorporated or a foreign legal entity directing its activities toward Russian users – collects, records, accumulates, stores, or otherwise processes personal data of Russian citizens in connection with the pursuit of commercial or professional purposes on Russian territory. The clarification also addresses data that is initially collected on a server located in Russia and subsequently transferred abroad for further processing: the existence of a Russian-hosted primary database, updated and maintained to reflect the current data of Russian individuals, satisfies the localisation requirement; a nominal local copy that is not operationally current does not.

For foreign companies, this is the more consequential of the two positions. Structures that relied on a token local instance pointing to a primary database held in the EU, the US, or Asia-Pacific now carry elevated enforcement exposure.

Who is affected, and which structures are now under scrutiny?

The clarification has direct consequences for three categories of foreign entity operating in Russia or directing services toward Russian individuals.

First, e-commerce and digital service providers who collect user data at point of registration or transaction and route that data to a centralised global database. Where the Russian-user dataset is not maintained as an operationally independent and current local copy, the structure sits within the scope of the clarification.

Second, multinational employers with Russian workforce data processed through a group-level HR information system hosted outside Russia. Employee personal data has consistently been treated as falling within the localisation obligation, and the Supreme Court's framing does not create an exception for intra-group flows.

Third, financial services groups and their Russian subsidiaries where client onboarding data – KYC records, identity documents, contact and payment information – flows directly into a global CRM or compliance platform. The clarification confirms that this category of data is within scope regardless of the processing entity's place of incorporation.

For in-house counsel managing a Russian subsidiary facing this compliance profile, the practical window for remediation without active enforcement exposure is narrowing. Roskomnadzor has historically accelerated its audit programme following major judicial clarifications that support its own interpretive position.

If your organisation's data architecture includes cross-border flows involving Russian users, make an enquiry: info@vetrovpartners.com |

What has not changed – and common misconceptions to address

The clarification does not alter several aspects of the framework that practitioners should be careful not to overstate.

The localisation requirement applies to personal data as defined under Russian law – data relating to identified or identifiable natural persons. It does not apply to anonymised or pseudonymised data sets where re-identification is not possible by the operator or third parties acting on its behalf. Aggregated analytics data, behavioural cohort data stripped of direct identifiers, and technical logs not linked to individual users remain outside the localisation requirement on the current regulatory position.

The requirement also does not prohibit cross-border transfer of personal data after the localisation condition has been satisfied. The legislative framework distinguishes between the obligation to store (which must be performed in Russia) and the permission to transfer (which may occur subsequently, subject to the consent and cross-border transfer conditions under Russian personal data law). Companies that have correctly structured their Russian data storage infrastructure retain the ability to route data internationally for processing, provided the primary local database meets the operational currency test the Supreme Court has now articulated.

Finally, the clarification does not retroactively impose liability for past processing conducted under the pre-clarification interpretive uncertainty. Enforcement consequences flow from the position as clarified, not from historical operations. This distinction matters for in-house counsel assessing the scope of any internal compliance review.

What should foreign companies do in light of this clarification?

The practical response to the Supreme Court's position requires attention across three areas.

The first is a data-mapping exercise. In-house counsel should commission or update a current map of all personal data flows involving Russian individuals – specifying the collection point, the primary storage location, the entities with access, and the operational relationship between any local and non-local instances of the same dataset. This exercise is the prerequisite for any accurate compliance assessment; it also constitutes the documentary foundation for responding to a Roskomnadzor enquiry.

The second is an architecture review. Where the data map reveals structures that rely on nominal local copies or on routing arrangements that do not satisfy the operational currency test, remediation typically involves either migrating the primary database to a Russian-hosted infrastructure, restructuring the synchronisation logic so that the Russian instance is the operationally active one, or – for smaller datasets – reconsidering whether the Russian user population is large enough to justify the compliance cost relative to the regulatory risk.

The third is a documentation audit. The Supreme Court's clarification, and Roskomnadzor's enforcement history, both point to the importance of contemporaneous records: written policies reflecting the current localisation architecture, data processing agreements with local hosting providers, and internal records of decisions made about cross-border transfer. Firms that can demonstrate a documented compliance posture consistently applied are substantially better positioned in an audit than those whose practices are correct but unrecorded.

Vetrov & Partners advises foreign companies on data localisation compliance as part of its Regulatory & Licensing practice. For companies that have reviewed their obligations under the earlier framework but have not yet assessed the impact of this clarification, an early review is advisable before Roskomnadzor's next enforcement cycle. Our related analysis of the broader data localisation framework under Russian law is available at Navigating data localisation requirements under Russian law, and our overview of Russian licensing and regulatory structures for foreign companies can be found at Industry licensing requirements in Russia.

To discuss the implications of this clarification for your organisation's Russian operations, make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What specifically changed following the Supreme Court's clarification on data localisation?

A: The Supreme Court aligned the judicial interpretation of Russia's localisation obligation with Roskomnadzor's broader regulatory position. The key clarification is that the localisation requirement captures any operator – including a foreign entity – that collects and processes personal data of Russian individuals in connection with commercial or professional activity on Russian territory, and that a nominal local database copy that is not operationally current does not satisfy the requirement. Structures that relied on a token local instance pointing to a primary database held abroad now carry materially elevated enforcement exposure.

Q: Which categories of foreign company are most directly affected by this clarification?

A: Three categories face the most immediate review obligation: e-commerce and digital service providers routing Russian user data to a centralised international database; multinational employers processing Russian workforce data through a group-level HR system hosted outside Russia; and financial services groups whose Russian subsidiary client data flows into a global CRM or compliance platform. All three are within the scope of the clarification as the Supreme Court has framed it. Companies in regulated sectors – financial services, telecommunications, healthcare – face additional Roskomnadzor attention because their data processing practices are already subject to sector-specific oversight.

Q: What should an in-house counsel do now in response to this development?

A: Three steps are advisable in the near term. First, commission or update a data-mapping exercise covering all personal data flows involving Russian individuals, including the storage location and operational relationship between local and non-local database instances. Second, assess whether the current architecture satisfies the operational currency test articulated by the Supreme Court, and if not, identify the remediation path. Third, review and update internal documentation – policies, processing agreements, and decision records – to reflect the current compliance posture. These steps are best completed before Roskomnadzor initiates the next audit cycle, at which point remediation options narrow significantly.

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