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

Federal law 152-fz personal data requirements in Russia: key developments in 2027

Elena Pavlova · July 2026 · 8 min read

Federal Law 152-FZ was amended materially in 2027, affecting foreign companies with Russian operations. What in-house counsel must review. Make an enquiry.

Amendments to Federal Law No. 152-FZ on Personal Data that took effect in early 2027 have materially altered the compliance obligations of foreign companies operating in Russia. The changes — spanning data localisation, cross-border transfer authorisation, administrative liability, and the scope of operator accountability — represent the most significant recalibration of the Russian personal data framework since the 2022 liability reforms. For in-house counsel managing a Russian subsidiary or a Russian branch of a foreign group, the practical consequences of these amendments are immediate and require structured review.

What changed in the Russian personal data framework in 2027?

The 2027 amendments to Federal Law 152-FZ addressed three areas that had generated the greatest compliance uncertainty for foreign companies: the data localisation requirement, the procedure for authorising cross-border personal data transfers, and the calculation basis for administrative penalties.

On localisation, the amendments clarified — and in practice tightened — the requirement that personal data of Russian citizens be initially collected and stored on servers physically located within the Russian Federation before any transfer abroad. Prior to the amendments, the boundary between initial recording and subsequent processing had been the subject of inconsistent interpretation by Roskomnadzor, the federal supervisory authority for personal data. Under the revised framework, the supervisory authority's position is that the primary database containing Russian citizens' data must be resident in Russia; a mirrored or synchronised foreign copy does not satisfy the requirement. Foreign companies operating shared CRM, HR, or ERP systems across multiple jurisdictions — where the master database is held abroad — face a structural compliance question that was less clearly articulated under the prior rules.

On cross-border transfers, the amendments replaced the earlier notification-based mechanism with a more prescriptive prior-authorisation procedure for transfers to countries that Roskomnadzor has not recognised as providing adequate data protection. Foreign companies transferring data to group entities in such countries are now required to conduct and document a transfer impact assessment, submit it to Roskomnadzor, and obtain a formal acknowledgement before the transfer commences. The implementing guidance on the format and content of these assessments was, as of the date of this article, still in the process of being finalised by the supervisory authority — companies should monitor the Roskomnadzor portal for publication.

On administrative liability, the penalty calculation methodology was revised to move away from fixed-range fines and towards turnover-based penalties for certain categories of violation — notably, repeated breaches of the localisation requirement and failure to notify Roskomnadzor of a data breach within the statutory period. The turnover-based approach mirrors the trajectory of European data protection enforcement and is expected to produce materially larger penalties for foreign companies with significant Russian revenue streams. In-house counsel should note that the liability framework applies to the Russian legal entity — subsidiary or branch — as the registered operator, even where the compliance decision was taken at group level abroad.

Which foreign companies are most directly affected by these changes?

The 2027 amendments do not impose obligations that are uniform across all operators. The practical exposure varies considerably by business model, data category, and the extent to which a company's data infrastructure was already aligned with Russian localisation requirements.

Foreign companies that are most directly affected fall into three broad categories. First, multinational groups that operate centralised data infrastructure — shared HR platforms, single-instance ERP systems, global CRM databases — hosted outside Russia. For these groups, the clarified localisation requirement creates an obligation to either migrate the primary database or restructure the system so that the Russian citizen data set is resident in Russia and independently identifiable as such. This is not a paper exercise; it requires engagement between legal counsel, IT architecture, and the relevant data processor.

Second, companies that transfer personal data to group entities or processors in jurisdictions not on Roskomnadzor's list of adequate countries. Many companies have historically managed this through contractual safeguards and relied on the prior notification mechanism. That mechanism has now been replaced, and the prior-authorisation procedure requires active steps before transfers continue. Foreign companies that have not reviewed their inter-group data flows since the 2027 amendments came into force may already be in non-compliance.

Third, companies in sectors where Roskomnadzor has historically concentrated its supervisory attention — retail, e-commerce, finance, healthcare, and HR technology. The enforcement posture of the supervisory authority has, in recent years, shifted towards proactive inspection rather than complaint-driven review. Foreign companies with a consumer-facing Russian operation should treat the 2027 amendments as a trigger for a structured internal audit, not a deferred compliance project.

