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

A practical guide to Federal Law 152-FZ personal data requirements in Russia for foreign companies

Elena Pavlova · June 2026 · 9 min read

Foreign companies processing personal data in Russia must comply with Federal Law 152-FZ. A step-by-step overview for in-house counsel. Make an enquiry.

In advising foreign companies with Russian operations on their data compliance obligations, one pattern recurs: the assumption that a head-office privacy programme — whether built around the GDPR, CCPA, or another mature framework — automatically satisfies Russian requirements. It does not. Federal Law No. 152-FZ on Personal Data ("152-FZ") is a standalone regime with its own notification procedure, localisation obligations, and enforcement authority. For in-house counsel managing a Russian subsidiary, branch, or representative office, understanding the structure of 152-FZ compliance is a practical priority, not a theoretical one.

This guide sets out the five core steps a foreign company must work through to achieve and maintain compliance with 152-FZ. It does not replace tailored legal advice but provides a structured starting point for counsel assessing their organisation's position.

What to prepare before you begin

Before any formal steps are taken, the following materials are needed:

This inventory drives every subsequent step. Gaps at this stage typically produce compliance gaps downstream.

Step 1. Determine whether 152-FZ applies to your organisation

152-FZ applies to any legal entity that processes personal data of individuals who are physically present in Russia at the time of collection — regardless of where the entity itself is incorporated or headquartered. A foreign company operating in Russia through a subsidiary, branch, or representative office will, in practice, fall within scope.

The scope question is not always straightforward for foreign companies that process data remotely — for example, a parent company receiving employee data from a Russian subsidiary, or a foreign platform collecting data from Russian users. The prevailing interpretation of Russian data protection law is that any such processing triggers 152-FZ obligations. Counsel should not assume that routing data through a non-Russian entity removes the obligation.

For companies that do fall within scope, the threshold question is then what category of data is being processed. 152-FZ distinguishes between general personal data, special categories (health, biometric, political, religious — which attract heavier requirements), and publicly available data. The categories processed by your Russian entity determine which compliance steps apply in full and which may be modified.

If you are assessing whether 152-FZ applies to your Russian operation, make an enquiry: info@vetrovpartners.com |

Step 2. Register as a personal data operator with Roskomnadzor

Any entity that processes personal data in Russia — referred to under 152-FZ as a "personal data operator" — is generally required to notify the Federal Service for Supervision of Communications, Information Technology and Mass Media (Roskomnadzor) and be entered on the official register of personal data operators.

Notification is made electronically through the Roskomnadzor portal. The notification form requires disclosure of: the purposes of processing, the legal basis relied upon, the categories of data subjects, the categories of personal data processed, the retention period, and whether data is transferred outside Russia. There is no filing fee.

Certain exemptions from notification exist — for example, where personal data is processed solely under an employment contract with the data subject, or for purposes of national security — but these exemptions are narrower than many foreign companies assume. Counsel should verify whether an exemption genuinely applies rather than relying on a general impression that notification is unnecessary.

Once entered on the register, the entry must be kept current. Any material change in processing activities — new purposes, new categories of data, new cross-border transfers — requires an updated notification. This is an ongoing obligation, not a one-time filing.

Step 3. Implement data localisation — where does the data physically sit?

The localisation requirement is the provision of 152-FZ that most frequently surprises foreign companies. Under Russian data protection law, when collecting personal data of Russian citizens, a personal data operator is required to ensure that the initial recording, systematisation, accumulation, storage, updating, and retrieval of such data takes place using databases located in Russia.

This does not prohibit all cross-border processing or transfer of personal data. Once data has been recorded in a Russian database, subsequent processing may involve servers abroad, subject to applicable transfer rules. However, the initial capture and primary storage must be in Russia. Using a global CRM, HR system, or cloud platform that stores data outside Russia may not satisfy this requirement unless the relevant Russian-citizen data is first written to a Russian-hosted instance.

In practice, localisation compliance requires companies to audit their technology stack and, where necessary, reconfigure or supplement it with Russian-hosted solutions. For multinational companies operating integrated global platforms, this is often the most operationally significant aspect of 152-FZ compliance.

