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

Navigating data protection audit and compliance programme in Russia at the enforcement stage: a step-by-step overview

Elena Pavlova · March 2026 · 11 min read

Foreign companies facing a Roskomnadzor data protection audit in Russia need a structured compliance programme to contain enforcement risk. Make an enquiry.

Unlike the GDPR's single supervisory authority model, Russia's data protection enforcement operates through Roskomnadzor — the Federal Service for Supervision of Communications, Information Technology and Mass Media — with a procedural logic that reflects the specific architecture of Federal Law No. 152-FZ on Personal Data rather than European frameworks. For foreign companies operating in Russia, this distinction matters most at the enforcement stage: when a scheduled or unscheduled audit is triggered, the compliance posture that was adequate for registration purposes may prove insufficient under Roskomnadzor's inspection criteria. This guide sets out a structured, step-by-step approach to navigating a Russian data protection audit and building a compliance programme that is designed to withstand enforcement scrutiny, not merely satisfy initial notification obligations.

What to prepare before the audit begins

Before any Roskomnadzor audit commences, a foreign company operating in Russia should have the following baseline documentation in place. Gaps identified at this stage are substantially easier and less costly to address than deficiencies surfaced during an active inspection.

For in-house counsel assessing whether existing documentation meets the current Roskomnadzor audit standard — make an enquiry: info@vetrovpartners.com |

Step 1. Identify the audit trigger and clarify its scope

The first practical step is to determine what has triggered the audit and what its formal scope encompasses. Roskomnadzor conducts both scheduled audits — which appear on the regulator's published inspection plan — and unscheduled audits, which may be triggered by a data subject complaint, a notification from another government body, a reported data breach, or the regulator's own initiative following media reports or monitoring activity.

The trigger matters because it directly affects the scope of documents the regulator may request and the timeline for response. A complaint-triggered audit will typically focus on the processing activities described in the complaint. An inspection initiated following a reported breach will extend to the company's technical and organisational security measures. Understanding the trigger also allows counsel to frame the response appropriately: a narrow complaint warrants a focused, factual response; a broad systemic audit warrants a comprehensive audit-trail submission.

Upon receiving a formal notification of audit from Roskomnadzor, the company has a defined response window — typically 10 business days for documentary submissions, though the regulator may request an extension or accelerate the timeline in urgent matters. This window is not generous, and assembling documentation without a pre-existing baseline almost invariably results in a submission that is incomplete or inconsistent.

Step 2. Assemble the internal audit team and establish the documentation baseline

Once the scope is confirmed, internal resource allocation is the immediate priority. For a foreign subsidiary or a Russian entity with foreign shareholders, the internal audit team typically comprises: the legal or compliance function (or external Russian counsel where internal resource is limited), the IT department responsible for data infrastructure, the HR function if employee data processing is in scope, and the business unit responsible for the processing activity under examination.

The documentation baseline established at this step forms the evidentiary record for the entire audit. Counsel should resist the temptation to produce documentation reactively — that is, to draft policies that post-date the audit notification. Roskomnadzor's inspectors are familiar with this pattern, and documents that are evidently freshly prepared may undermine the company's credibility on the entirety of its submission. Where gaps exist, the better approach is to acknowledge them, provide a remediation timeline, and demonstrate good-faith engagement with the regulator.

At this step, counsel should also identify whether the company has appointed a person responsible for organising personal data processing (the Russian equivalent of a data protection officer) and whether that appointment has been documented and communicated to Roskomnadzor. The absence of this appointment is a common finding in audits of foreign-controlled Russian entities and is treated as a standalone compliance deficiency.

If your Russian subsidiary's compliance documentation has not been reviewed against the current Roskomnadzor audit checklist — request our practice review: info@vetrovpartners.com |

Step 3. Conduct the data mapping and gap analysis

The data mapping exercise is the analytical core of the compliance programme. Its purpose is to produce a comprehensive record of every category of personal data processed by the entity in Russia: what data is collected, from whom, for what purpose, on what legal basis, where it is stored, how long it is retained, with whom it is shared (including transfers outside Russia), and what security measures protect it.

For foreign companies, the data mapping exercise typically surfaces three categories of gap that recur in Russian enforcement proceedings.

The first is localisation gaps. Under Russian data protection legislation, the initial recording, systematisation, accumulation, storage, adaptation, and retrieval of personal data of Russian citizens must be performed on databases located within Russian territory. Foreign companies that route all personal data through a parent-company ERP system located outside Russia — a common architecture — may find that their data flows are non-compliant regardless of whether they have a local server. The localisation requirement applies to the initial processing operation, not merely to storage in the narrow sense.

The second category is consent deficiencies. Where consent is relied upon as the legal basis for processing, that consent must be specific, informed, freely given, and capable of being withdrawn. Generic privacy notices that bundle multiple processing purposes into a single consent tick-box are routinely challenged by Roskomnadzor. Each processing purpose that is based on consent requires a separable consent mechanism.

The third category is cross-border transfer documentation. Transfers of personal data to countries that are not EAEU members and have not been recognised by Roskomnadzor as providing adequate protection require either explicit data subject consent or the execution of model contracts approved under Russian law. In practice, many foreign companies rely on intra-group data transfer agreements drafted for GDPR compliance, which do not satisfy the Russian requirements.

