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

GDPR and Russian Federal Law 152-FZ: bridging requirements under data localisation requirements: key developments in 2026

Elena Pavlova · March 2026 · 8 min read

Russia's 2026 data localisation changes widen the compliance gap between 152-FZ and GDPR. What in-house counsel must address now. Make an enquiry.

Amendments to Russia's personal data framework that took effect in the course of 2025 and carry forward into 2026 have materially tightened the localisation obligations that foreign companies with Russian operations must satisfy under Federal Law No. 152-FZ. For in-house counsel managing dual compliance – satisfying both a European data protection authority under the GDPR and Roskomnadzor under Russian law – the gap between the two regimes has widened rather than narrowed. Understanding precisely where the two frameworks diverge, and where a bridging compliance posture remains viable, is now an operational priority rather than an academic exercise.

§ I. What changed – the 2025–2026 amendments to Russian data localisation rules

Russia's data localisation requirements under Federal Law No. 152-FZ have always required that personal data of Russian citizens be stored on servers physically located within Russia when first collected. The amendments that entered into force in the 2025–2026 period have strengthened this obligation in three principal respects.

First, the scope of the notification and registration duties owed to Roskomnadzor has expanded. Foreign companies that collect personal data of Russian individuals – whether through a Russian subsidiary, a local website, or a mobile application accessible from Russian territory – are now subject to more granular pre-processing notification requirements. The previous position, under which many foreign operators treated their Russian subsidiary's registration as sufficient coverage for group-wide data activities touching Russian individuals, has become harder to sustain under the amended framework.

Second, the enforcement posture of Roskomnadzor has shifted. The regulator has moved from a predominantly complaint-driven model to a more proactive inspection regime, with spot checks and scheduled audits now extended to foreign-owned entities operating in Russia. Multinationals that previously operated on the assumption that regulatory scrutiny was concentrated on large Russian platforms are recalibrating their risk assessments accordingly.

Third, administrative penalties for localisation violations have been uplifted under the amended framework. Without citing specific figures – which are subject to ongoing legislative refinement – the general direction is towards penalties proportionate to the scale of data processing activity and the commercial revenue attributable to Russian operations, bringing the Russian approach closer in structure (though not in absolute quantum) to the GDPR's turnover-based penalty model.

For foreign companies in the Eurasian Economic Union (EAEU) sphere, an additional layer of complexity exists: EAEU framework rules on cross-border data transfer within member states operate alongside, and do not displace, domestic Russian localisation obligations. EAEU membership does not exempt a foreign data controller from Russian localisation requirements – a point that occasionally surprises companies with established cross-border transfer arrangements within the Commonwealth of Independent States.

If your organisation is reviewing its data localisation posture in light of the 2025–2026 amendments, make an enquiry: info@vetrovpartners.com |

"The compliance challenge for multinationals is not simply technical – it is structural. GDPR and 152-FZ were designed by legislators with fundamentally different governance philosophies, and bridging them requires deliberate architectural choices, not routine policy updates." — Elena Pavlova, Associate, Vetrov & Partners

§ II. How does Russian law interact with GDPR obligations – and where do the two frameworks conflict?

The GDPR and Federal Law No. 152-FZ share a common surface: both require legal basis for processing, both impose purpose limitation and data minimisation principles, and both grant individuals rights of access and erasure. For a multinational in-house counsel who has built a GDPR-compliant data governance framework, this surface-level alignment can generate a false sense of security.

The divergence emerges at the operational level. Under the GDPR, a lawful transfer of personal data to a third country is possible through a range of mechanisms – adequacy decisions, standard contractual clauses, binding corporate rules, and derogations for specific situations. Russia has not been granted an EU adequacy decision, which means that transfers of personal data from a European entity to Russia must rely on one of these alternative mechanisms, most commonly standard contractual clauses supplemented by a transfer impact assessment.

The Russian side of the equation imposes a sequencing requirement that runs in the opposite direction: data must be localised in Russia first, before any cross-border transfer outward is permissible. The practical consequence is that a multinational operating a centralised EU data centre as its single source of truth – a common architecture among European-headquartered groups – cannot simply route Russian personal data into that environment and then apply GDPR-compliant transfer safeguards. The data must first reside on Russian infrastructure; only then may it be replicated or transferred outward.

