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

Data localisation obligations for foreign companies in Russia: what in-house counsel need to know

Elena Pavlova · July 2026 · 12 min read

Foreign companies in Russia must localise personal data or face site blocking. A step-by-step compliance guide for in-house counsel. Make an enquiry.

Unlike the GDPR, which regulates the transfer of personal data out of the European Union but imposes no general obligation to keep data within it, Russian law takes an explicitly territorial approach: any personal data collected on Russian data subjects must be stored and initially processed on servers physically located within Russian territory. For foreign companies operating in Russia — whether through a legal entity, a branch, an e-commerce platform serving Russian consumers, or an employee-facing HR system — this obligation is not theoretical. Roskomnadzor, the Federal Service for Supervision of Communications, Information Technology, and Mass Media, enforces localisation requirements by means of access-blocking orders. Understanding what is required, in what sequence, and by what standard is the starting point for any in-house counsel conducting a compliance review of the company's Russian data footprint.

What to prepare before your compliance review

A structured compliance review begins not with technology, but with a mapping exercise. Before any decisions are made about server infrastructure or data processor contracts, in-house counsel should assemble the following:

This inventory is the foundation of the entire compliance exercise. Without it, subsequent steps — selecting a localisation model, drafting a data flow policy, and preparing the mandatory internal records — cannot be completed accurately.

If your Russian data inventory has not been reviewed in the past twelve months, consider requesting a structured compliance assessment. Make an enquiry: info@vetrovpartners.com |

Step 1 — Determine whether the localisation obligation applies to your company

The localisation obligation under Russian data protection legislation applies to any operator that collects personal data of Russian citizens. The law does not distinguish between a Russian legal entity and a foreign company accessing the Russian market. The decisive question is whether the data processing activity is directed at or involves individuals who are in Russia at the time of collection — not whether the company has a registered legal presence in the country.

For most multinational groups, this means the obligation is engaged at multiple points: the Russian subsidiary's HR records, the Russian-language website's contact forms, the customer account database for Russian e-commerce orders, and the employee monitoring or access-control systems operating at Russian facilities.

A common area of uncertainty is whether data collected outside Russia on Russian nationals (for example, in a global HR system populated before the employee was posted to Russia) triggers the localisation requirement once that employee is resident in Russia. The prevailing interpretation — consistent with Roskomnadzor's published guidance — is that once data relating to a Russian-based individual is processed, it falls within the scope of the requirement, regardless of where it was originally collected.

Two categories of processing are worth distinguishing at this stage: processing of data relating to Russian-based employees (almost always in scope) and processing of data relating to Russian customers or website users (in scope where any data is collected or retained, even for analytics purposes).

Step 2 — Select a localisation model that fits your group structure

Once scope is confirmed, the practical question is which technical and organisational model will satisfy the requirement. Russian legislation does not mandate any specific technical architecture. What is required is that the initial collection and primary storage of personal data takes place within Russia. Subsequent transfer of data to servers outside Russia is not categorically prohibited — but the Russian database must be the primary and current record.

There are three models commonly used by foreign groups:

Dedicated Russian server infrastructure — either owned hardware located in a Russian data centre, or a contract with a Russian cloud or hosting provider. This is the most straightforward approach from a regulatory standpoint and is typically adopted by companies with large Russian user bases or significant Russian operations.Russian instance of a global cloud platform — several major cloud providers operate Russian-based nodes or availability zones. This model preserves the group's existing cloud architecture while satisfying the territorial requirement, provided the Russian instance is the primary record and the contractual arrangements clearly designate it as such.Hybrid model with a Russian master record — the company maintains a Russian-hosted master database for personal data of Russian subjects, with selective synchronisation to a global system for specific functions (for example, group-level payroll processing or consolidated HR reporting) on a documented, legally reviewed basis.

Each model has distinct implications for data governance, access controls, incident response procedures, and the scope of intra-group data transfer agreements. The choice should be driven by an assessment of the company's data flows, not purely by IT cost. In-house counsel should request a written technical and legal assessment before committing to a particular model, since changing architecture after the fact is operationally disruptive.

Step 3 — Update records, notices, and processor agreements

Selecting a localisation model does not complete the compliance exercise. Russian data protection law requires operators to maintain written records of their processing activities, to notify Roskomnadzor prior to commencing processing in certain circumstances, and to ensure that any third-party data processors operating on the company's behalf comply with the same localisation requirements.

The key documentation steps are:

Foreign companies should note that Russian data protection law was materially amended in 2022 and again in 2023, introducing significantly higher administrative penalties for certain categories of violation. In-house counsel reviewing compliance frameworks established prior to those amendments should treat any pre-2022 documentation as presumptively out of date.

For in-house counsel reviewing processor agreements and Roskomnadzor notification status, our data protection practice can assist with a targeted documentation review. Make an enquiry: info@vetrovpartners.com |

Step 4 — Address cross-border data transfers within the group

