Russian employee data rules changed in 2027, affecting companies with Russian staff. What GCs at foreign companies need to know. Make an enquiry.
Following amendments to Russian personal data legislation that took effect in early 2027, companies employing staff in Russia face a materially revised set of obligations governing how they collect, store, and process employee personal data. The changes affect the scope of lawful processing grounds, the mechanics of employee consent, requirements for cross-border data transfers involving HR systems, and the administrative response powers available to Roskomnadzor, Russia's data protection regulator. For foreign-owned companies with Russian subsidiaries or locally employed staff, these are not abstract compliance questions: the new framework imposes stricter documentation standards and, in several areas, shorter remediation windows than under the prior regime.
The regulatory trajectory of Russian personal data law under Federal Law No. 152-FZ has, over several years, moved consistently in one direction: broader regulator powers, more granular consent requirements, and heavier documentation obligations on operators. The amendments that became operative in early 2027 continue that trajectory, but with two developments that are particularly consequential for employment-related processing.
The first concerns the lawful grounds for processing employee data. Under the framework as it stood before these amendments, employers could rely on a combination of statutory employment law grounds and employee consent to cover the majority of HR data flows. The 2027 amendments narrow the categories of processing that can be conducted on a statutory employment-law basis alone, without a separately documented consent. Processing of data that goes beyond what is strictly necessary for the performance of the employment relationship, or for compliance with Russian labour law obligations, now requires a standalone consent document that meets the updated formality requirements. This affects, in practice, a wider range of routine HR activities than employers may anticipate: performance management systems, internal benchmarking databases, wellbeing programmes, and certain uses of biometric attendance systems all fall into a zone that now requires closer examination.
The second development relates to cross-border data transfers in the HR context. Companies that route employee data through group-level HR platforms hosted outside Russia, or that transfer payroll data to a foreign parent's shared service centre, are subject to the transfer notification and documentation requirements under the amended regime. The prevailing regulatory position as of the date of this publication is that Roskomnadzor has indicated it will scrutinise HR-related cross-border transfers with greater attention than it applied in prior enforcement cycles. Operators are expected to demonstrate, documentarily, that the receiving jurisdiction provides an adequate level of data protection, or to rely on one of the recognised contractual mechanisms. In practice, timelines for obtaining regulator acknowledgements where notification is required have extended, and companies with pending group-level HR system migrations should factor this into project planning.
A third, more incremental change concerns breach notification obligations. The window within which an operator must notify Roskomnadzor of a personal data breach that involves employee data has been aligned with the general breach notification framework, which itself was tightened in preceding regulatory cycles. For in-house counsel managing incident response protocols across a group, this means ensuring that Russian subsidiary procedures are synchronised with the shortened notification timeline rather than the older, longer window that some legacy compliance programmes still reflect.
For an assessment of how these changes apply to your Russian HR data flows — make an enquiry: info@vetrovpartners.com |
The short answer, under the Russian law update on employee data processing, is that any foreign-owned entity that employs staff in Russia, or that operates an HR system which processes personal data of Russian-resident employees, is within scope. The practical exposure varies by operating model, but several categories of company face the most direct compliance implications.
Subsidiaries of foreign multinationals using group HR platforms are the most commonly affected. These companies typically route data including employment history, compensation details, performance records, and in some cases health-related data through a central platform administered outside Russia. Under the revised framework, each of these data categories is subject to specific processing ground requirements, and the cross-border transfer of HR data requires documented compliance with the transfer mechanism rules. A subsidiary that has not reviewed its data processing agreements with the group parent since the prior amendment cycle may be operating on a basis that no longer satisfies current requirements.
Representative offices and branches of foreign companies should note that the personal data obligations apply to them as operators in the same way they apply to Russian legal entities. The organisational form does not reduce the compliance obligation, and Roskomnadzor's enforcement record does not suggest any consistent pattern of reduced scrutiny for non-incorporated foreign presence structures.
Joint ventures where the foreign shareholder provides centralised HR or payroll services to a Russian entity create a specific structural issue: the service arrangement may constitute a transfer of employee data to a foreign operator, with attendant documentation requirements. In practice, this is an area where the regulatory position is still developing, and the safer approach is to treat such arrangements as subject to transfer compliance requirements unless specific guidance to the contrary has been obtained.
For in-house counsel at foreign parent companies, the risk that demands attention is not only the direct regulatory exposure of the Russian subsidiary, but also the group-level operational risk of non-compliant data flows being identified in the course of a Roskomnadzor inspection. Under the Russian regulatory update, the regulator has expanded its audit powers in ways that allow it to examine not just a specific processing activity but the broader data governance framework of the operator. A subsidiary with inadequate HR data processing documentation may, in an inspection, expose wider processing practices to regulatory scrutiny. This is the category of risk that compliance programmes built before the 2027 amendments may not adequately address.
"The 2027 amendments to Russian employee data processing rules widen the gap between what companies assumed their legacy HR consent frameworks covered and what the law now requires. The time to close that gap is before an inspection, not during one." — Elena Pavlova, Associate, Vetrov & Partners
For in-house counsel managing a Russian subsidiary whose HR compliance documentation has not been updated since the prior amendment cycle, the regulatory timeline for remediation leaves limited margin.
If your company operates an HR platform that transfers employee data across Russian borders — make an enquiry: info@vetrovpartners.com |
The practical response to these Russian law changes in the employee data processing context divides into three sequential priorities.
The first is a documentation audit. Existing employee consent forms, HR data processing policies, and records of processing activities should be reviewed against the updated requirements for processing grounds and consent formality. This is not a ceremonial exercise: the gap between legacy consent documentation and current requirements tends to be wider in companies that localised their compliance programmes quickly around an earlier amendment cycle and have not since re-examined the underlying documents. The audit should cover the Russian subsidiary specifically, not the group-level policy documents, which will typically not reflect Russian law requirements in the level of detail now required.
The second priority is an assessment of cross-border HR data transfer arrangements. For any transfer of Russian employee data to a foreign entity, the company should confirm that an adequate legal basis exists under the current transfer framework, that any required regulatory notifications are in place, and that contractual documentation between the Russian operator and the foreign recipient reflects the current mechanism requirements. Where a group HR platform migration is already in planning, data protection compliance should be incorporated as a workstream at the outset, not addressed as a post-implementation remediation item.
The third priority concerns breach notification procedures. The incident response protocol for the Russian subsidiary should be reviewed to confirm that internal escalation timelines allow the subsidiary to meet the external notification deadline to Roskomnadzor. Where the subsidiary's incident response procedures are embedded in a group-level policy designed around other jurisdictions' notification windows, a jurisdiction-specific annex or standalone Russian procedure may be required.
The Data Protection practice at Vetrov & Partners advises foreign-owned companies on Russian compliance programmes across all three of these areas. For a practical framework on the underlying HR data processing obligations, see also our practical guide to employee data processing and our case comment on recent Supreme Court guidance on employee data. Companies navigating Roskomnadzor inspections or seeking to align group HR governance with Russian requirements will also find the matters section of our website relevant to understanding how these questions arise in practice.
Q: What specifically changed in Russian employee data processing rules in 2027?
A: The principal changes effective in early 2027 concern three areas: the narrowing of statutory employment-law grounds for processing employee data without a separately documented consent; revised requirements for cross-border transfers of HR data, including through group-level HR platforms; and the alignment of employee data breach notification timelines with the shortened general framework. Companies that have not reviewed their HR data compliance documentation since a prior amendment cycle may find that their existing processing grounds and consent forms no longer satisfy current requirements. The changes do not affect companies' fundamental compliance architecture but do require targeted updates to documentation, consent mechanisms, and transfer arrangements.
Q: Which foreign companies with Russian operations are most directly affected by these changes?
A: The most directly affected are subsidiaries of foreign multinationals that use group HR platforms administered outside Russia, companies with cross-border payroll or shared-service arrangements involving Russian employee data, and joint ventures where a foreign shareholder provides HR services to a Russian entity. Representative offices and branches are subject to the same obligations as Russian legal entities. Companies whose HR data compliance programmes were last reviewed before the 2027 amendments came into effect should prioritise a documentation audit of their Russian subsidiary's processing grounds, consent forms, and cross-border transfer arrangements.
Q: What are the first practical steps for in-house counsel responding to these changes?
A: The recommended sequence is: first, audit existing employee consent forms and records of processing activities for the Russian entity against the updated requirements; second, review all cross-border HR data transfer arrangements to confirm the current legal basis and any required regulatory notifications; third, review breach notification procedures to ensure internal escalation timelines allow the Russian subsidiary to meet the regulatory notification deadline. Where group-level HR system changes are already planned, data protection compliance should be incorporated as a workstream from the outset. If external counsel support is needed for any of these steps, an initial enquiry can be directed to info@vetrovpartners.com.
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