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

Case comment: GDPR and Russian Federal Law 152-FZ: bridging requirements in the agriculture sector

Elena Pavlova · May 2026 · 7 min read

Foreign agribusinesses operating in Russia face dual data compliance: GDPR and Federal Law 152-FZ. A 2026 ruling clarifies the overlap. Make an enquiry.

In advising foreign agribusinesses with Russian operations, one question surfaces with increasing regularity: when a company is subject to GDPR by virtue of its EU establishment and simultaneously processes personal data of Russian-resident individuals, which regulatory framework takes precedence — and what happens when Russian courts assess compliance with Federal Law No. 152-FZ against the backdrop of a company's stated GDPR obligations? A recent decision by a Russian commercial court in a data protection enforcement matter involving a foreign-owned agricultural enterprise has provided a concrete reference point. It does not resolve all tensions between the two regimes, but it clarifies where Russian courts draw the line.

Background

The matter concerned a foreign-owned agribusiness operating through a Russian legal entity. The entity's parent company — incorporated within the European Economic Area — had configured its group-wide personal data processing infrastructure in accordance with GDPR requirements, including a unified consent management platform, a single data retention schedule, and a centralised data processing agreement structure. When Roskomnadzor, Russia's data protection authority, conducted a scheduled compliance audit of the Russian subsidiary, it found several areas of divergence from Federal Law 152-FZ requirements: the localisation obligation for personal data of Russian citizens had not been fully implemented at the Russian entity level, the consent forms used matched the GDPR standard but did not satisfy the specific affirmative consent requirements under Russian law, and the retention schedule applied by the group exceeded the periods that Russian courts have consistently treated as proportionate.

The regulatory finding was contested by the Russian entity in proceedings before the commercial courts. The company's argument centred on the proposition that compliance with GDPR — a regulation of comparable substantive rigour — should be treated as substantively equivalent to, or at minimum a mitigating factor in assessing, compliance with Federal Law 152-FZ. The court was therefore asked to consider whether the existence of a European regulatory framework could displace or qualify the Russian domestic data protection standard.

The decision

The court rejected the equivalence argument in clear terms. Russian data protection law operates as an autonomous domestic regime; compliance with a foreign regulatory framework — however robust — does not satisfy, discharge, or mitigate obligations arising under Federal Law 152-FZ. The court treated each obligation as independent: GDPR compliance neither creates nor diminishes a Russian law compliance obligation.

On the localisation requirement specifically, the court confirmed the established position: personal data of Russian citizens collected in the course of the entity's Russian business operations must be stored and primarily processed on servers located within Russian territory, regardless of where the parent company's infrastructure is hosted. The group's use of EU-based data centres, even under a GDPR-compliant data processing agreement with appropriate safeguards, did not satisfy this requirement. The court noted that the localisation obligation attaches at the point of collection, not at the point of transfer.

On the consent question, the court drew a distinction between GDPR's consent standard — which emphasises freely given, specific, informed, and unambiguous indication of agreement — and the Russian standard, which imposes additional formal requirements including explicit written or equivalent electronic confirmation in a form that is separable from other contractual terms. The group's unified consent form, while GDPR-compliant, bundled data processing consent with general terms of engagement in a manner the court found incompatible with the Russian separability requirement.

The court's treatment of the retention schedule was arguably the most instructive element of the decision. The entity applied a GDPR-derived retention period tied to the purposes of processing and a periodic review mechanism. The court assessed this against the principle of proportionality under Russian law and found that an open-ended, purpose-linked retention period without a defined outer limit was not consistent with Russian regulatory expectations in this sector. For agricultural businesses, where data on land use, employee identities, and commercial counterparties may be processed at scale, the court indicated that retention periods should be anchored to defined operational cycles rather than open-ended purpose assessments.

"This decision confirms that Russian data protection law will not accept GDPR compliance as a proxy — even where the substantive outcomes are broadly comparable. Foreign groups operating Russian subsidiaries need parallel compliance architectures, not a single framework applied extraterritorially." — Elena Pavlova, Associate, Vetrov & Partners

For foreign companies managing GDPR and 152-FZ compliance across a Russian subsidiary, early-stage legal review of the compliance architecture can identify misalignments before they become regulatory findings — make an enquiry: info@vetrovpartners.com |

What does this ruling mean for foreign companies in the agriculture sector?

The decision carries several practical implications for in-house counsel at foreign agribusinesses with Russian entities. The clearest is structural: a single compliance framework designed to satisfy GDPR will not automatically satisfy Federal Law 152-FZ, even where the underlying principles overlap. Foreign companies operating through Russian legal entities must maintain parallel, jurisdiction-specific compliance programmes rather than applying a top-down group framework.

For the agriculture sector specifically, the ruling has heightened relevance. Agribusinesses typically process personal data across multiple categories: employee and contractor data, data of rural landowners and tenants, data arising from precision agriculture platforms (which may capture individual-level operational data), and commercial counterparty data processed through supply-chain management systems. Each of these data streams is subject to the localisation and consent requirements under Federal Law 152-FZ, and the scale of agricultural data processing means that non-compliance risks accumulate quickly.

The ruling also has implications for how foreign agribusinesses structure their data processing agreements with Russian subsidiaries. A standard intra-group data processing agreement that designates the parent company as the primary controller and the Russian subsidiary as a processor — a structure that is common under GDPR — will not relieve the Russian subsidiary of its independent obligations under Russian law. The Russian entity remains a data operator in its own right under Federal Law 152-FZ and bears direct regulatory responsibility.

In-house counsel who are aware that their Russian subsidiary's data processing infrastructure was configured principally to satisfy GDPR — a pattern the firm has observed across several mandates in the agribusiness and food production sector — should treat this ruling as a prompt to audit the Russian entity's standalone compliance posture, including its localisation arrangements, consent documentation, and retention schedules. Under Russian data protection law, regulatory findings of the kind at issue in this matter may attract administrative penalties and, where repeated, operational restrictions. The regulatory timeline in these matters does not favour delay.

If your Russian subsidiary's data compliance posture has not been reviewed independently from the group's GDPR programme, the firm can conduct a focused 152-FZ compliance audit — make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What does this ruling change?

A: The ruling confirms that Russian commercial courts treat Federal Law 152-FZ as a wholly autonomous domestic regime. GDPR compliance — even full, documented GDPR compliance — has no mitigating or substitutive effect on a Russian entity's obligations under Russian data protection law. For foreign groups that had configured their Russian subsidiary's data processing infrastructure as an extension of the group's GDPR programme, this ruling closes off the argument that substantive equivalence between the two regimes could be a defence to a Roskomnadzor finding. It also clarifies that the localisation obligation attaches at the point of collection, not transfer — a point that matters for agribusinesses collecting data through field-based systems that may automatically route to EU infrastructure.

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

A: Companies should treat their Russian subsidiary's compliance posture under Federal Law 152-FZ as a discrete project, separate from the group's GDPR programme. The immediate priorities are three: first, verify that personal data of Russian citizens collected by the Russian entity is stored and primarily processed on Russian-territory servers; second, review consent documentation used by the Russian entity to ensure it satisfies the separability and form requirements under Russian law rather than the GDPR standard; third, audit retention schedules applied to the Russian entity's data sets and replace open-ended purpose-linked schedules with defined operational-cycle anchors. Where the Russian entity operates precision agriculture systems or large-scale land data platforms, the volume of personal data processed makes a structured compliance audit the practical starting point.

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