Roskomnadzor can inspect foreign companies operating in Russia with limited notice. What in-house counsel needs to know about each stage. Make an enquiry.
Unlike data protection supervisory authorities in many EU jurisdictions, which typically signal an investigation well in advance and follow a structured pre-notification sequence, Roskomnadzor — Russia's federal authority for the supervision of personal data processing — operates under a regime that can move from routine monitoring to a formal inspection order within weeks. For the general counsel of a foreign company with a Russian subsidiary, branch, or operational presence, understanding how that sequence unfolds, what triggers it, and where the critical procedural windows fall is not a background compliance concern. It is live operational risk management.
This guide sets out the five stages of a Roskomnadzor enforcement or inspection procedure as they apply in practice to foreign companies, including the documents you need to have ready before the process begins. For a broader treatment of personal data obligations under Russian law, see the firm's Data Protection practice page.
Before examining each procedural stage, in-house counsel should confirm the following baseline is in place. These items form the evidential foundation on which every subsequent response depends.
The absence of any item on this list — in particular the server localisation confirmation and the processing records — is one of the most common findings in Roskomnadzor inspections of foreign-linked entities. For in-house counsel managing a Russian entity remotely, verifying these items should not wait for an inspection order to arrive.
If your Russian entity has not undergone a data protection compliance audit, the time to act is before Roskomnadzor selects you for inspection — not after. Make an enquiry: info@vetrovpartners.com |
Russian data protection legislation applies to any operator that processes personal data of Russian citizens — regardless of where that operator is incorporated or headquartered. A company does not need a registered legal entity in Russia to fall within scope: operating a Russian-language website that collects user data, running a mobile application used by Russian nationals, or employing staff in Russia under a service arrangement are each capable of bringing an operator within Roskomnadzor's supervisory remit.
For companies with a Russian legal entity — a subsidiary (OOO or AO), a representative office, or a branch — the position is straightforward: the Russian entity is a data operator subject to the full compliance framework, including the localisation requirement and the notification obligation. The parent company's policies and technical infrastructure do not, as a matter of Russian law, discharge the obligations of the Russian legal entity. This is a distinction that causes difficulty in practice when a multinational's global DPO function assumes responsibility for Russian compliance without understanding the entity-level regulatory position.
For guidance on the underlying personal data obligations imposed by Federal Law No. 152-FZ, see Federal Law 152-FZ personal data requirements for foreign companies.
Roskomnadzor's enforcement activity begins, in most cases, not with a formal inspection but with monitoring. The regulator maintains a continuous programme of remote monitoring — reviewing publicly accessible websites, application store listings, and publicly filed documents for indicators of non-compliance. Complaints from data subjects, referrals from other regulatory bodies (including the Federal Security Service), and press coverage of data incidents are all documented trigger events.
The most common triggers in practice are: a complaint from a data subject that their personal data was transferred abroad without an adequate legal basis, the absence of a compliant privacy policy in Russian, evidence that personal data of Russian citizens is stored on servers outside Russia, and notification of a data breach reported (or not reported) by the operator itself.
An operator is not typically notified that it is under monitoring. The first formal contact from Roskomnadzor may therefore be a request for information (zapros) rather than an inspection order. Understanding the difference matters: a request for information is a lower-intensity instrument, but the response window is shorter than many foreign in-house teams expect, and a failure to respond — or an inadequate response — is itself a ground for escalation to a formal inspection.
Where monitoring or a complaint discloses a potential violation, or where the operator fails to respond adequately to a request for information, Roskomnadzor may issue a formal inspection order (prikaz o proverke). Inspections fall into two categories: scheduled (planovye) and unscheduled (vneplanovye). Scheduled inspections are published in an annual plan; unscheduled inspections may be initiated without advance publication and with a notice period that is, in practice, considerably shorter.
Note: Under the Russian framework governing state inspections, operators subject to a formal inspection order have a defined window within which they may challenge the legal basis for the inspection before the administrative or arbitrazh court. This window is narrow and runs from the date of receipt of the order — not from the date the order was issued. Foreign-linked entities that receive an inspection order and do not respond within the applicable period risk waiving procedural objections that could otherwise limit the scope of the inspection. In practice, timelines vary by inspection category, but operators should treat the response period as measured in days, not weeks.
This is the stage at which the regulatory risk crystallises. Roskomnadzor inspectors have authority to require the operator to produce documentary evidence, attend interviews, and provide access to information systems. Non-cooperation is not a neutral option: it is a separate ground for liability and may be treated as an aggravating factor in any subsequent penalty proceeding.
For in-house counsel managing this stage, the immediate priorities are: confirm receipt of the order and the applicable response window; instruct local Russian counsel immediately; begin assembling the documentary evidence most likely to be requested (processing records, consent forms, localisation confirmation, notification filing); and ensure that no information is destroyed, altered, or withheld.
Receiving a Roskomnadzor inspection order without local counsel already engaged is one of the most avoidable sources of procedural disadvantage. If your entity operates in Russia without a standing local counsel relationship, make an enquiry now: info@vetrovpartners.com |
The inspection itself may be conducted on-site (at the operator's Russian premises) or as a documentary inspection (documentary verification of submitted materials without a site visit). The form is specified in the inspection order. For foreign-linked entities — particularly those operating through a small representative office or a branch — a documentary inspection is the more common form, but this should not be taken as a signal of lower regulatory intensity. The documentary record produced at this stage forms the evidentiary basis for any penalty proceeding that follows.
Inspectors will typically request: the operator's personal data processing policy and internal regulations; records of processing activities and their legal bases; data processing agreements with third parties; evidence of server localisation; records of cross-border data transfers and their legal bases (consent, adequacy, or contractual clauses); and evidence of any data breaches and the steps taken in response.
The inspection has a defined statutory duration. Extensions are possible but require a formal order. If inspectors request materials not specified in the original order, the operator is entitled to seek clarification in writing. Keeping a contemporaneous record of every inspector request — and the operator's response — is important practical discipline at this stage, as these records form part of the administrative file.
For a detailed analysis of how Russian courts and the regulator have approached localisation and cross-border transfer requirements, see Russian Supreme Court clarification on Roskomnadzor enforcement practice.
At the conclusion of the inspection, Roskomnadzor issues a formal act (akt proverki) setting out the findings. Where violations are identified, the act is accompanied by a mandatory order (predpisanie) requiring the operator to remedy the identified deficiencies within a specified period.
The operator has the right to submit objections (vozrazheniya) to the inspection act within the period specified in the applicable procedural rules. This is not a formal appeal — it is an administrative objection, logged in the file. Where the operator disputes the findings on factual or legal grounds, a well-constructed written objection can influence the scope of the remediation order and, in some cases, the categorisation of the violation. In practice, this step is underused by foreign operators who do not have local counsel engaged at this stage.
Compliance with the mandatory order must be documented and confirmed to Roskomnadzor within the period specified. Failure to comply, or partial compliance without adequate documentation, is treated as a continuing or aggravated violation and is a direct path to a court referral for the imposition of penalties.
Where the inspection findings disclose violations and the operator fails to remedy them within the prescribed period — or where the violations are of a nature that attracts immediate penalty referral — Roskomnadzor initiates administrative liability proceedings. These proceedings are conducted under the Russian Code of Administrative Offences. The regulator prepares an administrative offence protocol, which is then submitted to the competent court (typically the magistrate's court or, for legal entities, the arbitrazh court, depending on the category of violation and the entity type).
Penalties under the current framework are tiered by violation category and operator type. Repeat violations, failures to comply with a mandatory order, and violations involving sensitive categories of personal data or data breaches that were not reported attract higher penalty ranges. The court is the decision-maker on penalty quantum, not Roskomnadzor itself, and the operator has the right to be heard and to submit evidence in mitigation. A well-documented compliance history — even partial compliance — is relevant to penalty quantum at this stage.
The penalty proceeding does not extinguish the remediation obligation. Even after a penalty is imposed, the operator remains under a continuing obligation to bring its processing into compliance. A second inspection may follow to verify remediation.
In proceedings before the arbitrazh court, foreign-linked entities with Russian legal representation are in a stronger procedural position than those attempting to engage remotely. See the firm's matters page at /matters/ for examples of regulatory and enforcement proceedings in which the firm has acted for foreign companies.
Q: How much advance notice does Roskomnadzor give before an inspection? A: The notice period depends on the inspection category. Scheduled inspections are included in an annual plan published by Roskomnadzor, giving operators advance visibility. Unscheduled inspections may be initiated without prior publication and may arrive with significantly shorter notice — in some cases, the operator's first formal contact is the inspection order itself. Foreign companies without a standing local counsel relationship in Russia should not assume that the notice period provides sufficient time to prepare a compliant documentary response from scratch. The baseline compliance documentation described in the checklist above must be in place before any inspection is initiated.
Q: What documents does Roskomnadzor typically request in a personal data inspection? A: In practice, inspectors most commonly request the operator's personal data processing policy, internal regulations governing personal data handling, records of processing activities and their legal bases, data processing agreements with third parties, evidence confirming server localisation within Russia, documentation of any cross-border data transfers and their legal bases, and records of any data security incidents and the operator's response. For foreign-linked entities, evidence of how the Russian legal entity's obligations are distinguished from those of the parent group is also commonly examined. Operators who cannot produce these documents promptly are at a structural disadvantage during the inspection.
Q: What happens if a foreign company does not comply with a Roskomnadzor mandatory order? A: Non-compliance with a mandatory remediation order issued following an inspection is treated as a continuing violation and is the primary basis on which Roskomnadzor initiates administrative penalty proceedings before the competent court. Penalties are imposed by the court, not the regulator, and the operator has the right to submit evidence in mitigation — including evidence of partial or ongoing compliance efforts. However, non-compliance without a documented remediation plan or legal challenge to the order's basis is the outcome most likely to result in the higher end of the applicable penalty range. A second inspection to verify compliance may follow the conclusion of penalty proceedings.
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