One of the most practically complex aspects of Russian data localisation compliance for multinational groups is managing ongoing cross-border data transfers. As noted above, having a Russian-hosted primary record does not prohibit all transfers of that data to foreign systems — but it does require that those transfers are properly structured and documented.

Russian data protection law distinguishes between transfers to countries that provide an "adequate" level of data protection (a list maintained and periodically updated by Roskomnadzor) and transfers to all other countries. Transfers to adequate-protection jurisdictions may proceed on a relatively straightforward basis. Transfers to countries not on the adequate-protection list — which includes the United States, and many other common destinations for multinational data flows — require either the data subject's explicit written consent or the conclusion of a specific contractual arrangement reviewed by Roskomnadzor.

For most multinational HR systems, consent is not a workable basis for intra-group transfers: consent must be freely given, and employee consent obtained as a condition of employment does not meet that standard under Russian law. This means that cross-border transfers to non-adequate countries within a corporate group typically require contractual arrangements — and those arrangements must be tailored to Russian requirements, not simply replicated from GDPR standard contractual clauses.

In practice, the firm has acted for foreign groups that assumed their existing GDPR-compliant intra-group transfer mechanisms would satisfy Russian requirements without modification. They do not. Russian regulators assess compliance by reference to Russian law, and a group that can demonstrate GDPR compliance has not thereby demonstrated Russian compliance.

Under Russian data protection enforcement practice, Roskomnadzor's most consequential enforcement tool is the blocking order — an instruction to telecommunications providers to block access to the company's Russian-language website or app. Blocking orders have been issued against major international platforms and can take effect within days of a non-compliance finding. For a foreign company whose Russian revenue is generated online, or whose Russian employees access critical HR or compliance systems via a web interface, a blocking order is not an abstract risk. The regulatory timeline from inspection trigger to blocking decision is shorter than most companies expect — in documented cases, the process has moved from initial inquiry to blocking within a matter of weeks.

Step 5 — Establish an ongoing compliance posture

Russian data protection compliance is not a one-time exercise. Roskomnadzor conducts both scheduled inspections and unscheduled (reactive) inspections triggered by complaints, incidents, or regulatory intelligence. A company that achieved compliance at a point in time but has since changed its CRM vendor, migrated to a new cloud platform, expanded its Russian customer base, or onboarded new data processors may no longer be compliant — without any internal process having flagged the change as a data protection issue.

The practical measures that support an ongoing compliance posture include:

For a broader treatment of the legal and interpretive framework underlying these obligations, our detailed analysis The Law and Practice of Data Localisation Obligations in Russia addresses the legislative history, enforcement record, and current regulatory approach in depth. Both pieces sit within the firm's Data Protection practice resource library.

For in-house counsel seeking a structured review of their company's ongoing Russian data protection compliance framework, our team is available to assist. Make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: How long does it typically take to achieve compliance with the Russian data localisation requirement?

A: The timeline depends heavily on the company's existing infrastructure and data flows. Companies that already use a Russian-based cloud provider and have limited cross-border data transfers can often bring documentation into order within six to eight weeks. Companies migrating data from a global platform to a Russian-hosted instance typically require three to six months, with the bulk of that time spent on technical migration, testing, and updating processor agreements. The documentation work — internal records, privacy notices, and Roskomnadzor notification — can proceed in parallel with the technical migration. In-house counsel should build in additional time if cross-border transfer arrangements with non-adequate countries require renegotiation with third-party vendors.

Q: What documents does our company need to have in place to demonstrate compliance during a Roskomnadzor inspection?

A: Roskomnadzor inspections typically focus on four categories of documentation: the company's record of processing activities (which must record the location of each data store, the legal basis for processing, and retention periods); the privacy notice or notices directed at Russian data subjects; data processor agreements with any third parties handling Russian personal data; and evidence of the technical architecture supporting localisation — typically in the form of a certificate or confirmation from the hosting provider confirming the server location. Companies that rely on a Russian instance of a global cloud platform should obtain explicit written confirmation from the cloud provider that the relevant data is stored exclusively within Russian territory. Verbal or informal assurances from account managers are not sufficient for inspection purposes.

Q: What happens if our company is found non-compliant — and is blocking the only enforcement tool available to Roskomnadzor?

A: Blocking is the most visible enforcement tool, but it is not the only one. Administrative penalties are available for a range of specific violations, including failure to notify Roskomnadzor as a data operator, failure to publish a compliant privacy notice, and non-compliance with a data subject's erasure or rectification request. The 2022–2023 legislative amendments introduced substantially higher penalty thresholds and, for repeat violations involving large-scale data breaches, the possibility of turnover-based fines. Blocking orders are typically reserved for more serious or persistent non-compliance — particularly where a company has failed to respond to a prior Roskomnadzor inquiry or instruction. The practical risk for a foreign company that has made a good-faith attempt at compliance but has documentation gaps is more likely to be administrative penalty and a mandatory remediation period than an immediate blocking order, though this cannot be guaranteed and is subject to Roskomnadzor's discretion in any given case.

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