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

The law and practice of data localisation obligations for foreign companies in Russia

Elena Pavlova · June 2026 · 15 min read

Foreign companies in Russia face mandatory data localisation obligations under Federal Law 152-FZ. What in-house counsel must address. Make an enquiry.

Following a series of amendments to Russian personal data legislation that came into force in stages between 2022 and 2025, the data localisation obligations imposed on foreign companies operating in Russia have become both more demanding and more actively enforced. For in-house counsel managing a Russian subsidiary, joint venture, or representative office, the central question is no longer whether these obligations apply — they do, categorically, to any operator that collects personal data of Russian citizens — but how to structure compliant data flows, what the regulator actually scrutinises, and what the practical consequences of non-compliance look like in a live enforcement environment.

§ I. What the Russian legal framework requires — and who it covers

The foundational obligation arises under Russian federal legislation governing the processing of personal data. The core rule is straightforward in its formulation and wide in its reach: personal data of Russian citizens must be recorded, systematised, accumulated, stored, adjusted, retrieved, and extracted using databases physically located in the Russian Federation. This is the localisation requirement in its statutory form.

The scope is deliberately broad. "Personal data" under Russian law covers any information that directly or indirectly identifies a natural person — a definition that encompasses employee records, customer databases, website registration data, loyalty programme entries, and, depending on context, certain analytics datasets that contain identifiers. Foreign companies often assume the obligation is confined to customer-facing operations. In practice, Russian data protection law draws no territorial carve-out based on the company's place of incorporation: the decisive factor is whether the company processes data of Russian citizens, not where that company is registered or where its headquarters sit. A German manufacturer whose Russian subsidiary maintains an HR database of its Novosibirsk plant staff is an operator under Russian law and is subject to the full localisation regime.

The legislation distinguishes the primary storage and processing obligation — which must be fulfilled on Russian territory — from the subsequent transfer of that data abroad for purposes such as global HR platforms, group-level analytics, or CRM synchronisation. Cross-border transfers remain permissible under specified conditions, but they are secondary operations: the data must first pass through a Russian database, and any cross-border transfer must comply with a separate layer of requirements governing the export of personal data. Foreign companies frequently misconfigure this hierarchy, treating the cross-border transfer rules as the primary compliance question when the localisation obligation is anterior.

The Data Protection practice at Vetrov & Partners advises multinational clients on mapping their existing data architecture against the localisation requirement, identifying which data streams require structural change and which qualify for available exceptions.

If your Russian subsidiary's data flows have not been reviewed against the current framework, the compliance gap may be wider than your internal assessment suggests — make an enquiry: info@vetrovpartners.com |

§ II. How the localisation obligation is fulfilled in practice

Meeting the localisation requirement in Russia is not a paper exercise: it demands a technical infrastructure decision with legal consequences. An operator must be able to demonstrate, if asked, that the primary database — in the sense of the definitional activities listed above — sits on servers located in the Russian Federation. Cloud storage arrangements need to be examined carefully: data hosted by a foreign cloud provider, even if processed in part by Russian staff, does not satisfy the localisation requirement unless the relevant servers are physically within Russia. Several major cloud providers now offer Russian data-centre options, and the regulator has provided informal guidance on what constitutes adequate localisation in a cloud environment, though that guidance remains non-binding and subject to revision.

From a structural standpoint, the compliant architecture for most foreign companies with significant Russian operations involves a Russian-hosted primary database — whether on-premises, via a colocation arrangement, or through a Russia-based cloud instance — from which data is replicated or synchronised to global systems. The synchronisation itself constitutes a cross-border transfer and must satisfy the additional requirements described in § III. This two-layer design is not merely a technicality: the order of operations matters. A foreign company that stores data initially on group servers and mirrors a subset to a Russian instance has the localisation obligation backwards and is, on the plain reading of the legislation, non-compliant.

The regulator, Roskomnadzor, has developed a supervisory methodology that includes both scheduled inspections and unscheduled audits triggered by complaints. Roskomnadzor maintains a register of violators, and entry onto that register can trigger further consequences including website-blocking orders — a sanction that has been applied to foreign platforms and that can disrupt commercial operations regardless of whether a company's primary business is conducted online. The Ministry of Finance has issued guidance on aspects of data localisation practice relevant to financial services operators — for analysis of that guidance, see Ministry of Finance guidance on data localisation.

Operators are also required to notify Roskomnadzor of their intention to process personal data. Foreign companies frequently overlook this notification requirement, treating localisation as the sole obligation. In practice, notification creates a formal record of the operator's processing activities and is a precondition for lawful processing; absent notification, even a technically compliant infrastructure does not cure the underlying regulatory deficiency.

§ III. The enforcement landscape — what Roskomnadzor actually does

Understanding the regulatory text is one exercise; understanding how Roskomnadzor exercises its supervisory authority is another. The two are related but do not map onto each other neatly, and the gap between them is where most foreign company risk is concentrated.

