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

Federal law 152-fz personal data requirements in Russia: a comprehensive analysis

Elena Pavlova · May 2026 · 13 min read

Foreign companies processing Russian personal data face strict obligations under Federal Law 152-FZ. What in-house counsel needs to know. Make an enquiry.

In the course of advising foreign companies on their Russian operations, one question recurs with notable regularity: does Russian data protection law actually apply to us if we are incorporated abroad? The answer, under Federal Law 152-FZ on Personal Data, is that the territorial scope of Russian data protection obligations extends well beyond the boundaries of Russian-incorporated entities. For multinational groups with Russian employees, customers, or website users, the compliance framework established by Federal Law 152-FZ creates substantive obligations — including a localisation requirement that many foreign in-house counsel encounter only when a regulatory audit or enforcement action is already under way. Understanding the structure of the Russian legal framework for personal data, and where it diverges from the GDPR baseline that most international compliance programmes are calibrated against, is the starting point for any meaningful Russian data protection compliance review.

Who is subject to Russian personal data law under 152-FZ?

Federal Law 152-FZ applies to operators — a defined category that encompasses any legal entity or individual who determines the purposes and means of personal data processing. In practice, this definition captures foreign companies in several common fact patterns: a foreign parent that processes personal data of employees in a Russian subsidiary; a foreign e-commerce operator whose platform accepts orders from Russian users; and a foreign service provider that processes personal data of Russian counterparties under a commercial agreement. The law does not require the operator to have a place of incorporation or a registered branch in Russia. What matters is whether the processing activity is directed at data subjects in Russia or is performed in connection with Russian operations.

The concept of personal data under Russian law is broad. It encompasses any information that directly or indirectly identifies or permits identification of an individual — covering names, contact details, employee records, customer profiles, and behavioural data. Sensitive categories, such as health data, biometric data, and criminal record information, attract additional processing restrictions and stricter consent requirements.

A foreign company operating in Russia through a subsidiary should not assume that Russian data protection obligations rest solely with the Russian legal entity. Where the foreign parent sets group-level data processing policies, operates the human resources information system, or hosts employee data on infrastructure located outside Russia, Russian regulatory analysis will typically treat the foreign entity as a co-operator with corresponding compliance obligations under the Russian legal framework.

For in-house counsel assessing whether your group's data processing arrangements are within scope of Federal Law 152-FZ, make an enquiry: info@vetrovpartners.com |

What are the core obligations of a personal data operator in Russia?

The foundational obligations under 152-FZ fall into four broad categories: lawful basis for processing, consent management, organisational and technical measures, and notification to the supervisory authority.

Lawful basis for processing mirrors, at a structural level, the GDPR approach — but the Russian framework is narrower in its recognition of legitimate interest as a standalone basis. The principal bases in practice are consent, performance of a contract to which the data subject is a party, and compliance with a legal obligation. Consent under Russian law must be specific, informed, freely given, and capable of withdrawal. For certain categories of processing — electronic marketing, biometric data, publicly available personal data — additional written or electronic consent requirements apply.

Operators are required to adopt internal policies, appoint a responsible person for data protection, and maintain records of processing activities. Where a third party processes personal data on behalf of the operator — the Russian equivalent of a data processor — a written agreement must govern that engagement, specifying the scope, purposes, and security requirements.

Notification to Roskomnadzor, the Federal Service for Supervision of Communications, Information Technology, and Mass Media, is required before the commencement of processing in most cases. Exemptions exist for processing personal data of the operator's own employees and for limited categories of processing that do not involve the transfer of data to third parties. However, the exemption scope has narrowed following amendments to the law over recent years, and the practical recommendation for foreign companies with Russian operations is to assess notification obligations proactively rather than to rely on an assumed exemption.

Does 152-FZ require personal data to be stored on Russian servers?

This question is, in the experience of practitioners advising foreign companies on their Russian legal issues, the most commercially significant aspect of the 152-FZ compliance framework. The localisation requirement, which obliges operators to store and initially process the personal data of Russian citizens using databases physically located in Russian territory, creates a material infrastructure constraint for multinational groups that operate on a centralised or cloud-based model.

The localisation obligation applies at the point of initial collection. An operator who collects personal data from a Russian data subject — whether through a website, an employment agreement, or a customer registration form — must ensure that the data is first recorded, systematised, accumulated, stored, or updated in a database located in Russia. Once that initial processing has occurred in a Russian database, the law permits the data to be transferred to and processed in a database located outside Russia, subject to the cross-border transfer rules discussed in the following section.

