Russian data protection law sets strict limitation periods on audit obligations. Key deadlines for in-house counsel to track. Make an enquiry.
Under Russian personal data legislation, the clock governing regulatory and judicial exposure begins running well before Roskomnadzor issues a formal notice. For foreign companies conducting a data protection audit or building a compliance programme in Russia, the limitation framework under Federal Law No. 152-FZ and the Code of Administrative Offences is the least-discussed but most consequential element of the procedural landscape. Missing a limitation period does not merely affect timing — it determines whether corrective action is still viable, whether a fine is challengeable, and whether voluntary remediation extinguishes or merely reduces liability.
Russian data protection law establishes distinct limitation periods depending on the type of violation and the enforcement pathway involved. The general limitation period for administrative liability in data protection matters runs from the date of the violation — not from the date of detection. This distinction is material for in-house counsel: a processing activity that was non-compliant for an extended period may attract liability for the full duration, and the period for bringing an administrative case typically begins from the moment the offending act or omission occurred or, for continuing violations, from the date it is discovered by the authority.
For violations characterised as continuing — for example, the ongoing absence of a mandatory privacy policy or the persistent failure to appoint a responsible person for personal data processing — the limitation clock runs from the day the violation is formally recorded. In practice, this means the limitation period on a continuing violation may be extended significantly beyond what operators assume, since Roskomnadzor retains discretion to treat each inspection as triggering a fresh limitation period for ongoing non-compliance.
Judicial challenge to an administrative penalty follows its own timetable. A company served with an administrative resolution has a limited window to challenge that resolution through the arbitrazh court system. The period is short relative to what foreign practitioners commonly expect from Russian court timelines, and missing it effectively renders the fine unappealable without a separate procedural restoration application.
Note: An administrative penalty not challenged within the prescribed statutory period becomes enforceable in full. Roskomnadzor may refer the enforcement file to the Federal Bailiffs Service without further warning. Foreign companies operating through a Russian subsidiary should ensure that the in-house function responsible for regulatory correspondence has a documented process for tracking resolution receipt dates and escalating to external counsel within the challenge window — not after it.
Roskomnadzor's published guidance and the pattern of arbitrazh court decisions in data protection enforcement matters indicate several recurring features that in-house counsel should build into a compliance programme.
First, the authority has consistently treated data processing without consent, data retention beyond the stated purpose, and the failure to fulfil subjects' requests for deletion as separate and independently actionable violations. Each instance carries its own limitation analysis. A single audit may therefore uncover multiple violations with overlapping but distinct limitation periods — requiring disaggregated tracking rather than a single programme-wide limitation assessment.
Second, Russian court practice in data protection cases shows that mitigation — including self-initiated corrective action, voluntary submission of an updated privacy notice, or post-violation appointment of a data protection officer equivalent — has been taken into account in penalty calibration, but only when the corrective measures were completed before the administrative resolution was issued. Corrective action taken after the resolution carries significantly less weight in a judicial challenge. The procedural implication is that remediation timelines in a compliance programme must be front-loaded relative to the regulatory timeline, not reactive to it.
Third, for cross-border data transfer violations — including the failure to comply with data localisation requirements under the amendments to Federal Law No. 152-FZ that took effect in stages — enforcement practice has developed further than for many other categories of violation. Courts have been willing to examine whether the primary storage obligation was met and whether any foreign transfers were genuinely incidental to localised processing. In-house counsel at foreign companies with data flows between a Russian entity and a parent or affiliated company outside Russia should treat this category as subject to active enforcement, with the limitation analysis conducted on each transfer category separately.
For in-house counsel managing a Russian subsidiary's data protection exposure, the limitation framework makes early legal review a material risk-management step, not an optional compliance exercise. To discuss a data protection audit or compliance programme review — make an enquiry: info@vetrovpartners.com |
The following steps reflect current procedural practice and the limitation analysis set out above. They are directed to in-house legal and compliance teams at foreign companies with Russian data processing operations.
Map violations by type before mapping them by severity. Distinguish point violations (non-compliant processing on a specific date) from continuing violations (ongoing absence of required documentation or measures). Each category attracts a different limitation analysis.Record the date on which each identified violation was first capable of detection, not merely the date it was discovered in the current audit cycle. This affects limitation exposure assessment.For any administrative resolution already received, calculate the challenge deadline immediately and brief external counsel before taking any internal position on whether to pay or contest the fine.Complete substantive remediation — updated privacy notices, consent mechanisms, data transfer agreements, and localisation confirmations — before, not after, any anticipated Roskomnadzor inspection or follow-up audit. Post-resolution remediation carries materially reduced procedural value.Maintain a written limitation register as a standing document within the compliance programme. This register should record the violation type, the date of occurrence (or commencement of continuing violation), the statutory limitation period applicable, the expiry date, and the current status of remediation. The register should be reviewed and updated at each internal audit cycle.
For broader context on the enforcement environment in which these limitation periods operate, see Roskomnadzor enforcement trends in data protection and How Russian courts approach data protection disputes.
The firm's Data Protection practice advises foreign companies on audit design, compliance programme construction, and regulatory defence before Roskomnadzor and in the arbitrazh court system.
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