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

Russian court practice on consent requirements under Russian personal data law for Turkish controllers: 2026 update

Elena Pavlova · May 2026 · 10 min read

Russian courts tightened 152-FZ consent standards in 2026. Turkish data controllers must review Russian compliance practices. Make an enquiry.

Throughout 2025 and into 2026, Russian courts handed down a series of decisions that materially tightened the standards for valid personal data consent under Federal Law No. 152-FZ. For Turkish companies operating in Russia — whether through a registered subsidiary, a representative office, or as a cross-border controller processing data belonging to Russian residents — those decisions have shifted the compliance baseline in ways that are not immediately apparent from reading the statute alone. This briefing sets out what changed, which Turkish-controlled operations are most directly affected, and what in-house counsel should prioritise before year-end.

§ I. What has changed in Russian consent practice in 2026?

Russian personal data law has always required that consent to data processing be "specific, informed, and conscious." Until recently, however, Russian courts and Roskomnadzor — the Federal Service for Supervision of Communications, Information Technology and Mass Media, which functions as the principal data protection supervisory authority — interpreted these requirements with a degree of flexibility that allowed controllers to rely on broadly worded consent forms, checkbox-based acceptance flows, and bundled consent clauses embedded in service agreements.

That latitude has contracted noticeably in the most recent cycle of enforcement decisions and administrative proceedings.

The before-and-after picture is as follows.

Before: Courts accepted that a single consent clause in a service or employment contract could validly authorise multiple, unrelated categories of data processing, provided the clause listed the processing purposes in aggregate. Roskomnadzor audits focused primarily on the presence of a consent mechanism, not its granularity. In cross-border transfer contexts, controllers could rely on a generalised contractual consent to authorise the transfer of personal data to a foreign recipient, including a Turkish parent entity, without specifying the foreign entity or the legal basis for the transfer separately from the domestic processing consent.

After: Decisions issued in 2025 and the first three quarters of 2026 have established, with increasing consistency across different circuits, that consent must identify each processing purpose separately, and that consent for cross-border transfer must be obtained as a distinct, standalone act — not bundled into broader processing consent. Courts have also found that consent forms which fail to identify the specific categories of data transferred, the recipient entity by name or at least by category, and the country of destination do not satisfy the statutory requirement of specificity. Where Roskomnadzor has brought administrative proceedings following complaints from Russian data subjects, several courts have declined to treat the existence of a contractual relationship as implicit consent to data transfer.

For Turkish controllers, this development carries particular weight. Turkey is neither an EAEU member state nor a CIS member state, and Russian data law does not grant Turkey the simplified cross-border transfer treatment available to jurisdictions on Russia's list of states providing adequate protection. A Turkish parent company receiving personal data from its Russian subsidiary must therefore rely either on a standalone cross-border transfer consent that now meets the heightened specificity standard, or on one of the narrow statutory alternatives — neither of which is automatic.

"

If your company's Russian data processing documentation was last reviewed before 2025, the current court standard for consent validity may differ materially from what your forms reflect — make an enquiry: info@vetrovpartners.com |

"

§ II. Which Turkish controllers are most affected?

The practical impact of the new consent standard is not uniform across all Turkish-controlled entities operating in Russia. It concentrates in three principal fact patterns.

The first is the Turkish parent receiving employee data from a Russian subsidiary. Russian employment relationships generate continuous flows of personal data — payroll records, performance information, HR documentation — that may be transferred to a Turkish parent for consolidated reporting or HR system purposes. If the transfer authorisation is embedded in an employment contract or onboarding consent form that does not separately and specifically address the transfer to a named or categorised foreign recipient, it is unlikely to survive scrutiny under the standard that Russian courts have applied in 2025–2026.

The second is the Turkish e-commerce or digital services operator processing data of Russian residents. Under Russian law, a foreign entity that collects personal data of Russian residents in connection with commercial activity directed at the Russian market is subject to 152-FZ obligations regardless of where it is incorporated. For Turkish operators in this category who have not localised their consent infrastructure to reflect Russian-specific requirements — including the separate cross-border transfer consent — the exposure is both administrative and reputational.

The third is the Turkish company engaged in joint processing arrangements with a Russian counterparty. Where a Turkish entity processes personal data jointly with or on behalf of a Russian controller, the question of which entity is responsible for obtaining valid consent has become more, not less, contested following the 2025–2026 decisions. Courts have shown a willingness to examine the substance of the data flow rather than the contractual characterisation, and to attribute consent obligations to the party that, in practice, determines the processing purpose.

A related risk affects Turkish entities relying on the "contract performance" ground as an alternative to consent for certain domestic processing. Courts have begun to scrutinise more carefully whether the specific processing purpose is genuinely necessary for contract performance or whether it is, in substance, a discretionary use of personal data for which consent — and now, more exacting consent — is required.

For in-house counsel at Turkish groups with Russian operations, the loss aversion framing is precise: Roskomnadzor's administrative penalty schedule has escalated significantly in recent amendments, and the regulator has the authority to require localisation of data that is found to be transferred without a valid legal basis. Addressing consent document deficiencies proactively is materially less costly than responding to a Roskomnadzor inspection or defending an administrative proceeding.

