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

Navigating cross-border data transfer restrictions from Russia: a step-by-step overview

Elena Pavlova · September 2026 · 11 min read

Russian law imposes layered restrictions on transferring personal data abroad. Here is how in-house counsel can navigate each step. Make an enquiry.

Unlike the GDPR's relatively streamlined mechanism for cross-border data flows, Russian data protection law imposes a layered and procedurally demanding regime on any operator seeking to transfer personal data of Russian-based individuals outside the country. Under the Russian Federal Law on Personal Data – the statute that governs data processing in Russia and has been substantially amended in the period since 2022 – foreign companies operating in Russia face obligations that go well beyond internal policy alignment. For in-house counsel managing Russian subsidiaries, distributors, or service contracts, understanding the precise sequence of compliance steps is not merely a governance formality: it is the condition for lawful data operations and, increasingly, the subject of regulatory audit.

What to prepare before you begin

Before initiating a cross-border data transfer from Russia, it is worth assembling a working compliance file. The following items are commonly required at multiple points in the process:

Assembling this file early reduces friction at every subsequent step and is the baseline the regulator will expect to see in any inspection.

Step 1 — Determine whether your activity falls within scope

The Russian Federal Law on Personal Data applies to operators who process personal data of individuals in connection with activities carried out in Russia, or who process data collected in Russia regardless of where processing infrastructure is located. For foreign companies, the threshold question is whether any data touching Russian-resident individuals flows through systems the company controls – directly or through a Russian subsidiary, a joint venture partner, or a third-party service provider acting as a processor.

The practical scope is broader than many GCs initially appreciate. A German parent company receiving HR data from its Novosibirsk subsidiary, a Dutch platform collecting Russian consumer data, or a Swiss fund holding KYC information on Russian-resident counterparties will each, on the standard regulatory interpretation, be subject to the cross-border transfer restrictions. The data localisation requirement – the obligation to store and conduct primary processing of Russian-resident personal data on servers located in Russia before any transfer takes place – applies to these operators as a precondition to any lawful outbound transfer.

For foreign companies with Russian operations, the question is rarely whether the law applies; it is whether the current data flows have been structured to comply with it. Mapping those flows in detail is the necessary first action.

For in-house counsel assessing the scope of Russian data protection obligations for a multinational group, an initial review of current data flows against the regulatory framework can identify gaps before they become enforcement points. Make an enquiry: info@vetrovpartners.com |

Step 2 — Identify the applicable legal ground for transfer

Russian law on cross-border data transfers operates through a tiered structure. At the first tier, transfers to countries that Roskomnadzor – Russia's data protection supervisory authority – has determined to provide an adequate level of personal data protection are treated more permissively than transfers to countries on no such list. A regularly updated register of adequate countries is maintained by the regulator; in-house counsel should verify the current status of the recipient country against this register at the time of transfer, not at the time of initial compliance review, since the list can and does change.

Where the recipient country is not on the adequate-protection list, the law provides for alternative grounds. These include the data subject's written consent (obtained specifically for the cross-border transfer, separate from any general consent to processing), the performance of a contract to which the data subject is party, and certain other grounds tied to the protection of life or the fulfilment of statutory obligations. For commercial data transfers within a corporate group – the most frequent scenario for foreign companies – the consent ground and the contractual ground are the most commonly deployed, though each carries its own documentation requirements and practical limitations.

It is important to note that none of these grounds dispenses with the localisation requirement or the prior notification obligation discussed in Step 3. They operate in addition to those requirements, not as substitutes for them. This is the most common structural error in compliance programmes built on GDPR assumptions: conflating a valid transfer ground with overall transfer authorisation.

For a detailed analysis of each transfer ground and the evidentiary standard the regulator applies in practice, see the firm's deep-dive briefing on cross-border data transfer restrictions and the accompanying note on Supreme Court clarifications affecting cross-border transfers.

Does your transfer require prior notification to Roskomnadzor?

In the majority of cases involving transfers to non-adequate countries, the answer is yes. The amendments to the Federal Law on Personal Data introduced a requirement for operators to notify Roskomnadzor of intended cross-border transfers before they commence, providing specified information about the recipient, the categories of data, the purpose, and the legal ground being relied upon. This is not a post-transfer notification: it is a pre-condition, and commencing a transfer without completing it exposes the operator to regulatory sanction.

The notification is submitted through the regulator's official portal and must meet prescribed formal requirements. In practice, Roskomnadzor may respond with a prohibition or a request for additional information within a defined review window; in the absence of a prohibition within that period, the transfer may generally proceed. However, the review window and the regulator's practical response time can vary, and in-house counsel should build a meaningful lead-time buffer into any project timeline that depends on data being transferred abroad.

Note: Commencing a cross-border data transfer without completing the prior notification requirement is an administrative violation under Russian law. Penalties apply per transfer incident and can accumulate where systemic non-compliance is identified in an audit. The regulator has the power to order cessation of processing and to refer matters to law enforcement where the violation is aggravated. Companies that have been transferring data without notification should take legal advice on remediation before the next audit cycle.

The localisation obligation also interacts with this step: Roskomnadzor's portal registration (the operator's notification of data processing activities, separate from the transfer notification) must accurately reflect the data categories being transferred. Where it does not, the operator will need to update its registration prior to submitting the transfer notification, adding a further procedural stage.

