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

Russian Supreme Court rules on Federal Law 152-FZ personal data requirements in Russia: analysis and implications

Elena Pavlova · January 2026 · 7 min read

Russia's Supreme Court has clarified core 152-FZ obligations for foreign companies. Review your data processing arrangements now. Make an enquiry.

Following a judicial development that in-house counsel across multinational organisations operating in Russia have been watching closely, the Russian Supreme Court has issued a ruling that clarifies how Federal Law No. 152-FZ on Personal Data applies to foreign companies with a presence, or operational footprint, in the Russian Federation. For legal and compliance teams managing Russian subsidiaries, data-sharing arrangements, or localised digital services, the decision resolves certain long-standing interpretive uncertainties – while, at the same time, raising practical compliance questions that will require early attention.

Background

Russia's data protection framework under Federal Law 152-FZ has, since its original enactment and subsequent amendment, imposed a range of obligations on operators who collect and process the personal data of Russian citizens: registration of data processing activities, localisation of primary databases on servers situated in Russia, restrictions on cross-border transfer of personal data, and requirements for obtaining adequate consent from data subjects. Roskomnadzor, the Federal Service for Supervision of Communications, Information Technology and Mass Media, functions as the principal supervisory and enforcement authority.

For foreign companies operating in Russia – whether through a wholly-owned subsidiary, a branch, a representative office, or via a digital distribution channel that reaches Russian users – the practical application of the localisation requirement and the consent regime has not always been uniform. Courts at different levels of the judicial hierarchy and in different circuits have, over the past several years, reached varying conclusions on questions such as: which category of processing activity triggers the localisation obligation, how cross-border data flows interact with the consent provisions, and what documentary record an operator must maintain to demonstrate lawful processing.

The proceeding that produced this ruling arose from an administrative enforcement action initiated by Roskomnadzor against a foreign-incorporated entity with Russian operations. The central legal questions before the Supreme Court concerned the scope of the localisation obligation for a company whose primary data infrastructure was maintained abroad, and whether the specific consent instrument used by the entity satisfied the requirements of Russian data protection legislation. The Court's analysis addressed both questions, and its reasoning carries implications beyond the immediate facts of the case.

The decision

In a decision handed down in the fourth quarter of 2025, the Supreme Court upheld the enforcement authority's position on the localisation question, confirming that the obligation to store the primary record of a Russian citizen's personal data on servers located in Russia is engaged upon initial collection – not, as the respondent company had argued, only when the data is subsequently used for the primary purpose for which it was collected. This sequencing point is significant: it means that companies cannot defer their localisation arrangements to the point of active data use; the obligation attaches at the moment personal data first comes under the operator's control.

On the consent question, the Court found that a consent instrument that bundled multiple processing purposes into a single click-through acknowledgement, without clearly identifying each distinct purpose and the corresponding data categories, did not meet the standard for valid consent under Russian data protection legislation. The ruling reiterated that consent must be specific, informed, and freely given in relation to each identified processing purpose – language that closely mirrors the standard articulated in earlier supervisory guidance from Roskomnadzor, but which now carries the weight of a Supreme Court determination.

The Court's reasoning on cross-border transfer is also material. The decision indicates that a foreign operator who directs personal data of Russian citizens to servers outside the territory of the Russian Federation, prior to completing the initial localisation step, exposes itself to administrative liability regardless of whether it has obtained a separate cross-border transfer consent. In the Court's framing, the transfer restrictions and the localisation obligation are sequential: localisation must precede any cross-border movement of the relevant data record.

"This ruling removes a significant area of ambiguity that compliance teams in foreign-parented companies have been navigating for some time. The sequencing of localisation before cross-border transfer is now settled at the highest judicial level in Russia." — Elena Pavlova, Associate, Vetrov & Partners

For in-house counsel who need to assess the implications of this ruling for their data processing arrangements, an early conversation can identify the specific exposure points. Make an enquiry: info@vetrovpartners.com |

What this means for foreign companies

The ruling's immediate practical significance falls into three areas for foreign companies that process the personal data of Russian citizens.

First, on localisation sequencing: companies that have structured their data flows on the assumption that initial collection may occur offshore – with the primary database later mirrored to a Russian server – should treat that model as carrying material enforcement risk under the current judicial interpretation. The Supreme Court's sequencing analysis suggests that the initial point of collection, not the downstream point of active processing, is the relevant trigger. In practice, this means that the data architecture for onboarding and registration workflows that involve Russian users warrants specific review.

Second, on consent instrument design: bundled or compound consent mechanisms – common in GDPR-aligned consent flows adapted for Russian compliance – may not satisfy the specificity requirement confirmed by this ruling. In-house counsel should verify that each processing purpose identified in their Russian data processing activities has a corresponding, separately expressed consent item, supported by documentation that can be produced to Roskomnadzor in the event of an audit or enforcement enquiry. The risk of a deficient consent record is not merely theoretical: Roskomnadzor's audit programme has been active, and the Supreme Court's ruling gives the authority a clear, judicially endorsed benchmark against which to assess operator conduct.

Third, on cross-border transfer: the court's framing of the transfer restrictions as sequential to – rather than concurrent with – the localisation obligation has direct relevance for foreign companies that use centralised international data platforms. Where personal data of Russian citizens is routed through a global data warehouse or analytical platform before the localisation step has been completed, the arrangement may now be characterised as a premature cross-border transfer, carrying potential administrative liability.

Foreign companies with Russian assets or operational presence should treat this ruling as a timely prompt to audit their current data processing activities against the Data Protection framework, particularly the localisation records, consent documentation, and cross-border transfer logs. For a comprehensive overview of the underlying legislative obligations, see Federal Law 152-FZ: personal data requirements in Russia and A practical guide to Federal Law 152-FZ for foreign companies.

Compliance exposure under Russian data protection legislation is not static: Roskomnadzor's enforcement posture has intensified over the past two years, and the Supreme Court's confirmation of core obligations at the highest level of judicial authority is likely to accelerate that trajectory. For legal teams managing Russian data compliance at a distance, the prudent response is a structured internal review before an enforcement enquiry arrives rather than after.

If your organisation processes personal data of Russian citizens and you have not recently reviewed your 152-FZ compliance position, the firm can assist with an internal audit framework and advise on gaps. Make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What does this ruling change?

A: The ruling settles two previously contested interpretive questions under Russian data protection legislation. First, it confirms that the localisation obligation – requiring primary data records relating to Russian citizens to be stored on servers located in Russia – is triggered at the point of initial collection, not at the point of active processing use. Second, it establishes that bundled multi-purpose consent does not meet the specificity standard: each processing purpose must be consented to separately. Together, these determinations provide a judicially authoritative benchmark that Roskomnadzor may apply in future enforcement actions. Foreign companies that structured their data flows or consent instruments on the prior, broader interpretation should now treat those arrangements as carrying elevated enforcement risk.

Q: What should foreign companies do in light of this decision?

A: Three steps are indicated as a matter of priority. First, review the data architecture for any workflow that collects personal data of Russian citizens – specifically to confirm that the initial storage point is a server located in the Russian Federation, not an offshore location. Second, audit existing consent instruments against the specificity standard confirmed by the Supreme Court: if a single consent form covers multiple processing purposes without separate articulation of each, it should be revised. Third, map cross-border data flows against the localisation sequencing requirement: where data moves to an international platform before localisation has been completed, the arrangement warrants legal review. If any of these steps reveals a gap, early voluntary remediation is materially preferable to an enforcement-prompted response, as Roskomnadzor's investigative and sanction tools have expanded in recent years.

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