Note: Roskomnadzor has the authority to order the blocking of websites and digital services found to be in violation of the localisation requirement. Several foreign platforms have been subject to blocking orders for non-compliance. For in-house counsel managing a Russian subsidiary, the risk that a non-compliant technology configuration could result in service disruption is a concrete operational concern — not a theoretical penalty.

What internal policies and documentation does 152-FZ require?

Beyond registration and localisation, 152-FZ imposes a series of documentation and governance obligations that foreign companies must implement at the level of their Russian entity:

Companies that have invested in GDPR-compliant documentation will find partial overlap, but direct translation of EU documentation into the Russian context is not sufficient. The legal bases are defined differently, the consent formulation differs, and certain Russian-law specifics — including the requirement to notify Roskomnadzor of a data breach within defined timelines — have no direct equivalent in the GDPR.

For in-house counsel managing the documentation requirements across a Russian subsidiary and a head-office compliance programme, request our practice review: info@vetrovpartners.com |

Step 5. Prepare for Roskomnadzor inspections and manage cross-border transfers

Roskomnadzor has the authority to conduct scheduled and unscheduled inspections of personal data operators. Scheduled inspections are typically announced in advance; unscheduled inspections may follow a complaint from a data subject, a media report, or a referral from another government body. In practice, foreign-owned entities are not immune from inspection — and companies that have not completed the steps above are typically more exposed.

During an inspection, Roskomnadzor may request access to the operator's notification records, internal policies, consent documentation, data subject request logs, and technical documentation relating to data storage infrastructure. Companies that cannot produce this documentation in an orderly manner during an inspection face a significantly more difficult regulatory engagement.

Cross-border data transfers require separate attention. 152-FZ permits transfers to countries that the Russian government has assessed as providing adequate protection for personal data — a list that does not align with the EU adequacy list and must be checked separately. For transfers to countries not on the Russian adequacy list, the operator must ensure that the recipient provides adequate protection for data subjects' rights, typically through a contractual instrument. Transfers for the performance of an international treaty to which Russia is party, or for the protection of the vital interests of the data subject, may also be permitted under defined conditions.

The EAEU dimension is relevant for companies operating across multiple Commonwealth of Independent States jurisdictions: while EAEU member states share certain regulatory coordination principles, each jurisdiction — including Russia — maintains its own personal data law. 152-FZ obligations cannot be satisfied by compliance with the law of another EAEU or CIS member state.

If your organisation is preparing for a Roskomnadzor inspection or reviewing its cross-border transfer arrangements, make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: How long does it take to register as a personal data operator with Roskomnadzor?

A: The Roskomnadzor notification process itself is not subject to a statutory processing period in the sense of a waiting time before compliance obligations arise. The notification is made electronically, and the operator's entry on the public register is typically reflected within a short period following submission. However, the substantive compliance work — completing the data inventory, drafting internal policies, configuring data storage to meet localisation requirements — will in most cases take significantly longer. Foreign companies should not treat the notification filing as the end of the compliance process; it is one step within a broader programme.

Q: What documents does a foreign company need to implement Federal Law 152-FZ compliance?

A: The core documentation set includes: a publicly accessible privacy policy; consent forms (where consent is the legal basis); internal data processing regulations; records of data subject requests and responses; technical and organisational security documentation; and the Roskomnadzor notification itself. For companies processing special-category data — health, biometric, or other sensitive categories — additional documentation requirements apply. The documentation must reflect Russian-law requirements; adapted GDPR documentation is not automatically compliant.

Q: What happens if a foreign company fails to meet its obligations under Federal Law 152-FZ?

A: Non-compliance with 152-FZ may result in several consequences. Administrative penalties may be imposed on the operator and, in some cases, on responsible individuals. Roskomnadzor may issue a binding order requiring remediation within a defined period, and failure to comply with such an order is an independent ground for further action. In cases of serious or repeated non-compliance involving localisation breaches, Roskomnadzor may apply to a court for the blocking of the relevant website or digital service. For foreign companies with Russian-facing digital operations, a blocking order has direct operational consequences — making early compliance a more cost-effective course than post-incident remediation.

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