Roskomnadzor's enforcement activity has increased materially since 2022. The regulator conducts both scheduled inspections — published in advance on the government's unified inspection schedule — and unscheduled audits, which can be initiated on the basis of citizen complaints, referrals from other authorities, or the regulator's own monitoring. Unscheduled audits carry a shorter notice period and are not subject to the same procedural constraints as scheduled inspections. For foreign companies, the practical significance is that a customer complaint — including a complaint of the kind that might be dismissed as low-risk in a Western European context — can serve as the trigger for a full audit of a company's data processing infrastructure.

"What distinguishes the current enforcement environment from the pre-2022 period is not the statutory framework — that has been in place since 2014 — but the regulator's evident willingness to use the tools available to it, including blocking orders, against operators who have treated notification and localisation as administrative formalities."

— Elena Pavlova, Associate, Vetrov & Partners

The sanctions available to Roskomnadzor have been strengthened. Administrative fines have increased significantly, and for certain categories of repeated or aggravated violations, the penalty framework has moved into a range that constitutes a material financial risk for mid-sized operations rather than a cost of doing business. Critically, fines are assessed per violation, and a single audit that identifies multiple localisation failures — different categories of data processed in breach — can generate multiple concurrent penalty assessments. Under Russian data protection legislation, companies that have failed to localise personal data by the time of an audit face the risk of such multiple assessments without any opportunity to cure during the inspection period itself. In-house counsel who have deferred a localisation audit on the assumption that a single fine would be manageable should note that this assumption does not reflect the current enforcement practice.

The website-blocking mechanism operates through a separate but connected channel. Roskomnadzor maintains a registry of websites associated with operators who have been found to be in violation of localisation requirements. Inclusion on the registry results in access restrictions imposed at the telecommunications carrier level — carriers are legally obliged to implement the blocks. For a foreign company whose Russian commercial operations depend on digital channels, this consequence is disproportionate to the administrative fine in practical terms: it can suspend customer-facing services without prior notice and without a court order. For a detailed examination of how these obligations bear on different corporate structures, see Data localisation obligations for foreign companies — a practice briefing.

For in-house counsel managing Russian legal exposure, the regulatory timeline creates a genuine pressure point: a company identified by Roskomnadzor as non-compliant enters a process that moves faster than most internal escalation cycles can accommodate.

If your company has received an inquiry from Roskomnadzor or is preparing for a scheduled inspection — make an enquiry: info@vetrovpartners.com |

What obligations apply to cross-border data transfers from Russia?

Cross-border data transfers — the export of personal data from Russian databases to systems or processors located abroad — constitute a distinct layer of obligation, operating in parallel with the localisation requirement rather than as a substitute for it. An operator that has satisfied the localisation obligation must separately satisfy the cross-border transfer conditions before exporting data to group systems, a global HR platform, or a foreign service provider.

Russian law sets out a hierarchy of permitted bases for cross-border transfers. Transfer to countries recognised by the regulator as providing an adequate level of personal data protection is the most straightforward route. A published list of such countries is maintained by Roskomnadzor, and the list has evolved over time; in-house counsel should verify the current list rather than relying on an assessment made at an earlier stage of a compliance programme. Transfer to countries not on the adequate-protection list is permissible but requires either the consent of the data subject (which must be specific, informed, and documented) or — for B2B data flows — a cross-border transfer permit issued by Roskomnadzor.

The permit mechanism was introduced by amendments that came into force in 2023. The permit application requires the operator to submit information about the recipient, the categories of data being transferred, the purpose of the transfer, and the safeguards in place. Roskomnadzor reviews applications and may impose conditions. The permit is not a one-time administrative formality: if the recipient's circumstances change materially, the operator is expected to notify the regulator, and a permit can in principle be revoked. For foreign companies that route Russian employee or customer data to a group entity in a non-adequate-protection country — a common configuration in global HR and CRM deployments — the permit requirement is typically the most operationally complex element of the compliance programme.

EAEU member states occupy a somewhat differentiated position under Russian domestic law in that cross-border transfers within the EAEU space are treated more permissively in certain respects, reflecting the data-sharing arrangements embedded in the EAEU's internal legal order. However, the localisation obligation itself is not displaced by EAEU membership: even for operators processing data that flows between EAEU member states, the primary Russian database must be localised in Russia if Russian citizens' data is involved. In-house counsel advising companies with operations across multiple EAEU jurisdictions should not assume that EAEU data-sharing provisions substitute for compliance with Russian domestic localisation requirements.

The Regulatory & Licensing practice at the firm advises on the interface between Russian data protection law and sector-specific regulatory requirements — a consideration that arises acutely in financial services, healthcare, and telecommunications.

§ V. What in-house counsel should prioritise now

The compliance posture of most foreign companies with Russian operations can be characterised along a spectrum. At one end are companies that underwent a full localisation review in the 2014–2015 period when the requirement first entered into force and have not revisited their architecture since — a position that is likely non-compliant given the subsequent amendments and the expanded enforcement perimeter. At the other end are companies that have implemented a compliant Russian-hosted primary database, obtained a Roskomnadzor notification registration, and reviewed their cross-border transfer arrangements against the current permit framework. Most foreign companies sit somewhere between these points.

The practical priorities for in-house counsel in early 2027 are as follows.