"

Firms advising Turkish corporate groups with Russian subsidiaries or Russian market exposure should confirm their local counsel relationship before a Roskomnadzor inquiry makes the timeline a live constraint — make an enquiry: info@vetrovpartners.com |

"

§ III. What should Turkish controllers do now?

The practical response to the 2026 consent standard involves four areas that in-house counsel should assess against their current documentation.

First, audit existing consent forms for specificity. Each processing purpose must be identified separately. A consent form that lists "processing for business purposes" or that incorporates purposes by reference to a privacy policy without specifying them in the consent instrument itself is unlikely to satisfy the current standard. This applies to both domestic processing consent and cross-border transfer consent.

Second, verify that cross-border transfer consent is structurally separate. The consent for transfer of personal data from a Russian entity to a Turkish recipient should be a distinct document or a clearly demarcated, separately signed section — not a clause within a longer agreement. It should identify the Turkish recipient (by name or, at minimum, by legal category and country), the categories of data transferred, and the purposes of the transfer.

Third, review the legal basis for any processing that has been characterised as "contract performance." If the specific processing activity is not self-evidently necessary to execute the contractual obligation — if it goes to commercial optimisation, analytics, or parent-company reporting — it may need to be supported by a separate consent that meets the current specificity requirements.

Fourth, update consent mechanisms for Russian-resident data subjects in digital services. For Turkish e-commerce or digital operators, this means ensuring that the consent layer presented to Russian users is granular, purpose-specific, and includes a separate, clearly labelled consent for any cross-border transfer to Turkey. Bundled acceptance — a single "I agree" button covering all processing — is the fact pattern that has attracted the most adverse administrative findings in the 2025–2026 cycle.

A review of the firm's analysis of key risk points in consent documentation under Russian personal data law is available at Key risk points in consent requirements under Russian personal data law. A court-level case comment on the appellate reversal that sharpened the specificity standard is at Court of Appeal reverses on consent requirements.

The data protection practice at Vetrov & Partners advises on compliance with Russian data protection law and cross-border transfer obligations for foreign controllers with Russian exposure.

§ IV. Open questions — where court practice remains unsettled

Two areas remain genuinely unsettled following the 2025–2026 decisions and warrant continued monitoring.

The first is the standard applicable to consent obtained before the current judicial trend. Several decisions have addressed whether pre-existing consent documentation — obtained under the prior, more permissive standard — must be replaced prospectively, or whether Roskomnadzor and courts will treat historical consent as valid for processing that began before the new standard crystallised. Practice varies by circuit, and there is no Supreme Court-level clarification as of the date of this update.

The second is the interaction between the Russian consent standard and Turkey's own data protection framework, the KVKK. A Turkish parent receiving personal data from its Russian subsidiary must comply with both regimes simultaneously. In particular, the KVKK's conditions for lawful transfer into Turkey and Russian law's conditions for lawful transfer out of Russia must both be satisfied. Where these conditions diverge — for example, in their respective specificity requirements for the transfer consent — there is no settled guidance on which regime's requirements should drive the form of the consent document. Controllers in this position are currently managing dual-standard uncertainty, and the prudent approach is to design consent documentation that satisfies the stricter requirement of the two.

"Russian court practice on consent requirements is moving quickly, and the 2025–2026 cycle of decisions has introduced specificity standards that Turkish controllers have not previously had to address in their Russian compliance programmes." — Elena Pavlova, Associate, Vetrov & Partners

Frequently asked questions

Q: What specifically changed about consent requirements under Russian personal data law in 2025–2026?

A: Russian courts and Roskomnadzor moved from accepting broadly worded, bundled consent clauses to requiring purpose-specific, separately structured consent for each processing activity. Critically, consent for cross-border data transfer to a foreign recipient — including a Turkish parent entity — must now be obtained as a standalone act, not embedded in a broader service or employment contract consent. Forms that previously satisfied administrative audits may not meet the standard being applied in the current enforcement cycle.

Q: Which Turkish-controlled entities are most directly affected by the new Russian consent standard?

A: Three categories face the highest immediate exposure: Turkish parent companies receiving employee or operational data from Russian subsidiaries; Turkish digital operators processing data of Russian residents in connection with services directed at the Russian market; and Turkish entities engaged in joint processing arrangements with Russian counterparts. All three categories should audit their consent documentation against the current specificity standard before engaging with Roskomnadzor on any new or pending inquiry.

Q: What should a Turkish company do now to address Russian personal data consent compliance?

A: The immediate steps are: (1) audit all consent forms used in Russia-connected processing for specificity — each purpose must be listed separately; (2) ensure that cross-border transfer consent to Turkey is structurally distinct from domestic processing consent and identifies the Turkish recipient and transferred data categories; (3) review whether any processing characterised as "contract performance" genuinely meets that threshold or requires separate consent; and (4) update digital consent layers for Russian-resident users to remove bundled acceptance mechanisms. Counsel with experience in Russian data protection enforcement can assist with a gap analysis calibrated to the current court standard.

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