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

Strategic notes on cross-border data transfer restrictions from Russia for cross-border practitioners

Elena Pavlova · March 2026 · 5 min read

Russian law requires pre-transfer Roskomnadzor notification — many foreign operators miss this step. Guidance for in-house counsel. Make an enquiry.

Before a foreign company operator transfers personal data of Russian individuals to a system outside Russia, it must first complete a Roskomnadzor notification procedure — a step that GDPR-trained compliance teams routinely omit, because it has no direct equivalent in European data protection frameworks.

This note sets out the core obligations under Russian personal data legislation applicable to cross-border data transfer, flags the points of most frequent misapplication for in-house counsel managing Russian operations, and identifies the steps that should be addressed before any outbound transfer commences.

What the regime requires

Under Russian personal data legislation, a cross-border transfer — meaning any transmission of personal data to a recipient located outside Russia — is a regulated activity subject to specific preconditions. The framework distinguishes between transfers to countries that Roskomnadzor has recognised as providing adequate data protection and transfers to all other destinations. EU member states are generally included on the adequacy list, but this designation does not eliminate the notification obligation; it affects only the form of the substantive justification required.

The central procedural requirement — introduced by amendments that came into force in September 2022 — is a pre-transfer notification to Roskomnadzor. The operator must submit notification through the Roskomnadzor portal before the first transfer takes place, and must specify: the categories of data subject, the categories of personal data, the purpose of the transfer, the destination country, and information about the recipient. Roskomnadzor may, within approximately ten business days under the standard procedure, prohibit or restrict the proposed transfer if it is not satisfied that adequate protection exists at the destination.

Three grounds permit transfer to non-adequate countries without the full notification procedure: execution of an international treaty to which Russia is party; protection of life, health, or vital interests of the data subject where consent cannot be obtained; and certain public-interest grounds. In practice, none of these grounds is routinely available to commercial operators transferring employee or customer data to a foreign parent or service provider.

The localisation obligation — requiring that personal data of Russian citizens be initially collected and stored on Russian-based infrastructure — is a distinct and separate requirement. It is not a precondition to cross-border transfer; it operates in parallel. Both obligations must be met independently.

How it applies in practice for foreign company operators

The operator obligation sits with the Russian entity. A foreign parent company that has established a Russian subsidiary, or a foreign entity that directly processes personal data collected from Russian individuals, is subject to these requirements in its capacity as an operator under Russian law. This has a direct compliance consequence that in-house teams sometimes underestimate: the Russian subsidiary cannot discharge its notification obligation simply because the parent has compliant data transfer arrangements under GDPR or another foreign framework.

GDPR standard contractual clauses have no formal legal standing under Russian personal data legislation. They may provide contractual protections between the parties, but they do not substitute for Roskomnadzor notification or satisfy the adequacy analysis under Russian law. In-house counsel who manage Russian operations alongside EU operations should treat these as parallel and independent compliance tracks.

A further practical point concerns the scope of transfers that trigger the notification obligation. Transfers to cloud service providers, IT systems maintenance vendors, HR platforms, and intra-group data exchanges — including those made in the course of ordinary business operations — each qualify as cross-border transfers if the data leaves Russian territory. Many operators have addressed the headline consumer data flows but have not reviewed their infrastructure and vendor arrangements for incidental transfers.

For matters relating to the broader Russian data protection compliance landscape, the firm's Data Protection practice provides a fuller treatment of the applicable framework.

If your organisation has Russian operations involving personal data transfers — make an enquiry: info@vetrovpartners.com |

What to do

In-house counsel conducting a review of cross-border data transfer arrangements for a Russian operation should address the following steps.

Identify all data flows crossing the Russian border. This includes transfers to group entities abroad, SaaS and cloud platforms hosted outside Russia, HR and payroll systems, and professional services providers. The review should extend to infrastructure-level transfers, not only application-layer data flows visible to the legal team.Determine whether a Roskomnadzor notification has been filed for each identified transfer. Where a notification was not filed before the transfer commenced, or where the nature of the transfer has materially changed since filing, the position should be regularised. The Roskomnadzor portal provides the submission mechanism; the substantive content of the notification must reflect the current transfer accurately.Assess the adequacy status of each destination country. For transfers to non-adequate countries, confirm whether a statutory exception applies or whether the transfer requires restructuring. The most frequently used lawful basis for commercial transfers — where no exception applies — is the informed written consent of the data subject, which carries its own requirements for validity under Russian law.Review the localisation position independently. Confirm that initial collection and primary storage of relevant data occurs on Russian territory. Localisation and transfer restrictions are parallel obligations; completing the notification procedure does not satisfy the localisation requirement.Map Russian compliance requirements separately from GDPR or other applicable frameworks. Shared mechanisms — such as standard contractual clauses or binding corporate rules — do not carry cross-jurisdictional effect under Russian law.

For further reading on the judicial and regulatory treatment of these requirements, see Russian Supreme Court clarification on cross-border data transfers and Navigating cross-border data transfer restrictions in Russia.

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