Russian law restricts cross-border personal data transfers from Russia. Three compliance obligations apply to foreign-owned entities. Make an enquiry.
In advising multinational companies with Russian operations on their data compliance programmes, one issue recurs with notable consistency: the assumption that the data flows configured for GDPR compliance will carry across into Russia without adjustment. They will not. Russian data protection law operates on a distinct statutory basis, with obligations that have no direct equivalent in European frameworks — and the gap between those two regimes has widened materially following amendments to Federal Law No. 152-FZ that took effect in stages since 2022. For in-house counsel managing a Russian subsidiary or a data-processing arrangement that touches Russian residents, understanding the three-part structure of cross-border data transfer restrictions is not an optional supplement to a global data map: it is a prerequisite.
The Russian legal framework for cross-border data transfers is anchored in Federal Law No. 152-FZ "On Personal Data," which governs the processing of personal data of Russian residents by operators — a term that encompasses foreign companies that collect, store, or otherwise process personal data of individuals located in Russia. The law applies regardless of where the data operator is incorporated: a German parent company receiving employee or customer data from its Russian subsidiary is an operator for purposes of 152-FZ if it determines the purposes and means of processing.
The framework distinguishes between two categories of recipient countries for cross-border transfers. The first category comprises states that have ratified the Council of Europe's Convention for the Protection of Individuals with regard to Automatic Processing of Personal Data (Convention 108) and its additional protocol, or that have been assessed by Roskomnadzor — Russia's data protection authority — as providing an adequate level of personal data protection. Transfers to these jurisdictions are subject to a lighter procedure: the operator is required to notify Roskomnadzor before the first transfer, but may proceed without awaiting a response. The second category covers all other states. Transfers to non-assessed countries require not only prior notification but also the execution of a written agreement with the foreign recipient that satisfies specific statutory content requirements, or reliance on one of the enumerated statutory grounds that allow the transfer without an agreement.
This two-track structure is the starting point for any compliance analysis. The practical implication for foreign companies is immediate: a company receiving Russian-origin personal data in a jurisdiction that has not been assessed by Roskomnadzor — and many common processing hubs have not — must have a compliant legal basis in place before the transfer occurs, not after.
Russia's membership of the Commonwealth of Independent States and the Eurasian Economic Union introduces an additional layer of complexity addressed in § IV below.
Before any question of cross-border transfer arises, a foreign company operating in Russia must address the data localisation requirement. Under Russian law, personal data of Russian citizens must be recorded, systematised, accumulated, stored, updated, and retrieved using databases physically located within the territory of the Russian Federation. This obligation applies at the point of initial collection: if a company collects personal data from Russian residents — through a website, an employment form, a customer registration process, or any other means — the first recording of that data must be in a Russian database.
The localisation obligation does not prohibit subsequent cross-border transfer of the same data. It requires, however, that the Russian database serve as the primary record and that the locally stored version remain current. A mirroring arrangement where data is simultaneously written to a foreign server at the point of collection is not compliant: the Russian database must be the originating record. Operators that have maintained a foreign-primary, Russian-mirrored architecture should treat this as a live compliance gap.
The second core obligation is prior notification to Roskomnadzor before any cross-border transfer. The notification must specify the recipient country, the categories of personal data being transferred, the purpose of the transfer, the legal basis, and — for transfers to non-assessed countries — a description of the measures taken to protect the data. Notification is not a one-time filing: each new transfer destination, new category of data, or change in legal basis triggers a fresh notification obligation. The regulator maintains a register of cross-border transfer notifications, and enforcement action has been taken against operators who proceeded with transfers without completing this step.
The third obligation concerns the legal basis for the transfer itself. For transfers to assessed countries, the prior notification is itself sufficient — no separate contractual instrument is required, though consent of the data subject or a statutory exemption may still be needed depending on the processing purpose. For transfers to non-assessed countries, operators must rely on one of the following: a written agreement with the foreign recipient in a form that satisfies 152-FZ requirements; the consent of the data subject to the specific cross-border transfer (a separate and distinct consent from any consent to the underlying processing); or a statutory ground such as the performance of a treaty obligation of the Russian Federation, the protection of the vital interests of the data subject, or the execution of a contract to which the data subject is a party. In practice, the written agreement route is the most commonly used for corporate data flows, but the statutory content requirements for that agreement are detailed and not satisfied by a standard data processing addendum drafted for GDPR purposes.
For in-house counsel assessing whether existing data transfer arrangements with a Russian entity meet the notification and legal basis requirements under 152-FZ — make an enquiry: info@vetrovpartners.com |
The enforcement landscape under 152-FZ has shifted substantially. For several years following the enactment of the localisation obligation, Roskomnadzor's enforcement activity was modest by the standards of European data protection authorities: warnings and administrative fines were issued, but the monetary penalties were low and the reputational consequence limited. That position has changed. The regulator has invested significantly in its technical monitoring capability, and its willingness to impose access restrictions — including blocking of websites and services — on operators found to be in violation has been demonstrated in cases affecting both Russian domestic companies and foreign operators.
For foreign companies, the two enforcement tools of primary concern are: administrative fines for violation of the notification requirement and for transfer without a compliant legal basis, and the threat of restriction of access to the operator's Russian-facing digital services. The latter is a disproportionate remedy in the context of a minor technical violation, but the regulator retains statutory authority to seek it, and the procedural threshold for initiating restriction proceedings is not high.
Under Russian data protection legislation, preferential treatment is not available to foreign operators simply because they are incorporated abroad. The law applies to any operator who processes personal data of Russian residents, regardless of where the operator is registered. This is a point that in-house counsel at European parent companies sometimes underestimate: the Russian subsidiary's compliance failures are attributable to the operator, which may in certain circumstances include the parent.
The practical consequence for legal and compliance teams is that periodic review of the data flow map — specifically the list of transfer destinations, legal bases on file, and notification register entries — should be treated as a standing compliance task, not a project triggered only by regulatory contact. Roskomnadzor does not provide advance warning before initiating an inspection.
Russia's membership of the Eurasian Economic Union — alongside Armenia, Belarus, Kazakhstan, and Kyrgyzstan — and its participation in the Commonwealth of Independent States both introduce treaty-level frameworks that interact with the domestic 152-FZ regime.
Within the EAEU, the member states have committed to harmonising their data protection legislation and have adopted a series of acts directed at enabling data flows within the single economic space. In practice, the degree of harmonisation achieved varies significantly between EAEU members, and the domestic laws of each member state continue to apply to transfers of personal data. A transfer from a Russian entity to a Kazakhstani affiliate is not automatically exempt from the 152-FZ cross-border transfer procedure simply because Kazakhstan is an EAEU member. The Russian operator must still assess whether Kazakhstan appears on the Roskomnadzor adequacy list and complete the applicable notification procedure. What the EAEU framework provides is a political commitment to data flow facilitation that may, over time, translate into bilateral or multilateral instruments reducing the notification burden — but as of the current drafting of this analysis, no blanket EAEU transfer exemption has been enacted under Russian domestic law.
The CIS framework is similarly treaty-based rather than operationally exemptive. Russia's obligations under various CIS instruments in the field of information exchange and data protection do not displace the notification and legal basis requirements of 152-FZ for transfers to CIS states. Several CIS member states are on the Roskomnadzor adequacy list, which means the lighter notification procedure applies; but the obligation to notify prior to the first transfer, and to document the legal basis, remains.
For operators managing data flows across a broader network of jurisdictions — a common situation for multinational companies with operations across the former Soviet space — the practical implication is that each transfer route must be assessed individually against the Roskomnadzor adequacy list and the applicable legal basis, regardless of any regional membership. A blanket "rest of world" treatment is not adequate.
Foreign companies receiving data from Russia into jurisdictions such as the Netherlands, Germany, or the United States — all among the most common inbound transfer destinations from Russian subsidiaries — face two distinct requirements: the Russian export restriction under 152-FZ, and the recipient-country's own import obligations (including, in the case of EU member states, the full GDPR transfer mechanism). The two regimes must both be satisfied; compliance with one does not imply compliance with the other.
Firms advising multinational clients with Russian data processing operations — or in-house teams reviewing their data flow maps for 152-FZ compliance — may benefit from a structured practice review. Request our practice review: info@vetrovpartners.com |
The compliance analysis for a foreign company with a Russian data nexus follows a consistent structure, regardless of the sector or scale of operations.
The first step is to establish whether the company is an operator under 152-FZ. This requires identifying whether the company processes personal data of Russian residents — employees, customers, website visitors, or business contacts located in Russia — and whether it determines the purposes or means of that processing. If the answer is yes, the full framework applies.
The second step is to audit existing data flows against the localisation requirement. Where is the originating database for Russian-resident personal data? Is it located in Russia? Is it the primary record, or a replica of a foreign primary? This audit frequently reveals that cloud-based HR, CRM, or ERP systems used globally by multinationals do not satisfy the Russian localisation requirement out of the box — particularly where the system is contracted by the parent company rather than the Russian subsidiary.
The third step is to map each cross-border transfer against the Roskomnadzor adequacy list and confirm the legal basis in place for each transfer route. This means identifying not only the recipient country but the specific data categories transferred, the processing purpose, and the instrument — notification receipt, data transfer agreement, or statutory ground — on which the transfer rests.
The fourth step is to review the notification register. Has a prior notification been submitted to Roskomnadzor for each active transfer route? Is it current? Does it reflect the actual categories of data and legal basis now in use? Outdated or incomplete notifications are a common source of regulatory exposure.
The fifth step, and one that is often deferred, is to align the 152-FZ documentation with any parallel GDPR or other foreign-law transfer mechanism. Where both regimes apply to the same data flow — as they typically do for transfers from a Russian subsidiary to an EU parent — the company needs documentation that satisfies both. This requires care, because GDPR instruments such as standard contractual clauses are not sufficient on their own to satisfy the 152-FZ written agreement requirement, and vice versa. A bespoke instrument that addresses the content requirements of both regimes is the technically correct solution.
"The assumption that a GDPR-compliant transfer mechanism automatically satisfies 152-FZ is the single most common structural error we see in multinational data programmes touching Russia." — Elena Pavlova, Associate, Vetrov & Partners
Engagement with a Russian-qualified adviser at the audit stage — before a regulatory inquiry rather than after — is materially more cost-effective than remediation under enforcement pressure. The Data Protection practice at Vetrov & Partners advises foreign companies and their Russian subsidiaries on the full lifecycle of 152-FZ compliance, including cross-border transfer documentation, Roskomnadzor notifications, and data flow mapping.
Q: Do cross-border data transfer restrictions under Russian law apply to a foreign parent company receiving HR data from its Russian subsidiary?
A: Yes. A foreign parent company that receives personal data of Russian residents — including its Russian subsidiary's employees — is treated as a personal data operator under Russian law if it determines the purposes or means of that processing. The restriction on cross-border transfers applies regardless of where the operator is incorporated. The parent must ensure a prior notification has been filed with Roskomnadzor and that a compliant legal basis exists for the transfer route before any data is transmitted. Processing personal data through a global HR system contracted by the parent without addressing these requirements is a common source of regulatory exposure.
Q: Is localisation the same as a prohibition on transferring data abroad?
A: No. The localisation requirement and the cross-border transfer restriction are distinct obligations that apply in sequence. Localisation requires that the initial recording and primary storage of Russian-resident personal data occur in a database physically situated in Russia. It does not prohibit subsequent transfer of the same data to a foreign recipient. The cross-border transfer restriction governs that subsequent transfer: it requires prior notification to Roskomnadzor and a compliant legal basis for the specific transfer route. A foreign company must satisfy both obligations independently — localisation compliance does not automatically constitute transfer compliance.
Q: What makes a transfer agreement compliant with 152-FZ, and can a standard GDPR data processing addendum be used?
A: A transfer agreement for the purposes of 152-FZ must contain specific elements prescribed by the law, including identification of the parties, the categories of data, the purposes of the transfer, the obligations of the recipient with respect to data protection, and the conditions under which the recipient may engage sub-processors. A standard GDPR data processing addendum will typically not satisfy these requirements in full: the two instruments address different regulatory concerns and are drafted to different specifications. In practice, a bespoke transfer agreement that addresses both the 152-FZ content requirements and the applicable GDPR transfer mechanism is the technically correct approach for transfers from a Russian entity to an EU recipient. Using only a GDPR instrument leaves the Russian leg of the transfer without a compliant legal basis.
Q: How does membership of the EAEU affect cross-border data transfer obligations for transfers within the union?
A: EAEU membership does not currently create a blanket exemption from the Russian cross-border data transfer procedure for transfers to other EAEU member states. Each transfer from a Russian operator to a recipient in Armenia, Belarus, Kazakhstan, or Kyrgyzstan must be assessed against the Roskomnadzor adequacy list for the recipient country and the applicable notification and legal basis requirements. Several EAEU member states are on the adequacy list, which reduces the procedural burden to prior notification without the need for a bilateral transfer agreement. However, the notification obligation itself remains, and no EAEU instrument has enacted a domestic-law exemption under Russian 152-FZ to date.
Q: What is the practical risk if Roskomnadzor has not been notified of an existing cross-border transfer?
A: An unnotified cross-border transfer is a violation of 152-FZ that Roskomnadzor has authority to pursue through administrative proceedings. The enforcement tools available to the regulator include administrative fines for the operator, formal warnings, and — in more serious cases — an application to restrict access to the operator's Russian-facing digital services. For foreign companies, the administrative fine is a secondary concern compared to the operational disruption that a service restriction can cause. In practice, the most effective response to a discovered notification gap is proactive remediation: filing the notification, documenting the legal basis, and addressing any localisation deficiency before the regulator's attention is drawn to the specific operator. Waiting to address the gap until after an inquiry has been opened significantly narrows the available remediation options.
If your organisation processes personal data of Russian residents and has not completed a structured 152-FZ compliance review — including cross-border transfer notifications and localisation audit — speak to our team: info@vetrovpartners.com | | Vetrov & PartnersVetrov & Partners is a Russian boutique law firm established in 2009. The firm is recognised by Pravo-300 – Russia's principal legal directory – for eight consecutive years, and is listed as a trusted adviser by the German Consulate General in Novosibirsk.
The firm's data protection practice advises foreign companies and their Russian subsidiaries on compliance with Federal Law No. 152-FZ, including personal data localisation, Roskomnadzor notifications, cross-border transfer documentation, and regulatory response. With over 1,000 matters handled since inception, the team combines deep procedural knowledge with direct partner involvement on every engagement. Foreign companies managing the intersection of 152-FZ and GDPR obligations form a core part of the practice's client base.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry