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

Cassation review of data protection audit and compliance programme in Russia: a critical analysis

Elena Pavlova · June 2026 · 5 min read

Russian cassation courts are scrutinising corporate data protection audit programmes. Here is what in-house counsel needs to know. Make an enquiry.

In practice, the first signal that a corporate data protection audit programme falls short of Russian legal standards tends not to arrive from a Roskomnadzor inspector — it arrives when a cassation-level court ruling reveals that the evidentiary threshold for demonstrating compliance is materially higher than most foreign companies have assumed. A recent cassation court decision concerning the adequacy of a corporate data protection audit and compliance programme under Federal Law No. 152-FZ has clarified expectations in ways that carry direct relevance for any multinational operating a Russian subsidiary or processing the personal data of Russian residents.

Background

Russian data protection law imposes an obligation on operators — a term that includes foreign companies processing personal data within the Russian Federation or targeting Russian residents — not merely to adopt a compliance programme on paper, but to demonstrate that internal audit processes are substantively effective. Roskomnadzor, the principal data protection regulator, has authority to inspect, to issue mandatory prescriptions, and to refer matters for administrative prosecution. The proceedings that gave rise to the cassation review in question originated from a regulatory inspection of a company whose internal data protection documentation appeared, at first instance, to satisfy the formal requirements of the legislation. A lower court initially found in the company's favour. The matter was subsequently appealed, and ultimately reached cassation review. At each stage, the central question was the same: does a documented audit programme, without evidence of its operational execution, constitute compliance under Russian law?

What did the cassation court hold?

The cassation court found that formal documentation of a compliance programme — including an internal data protection audit policy, a register of personal data processing activities, and standard-form consent templates — did not, without more, establish that the operator had fulfilled its obligations under Russian data protection legislation. The court's analysis focused on the distinction between procedural compliance (the existence of policies and records) and substantive compliance (demonstrable evidence that those procedures had been actively implemented and reviewed). In its reasoning, the court noted that an audit programme must produce verifiable outputs: audit reports, remediation logs, staff training records, and evidence of periodic review. The mere adoption of a policy document — however comprehensive on its face — was held insufficient to discharge the operator's statutory obligations. This position reinforces a direction of travel already visible in Roskomnadzor's published enforcement guidance and in the growing body of administrative decisions reviewed by Russian courts: see Roskomnadzor enforcement trends in data protection and how Russian courts approach data protection adequacy.

"The cassation court's reasoning draws a clear and, frankly, demanding line between having a compliance programme and running one — a distinction that many corporate operators have not yet fully internalised." — Elena Pavlova, Associate, Vetrov & Partners

If you are reviewing your Russian data protection compliance programme in light of this ruling — make an enquiry: info@vetrovpartners.com |

What this means for foreign companies operating in Russia?

For in-house counsel managing a Russian entity or overseeing data processing operations that touch Russian residents' personal data, the practical implications of this ruling are significant. First, the evidential bar for demonstrating compliance in any regulatory inspection or subsequent litigation has risen. A binder of policies is no longer sufficient — and, under the prevailing approach of Russian courts, it may never have been. Counsel should expect that any future inspection or enforcement action will look for documentary proof that the audit programme has been executed: reports bearing dates, reviewers' sign-offs, and records of corrective action. Second, the ruling is relevant to the broader question of how Russian courts assess the liability of corporate officers and the parent entity in cross-border group structures. Where a foreign parent has approved or mandated a group-wide compliance template without verifying its local implementation, the cassation court's reasoning suggests that the defence of formal policy adoption will carry limited weight. Third, and most practically, this decision creates a time-sensitive consideration. Foreign companies that have relied on documentation-centred compliance — a common approach in entities that have adopted GDPR-oriented frameworks and assumed Russian law alignment — should treat this ruling as a prompt to audit their audit: to verify that operational evidence of programme execution exists and is retrievable. The data protection practice overview at Vetrov & Partners sets out the assessment framework the firm applies in these circumstances.

For multinationals whose Russian compliance programmes have not been reviewed since the tightening of Roskomnadzor enforcement activity in the past two years, the evidentiary gap identified by the cassation court is a live exposure, not a theoretical one.

To discuss your Russian data protection audit programme with an adviser who understands both the regulatory and litigation dimensions — make an enquiry: info@vetrovpartners.com |

Frequently asked questions

Q: What does this ruling change?

A: The cassation court's decision clarifies that Russian data protection law requires operators to produce verifiable evidence of audit programme execution — not merely the existence of policy documentation. Before this ruling, the evidentiary standard for demonstrating compliance was understood by many operators to be satisfied by having well-drafted internal policies and a processing activity register. The court has now confirmed, at cassation level, that substantive compliance requires operational outputs: audit reports, remediation logs, staff training records, and evidence of periodic review. For foreign companies with Russian operations, this shifts the compliance question from "do we have policies?" to "can we prove we have run them?"

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

A: In-house counsel should carry out an immediate review of the documentary evidence supporting their Russian data protection audit programme. The review should confirm that audit cycles have been completed and recorded, that staff training has been delivered and attendance documented, and that any remediation identified in previous audits has been logged and closed. Where gaps exist, they should be remediated before the next regulatory inspection cycle. Foreign companies that have implemented a GDPR-aligned group compliance programme should not assume that programme satisfies the evidential requirements of Russian law without a jurisdiction-specific assessment. If the Russian data protection programme has not been reviewed operationally within the past twelve months, a fresh audit — conducted with local Russian counsel — is advisable.

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