The gap analysis should produce a prioritised remediation register: items that represent a direct enforcement risk (localisation, consent) at the top; process improvements and documentation refinements further down. This register then becomes the backbone of the compliance programme.

Step 4. How does the Roskomnadzor inspection proceed in practice?

The inspection itself follows a defined procedural sequence. For a documentary audit — the most common format for initial enforcement contact — the regulator issues a formal request specifying the documents required and the submission deadline. The company responds in writing, typically through its legal representative in Russia. Roskomnadzor reviews the submission and either issues a compliance order (predpisanie) if deficiencies are found, requests supplementary information, or closes the audit without findings.

For an on-site inspection — which is more likely following a serious breach notification or a pattern of prior non-compliance — the regulator's inspectors attend the company's premises and may review IT systems, interview personnel, and examine physical document storage. Foreign companies should note that inspectors have the right to access systems and documents without prior consent during an authorised inspection; obstructing or delaying an on-site inspection is treated as an aggravating factor in any subsequent enforcement action.

The key procedural protection for companies at this stage is the right to make representations before any enforcement measure is imposed. If Roskomnadzor's inspection reveals deficiencies and the regulator intends to issue a compliance order or refer the matter for administrative proceedings, the company has the right to submit written explanations and, in some circumstances, to request a meeting with the responsible inspector. Counsel should ensure this right is exercised in every case — the representations made at this stage form part of the administrative record and are relevant to any subsequent appeal.

Under Russian data protection legislation, material administrative penalties for operators — including foreign companies operating in Russia — may be imposed for a range of violations, from processing personal data without a legal basis through to failure to comply with a Roskomnadzor order within the prescribed period. The penalty exposure has increased substantially following legislative amendments in recent years, and the risk of reputational and operational disruption from a compliance order — including the possibility of a temporary processing restriction — is, in practice, often as significant as the monetary penalty itself.

Step 5. How should the compliance programme be structured for ongoing enforcement resilience?

The compliance programme that follows an audit is most effective when it is built around the gap analysis findings rather than constructed as a generic template. A programme that addresses the actual deficiencies identified — with documented remediation steps, ownership, timelines, and verification mechanisms — will carry substantially more weight with Roskomnadzor than a general policy framework that does not connect to the inspection findings.

The structural elements of an effective compliance programme for a foreign company operating in Russia comprise the following.

A data protection policy suite: the processing policy, the privacy notice, the internal regulations for each processing system, and the data retention schedule — each reviewed against current 152-FZ requirements and signed off by an authorised officer of the Russian entity.

A consent management mechanism: where consent is used as a legal basis, a technical mechanism for capturing, recording, and withdrawing consent that is integrated into the company's customer-facing and HR-facing systems.

A data subject rights response process: a documented procedure for handling requests to access, rectify, erase, or restrict processing of personal data, with a response timeline that meets the statutory requirement — currently 30 calendar days for most requests.

A processor management framework: a register of all third-party processors with whom the company shares personal data, supported by executed data processing agreements that comply with Russian requirements, and a periodic review process.

A security incident response plan: a documented procedure for identifying, assessing, and notifying Roskomnadzor of data security incidents, reflecting the notification obligation that applies from the moment an operator becomes aware of an incident.

Finally, a periodic internal audit: a scheduled annual review of all of the above elements, with documented findings and a remediation cycle. The internal audit record demonstrates to Roskomnadzor — in any future enforcement contact — that the company's compliance programme is a living system rather than a static document set.

For in-house counsel responsible for a Russian subsidiary's data protection compliance — an initial 30-minute meeting, complimentary: info@vetrovpartners.com |

Frequently asked questions

Q: How long does a Roskomnadzor data protection audit typically take?

A: The duration depends on the audit format and the complexity of the matter. A documentary audit — where the company submits written responses and documentation — typically runs from the initial request to a formal outcome in four to eight weeks, though this can extend if Roskomnadzor requests supplementary information. An on-site inspection is usually completed within a defined statutory inspection period, after which the regulator has a further period to issue any compliance order or referral. Companies should plan for the full process, from the initial audit notification to final closure, to take between six and twelve weeks in straightforward cases; contested matters or those involving a referral for administrative proceedings take longer.

Q: What documents does a foreign company need to submit during a Russian data protection audit?

A: The precise document list varies by audit scope, but the core set invariably includes: the company's published privacy notice in Russian; its internal personal data processing policy; its written regulations for each processing system; evidence of data localisation compliance (confirmation of server location); consent records where consent is the legal basis; data processing agreements with third-party processors; and documentation of the appointment of the person responsible for personal data processing. For audits triggered by a breach notification, technical and organisational security documentation will also be required. Counsel should ensure all documents are current at the time of submission and consistent with one another — inconsistencies between a privacy notice and internal regulations are a common finding that prolongs the process.

Q: What happens if a company fails to respond to a Roskomnadzor audit request?

A: Failure to respond within the prescribed period, or a substantively inadequate response, may prompt Roskomnadzor to escalate from a documentary audit to an on-site inspection, to issue a compliance order in the absence of explanation, or to refer the matter directly for administrative proceedings. In administrative proceedings, the range of penalties available to the regulator has expanded, and the absence of engagement by the company is treated as an aggravating factor in the penalty calculation. It is also worth noting that a failure to engage does not halt the regulatory timeline — Roskomnadzor may proceed to impose a compliance order and, if that order is not complied with within the specified period, to impose further penalties for non-compliance with the order itself.

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