First, a data mapping exercise that identifies all personal data of Russian citizens processed by the Russian entity — including HR data, customer data, supplier contact data, and any data processed by third-party service providers on the entity's behalf. The scope of what constitutes personal data under Russian law is wider than many in-house teams assume at the outset.

Second, an infrastructure audit to confirm that the primary database for each identified data category is hosted in Russia. For companies using global SaaS platforms for HR or CRM functions, this typically involves engagement with the vendor on Russian data residency options and may require a platform migration or a supplementary Russian-hosted instance.

Third, a review of the Roskomnadzor notification register to confirm that the Russian entity's notification is current, accurate, and reflects the actual scope of its processing activities. Notifications filed several years ago frequently understate current processing activities following organic business growth.

Fourth, an assessment of every cross-border transfer: recipient country, legal basis, documentation, and — where the recipient country is not on the adequate-protection list — whether a permit is in place or needs to be applied for. This assessment should include transfers to group entities, not only to third-party processors.

Fifth, an internal escalation protocol for Roskomnadzor contact: who within the organisation is authorised to respond to regulator inquiries, on what timelines, and with what legal support engaged. The absence of a clear escalation path is itself a risk multiplier, as the initial response to a regulator contact often determines whether an inquiry becomes an audit and whether an audit becomes an enforcement proceeding.

Vetrov & Partners maintains a record of matters handled in this area — including regulatory audit support and cross-border transfer permit applications — accessible via the Matters page.

For a structured review of your Russian subsidiary's data compliance position — make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: Does the data localisation obligation apply to a foreign company that has no legal entity in Russia but collects data from Russian users through a website?

A: Yes. Russian data protection law applies on the basis of the data subjects' citizenship or habitual residence, not the operator's place of incorporation. A foreign company that deliberately targets Russian users — through a Russian-language website, ruble pricing, or delivery to Russian addresses — is treated as an operator subject to Russian law, including the localisation requirement. The absence of a Russian legal entity does not shield the company from regulatory scrutiny, and Roskomnadzor has taken enforcement action against foreign platforms on precisely this basis, including by adding them to the website-blocking registry. Foreign companies in this position typically need to make a commercial decision about whether to serve the Russian market in compliance with localisation requirements or to geofence Russian traffic.

Q: Can a foreign company satisfy the localisation requirement by using a global cloud provider's Russian data-centre option?

A: In principle, yes — provided the servers on which the primary database resides are physically located in the Russian Federation and the contractual and technical arrangements give the Russian entity adequate control over that data. In practice, the analysis is fact-specific. Roskomnadzor has not issued binding guidance on all cloud configurations, and informal guidance is subject to revision. The regulator has historically taken a substantive rather than formalistic approach to localisation — examining where data is actually processed, not merely where it is contractually stated to reside. For companies relying on a cloud provider's Russian-region option, a documented legal and technical analysis of the configuration is advisable before treating localisation as satisfied.

Q: What is the practical timeline for a Roskomnadzor audit, and what happens if violations are found during an inspection?

A: Scheduled inspections are published on the unified government inspection schedule, and the operator typically receives advance notice. Unscheduled audits can be initiated with short notice — sometimes 24 hours — where triggered by a complaint or referral. During an audit, Roskomnadzor inspectors may request documentation of the operator's processing activities, database architecture, notification registration, consent records, and cross-border transfer arrangements. Where violations are identified, the inspector issues an act and may refer the matter for administrative proceedings. The timeline from audit to fine issuance varies, but the administrative process is not lengthy. Companies that use the post-audit period as the first moment to address localisation deficiencies are in a materially worse position than those that entered the audit with documented compliance.

Q: Are there any categories of personal data that are exempt from the localisation requirement?

A: Russian personal data legislation provides limited exemptions, the most significant of which relates to data processed in the context of cross-border treaties to which Russia is a party — primarily relevant for diplomatic and consular functions rather than commercial operators. There are also provisions addressing data processed for transport and ticketing purposes under certain bilateral arrangements. For most foreign companies operating commercially in Russia, these exemptions are not available, and in-house counsel should approach any suggestion that a commercial operation falls within an exemption with considerable caution and obtain specific legal advice before relying on it. The regulator does not look favourably on post-hoc exemption arguments advanced for the first time during an audit.

Q: How does Russian data localisation law interact with GDPR obligations applicable to the same data?

A: The interaction is a live compliance challenge for companies subject to both regimes. Russian law requires primary storage in Russia; GDPR imposes data minimisation, purpose limitation, and transfer restrictions that may constrain what can be sent into Russia in the first place and what can be exported from Russia to non-adequate-protection countries. These obligations are not always reconcilable without structural choices at the system-design level. A common configuration adopted by multinationals involves a Russian database that is technically isolated for localisation purposes, with carefully scoped synchronisation to group systems under documented legal bases satisfying both GDPR Article 46 mechanisms and the Russian cross-border transfer permit requirements. This design requires legal analysis from both sides: Vetrov & Partners handles the Russian law element, and, where GDPR analysis is required, we collaborate with trusted counsel in the relevant EU jurisdiction.

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