Roskomnadzor issued new guidance on data localisation for foreign companies in Russia. What in-house counsel needs to review. Make an enquiry.
Following Roskomnadzor's publication of updated interpretive guidance on data localisation obligations, the compliance position for foreign companies operating in Russia has shifted in ways that in-house counsel should not treat as incremental. The guidance addresses directly the conditions under which a foreign entity's processing activities trigger the Russian personal data localisation requirement under Federal Law No. 152-FZ, clarifying both the threshold for applicability and the expectations on record-keeping and audit-readiness. For multinationals with Russian operations, joint ventures, or digital services directed at Russian users, the practical implications are immediate.
Russia's data localisation framework has been in place since 2015, when the requirement to store the personal data of Russian citizens on servers physically located in Russia first entered into force. What the regulatory guidance addresses is the interpretive gap that has persisted since then: precisely when a foreign company — one incorporated outside Russia, without a registered legal entity in Russia, or operating through a distributor or agent — falls within the scope of that obligation.
Before this guidance, the prevailing approach among compliance teams was to apply a targeting test: if a company's website, application, or service was clearly directed at Russian users — through Russian-language content, rouble pricing, or Russian-domain presence — localisation was assumed to be required. Companies operating in a grey zone, such as those accepting Russian users incidentally rather than by design, could reasonably argue that the obligation did not apply. That interpretive space has narrowed.
The guidance establishes that Roskomnadzor will apply a functional targeting analysis rather than a formal-establishment test. The regulator's position, as expressed in the guidance, is that the mere fact of collecting, recording, or systematically processing personal data of individuals located in Russia — regardless of where the data controller is incorporated or where its primary servers are located — is sufficient to bring the entity within scope. The emphasis is on the data subject's location at the time of collection, not on any formal nexus between the controller and Russian territory.
The guidance also addresses transfers. The longstanding position that a separate consent-based transfer mechanism operates independently of the localisation obligation is confirmed, but the guidance clarifies that consent alone does not discharge the localisation duty: the initial copy of the data must still be stored in Russia before any cross-border transfer takes place. This "copy first, transfer later" principle is not new in the text of the law, but enforcement practice has historically been inconsistent. The guidance signals a more systematic approach.
"The regulator's articulation of a functional targeting test, rather than a formal-establishment threshold, is the development that changes the compliance calculus for foreign companies most significantly. The question is no longer whether you have a Russian entity, but whether Russian users are in your data set." — Elena Pavlova, Associate, Vetrov & Partners
The guidance has direct relevance for three categories of foreign company, each of which will need to reassess its compliance position with reference to the specific framing Roskomnadzor has now adopted.
The first category is multinationals with a registered Russian subsidiary or branch. These entities have always been within scope, but the guidance clarifies that the subsidiary's localisation obligations extend to data processed by the parent on behalf of or in connection with Russian-facing operations. A parent company processing employee data, customer data, or user data that originates from Russian territory is now on explicit notice that the localisation obligation follows the data, not the corporate structure.
The second category is foreign companies without a Russian legal presence that nonetheless process Russian user data — e-commerce platforms, SaaS providers, media services, and financial technology companies among them. For these entities, the guidance is the most consequential. The functional targeting analysis described above means that user-facing criteria such as language, currency, and regional availability settings will be treated as evidence of deliberate targeting. Companies in this category that have not yet established a Russian data storage arrangement face material exposure.
The third category — and the one most likely to have underestimated its exposure — is companies operating through distributors, franchisees, or commercial agents in Russia where the foreign principal retains control over personal data collected in the course of the Russian operation. Where a foreign brand collects customer data through a Russian point of sale, the guidance signals that the foreign entity, as the effective data controller, carries the localisation obligation regardless of the contractual intermediary.
For in-house counsel managing a Russian subsidiary or reviewing the firm's cross-border data architecture, the regulatory timeline does not create a transitional grace period. The guidance takes effect as interpretive policy immediately — non-compliant companies should treat audit and remediation as a current-quarter priority rather than a scheduled review.
If your company processes personal data of individuals in Russia, regardless of whether you have a Russian legal entity, make an enquiry: info@vetrovpartners.com |
The immediate practical priority is a data-flow mapping exercise scoped specifically to Russian-origin personal data. For many multinationals, existing data maps have been built to satisfy GDPR or equivalent obligations and do not distinguish Russian-origin data as a discrete category. That distinction now matters. The mapping exercise should identify: (a) what categories of personal data are collected from individuals located in Russia; (b) where that data is currently stored and processed; (c) whether a Russian-localised copy exists; and (d) what cross-border transfer mechanisms are currently in use.
The second step is a gap analysis against the localisation standard as clarified by the guidance. In practice, this means reviewing whether current storage infrastructure satisfies the physical-location requirement — cloud deployments require particular attention, since the legal sufficiency of a Russian-region cloud node under a global cloud provider agreement remains a point of ongoing regulatory uncertainty. Companies relying on cloud-based localisation solutions should obtain written confirmation from their cloud provider as to the physical location and contractual treatment of the relevant data.
Third, companies should review their Roskomnadzor registration status. Foreign companies within the scope of Russian data protection law are required to notify Roskomnadzor of their processing activities. The guidance does not alter the notification framework, but it increases the likelihood that non-notifying companies will come to the regulator's attention through complaint or audit. Companies that have not notified should assess whether registration is now appropriate.
Finally, legal counsel should review contractual arrangements with Russian distributors, agents, and franchisees to establish whether the company's position as a data controller is explicitly addressed. Where the foreign company retains effective control over personal data collected through a Russian commercial intermediary, the contract should clearly allocate data protection responsibilities and confirm the localisation arrangement in place.
The firm's Data Protection practice advises foreign companies on compliance with Russian personal data law, including localisation assessments and Roskomnadzor engagement. For a more detailed analysis of the underlying obligation and its scope, see our overview of data localisation obligations for foreign companies and our analytical piece on the law and practice of data localisation.
To discuss your company's data localisation position in Russia — make an enquiry: info@vetrovpartners.com |
Q: What specifically did Roskomnadzor's guidance change about the data localisation obligation?
A: The guidance does not alter the text of the law, which has required localisation of Russian citizens' personal data since 2015. What it changes is the interpretive position on when a foreign company falls within scope. The regulator has adopted a functional targeting test: if a foreign entity collects or processes personal data of individuals located in Russia, the localisation obligation applies regardless of whether that company has a Russian legal entity. The guidance also reaffirms the "copy first, transfer later" principle for cross-border transfers, signalling closer scrutiny of companies that rely on consent mechanisms alone to justify foreign storage.
Q: Which types of foreign company are most immediately affected by this development?
A: Three categories face the most direct impact: multinationals with Russian subsidiaries where the parent processes Russian-origin data centrally; foreign companies without a Russian presence that provide digital services to Russian users; and foreign principals operating through Russian commercial intermediaries who retain control over customer or user data collected in Russia. Companies in the second and third categories are the most likely to have underestimated their exposure prior to this guidance. In-house counsel at these entities should treat an immediate data-flow mapping exercise as the priority action.
Q: What should a company do if it has not yet notified Roskomnadzor of its processing activities in Russia?
A: The first step is to assess whether the company's activities fall within scope, applying the functional targeting analysis the guidance describes. If they do, legal advice should be obtained before taking any voluntary disclosure step, since the timing and framing of a notification can affect the regulator's response. Companies that are within scope and have not notified carry a risk of regulatory scrutiny arising from complaint, audit, or the regulator's own monitoring of digital services accessible in Russia. Early advice is preferable to reactive compliance. Contact info@vetrovpartners.com for an initial assessment.
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