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

Case comment: cross-border data transfer restrictions from Russia

Elena Pavlova · March 2026 · 6 min read

Russian courts tightened the compliance threshold for cross-border personal data transfers under 152-FZ. What in-house counsel must review. Make an enquiry.

Foreign companies managing cross-border data flows to and from Russia have long treated Federal Law No. 152-FZ on Personal Data as a localisation obligation — a rule about where data is stored, not how it moves. A recent ruling by a Russian arbitrazh court has challenged that reading. The court examined whether a foreign company's ongoing transmission of Russian employees' personal data to a parent entity abroad could proceed without specific regulatory authorisation, and found that it could not. For in-house counsel responsible for a Russian subsidiary, the ruling narrows the compliance margin that many organisations have implicitly relied upon.

Background

Cross-border personal data transfer under Russian law has never been a freely permissible activity. Federal Law No. 152-FZ establishes that personal data of Russian subjects may be transferred abroad only to countries that ensure an adequate level of protection, or — where adequacy is not confirmed — subject to specific conditions including the data subject's written consent or, in certain cases, a contractual necessity ground. Roskomnadzor, the federal supervisory authority, maintains a list of countries recognised as providing adequate protection, but this list is materially shorter than the equivalent EU adequacy list, and several jurisdictions where multinationals routinely route data — including some EU member states — are not confirmed on it as a matter of straightforward administrative record.

The matter at issue arose from a compliance investigation initiated following a Roskomnadzor inspection of a Russian subsidiary of a foreign group. The subsidiary was transmitting employee personal data — payroll records, HR information, and access credentials — to a parent company registered outside Russia. The transfer had been in operation for several years and was underpinned by intragroup agreements, but no written consent from the affected data subjects had been obtained, and no contractual necessity analysis had been conducted or documented. The subsidiary's position was that the data transfer was covered by the employment relationship and the legitimate interests of the group. The court was asked to assess whether that position was legally sustainable under the current framework.

The decision

The court rejected the subsidiary's framing. It held that an intragroup operational necessity argument does not, by itself, satisfy the requirements of Russian data protection legislation for cross-border transfers to non-adequate countries. The court reasoned that the statute requires one of the specific authorisation grounds to be established and documented in advance of the transfer — not merely asserted after the fact in response to regulatory scrutiny. The employment relationship, the court noted, provides a basis for processing personal data within Russia for purposes directly connected to employment; it does not automatically extend to transmission of that data to a foreign entity, even within the same corporate group.

The court also addressed the adequacy question directly. It held that, where a destination country has not been confirmed as adequate by Roskomnadzor, the data controller bears the burden of establishing an alternative legal ground. The court found that the subsidiary had neither obtained written consent from data subjects nor demonstrated that the transfer was strictly necessary to perform a contract to which the data subjects were party — the two most practically accessible grounds where adequacy is absent. The subsidiary's reliance on intragroup data-sharing agreements, without aligning those agreements to the statutory requirements, was found insufficient.

"This ruling makes explicit what the regulatory framework has long implied: intragroup transfers to non-adequate jurisdictions require documented legal grounds, not merely a transfer agreement." — Elena Pavlova, Associate, Vetrov & Partners

The practical effect of the ruling is that companies cannot treat their existing intragroup data-transfer architecture as compliant by default. Each transfer must be mapped to an authorisation ground that survives regulatory and judicial scrutiny.

If your Russian subsidiary transfers personal data to a parent entity or affiliated company abroad, the compliance position described in this ruling may apply to your existing arrangements. Make an enquiry to assess your exposure: info@vetrovpartners.com |

What this means for foreign companies?

For in-house counsel overseeing a Russian subsidiary, the immediate question is whether current cross-border data transfer arrangements rest on a documented legal ground or on an operational assumption. The ruling applies most directly to three common patterns: HR and payroll data transmitted to a group shared-services centre abroad; employee monitoring or productivity data transmitted to IT systems hosted outside Russia; and customer or user data shared with group analytics, CRM, or marketing platforms in non-adequate countries.

The decision reinforces an existing obligation rather than creating a new one — but it does so in terms that are difficult to ignore. The court's insistence on prior documentation means that retrospective remediation, while not impossible, will be harder to rely upon if a further inspection occurs. Organisations that have conducted data mapping under the Data Protection framework but have not updated their cross-border transfer analysis since the 2022 amendments to 152-FZ should treat this ruling as a prompt to revisit. A practical review should address whether each destination country is on the Roskomnadzor adequacy list; whether valid written consent has been collected from affected data subjects; and whether contractual necessity grounds have been assessed and recorded.

Foreign companies with Russian operations may also find this ruling relevant to their Supreme Court clarification on cross-border transfers reading — particularly where that guidance touches on the scope of the adequacy assessment and the relationship between 152-FZ requirements and intragroup processing agreements. The procedural aspects of cross-border transfer compliance are examined further in our guide Navigating cross-border data transfer restrictions.

The ruling also carries a secondary implication. It signals that Roskomnadzor inspection findings are increasingly being tested before courts rather than resolved administratively — a shift that foreign companies should factor into their compliance posture. Where a subsidiary faces an inspection, having external Data Protection counsel involved early limits the risk of positions being stated that are difficult to maintain in subsequent proceedings. See also our Matters hub for representative cross-border enforcement matters.

Firms advising clients with Russian subsidiaries will often require a confirmed Russian data protection counsel relationship before an inspection notice becomes a live issue. Speak to our team: info@vetrovpartners.com |

Frequently asked questions

Q: What does this ruling change?

A: The ruling does not introduce new legal obligations, but it confirms that courts will not accept operational necessity or intragroup contractual arrangements as a freestanding legal ground for cross-border personal data transfers to non-adequate countries. Russian data protection legislation has always required a documented authorisation ground — consent, contractual necessity, or an adequacy finding — before data is transmitted abroad. The significance of this decision lies in its explicit rejection of the argument that group-level data sharing arrangements satisfy that requirement. In-house counsel should treat this as confirmation that compliance requires documented, transaction-level analysis of each transfer, not reliance on an umbrella policy.

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

A: The priority action is to audit existing cross-border data transfer arrangements from Russian entities and verify that each transfer is mapped to a documented legal ground. Where the destination country is not on the Roskomnadzor adequacy list, the audit should determine whether valid written consent exists from affected data subjects or whether a contractual necessity ground has been assessed and recorded. Intragroup transfer agreements should be reviewed against the statutory requirements. Where gaps are identified, remediation — updating consent language, documenting necessity assessments, or restructuring the transfer architecture — should be completed before the next scheduled Roskomnadzor inspection cycle. Early engagement of Russian data protection counsel is advisable for subsidiaries operating HR, payroll, or customer data systems with cross-border exposure.

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