Foreign companies with Russian staff must comply with Federal Law No. 152-FZ on personal data. Key obligations explained. Make an enquiry.
Unlike data protection regimes in the EU, which consolidate employer obligations under a single instrument with well-established supervisory guidance, Russian law imposes a distinct and separately administered framework on every organisation that processes personal data on Russian territory. For foreign companies operating a Russian subsidiary, employing Russian-resident staff, or processing employee records that touch Russian jurisdiction, Federal Law No. 152-FZ on Personal Data is not an optional compliance overlay — it is the operative legal baseline. The supervisory authority is Roskomnadzor, and its enforcement posture has sharpened measurably in recent years. This guide sets out the five practical steps that in-house counsel should work through when assessing or building a compliant employee data processing function in Russia.
Before addressing specific obligations, it is worth establishing which entities within a corporate group are caught by Russian data protection law. The framework applies to any operator that processes personal data — defined broadly — in Russia. A foreign parent that processes records of Russian-resident employees through a Russian subsidiary, or that receives employee data from a Russian legal entity, will typically be within scope. The legal exposure runs to the Russian entity, but group-level policies and system architecture have direct practical consequences.
A basic readiness review should cover:
Addressing these five points before formal compliance work begins significantly reduces the risk of structural remediation at a later stage.
For in-house counsel assessing the scope of Russian data protection exposure for the first time — make an enquiry: info@vetrovpartners.com |
Russian data protection legislation recognises several legal grounds for processing personal data. In an employment context, the most commonly applicable are: the performance of the employment contract, a statutory obligation incumbent on the employer under Russian labour legislation, and — in certain limited circumstances — the employee's written consent.
The relationship between these grounds matters in practice. Russian law takes a narrow view of consent in the employment context: where processing is necessary to fulfil an employment contract or a statutory employer obligation, reliance on consent alone is considered procedurally inadequate. Consent is, however, required for certain categories of sensitive data — notably health information where processed beyond what is strictly necessary for occupational safety purposes — and for any processing that falls outside the scope of the direct employment relationship.
For each category of employee data that an organisation processes, counsel should document the applicable legal ground and ensure that internal data processing policies reflect that mapping. This documentation becomes relevant if Roskomnadzor conducts an inspection or if a data subject makes a complaint.
Russian law imposes a set of baseline obligations on every data operator regardless of the size of the organisation or the volume of data processed. The principal obligations that arise in an employment context are:
Foreign companies running a single Russian subsidiary sometimes assume that group-level policies drafted for EU or US compliance are sufficient. In practice, they are not — Russian requirements differ on notification timing, consent language, and internal documentation structure.
The practical focus for most in-house teams at this stage is documentation. Russian data protection law sets out a specific set of internal instruments that every operator must have in place. These include:
The documentation set is not a formality. Roskomnadzor inspections routinely begin with a review of these instruments. Organisations that cannot produce a current and complete documentation set at the point of inspection face immediate exposure to administrative findings, irrespective of whether any breach of employee rights has occurred.
Firms advising clients with Russian operations will often need a confirmed Russian counsel relationship before documentation reviews become urgent. Request our practice review: info@vetrovpartners.com |
The data localisation requirement is the obligation that most frequently creates practical difficulty for foreign corporate groups. The rule applies from the point at which personal data of a Russian citizen is first collected — whether through an employment contract, an onboarding form, a payroll record, or a time-tracking system. The primary database must reside on Russian territory.
Several configurations arise in practice. A Russian subsidiary that stores all employee data locally and transmits only anonymised or aggregated data to a foreign parent generally has the most straightforward compliance position. A subsidiary that relies entirely on a foreign-hosted cloud HR platform — without any Russian-territory mirroring — typically does not. Hybrid configurations, where a Russian database is maintained as the primary record and the foreign platform functions as a downstream system, are the most common workable arrangement; however, the data flows must be carefully mapped and documented to sustain that characterisation.
Biometric data — including facial recognition data used in access control systems, fingerprint records, and similar identifiers — is subject to more stringent localisation requirements and cannot be transmitted cross-border without specific justification under Russian law.
Foreign companies that have not yet audited their HR technology stack against Russian localisation requirements carry a material compliance gap. Remediation can be technically straightforward but requires procurement decisions and system reconfiguration that take time to implement. The regulatory timeline does not accommodate delay: Roskomnadzor has the authority to issue binding orders requiring immediate cessation of non-compliant processing.
Russian data protection legislation imposes requirements on the cross-border transfer of personal data that are distinct from — and in certain respects more prescriptive than — those under the GDPR. A transfer is defined as any transmission of personal data to a foreign state or to a foreign entity.
The general rule is that cross-border transfers are permissible to states that provide adequate protection of personal data rights, as assessed by Roskomnadzor. A list of adequate jurisdictions is maintained and updated. Transfers to states not on the list — which include a number of jurisdictions in which multinational groups commonly locate their regional HR functions — require additional justification: either the data subject's specific consent to the transfer, or the conclusion that the transfer is necessary for the performance of the employment contract.
For routine HR reporting from a Russian subsidiary to a foreign parent, the most commonly applied basis is contractual necessity. Counsel should document the specific categories of data transferred, the frequency and mechanism of transfer, and the contractual relationship that justifies it. This documentation should be maintained at the Russian entity level and be available for Roskomnadzor review.
One significant practical point: a cross-border transfer does not override the data localisation requirement. The primary database must remain in Russia even if the data is also processed abroad. These are cumulative obligations, not alternatives.
For a detailed examination of the rules governing cross-border transfers, including the post-2022 amendments to the applicable framework, see our related briefing on employee data processing in Russian companies.
Regulatory engagement is the practical endpoint of any compliance programme. Roskomnadzor conducts scheduled and unscheduled inspections of data operators. For foreign-owned Russian entities, the risk profile is not lower than for domestic companies — and in practice, foreign ownership may attract closer scrutiny in inspections driven by data localisation concerns.
An inspection will typically examine: operator notification status, the existence and currency of internal documentation, the technical and organisational measures in place to protect personal data, and evidence of compliance with localisation and cross-border transfer requirements. Inspectors may request to review system architecture diagrams, data processing agreements with third-party processors, and consent forms.
The incident response obligation is equally important. Russian law requires data operators to notify Roskomnadzor within a short statutory window following discovery of a personal data breach. The specific timelines and notification content are defined in implementing rules and have been tightened in recent legislative cycles. Organisations that have not tested their incident response procedures against Russian statutory requirements — as distinct from their GDPR notification procedures — should treat this as a priority.
For an analysis of recent Roskomnadzor enforcement trends in the employment context, including the Supreme Court's approach to employee data disputes, see our case comment at Russian Supreme Court rules on employee data.
The firm's Data Protection practice assists foreign companies at each stage of this process, from initial scoping through documentation implementation and regulatory engagement. Representative matters are published on the firm's Matters page.
For in-house counsel managing a Russian subsidiary with unresolved data protection exposure — the regulatory timeline leaves limited margin for delay. Make an enquiry: info@vetrovpartners.com |
Q: How long does it typically take to bring a Russian subsidiary into compliance with Federal Law No. 152-FZ for employee data?
A: The timeline depends principally on two factors: the complexity of existing HR systems and the extent of documentation already in place. For a subsidiary with a straightforward data architecture — local HR records, standard employment contracts, no biometric processing — a structured compliance project typically takes between six and twelve weeks. Organisations that rely on foreign-hosted HR platforms and have not addressed data localisation should plan for a longer remediation period, as system changes and procurement decisions add time. Notification to Roskomnadzor of operator status should be completed before any other processing steps are taken.
Q: What documents must a Russian subsidiary produce for a Roskomnadzor inspection?
A: Inspectors will ordinarily expect to review the operator notification, the publicly accessible personal data processing policy, the internal regulation on personal data processing, the list of authorised persons and their access levels, data processing agreements with any third-party processors, and, where consent is the legal basis for processing, the consent forms used and records of their execution. For subsidiaries of foreign groups, inspectors may also ask to see documentation of cross-border transfer arrangements and evidence of the basis on which transfers are made.
Q: Does a foreign parent company have direct obligations under Russian data protection law, or only the Russian subsidiary?
A: The direct obligations under Russian data protection legislation rest on the entity acting as data operator — in most group structures, this is the Russian legal entity. However, the foreign parent can have indirect exposure in several ways. Where the parent processes employee data received from the Russian entity (for example, through a group HR platform), it may itself qualify as an operator or processor under Russian law, depending on the nature and purpose of that processing. Additionally, group-level policies, system architecture decisions, and contractual arrangements made at parent level directly affect whether the Russian entity can achieve and maintain compliance. In-house counsel at the parent company should treat Russian data protection requirements as a group-level governance matter, not a purely local one.
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