For matters governed by foreign law or requiring local admission in another jurisdiction, we collaborate with trusted counsel in the relevant jurisdiction.

Step 4 — Put contractual and technical safeguards in place

Having identified the legal ground and completed the notification procedure, the operator must ensure that appropriate contractual and technical measures govern the actual transfer. On the contractual side, this means a data transfer agreement with the recipient that specifies the purpose of the transfer, the categories of data, the recipient's processing obligations, and the security measures in place. Where the recipient is a group entity, this will typically take the form of an intra-group data transfer agreement; where it is a third-party processor, a data processing agreement satisfying Russian law requirements will be required.

Russian law does not provide a set of standard contractual clauses equivalent to the SCCs under the GDPR. The content requirements for transfer agreements are set out in the legislation, but the drafting is the operator's responsibility, and the regulator's expectations as to adequacy of contractual protection have been elaborated through inspection practice and methodological guidance rather than through prescribed templates. Counsel familiar with the current inspection practice will be better placed to draft agreements that withstand scrutiny than those working from GDPR precedents adapted without Russian-law review.

On the technical side, the key requirement is security of the transferred data appropriate to its category and volume. For special categories of personal data – health data, biometric data, data on political or religious beliefs, and similar – enhanced security requirements apply. Encryption in transit, access controls at the recipient end, and documented security assessments are the standard baseline; for sensitive categories, additional measures may be required and should be documented.

For in-house counsel managing a Russian subsidiary where data flows involve both employee data and customer or user data, it is worth treating each category separately in the compliance file, since the applicable requirements and the regulator's scrutiny level differ materially between them.

For legal teams preparing cross-border data transfer agreements that must satisfy both Russian regulatory requirements and the governance standards of a foreign parent, the firm's data protection practice can provide template review, Russian-law gap analysis, and regulatory correspondence support. Make an enquiry: info@vetrovpartners.com |

What records must you maintain to satisfy a regulatory audit?

Roskomnadzor conducts both scheduled and unscheduled inspections of data operators. For foreign companies with Russian operations, the practical audit risk is concentrated at the subsidiary level, since the subsidiary is the registered operator and the entity that will receive the inspection notice. The inspection will typically examine the processing register, the transfer notification records, the contractual documentation, and the technical security measures. Absence of any of these elements – or their presence in a form that does not match actual data flows – is the most common finding in practice.

The records that operators should maintain and keep current include: the processing register (updated to reflect all active data categories and processing purposes), copies of all transfer notifications submitted to and confirmed by Roskomnadzor, copies of all data transfer agreements with recipients, documentation of the legal ground relied upon for each transfer, evidence of data subject consents where consent is the basis, and records of security assessments and technical measures. For special-category data, additional documentation requirements apply.

The localisation compliance record deserves particular attention: the operator must be able to demonstrate, at the point of inspection, that primary processing and storage of Russian-resident data is occurring on Russian-based infrastructure. In practice, this means contemporaneous evidence – server location records, hosting agreements, infrastructure architecture diagrams – not a retrospective reconstruction. Companies that have recently migrated data infrastructure or changed hosting providers should verify that their localisation documentation reflects the current state, not the prior arrangement.

For foreign companies that have experienced audit-related findings at their Russian subsidiary, the matters section of this website provides anonymised examples of compliance remediation engagements handled by the firm.

Roskomnadzor's inspection practice has become more systematic in recent years, and the expectation that multinational companies will have a fully documented and current compliance programme is now firmly established. In-house counsel who have not reviewed their Russian subsidiary's data protection compliance file within the past 12 months should treat that review as an overdue priority.

Frequently asked questions

Q: How long does the Roskomnadzor notification process typically take?

A: The review window within which Roskomnadzor may issue a prohibition or request additional information is set by the legislation, but in practice the timeline from submission to the point at which a transfer may lawfully commence varies. Operators should budget for a minimum of several weeks in project planning and should not treat the absence of an immediate response as confirmation of approval. Where a notification receives a request for additional information, the timeline extends further. The firm advises clients to initiate the notification process well in advance of any operational deadline that depends on data being transferred.

Q: What documents should foreign companies prepare before initiating a cross-border data transfer from Russia?

A: The baseline document set includes an updated processing register, a transfer notification form with supporting particulars (recipient entity, country, categories of data, legal ground), a draft data transfer agreement with the recipient, evidence of current localisation compliance, and, where consent is the relied-upon transfer ground, executed data subject consents specific to the cross-border transfer. For transfers of special-category data, a security assessment must also be prepared. Assembling this documentation before submitting the notification reduces the risk of a regulatory request for additional information that would delay the transfer.

Q: What happens if a cross-border data transfer takes place without proper authorisation?

A: Conducting a cross-border transfer without completing the required notification procedure and without a valid legal ground is an administrative violation carrying per-incident penalties under Russian administrative law. Where the regulator identifies systemic non-compliance – for instance, sustained data flows abroad without any notification on record – it may order cessation of transfer operations and require the operator to remediate its compliance programme within a specified period. In aggravated circumstances involving sensitive data categories or repeated violations, the matter may be referred to law enforcement. For companies that have identified a historical compliance gap, voluntary remediation before an inspection is materially preferable to remediation under regulatory direction; legal advice on the appropriate remediation approach should be sought promptly.

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