Several implementation points are relevant for foreign in-house counsel designing or reviewing a compliance programme. First, the localisation requirement is not satisfied by storing data in a data centre operated by a foreign-incorporated entity if that data centre is not physically located in Russian territory. Second, cloud deployments using hyperscale providers who offer Russian availability zones may satisfy the localisation requirement, but the contractual and technical architecture should be reviewed to confirm that data residency is genuinely achieved and auditable. Third, the localisation requirement applies to the personal data of Russian citizens specifically — not to all data subjects whose data an operator processes in Russia — which creates segmentation obligations in mixed-nationality datasets.

"The localisation obligation is frequently misunderstood as a blanket prohibition on processing Russian personal data abroad. It is more accurately described as a sequencing requirement: the initial processing must occur in Russia, after which cross-border transfer is permissible under the applicable rules." — Elena Pavlova, Associate, Vetrov & Partners

What rules apply to cross-border transfers of personal data from Russia?

Cross-border transfer of personal data from Russia is regulated separately from the localisation requirement, and the two frameworks must be read together. Once the initial localisation obligation has been met, an operator may transfer personal data to a database located outside Russia, but only in accordance with the transfer rules applicable to the destination jurisdiction.

Russian law distinguishes between transfers to countries that Roskomnadzor has determined provide an adequate level of personal data protection — broadly corresponding to Council of Europe Convention 108 member states and certain other jurisdictions on an approved list — and transfers to all other countries. Transfers to adequate countries are permissible subject to notification or without additional formality. Transfers to non-adequate countries, which include the United States and a number of other jurisdictions material to multinational groups, require either the explicit consent of the data subject for each transfer or the conclusion of a personal data transfer agreement in a form compliant with Russian requirements.

Amendments to the Russian legal framework that took effect in 2023 introduced a notification mechanism for cross-border transfers to non-adequate countries: operators are required to notify Roskomnadzor in advance of the first cross-border transfer to a given destination, setting out the purposes, the categories of data, and the legal basis. Roskomnadzor has the power to prohibit a notified transfer if it considers that adequate protection cannot be ensured in the destination country. This procedure is functionally distinct from the EU standard contractual clauses mechanism and requires a tailored compliance approach rather than simple adaptation of GDPR transfer documentation.

For foreign companies holding personal data of Russian employees in group HR systems located outside Russia — a common fact pattern encountered in the firm's advisory practice — both the localisation and cross-border transfer obligations are engaged simultaneously. The compliance solution typically involves establishing a Russian-hosted database as the system of record for Russian employee data, with a documented transfer agreement governing the export of data to the group's global HR platform.

For in-house counsel managing a multinational HR or customer data architecture with Russian data subjects in scope, early-stage legal analysis of your transfer arrangements can significantly reduce regulatory exposure. Make an enquiry: info@vetrovpartners.com |

How does Roskomnadzor enforce 152-FZ against foreign companies?

Roskomnadzor holds a range of enforcement powers under Russian law, and its enforcement posture has become progressively more active over recent years. The principal tools are scheduled and unscheduled inspections, orders to remedy identified violations, administrative proceedings, and — for the most significant breaches — application to a court for the blocking of a website or online service accessible from Russian territory.

Scheduled inspections follow a risk-based planning cycle and are notified to operators in advance. Unscheduled inspections may be triggered by a complaint from a data subject, information received by the regulator from other government bodies, or media coverage of a potential violation. For foreign companies, the most practically significant enforcement risk is the blocking mechanism: Roskomnadzor has the power to apply to an arbitrazh court for an order requiring Russian internet service providers to block access to a foreign operator's online service if that operator is found to be in persistent non-compliance with the localisation requirement.

The commercial consequence of a blocking order — restricted access to a Russian online platform or service for the entire Russian user base — represents a material business risk for foreign companies with significant Russian consumer-facing operations. Foreign in-house counsel who operate on the assumption that a company incorporated outside Russia is beyond the reach of Roskomnadzor enforcement should note that the regulator has demonstrated a willingness to pursue blocking orders against large foreign platforms, creating a precedent that extends, in principle, to any operator whose service is accessible from and directed at Russian users.

Administrative penalties under the Russian administrative offences framework are also available for a range of 152-FZ violations, including failure to notify, failure to provide data subjects with required information, and failure to comply with a Roskomnadzor order. Penalty levels have been increased by successive amendments to the law; while they remain lower in absolute terms than GDPR maximum fines, the combination of financial penalty, reputational impact, and the blocking risk creates a compliance calculus that should not be underweighted.

