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

Data protection audit and compliance programme in Russia at the inspection stage: key developments in 2026

Elena Pavlova · May 2026 · 8 min read

Roskomnadzor tightened inspection procedure for Russian data protection compliance in 2026. What in-house counsel must prepare now. Make an enquiry.

Following amendments to Russian data protection legislation and regulatory practice that took effect or consolidated through 2025 and into 2026, foreign companies operating in Russia as personal data operators face a materially different inspection environment. Roskomnadzor — Russia's supervisory authority for personal data — has sharpened both the triggers for inspection and the documentary standard it applies when assessing whether a compliance programme is functioning in practice rather than on paper. For in-house counsel managing a Russian subsidiary or a locally registered entity that processes Russian personal data, understanding what has changed at the inspection stage is now a baseline operational requirement.

What changed in Russian data protection inspection practice in 2026?

The most consequential shift in 2026 inspection practice is the move from a document-collection model to a substantive assessment model. Under the previous approach, a Roskomnadzor scheduled inspection could typically be satisfied by producing a privacy notice, a consent form, and a designation of a responsible officer. That approach has become materially insufficient.

In the current environment, inspectors assess whether the compliance programme operates as a live system. This means verification of actual data flows against declared processing purposes, confirmation that data localisation requirements are met for Russian citizens' personal data, and review of internal processing records that document each category of data, the legal basis for processing, retention periods, and the identity of any third-party processors or cross-border transfer recipients.

The inspection stage now also includes a behavioural assessment component: inspectors may request evidence of staff training completion, records of incident response exercises, and logs of data subject requests received and actioned. Organisations that have maintained compliance programmes as static documents without operationalising them are encountering the practical consequences of that gap during inspection.

A secondary development concerns unscheduled inspections. The threshold for triggering an unscheduled inspection has, in practice, been interpreted more broadly: a complaint filed by a data subject, a notification in the media, or a discrepancy identified during a scheduled inspection of a related entity can each be sufficient to initiate unscheduled review. Foreign-owned companies with Russian operations have reported receiving inspection notices with short lead times, which creates acute pressure on in-house teams that have not maintained inspection-ready documentation on a continuous basis.

"

"Roskomnadzor's shift to substantive assessment reflects a broader regulatory maturation: inspectors are now asking whether the compliance system functions day-to-day, not merely whether the documents exist."— Elena Pavlova, Associate, Vetrov & Partners

"

Who is affected by the 2026 inspection developments?

The revised inspection approach applies to any entity registered as a personal data operator with Roskomnadzor, which in practice means any legal entity incorporated in Russia that processes personal data — including employees' data — as well as foreign companies that have registered a branch or representative office and process Russian residents' data through Russian infrastructure.

For foreign companies with Russian subsidiaries in manufacturing, retail, logistics, financial services, and technology sectors, the risk profile is elevated for several reasons. First, these subsidiaries typically process multiple categories of data — employee data, customer data, and in some cases special-category data such as biometric or health data — each of which is subject to distinct documentary requirements. Second, cross-border transfers of data from Russia to parent companies or group processors abroad require a specific legal basis and, in certain configurations, may require prior notification. Third, the personal data localisation requirement — which mandates that initial collection and storage of Russian citizens' personal data occur on servers physically located in Russia — remains strictly interpreted, and inspectors have focused on organisations where IT infrastructure decisions are made centrally outside Russia.

EAEU and CIS member-state entities operating in Russia are subject to the same domestic data protection framework. Membership of a regional economic arrangement does not create an exemption from Russian data protection obligations or from Roskomnadzor's inspection authority.

For in-house counsel at the group level, the structural challenge is that Russian data protection compliance cannot be managed as a uniform extension of a global GDPR programme. The legal bases differ, the localisation obligation has no GDPR equivalent, and the supervisory authority's enforcement style — including its inspection methodology — reflects Russian administrative law, not European data protection practice.

For in-house counsel reviewing the Russian data protection exposure of a subsidiary ahead of the inspection cycle — make an enquiry: info@vetrovpartners.com |

What should foreign companies do before an inspection is announced?

The practical implication of the 2026 inspection developments is that preparation must be continuous, not reactive. An organisation that begins assembling its compliance documentation after receiving an inspection notice is operating at a structural disadvantage: Russian administrative inspection timelines typically allow limited scope for post-notice remediation.