This sequencing constraint creates a structural tension with the GDPR accountability principle, under which a data controller is expected to maintain centralised oversight and documentation of its processing activities. Distributed localisation – maintaining separate Russian data stores alongside EU-based systems – increases the risk of data inconsistency, complicates subject access request responses, and requires that data retention schedules be managed in parallel rather than centrally. These are compliance risks that sit squarely within the GDPR's scope, even as they are generated by Russian law obligations.

The EAEU dimension adds a further nuance. Where a multinational routes data through an EAEU-member-state subsidiary – for example, a Kazakhstani or Belarusian entity in the group structure – domestic EAEU transfer rules may permit certain intra-group movements without the same documentation burden. However, such arrangements do not resolve the Russian localisation question for data pertaining to Russian individuals: Russian regulatory expectations follow the data subject's location, not the routing path of the transfer.

§ III. What should foreign companies do now?

For in-house counsel managing Russian data protection compliance alongside a GDPR framework, the 2026 position calls for a structured review across four dimensions.

The first is an inventory of Russian data flows. Organisations should map which personal data sets touching Russian individuals are currently stored, processed, or transferred in ways that engage the 152-FZ localisation requirement. This mapping exercise frequently reveals legacy arrangements – CRM systems, HR platforms, marketing databases – that were configured before the 2025 amendments and have not been revisited.

The second is an assessment of Roskomnadzor registration status. The expanded notification requirements mean that prior registrations completed by a Russian subsidiary may not cover the full scope of current data processing activity, particularly where the parent company or other group entities directly collect Russian personal data through digital channels. Closing this registration gap is a precondition for any meaningful compliance posture.

The third is a review of cross-border transfer mechanisms from the EU side. Where standard contractual clauses or other GDPR mechanisms are in place to authorise transfers to Russia, the underlying transfer impact assessment should be revisited in light of the 2026 enforcement environment. A transfer impact assessment completed in 2022 or 2023 does not reflect the current regulatory landscape on either side.

The fourth – and for many organisations the most operationally demanding – is an architectural decision about data infrastructure. Companies that have deferred the question of Russian-resident data storage on cost grounds are now facing a more acute cost-benefit calculation: the cost of establishing or contracting for Russia-based storage versus the exposure from ongoing non-compliance under the amended penalty framework.

Organisations with EAEU-member-state entities in their group structure should additionally review whether those entities' data handling roles have been correctly documented, and whether any assumed EAEU-level transfer permissions have a defensible basis under current Russian regulatory interpretation.

If your organisation needs a structured review of its 152-FZ and GDPR dual-compliance posture, make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What specifically changed in Russia's data localisation rules in 2025–2026?

A: The principal changes under the amended framework are threefold: a broadening of pre-processing notification duties owed to Roskomnadzor, an extension of the regulator's inspection and enforcement remit to include proactive audits of foreign-owned operators, and an upward revision of administrative penalties for localisation violations. The overall direction of the amendments is to bring a larger proportion of foreign companies' Russian data processing activity within the direct oversight of Russian data protection enforcement, and to make non-compliance more costly in absolute terms. Companies that previously operated under a subsidiary-centric compliance model – relying on a Russian legal entity's registration to cover group-wide data activity – are most directly affected by these changes.

Q: Which foreign companies are most affected by the 2026 changes, and why?

A: The companies most directly affected are those that: collect personal data of Russian individuals through digital channels (websites, mobile applications, e-commerce platforms) operated at a group level rather than through a dedicated Russian subsidiary; centralise data storage in EU or other non-Russian infrastructure; or rely on intra-group transfer arrangements that have not been reviewed since the pre-2025 regulatory environment. European multinationals in the consumer-facing, financial services, and technology sectors are disproportionately represented in this category. Companies with EAEU-member-state entities in their structure should also review whether those arrangements provide any genuine compliance benefit under current Russian regulatory interpretation, as the localisation obligation follows the Russian data subject regardless of routing.

Q: What should foreign companies do as an immediate practical step?

A: The most immediately actionable step is a data flow mapping exercise focused on Russian personal data – identifying which systems collect, store, process, or transfer such data and whether each system satisfies the localisation sequencing requirement. This exercise typically surfaces gaps that cannot be remedied by contractual measures alone and that require infrastructure decisions. It also informs the scope of any Roskomnadzor notification or registration update required. For organisations that have not revisited their 152-FZ compliance posture since 2023, a structured compliance review – covering notification status, transfer mechanisms, and data architecture – is a proportionate and prudent response to the current regulatory environment.

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