For in-house counsel managing these entities, the regulatory timeline does not accommodate extended internal deliberation. Roskomnadzor has indicated that the revised penalty framework is expected to be applied to violations identified from the first half of 2027 onwards — companies that act promptly can document a compliance programme that may be relevant to any supervisory engagement.

If your company holds personal data of Russian citizens or operates data infrastructure in Russia, make an enquiry to discuss a compliance review: info@vetrovpartners.com |

What should foreign companies do now?

The practical response to the 2027 amendments is structured and sequential. It does not require a comprehensive overhaul of a company's global data architecture before any other step is taken — but it does require that in-house counsel understand the current state of their Russian data footprint before the next supervisory cycle begins.

The first step is a data mapping exercise specific to Russian operations. In-house counsel should identify, with input from IT and business functions: what personal data of Russian citizens the Russian entity processes; where the primary database for that data is located; which transfers of that data occur, to which destinations, and on what legal basis. For many foreign companies, this mapping has not been refreshed since the prior rounds of 152-FZ amendment, and the 2027 changes may reveal gaps that were not present under the old framework.

The second step is a cross-border transfer review. Following the mapping exercise, counsel should assess each outbound transfer of Russian citizens' personal data against the new prior-authorisation procedure. Transfers to Roskomnadzor-recognised adequate countries require no additional action beyond documentation. Transfers to other countries require a transfer impact assessment, in a format that the supervisory authority is expected to publish. Where the implementing guidance remains outstanding, a prudent approach is to draft the assessment on the basis of the statutory criteria already set out in the amended law, so that it can be finalised and submitted once the format is confirmed.

The third step is a review of the company's registered status as a personal data operator with Roskomnadzor, and the accuracy of the information held on the register. The 2027 amendments introduced revised notification requirements for operators that process data across multiple legal bases — foreign companies that have not updated their Roskomnadzor notifications since 2025 should verify that the current registration reflects their actual processing activities.

The firm's Data Protection practice has advised foreign companies on the practical implementation of Federal Law 152-FZ requirements across a range of industries. For a structured introduction to the compliance framework, see our Practical Guide to Federal Law 152-FZ and our overview of 152-FZ personal data requirements. Related compliance considerations frequently arise alongside broader regulatory licensing questions.

"The shift to turnover-based penalties means that a compliance failure that was a manageable fixed fine in 2025 can now carry a materially different exposure for a company with significant Russian revenue." — Elena Pavlova, Associate, Vetrov & Partners

Frequently asked questions

Q: What specifically changed in Federal Law 152-FZ in 2027?

A: The 2027 amendments addressed three principal areas: the scope and interpretation of the data localisation requirement for Russian citizens' personal data; the procedure for authorising cross-border personal data transfers, which shifted from notification to prior authorisation for transfers to non-adequate countries; and the penalty calculation methodology for certain violations, which moved towards a turnover-based approach for repeated or serious breaches. The amendments clarified Roskomnadzor's supervisory position on centralised data infrastructure held outside Russia, and introduced a transfer impact assessment requirement for outbound transfers to non-recognised jurisdictions.

Q: Which foreign companies are most affected by the 2027 changes to Russian personal data law?

A: Foreign companies most directly affected are those operating centralised data infrastructure outside Russia — including shared HR, CRM, or ERP systems where the master database is held abroad — and those that transfer personal data of Russian citizens to group entities or processors in countries not recognised as adequate by Roskomnadzor. Companies in consumer-facing sectors, including retail, e-commerce, finance, and healthcare, face a higher supervisory risk profile given Roskomnadzor's proactive enforcement posture. The revised penalty framework applies to the Russian legal entity as the registered operator, regardless of where the compliance decision was made within the group.

Q: What steps should in-house counsel take in response to the 2027 152-FZ amendments?

A: The recommended sequence is: first, conduct a data mapping exercise to establish what personal data of Russian citizens the Russian entity processes, where the primary database is located, and on what legal basis each transfer occurs; second, review all cross-border transfers of Russian citizens' data against the revised prior-authorisation procedure, and prepare transfer impact assessments for transfers to non-adequate countries; third, verify and update the company's registration as a personal data operator with Roskomnadzor to reflect current processing activities. Where the implementing guidance on assessment formats remains outstanding, counsel should draft on the basis of the statutory criteria already enacted, to allow prompt finalisation once guidance is published.

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