Russian law requires foreign companies to store personal data on Russian servers. What in-house counsel must do to comply. Make an enquiry.
Unlike the GDPR, which primarily governs how personal data is processed and transferred, Russian data protection law under Federal Law No. 152-FZ imposes an additional structural obligation: personal data of Russian citizens must be initially collected and stored using databases physically located within the Russian Federation. For multinational companies with any touchpoint with Russian users — whether through e-commerce, employment, or service delivery — this data localisation requirement is not a compliance nuance but a baseline condition of lawful operation. Roskomnadzor, Russia's data protection regulator, holds statutory authority to block access to non-compliant services, and has exercised that authority against major international platforms. This guide sets out the compliance pathway in five practical steps for in-house counsel managing a Russian operational footprint.
Before mapping the compliance pathway, it is useful to confirm what you are dealing with. Gather the following:
This assessment shapes every subsequent step and determines whether your exposure is confined to the Russian subsidiary or extends to the foreign parent's systems.
The first step is understanding precisely which data you collect, from whom, and where it currently resides. Under Russian personal data law as currently in force, the localisation obligation applies to personal data of Russian citizens at the point of initial collection — meaning the first recording of that data must occur in a Russian-hosted database.
In practice, this requires a cross-functional data flow mapping exercise. Engage your IT and data architecture teams alongside legal counsel to trace every input point: website registration forms, mobile app sign-up flows, HR onboarding systems, and customer order processes. For each input, identify the primary database location — whether hosted in Russia, within the EU, or on cloud infrastructure with nodes in multiple jurisdictions.
The localisation rule does not prohibit subsequent transfer of data to foreign servers for processing purposes, provided the primary copy remains in Russia. This distinction — initial collection and storage in Russia, with subsequent processing permitted abroad — is material for companies operating hybrid cloud environments. It is also the source of much practical confusion, and a point on which regulatory guidance has developed over time.
For in-house counsel assessing the scope of your company's data localisation exposure in Russia, an initial review of your data architecture against the current regulatory framework is the recommended starting point — make an enquiry: info@vetrovpartners.com |
Any entity that processes personal data of Russian citizens in the course of its activities is, under Russian personal data law, classified as a personal data operator. Foreign companies operating in Russia — whether through a subsidiary, a branch, or direct digital service delivery — are not exempt from this classification.
Notification of Roskomnadzor is the formal mechanism by which an operator enters the register of personal data processors. The notification is submitted electronically through the regulator's portal and must specify, among other things: the categories of personal data processed, the purposes of processing, the legal basis, the location of the databases, and the measures taken to ensure security. For foreign entities processing data through a Russian subsidiary, the subsidiary is typically the registered operator.
There are limited exemption categories under Russian personal data law — notably for processing carried out under an employment contract, or processing necessary to fulfil a direct contractual obligation with the data subject — but these exemptions do not remove the localisation requirement. They affect only the notification obligation. In-house counsel should not conflate the notification exemption with any broader exclusion from the localisation rules.
Practical note: the Roskomnadzor portal is available in Russian only. Legal counsel with Russian-language capability is required to complete the notification without error.
Once the operator's obligations are mapped and notification is either completed or its applicability confirmed, the operational step of database localisation must be addressed. This means ensuring that the primary database storing Russian personal data is physically hosted on servers located in Russia.
The Russian cloud infrastructure market includes a number of major providers — including Russian subsidiaries of international cloud vendors and domestic providers — capable of hosting compliant infrastructure. The practical options vary by company size and architecture: greenfield deployment of a dedicated Russian instance, replication of an existing database to a Russian node (with the Russian copy designated as primary), or migration to a Russian cloud provider entirely.
Note: Roskomnadzor's enforcement powers include the authority to require operators to restrict access to data from outside Russia and, in cases of persistent non-compliance, to block the service at ISP level. Foreign companies providing digital services to Russian users should treat the blocking risk as a credible operational consequence, not a theoretical one. Enforcement has been applied to large international platforms and is not confined to smaller operators.
For companies operating in regulated sectors — financial services, healthcare, telecommunications — additional sector-specific data requirements may apply alongside the general 152-FZ framework. These overlay requirements are administered by the relevant sector regulator (the Central Bank of Russia for financial data, for example) and must be identified separately. The firm's Regulatory & Licensing practice can assist in mapping sector-specific obligations.
The Russian framework on cross-border personal data transfers is distinct from the localisation rule and operates in parallel with it. An operator wishing to transfer personal data to a foreign recipient — whether a parent company, a data processor, or a service provider — must satisfy a separate set of requirements under Russian personal data law as currently in force.
Prior to initiating a cross-border transfer, the operator must conduct an assessment of whether the recipient country ensures adequate protection of personal data. Roskomnadzor maintains a list of countries recognised as providing adequate protection. For transfers to countries not on that list — including most commercially significant jurisdictions for multinational groups — the operator must obtain the data subject's specific consent or rely on one of the limited statutory bases, and must notify Roskomnadzor before the first transfer.
The notification requirement for cross-border transfers was significantly reinforced by amendments that took effect in 2022. In practice, many multinational groups discovered that their existing data processing agreements and standard contractual clauses — designed for GDPR compliance — did not automatically satisfy the Russian notification and documentation requirements. A separate cross-border transfer compliance review is therefore warranted for any company that has not revisited its Russian data transfer arrangements since those amendments.
For companies that have recently restructured their corporate or operational arrangements in Russia, the Supreme Court's clarification on data localisation obligations provides useful judicial framing on how the localisation and transfer requirements interact.
If your company's cross-border data transfer arrangements have not been reviewed under the current Russian regulatory framework, this represents a discrete and addressable compliance gap — make an enquiry: info@vetrovpartners.com |
Data localisation compliance is not a one-time project. Roskomnadzor retains inspection and audit powers, and the regulatory framework has been subject to iterative amendment. Sustained compliance requires institutional mechanisms rather than periodic ad hoc reviews.
At a minimum, an ongoing compliance programme for Russian personal data law should include: annual review of the Roskomnadzor notification to confirm it remains accurate (changes to data categories, processing purposes, or database locations require updated notification); a documented procedure for responding to Roskomnadzor requests and inspections; a data subject rights handling process in Russian (requests for access, correction, and deletion); and a personal data breach notification procedure, since Russian law imposes specific breach notification obligations on operators.
In-house counsel managing a Russian subsidiary should also maintain awareness of ongoing legislative developments in this area. Russian data protection regulation has been amended several times since the localisation requirement was first introduced, and further amendments affecting cross-border transfers and operator obligations cannot be excluded. The firm issues regulatory updates across the full scope of Russian regulatory and licensing law when material developments occur.
For companies that have recently handled a data-related regulatory matter in Russia — or are managing open Roskomnadzor correspondence — the firm's matters record illustrates the range of regulatory and compliance mandates we have acted on.
Q: How long does it take to achieve initial compliance with Russian data localisation requirements?
A: The timeline varies considerably depending on the complexity of your existing data architecture. For companies operating a single Russian-facing application with a straightforward database, the technical migration to Russian-hosted infrastructure can be completed in a matter of weeks. For multinational groups with distributed cloud infrastructure and multiple data categories, the full compliance programme — encompassing mapping, infrastructure migration, Roskomnadzor notification, and cross-border transfer documentation — typically extends to several months. Legal steps, including the Roskomnadzor notification and any cross-border transfer notifications, are procedurally straightforward once the data inventory is complete, but require Russian-language drafting and accurate categorisation of data flows to avoid errors that trigger follow-up correspondence from the regulator.
Q: What documents does a foreign company need to process personal data in Russia lawfully?
A: The core documentation set includes: a current and accurate Roskomnadzor notification (or a written record of the applicable exemption basis); a privacy policy in Russian that meets the disclosure requirements under Russian personal data law; consent forms or other documented legal bases for each processing purpose; data processing agreements with any Russian third-party processors; and, for cross-border transfers, either evidence of data subject consent or a Roskomnadzor cross-border transfer notification. Companies operating in regulated sectors will additionally require sector-specific documentation as directed by the relevant regulator. The adequacy of existing documentation — much of it often drafted primarily for GDPR purposes — should be reviewed separately for Russian law compliance, as the two frameworks use different consent and disclosure standards.
Q: What happens if a company fails to localise its data on Russian servers?
A: Non-compliance with the localisation requirement exposes an operator to administrative proceedings initiated by Roskomnadzor, which may result in administrative fines and — in cases of persistent or serious non-compliance — a requirement to restrict or block access to the service for Russian users at ISP level. Blocking has been applied against international platforms in practice and is not purely theoretical. Separate to the blocking risk, operators that fail to notify Roskomnadzor of processing activities or cross-border transfers face administrative liability under the Russian Code of Administrative Offences. In-house counsel should also note that individual officers of a legal entity can, in some circumstances, bear personal administrative liability alongside the corporate entity. Early-stage compliance reduces exposure across all of these dimensions.
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