The priority actions for a Russian subsidiary or Russian branch operating under foreign ownership are the following.

First, conduct a data flow mapping exercise that accurately reflects current processing activities — not the activities described when the privacy policy was last revised. The gap between declared and actual data flows is one of the most common findings at the inspection stage, and it is one that a functioning compliance programme should resolve before any external review.

Second, verify that the personal data localisation requirement is met. This requires confirmation from the IT function — not just a contractual assurance — that the primary database for Russian citizens' personal data is hosted on infrastructure located in Russia. Where cloud services are used, the specific geographic configuration of storage must be documented.

Third, review the register of personal data processing operations (often referred to as the operator's internal processing record). This document should accurately reflect each processing activity, the legal basis, the retention period, the categories of data subjects, and any third-party processors or cross-border recipients. It is a primary inspection document.

Fourth, ensure that the documentation trail for employee consent and data subject requests is complete and retrievable. Inspectors have increasingly requested evidence of how individual subject access and deletion requests were handled, including the timeline of the organisation's response.

Fifth, assess whether the responsible person (or data protection officer equivalent) has the authority, budget, and internal access required to manage compliance effectively. Roskomnadzor inspectors assess organisational capacity, not just documentation.

Foreign companies whose Russian operations are covered by a group-level data protection function should consider whether that function has sufficient visibility into Russian-specific requirements to support an inspection-ready posture. Our practice note on strategic considerations in data protection compliance for foreign companies in Russia addresses this structural question in detail.

The Data Protection practice at Vetrov & Partners assists foreign-owned entities in preparing for and responding to Roskomnadzor inspections, including compliance gap assessments, documentation audits, and representation during inspection proceedings.

Open questions — where interpretation remains unsettled

Two areas of the 2026 framework remain subject to interpretive uncertainty, and in-house counsel should be alert to them.

The first concerns cross-border transfers following regulatory evolution in the permissible bases. The supervisory authority's published positions on which foreign countries or organisations may receive Russian personal data, and on what procedural basis, have evolved through the period under review. Organisations that established their cross-border transfer arrangements under earlier guidance should verify that those arrangements remain compliant under the current position.

The second concerns the application of enhanced requirements to biometric personal data. Russian data protection law has long subjected biometric data to stricter requirements, but the practical scope of what constitutes biometric data in an employment context — including whether certain access control systems generate biometric data within the meaning of the legislation — has been the subject of inconsistent regulatory commentary. Organisations using biometric-adjacent technologies in their Russian operations should treat this as an area requiring specific legal analysis rather than reliance on the general compliance framework.

For analysis of how Russian courts have approached data protection disputes, including enforcement of subject rights and operator liability, see How Russian courts approach data protection: a practitioner's overview.

Frequently asked questions

Q: What specifically changed in Russian data protection inspection practice in 2026?

A: Roskomnadzor has moved from a document-collection model to a substantive assessment model at the inspection stage. Inspectors now verify that a compliance programme operates as a live system — examining actual data flows, localisation compliance, internal processing records, staff training logs, and data subject request handling — rather than accepting a static set of standard documents as evidence of compliance. The threshold for triggering unscheduled inspections has also been interpreted more broadly in practice, increasing the risk of short-notice review.

Q: Which foreign-owned entities in Russia are most exposed to the revised inspection approach?

A: Any entity registered as a personal data operator in Russia is within Roskomnadzor's inspection jurisdiction, regardless of foreign ownership. Subsidiaries and branches of foreign companies are particularly exposed where they process multiple categories of personal data, rely on cross-border transfers to parent companies or group processors, or use IT infrastructure with non-Russian storage components. EAEU and CIS membership of the parent company's home jurisdiction does not provide exemption from Russian data protection obligations or from the inspection framework.

Q: What is the most effective first step for a Russian subsidiary that has not recently reviewed its data protection compliance programme?

A: A data flow mapping exercise — conducted against current processing activities, not legacy documentation — is the most actionable starting point. It will typically reveal gaps between what the subsidiary's privacy documentation declares and what the organisation actually does with personal data. Those gaps are among the most common inspection findings. Verifying localisation compliance and updating the internal processing record should follow immediately. For subsidiaries that have not undertaken a structured review in the past 12 to 18 months, a formal compliance gap assessment against the current inspection standard is advisable before the next inspection cycle.

To discuss data protection inspection readiness for your Russian operation — make an enquiry: info@vetrovpartners.com |

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