Under Russian insolvency and corporate law, individual liability for senior management — including foreign executives stationed at or responsible for a Russian subsidiary — can also arise where a systematic failure to comply with personal data obligations results in regulatory action or data subject claims. For groups where the Russian data protection compliance programme sits within a wider global framework managed from headquarters, ensuring that the Russian-specific requirements are adequately addressed at the local level is a governance point that in-house counsel should raise in advance of any regulatory review.

If your organisation has received a Roskomnadzor inquiry, is preparing for a scheduled inspection, or has identified potential gaps in its Russian data protection compliance programme, contact Vetrov & Partners for an initial assessment: info@vetrovpartners.com |

Frequently asked questions

Q: Does Federal Law 152-FZ apply to a foreign company that has no legal entity registered in Russia?

A: Yes, in practice. The Russian legal framework defines an operator by reference to the activity of processing personal data, not by the place of incorporation of the entity performing that activity. A foreign company that collects personal data from Russian users through a website, processes personal data of Russian employees under a group HR arrangement, or handles personal data of Russian counterparties in the course of a commercial relationship will typically be treated as an operator subject to 152-FZ obligations. The absence of a registered branch or subsidiary in Russia does not, in the regulator's approach, remove the foreign entity from the scope of the law. Foreign companies in this position should conduct a scoping analysis to determine which specific obligations are triggered by their particular processing activities.

Q: What is the localisation requirement under 152-FZ and how does it affect cloud-based data infrastructure?

A: The localisation requirement obliges operators to ensure that, at the point of initial collection, the personal data of Russian citizens is recorded and stored in a database physically located in Russian territory. For groups operating on a unified cloud infrastructure, this typically requires establishing a dedicated Russian-resident database as the initial collection point for Russian personal data, before that data can be replicated or transferred to infrastructure located elsewhere. Cloud deployments using providers with Russian availability zones may satisfy the requirement, but the contractual and technical documentation must clearly evidence that data is genuinely stored in Russia at the initial processing stage. A system that routes data first to infrastructure outside Russia and then synchronises to a Russian database does not satisfy the obligation.

Q: Can foreign companies rely on GDPR-standard data processing agreements to meet 152-FZ transfer requirements?

A: Not without adaptation. The Russian cross-border transfer framework operates independently of the GDPR standard contractual clauses mechanism and requires documentation specifically compliant with Russian requirements. Where a transfer is to a non-adequate country, either the explicit consent of each data subject or a compliant Russian personal data transfer agreement is required. In addition, the 2023 notification procedure — under which operators must notify Roskomnadzor before the first transfer to a given non-adequate destination — has no direct equivalent in the GDPR framework. Groups that have implemented a global data transfer programme based on EU standard contractual clauses should treat Russian transfers as requiring a parallel, Russia-specific documentation exercise rather than an extension of the existing EU programme.

Q: What triggers a Roskomnadzor inspection and how much notice is typically given?

A: Scheduled inspections are conducted on a risk-based annual plan published by Roskomnadzor, and operators on the schedule receive advance notice in accordance with the general Russian administrative inspection procedure — typically several weeks. Unscheduled inspections may be initiated without prior notification on the basis of a data subject complaint, information from another government body, or a media report indicating a potential violation. In practice, large consumer-facing operators and companies processing significant volumes of sensitive personal data attract closer regulatory attention. For foreign companies with a Russian online presence, a data subject complaint — which can be filed with Roskomnadzor directly — is a relatively accessible trigger for an unscheduled inspection, making proactive compliance a more reliable risk management approach than reactive remediation.

Q: Are there any exemptions from 152-FZ obligations that foreign companies commonly rely on?

A: Several exemptions are available in principle, but their scope is narrower in practice than in-house counsel sometimes assume. Processing personal data of a company's own employees is exempt from the notification requirement, but the substantive obligations — lawful basis, consent management where required, security measures, data subject rights — continue to apply. Processing for personal or household purposes, journalistic activities, and certain archival or statistical uses attract limited exemptions. The exemptions do not, however, remove the localisation obligation, which applies broadly to any operator collecting personal data of Russian citizens, nor do they affect the cross-border transfer rules. Foreign companies should not structure their Russian compliance programme around an assumed exemption without first confirming through legal analysis that the specific processing activity falls clearly within an established exemption category.

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