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

Regulatory update: data localisation obligations for foreign companies in Russia in the pharmaceuticals sector

Elena Pavlova · January 2026 · 9 min read

Russian data localisation rules apply to pharmaceutical companies handling patient and employee data. What in-house counsel must verify. Make an enquiry.

Following Roskomnadzor's intensified audit programme and the expansion of Russia's data localisation framework under Federal Law No. 152-FZ, foreign pharmaceutical companies operating in Russia face materially elevated compliance obligations in 2026. The intersection of patient data, clinical trial records, pharmacovigilance databases, and standard employment data means that the volume of personal data processed by a pharmaceutical entity is significantly higher than in many other sectors – and the regulatory exposure tracks that volume directly. For in-house counsel managing Russian subsidiaries or local representative offices, understanding precisely which datasets must be localised, and what "localisation" means in operational terms, is no longer a compliance formality.

§ I. What has changed – the before and after of Russia's data localisation framework

Russia's data localisation requirement for foreign companies is not new. The obligation to store the personal data of Russian citizens on servers physically located within Russia has been embedded in Federal Law No. 152-FZ since amendments that took effect in September 2015. What has changed – and what makes the current position materially different from the framework that many foreign compliance teams mapped several years ago – is the combination of three developments that have converged over the 2024–2025 period and into 2026.

First, Roskomnadzor's enforcement posture has shifted from reactive to proactive. Before 2023, the regulator principally investigated complaints. Since then, scheduled and unscheduled audits have become a standard instrument, and the pharmaceuticals sector has been explicitly identified as a priority area given the sensitivity of patient and clinical data. The practical consequence is that a pharmaceutical company that has not been the subject of a complaint may nevertheless find itself subject to an audit.

Second, the administrative fine structure was revised upward in legislation that entered into force in late 2024. The previous penalty ceiling – modest by international standards and widely treated by foreign companies as a manageable cost of non-compliance – no longer applies. Fines are now calibrated by the category of violation and the volume of data affected, and repeat violations attract a separate penalty tier. For a pharmaceutical entity processing pharmacovigilance data on tens of thousands of patients, the exposure is not trivial.

Third, the legal basis for blocking a company's Russian-facing digital services was clarified. Roskomnadzor retains the authority to restrict access to the online services of a non-compliant operator. For a pharmaceutical company that processes physician queries, patient-facing applications, or clinical portal data through centralised group infrastructure hosted outside Russia, the blocking risk is real and operationally disruptive in a way that the earlier framework did not make credible.

"

"What foreign pharmaceutical companies most frequently underestimate is not the localisation rule itself – it is the point at which the obligation attaches: initial recording, not subsequent transfer."— Elena Pavlova, Associate, Vetrov & Partners

" — Elena Pavlova, Associate, Vetrov & Partners

§ II. Which pharmaceutical companies and datasets are affected?

The localisation obligation under Russian law applies to operators that collect, record, systematise, or otherwise process the personal data of Russian citizens. For a foreign pharmaceutical company, this covers a wide range of operational activity.

Patient and clinical data is the category with the highest regulatory sensitivity. Pharmaceutical companies conducting or sponsoring clinical trials in Russia process the personal data of trial participants – including medical history, treatment outcomes, and adverse event records. This data is personal data within the meaning of Russian law. To the extent it is recorded, stored, or systematically processed as part of a trial database managed outside Russia, a localisation question arises. Pharmacovigilance databases that aggregate adverse drug reaction reports from Russian patients are in the same position.

Employee data is often underestimated. Every foreign pharmaceutical company with a Russian subsidiary or representative office processes the personal data of its Russian employees – name, address, tax identification, bank details, payroll records, performance data. This data must be stored on Russian-territory servers on first recording. HR systems hosted on group infrastructure outside Russia frequently create a structural non-compliance at the moment of onboarding, not as a result of any deliberate policy decision.

Healthcare professional (HCP) data occupies a distinct position. Pharmaceutical companies maintain records of the medical professionals they engage – for detailing visits, medical education programmes, speaker arrangements, and transparency reporting. These records are personal data. The extent to which such data must be localised depends on the scope of processing, but companies that maintain comprehensive CRM platforms for HCP engagement outside Russia should not assume they fall outside the framework.

The data categories that are expressly excluded from the localisation obligation – or where the obligation is modulated – include data processed for journalistic, scientific, or statistical purposes under specific conditions, and certain categories of data subject to sector-specific rules under financial and tax legislation. Pharmaceutical companies do not typically benefit from these carve-outs for their core processing activities.

The question of whether a foreign company that has no legal entity in Russia but processes Russian citizen data through a website, application, or remote service is subject to the localisation obligation has been addressed by the regulator. The position taken is that the obligation follows the data subject, not the organisational structure of the operator. A foreign pharmaceutical company with no Russian registration that runs a patient portal accessed by Russian users is, on the prevailing regulatory reading, an operator within the meaning of Russian law.

