Foreign companies with Russian operations face Roskomnadzor audit risk under 152-FZ. A structured compliance programme reduces exposure. Make an enquiry.
Following the 2022–2024 wave of amendments to Russian personal data legislation, foreign companies operating in Russia face a data protection audit and compliance environment that has shifted materially from the framework many in-house counsel assessed at market entry. Roskomnadzor – the federal regulator responsible for personal data supervision – has expanded its inspection programme, and the consequences of non-compliance now extend beyond administrative fines to include processing restrictions, mandatory database localisation requirements, and, in serious cases, court-ordered suspension of data processing activities. For in-house counsel managing a Russian subsidiary or a cross-border data flow touching Russian nationals, a structured 152-FZ compliance programme is no longer optional infrastructure: it is the primary instrument for controlling regulatory exposure.
Before initiating a formal data protection audit or responding to a Roskomnadzor inspection, confirm that the following documentation exists and is current:
This checklist applies to Russian legal entities and to foreign entities processing personal data of individuals located in Russia. A foreign company that collects data through a Russian-facing website, mobile application, or commercial agreement may be within the scope of Russian personal data legislation regardless of where its servers are located.
If your organisation's compliance documentation is incomplete or has not been reviewed since the 2023–2024 amendments, this is the appropriate point to seek a gap assessment — make an enquiry: info@vetrovpartners.com |
The foundation of any data protection audit in Russia is an accurate and complete map of what personal data the organisation processes, on what legal basis, and through which technical and organisational systems.
Begin by identifying each processing activity in the business: HR data of Russian employees, customer or subscriber data, supplier and contractor contact data, CCTV or biometric data (if applicable), and any marketing or analytics processing. For each activity, confirm: the processing purpose; the category of data subjects; the data categories involved (ordinary personal data, special categories, or biometric data — each category attracts a different compliance intensity); the legal basis under Russian law; and the retention period.
The legal bases available under Russian personal data legislation are narrower in practice than their formal list suggests. Consent is frequently used, but Russian courts and Roskomnadzor have increasingly scrutinised consent forms that are excessively broad or bundled with general terms and conditions. Contract performance and legitimate interests operate differently under Russian law than under the GDPR framework that many in-house counsel use as a reference point. Do not assume GDPR compliance maps directly onto 152-FZ compliance — the two regimes overlap in structure but diverge in procedural requirements.
Once the processing map is complete, it becomes the core working document for every subsequent step of the audit.
Data localisation is the single most operationally significant requirement for foreign companies under Russian data protection law. The requirement is that personal data of Russian nationals must be recorded, systematised, accumulated, stored, clarified, and extracted using databases physically located within the Russian Federation. This is not a prohibition on cross-border transfer; it is a sequencing requirement. The data must first be stored locally before it is transferred abroad.
In practice, this means that cloud infrastructure decisions, CRM deployments, ERP configurations, and HR system architectures all carry localisation compliance implications. The firm has seen situations where a foreign parent's group-wide SaaS rollout inadvertently routed Russian employee or customer data through servers outside Russia at the point of initial collection — a configuration that regulators have treated as a localisation violation regardless of whether the data was later replicated to a Russian instance.
Confirm the following for each processing system:
Roskomnadzor has authority to block access to information systems that fail to meet localisation requirements. Enforcement has historically been applied to large platforms, but the inspection programme as of early 2026 extends to commercial operators including foreign subsidiaries.
Consent is a legal basis under Russian personal data legislation, but it is not interchangeable with GDPR-style consent. Russian regulatory practice has developed specific expectations that differ in several respects from the framework most foreign in-house counsel will be familiar with.
Under the regulatory approach applied by Roskomnadzor and reflected in court practice, consent must be: specific to each processing purpose (bundled or blanket consent is routinely challenged); freely given without conditioning access to a service on consent to processing that is not necessary for that service; expressed in writing or electronic form that allows the data subject to identify what they are agreeing to; and capable of being withdrawn, with a mechanism for withdrawal that is at least as accessible as the mechanism for giving consent.
Special categories of personal data — including health data, biometric data, racial or ethnic origin, religious or political views — require explicit written consent, and the bar for what constitutes valid explicit consent is applied strictly. In practice, a consent form that satisfies this standard will be longer, more specific, and more procedure-heavy than the equivalent under GDPR. Review existing consent documentation against current Roskomnadzor guidance rather than against GDPR compliance templates.
For processing based on legal bases other than consent — contract performance, statutory obligation, legitimate interests — confirm that the legal basis is correctly identified in the processing register and that the applicable basis is one that Russian law recognises for that processing purpose. Substituting consent for a statutory obligation basis, for example, can create problems if the data subject later withdraws consent and the company has no fallback basis.
For in-house counsel managing a Russian data compliance programme from abroad, confirming the consent and legal-basis architecture is a common gap — make an enquiry: info@vetrovpartners.com |
A Roskomnadzor inspection — whether scheduled (planovaya) or unscheduled (vneplanovaya) — follows a defined procedural sequence. Understanding the sequence helps an organisation prepare rather than react.
The regulator issues an inspection notice specifying the scope and the documents to be produced. The initial documentary review covers the organisation's data processing register, public-facing privacy documentation, consent forms, and cross-border transfer instruments. Inspectors examine whether the documentation covers all actual processing activities — a common gap is that the formal documentation predates a system migration or a new product launch and no longer reflects live processing.
If documentary gaps are identified, Roskomnadzor issues a compliance instruction (predpisanie) specifying the deficiency and a remediation timeline. Failure to remedy within the specified period can result in an administrative protocol being drawn up. The administrative protocol is the precursor to an administrative case, which is adjudicated either by Roskomnadzor itself (for matters within its administrative jurisdiction) or referred to a court.
Courts considering data protection administrative cases assess: whether the company had a data protection compliance programme in place at the time of the inspection; whether it cooperated with the regulator during the inspection process; whether any violation was of a continuing or one-off nature; and whether remediation steps were taken between the inspection and the administrative hearing. A documented, functioning compliance programme — even if it contained gaps — is consistently treated as a mitigating factor in administrative proceedings. An absence of any compliance documentation is consistently treated as an aggravating factor.
Under Russian law, foreign companies operating in Russia directly — rather than through a subsidiary — may face additional requirements to designate a representative authorised to interact with Roskomnadzor on compliance matters. This is an area of active regulatory development, and the position has shifted since the 2022–2024 amendments. Seek current advice before assuming prior compliance positions remain valid.
Note: Roskomnadzor may initiate an unscheduled inspection in response to a data subject complaint or a data incident notification without prior notice requirements applying. Organisations that have experienced a data incident should prepare for the possibility of an inspection concurrent with the incident response process.
The audit process described in the preceding steps is not a one-time exercise. Russian data protection law requires operators to maintain ongoing compliance, and Roskomnadzor's inspection methodology explicitly evaluates the sustainability of compliance arrangements rather than just point-in-time conformity.
A documented compliance programme for a foreign company with Russian operations will typically include the following structural elements:
Each of these elements should be documented in a form that can be produced to an inspector. A compliance programme that exists only in the knowledge of a single compliance officer, without written policies and training records, provides substantially less regulatory protection than one that is formally documented.
For groups that have implemented GDPR programmes, the Russian compliance programme can be structured as a parallel track that maps onto the existing governance framework. The terminology differs, the legal bases differ, and some procedural requirements have no GDPR equivalent, but the overall governance logic — accountability, documentation, access rights, incident response — is comparable. An efficient approach for most in-house counsel is to use the GDPR programme as the architectural template and then audit each element against Russian requirements, recording where the Russian position diverges.
For organisations building or reviewing a data protection compliance programme for Russian operations, an initial review call helps identify the most significant gaps efficiently — make an enquiry: info@vetrovpartners.com |
Q: How long does a Roskomnadzor scheduled inspection typically take, and what happens if the organisation is not ready? A: A scheduled inspection typically runs for 20 working days from the date of the inspection order, though the period can be extended in more complex matters. Roskomnadzor will specify the documents required at the outset. If the organisation cannot produce requested documentation within the inspection window, this is treated as non-compliance with the inspector's request — an independent administrative violation in addition to any underlying substantive gaps. Organisations that receive an inspection notice and identify gaps in their documentation should take immediate steps to prepare remediation evidence, even if the documentation itself cannot be completed within the window. A documented remediation plan, presented cooperatively, is treated more favourably than a failure to engage.
Q: Does a foreign company that has no Russian legal entity but processes data of Russian individuals need to comply with Russian data protection law? A: The territorial scope of Russian personal data legislation extends to operators that process personal data of individuals located in Russia, regardless of where the operator is incorporated or where its infrastructure is located. A foreign company providing services to Russian individuals through a website, application, or platform — without a Russian subsidiary — may be within scope. The practical enforceability of regulatory action against a purely foreign entity is more limited than against a Russian legal entity, but the compliance obligation exists in law, and registration requirements for foreign operators interacting with Russian data subjects have been expanding. Foreign companies considering or maintaining Russia-facing activities should take a position on scope and document the reasoning.
Q: What is the most common gap identified in data protection audits of foreign subsidiaries in Russia? A: In practice, the most frequently identified gap is the localisation configuration — specifically, a disconnect between the formal localisation policy (which states that Russian data is stored locally) and the actual technical architecture (where a parent-group system routes initial data collection through infrastructure outside Russia). The second most common gap is consent documentation that predates the 2022–2024 amendments and does not meet current Roskomnadzor expectations for specificity and withdrawability. Both gaps are remediable, but remediating the localisation gap in particular can involve significant technical project work, which reinforces the case for identifying and addressing it before, rather than during, an inspection.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry