GDPR and Russian Federal Law 152-FZ impose overlapping data localisation duties on foreign companies active in Russia. Expert analysis. Make an enquiry.
Foreign companies active in Russia that process personal data of individuals in the European Union face a dual compliance obligation: they must satisfy both the EU General Data Protection Regulation and Russian Federal Law No. 152-FZ simultaneously. Russian law does not exempt organisations subject to GDPR from its own data localisation requirements, and GDPR does not disapply because a controller also holds obligations under Russian law. The two frameworks operate in parallel, and compliance with one does not discharge obligations under the other.
Under Russian data protection legislation, any operator collecting personal data of Russian citizens is required to ensure that the initial recording, systematisation, accumulation, storage, retrieval, and amendment of such data takes place using databases physically located within the Russian Federation. This obligation applies regardless of where the data controller is incorporated or where its primary processing infrastructure sits. Roskomnadzor, the Russian supervisory authority for personal data, monitors compliance and maintains a register of violators whose websites may be blocked. Subsequent cross-border transfer of the data to infrastructure outside Russia is generally permissible under 152-FZ, provided the primary localisation obligation has first been satisfied and the destination country is assessed as ensuring adequate protection – or the transfer is covered by an authorised ground such as consent or contractual necessity.
GDPR adds a separate layer. Under its territorial scope provisions, GDPR applies to processing by a controller or processor not established in the EU where that processing relates to the offering of goods or services to individuals in the EU, or to the monitoring of their behaviour within the EU. A foreign company operating in Russia that also targets EU-resident individuals must therefore maintain a lawful basis under GDPR, honour data subject rights, and observe GDPR's own rules on international transfers – including standard contractual clauses or adequacy decisions where relevant. Russia does not currently hold an EU adequacy decision.
For in-house counsel managing a Russian subsidiary or cross-border data operation, the practical implication is that a single data flow touching both Russian and EU individuals may require localised Russian storage infrastructure, a documented GDPR lawful basis, and transfer safeguards in both directions. Architecture decisions made at the infrastructure level – where to host the primary database, how to structure data replication – have direct legal consequences under both regimes.
The firm's Data Protection practice advises foreign companies on mapping their data flows against both frameworks and structuring compliant processing arrangements. For a deeper analysis of the current legislative position, see GDPR and Russian Federal Law 152-FZ: Bridging Requirements and the related legislative update.
To discuss your organisation's specific data compliance position under Russian law — make an enquiry: info@vetrovpartners.com |
— Elena Pavlova Associate, Vetrov & Partners vetrovpartners.com/pavlova/
Elena Pavlova advises foreign companies on Russian data protection law (Federal Law No. 152-FZ), regulatory compliance, and distribution arrangements. She assists in due diligence for cross-border transactions and supports the firm's corporate and IP practices.
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