For in-house counsel reviewing the data compliance position of a Russian subsidiary or affiliated entity, the current regulatory environment makes a structured audit a matter of operational priority – not a precautionary exercise. Make an enquiry: info@vetrovpartners.com |

§ III. What foreign pharmaceutical companies should do now

The practical implication of the current framework is that in-house counsel should treat a data localisation review as a structured, time-bound exercise with defined outputs – not as a general compliance aspiration.

The first step is to map the actual data flows. Many pharmaceutical companies have a formal record of processing activities that was constructed at the time GDPR implementation required documentation of cross-border transfers. That map is a useful starting point but is rarely sufficient for Russian law purposes, because the localisation obligation applies on first recording and requires Russian-territory storage as a precondition to any subsequent transfer, not merely as a restriction on ongoing transfer. The distinction matters operationally: a group HR system that collects Russian employee data at onboarding and replicates it to a Russian-hosted mirror database after the fact may not satisfy the requirement if the initial recording occurs on non-Russian infrastructure.

The second step is to assess the Russian hosting position. Compliance with the localisation obligation requires that the initial recording and primary storage of Russian citizen personal data takes place on servers physically located within Russia. This can be achieved through a Russian data centre arrangement (a number of international co-location providers operate Russian-based facilities) or through a local database instance maintained by a Russian group entity. Either approach requires technical implementation and ongoing governance.

The third step is to review cross-border transfer arrangements in light of the localisation baseline. Russian law permits the cross-border transfer of personal data that has been lawfully localised, subject to conditions that include confirmation that the destination country provides an adequate level of protection or that specific consent or contractual grounds apply. Pharmaceutical companies that transfer Russian patient or HCP data to a global pharmacovigilance system or a group regulatory affairs platform should verify that the transfer is structured on a sound legal basis under Russian law, separately from any GDPR transfer mechanism already in place.

The fourth step – and one that companies with a history of non-compliance should approach with care – is to consider whether voluntary engagement with Roskomnadzor is appropriate. The regulator has a formal notification and compliance process, and voluntary disclosure of a remediation plan has, in practice, affected the manner in which enforcement proceedings have been approached. This is a matter where legal advice specific to the company's position is essential before any communication with the regulator is initiated.

For companies that are part of a larger group with a global data governance framework, the challenge is frequently one of internal coordination: the Russian compliance position must be squared with GDPR obligations, transfer impact assessments, and group security policies that may not have been designed with the Russian localisation baseline in mind. The data protection practice at Vetrov & Partners advises on this intersection as a standalone mandate.

If your organisation processes Russian citizen personal data through pharmaceutical operations, clinical trials, or HCP engagement programmes, a targeted review of your Russian localisation position is advisable before Roskomnadzor's audit cycle reaches your sector. Make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What specifically changed about Russia's data localisation rules that affects pharmaceutical companies in 2026?

A: The core obligation – that personal data of Russian citizens must be initially recorded and stored on servers physically located in Russia – has not changed. What changed in the 2024–2025 period is the enforcement architecture around that obligation. Administrative penalties were revised upward and structured by violation category and volume of data affected. Roskomnadzor shifted to proactive scheduled audits in priority sectors, of which pharmaceuticals is one. The blocking authority for non-compliant digital services was clarified in a manner that makes it operationally credible. Taken together, these changes mean that a pharmaceutical company which mapped its Russian data compliance position several years ago, and treated it as low-priority since then, should not assume its position is still adequate.

Q: Which foreign pharmaceutical companies are most directly affected by the current Russian data localisation obligations?

A: Any foreign pharmaceutical company that processes the personal data of Russian citizens is potentially within scope – regardless of whether it has a legal entity in Russia. This includes companies with Russian subsidiaries or representative offices (which are subject to the obligation across all categories of personal data they process: patient, employee, HCP), companies sponsoring or conducting clinical trials with Russian participants, companies running pharmacovigilance databases that include Russian adverse event reports, and companies operating patient-facing or HCP-facing digital platforms accessible in Russia. The absence of a Russian legal entity does not exclude a company from the framework on the prevailing regulatory interpretation.

Q: What should in-house counsel do now to assess and address the Russian data localisation position?

A: The practical starting point is a data flow mapping exercise that identifies every category of Russian citizen personal data the organisation processes and where the initial recording and primary storage of that data occurs. This should then be tested against the Russian-territory hosting requirement and the cross-border transfer conditions under Russian law. For companies that identify gaps, the remediation path typically involves either establishing a Russian-hosted database instance or migrating the relevant processing to a Russian co-location arrangement. Companies with a compliance gap should take legal advice before any engagement with Roskomnadzor. The firm's data localisation practice briefing sets out the general framework; the law and practice note addresses the legal analysis in greater depth.

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