Employee Data Transfers Within Russian Holdings: Why Affiliates Count as Third Parties Under 152-FZ
Russian companies frequently move employees between legal entities inside a single holding, yet 152-FZ on personal data treats each employer as an independent operator. This creates strict consent requirements even when staff remain in the same office and report to the same management.
Core Legal Position
Under paragraph 2 of Article 3 of 152-FZ, an operator is any entity that independently determines the purposes of processing. The law contains no concept of a “group of companies,” so ООО «Торговый дом» and ООО «Логистика» are two separate operators. Article 88 of the Labor Code reinforces this by stating that an employer may disclose employee data to a third party only with written consent, except where statute provides otherwise. Internal transfers within one legal entity are permitted under a local normative act, but movement to a neighboring legal entity crosses the boundary.
Five Practical Routes
The article maps five decision points that allow organizations to complete transfers lawfully or avoid data exchange altogether.
Route 1 – Invitation Letter Routed Through the Employee
The receiving company issues a written invitation to the employee. The employee then submits a resignation request to the current employer citing transfer under part 2 of Article 72.1 of the Labor Code. No direct correspondence between the two companies is required. This route relies on paragraph 5 of part 1 of Article 6 of 152-FZ, which permits processing when a contract is concluded at the initiative of the data subject.
Route 2 – Documents Obtained Directly from the Employee
Under Article 62 of the Labor Code the outgoing employer must issue certified copies of orders, salary certificates and other documents within three working days upon written request. On the last day of work the employee receives either an electronic employment record (СТД-Р) or the paper work book. The employee then presents these documents to the new employer exactly as any external hire would. No data crosses between the two companies.
Route 3 – Retention by the Former Employer
After termination the former employer may continue processing data for statutory accounting, tax and archival purposes under paragraph 2 of part 1 of Article 6 of 152-FZ. Personal files are retained for 50 or 75 years according to Rosarkhiv Order No. 236. Archival storage falls outside the scope of 152-FZ pursuant to paragraph 2 of part 2 of Article 1.
Route 4 – Shared Systems and Access Controls
Access to joint HR systems such as 1C ЗУП or access-control databases must be limited to authorized personnel of each legal entity. Biometric data used for physical access triggers Article 11 of 152-FZ and generally requires fresh written consent from the employee for the new employer.
Route 5 – Central HR Entity Acting Under a Processing Agreement
When a parent company performs HR functions for multiple subsidiaries, the relationship is characterized as data processing on behalf of the employer (part 3 of Article 6 of 152-FZ). A written data-processing agreement is mandatory. Roskomnadzor guidance indicates that employee consent is still advisable to avoid disputes.
Consent Requirements and Risks
Consent must be documented separately from the employment contract, list specific recipients, purposes and categories of data, and comply with the new separation rule effective 1 September 2025. Failure to obtain proper consent may result in administrative fines of 150,000–300,000 rubles under part 1 of Article 13.11 of the Code of Administrative Offenses, or 300,000–700,000 rubles under part 2 when written consent was required. Employees may also seek moral damages under Article 24 of 152-FZ.
Template Consent Language
The article supplies a model consent form that names both legal entities, lists the exact data items transferred, states the purpose of оформление перевода, and references part 2 of Article 72.1 of the Labor Code.
Related articles
Unconfirmed Reports of Steam Blockade in Russia: Valve Faces User Data Demands and Tax Scrutiny
On November 16, media outlets and Telegram channels reported that Russian authorities are demanding user data from Valve's Steam platform, including accounts registered in Kazakhstan, while threatening to block the service. The claims also suggested plans to track undeclared income from high-value in-game skins, but no official statements or documents have confirmed these assertions. The original source was an analytical piece by ProFinance that cited unnamed sources without specifying any government agency, official, or legal document. Roskomnadzor, the Federal Tax Service, and other agencies have made no such announcements, and Valve has not confirmed receiving any requests. Confirmed information is limited to tax payments: Kazakhstan's Committee of State Revenues reported that Valve paid approximately 2 billion rubles in VAT for the first half of 2026, the highest among foreign internet companies. This amount more than doubled compared to the same period in 2025, attributed to Russian users relocating their accounts to the Kazakh region after Visa and Mastercard exited Russia. Vice Speaker of the State Duma Vladislav Davankov opposed any potential blockade, comparing it to freezing bank deposits, and pledged to raise the issue at the Duma session on November 17.
Russia's MinTsifry Mandates Qualified Electronic Signatures for Remote eSIM Registration to Combat Fraud
Russia's Ministry of Digital Development has directed telecom operators to allow remote eSIM issuance and contract signing exclusively through enhanced qualified electronic signatures (UKEP). The use of enhanced unqualified electronic signatures (UNEP) via the GosKlyuch system will be prohibited starting December 1. Operators must re-integrate with GosKlyuch exclusively through the SMEV interagency system and verify all remotely issued eSIMs registered before November 15. The measures address widespread fraud involving unauthorized number porting to attacker-controlled eSIMs, enabling interception of SMS codes for banking and messenger access. Independent experts note that UNEP certificates require only a verified Gosuslugi account, making them vulnerable to account takeover, while UKEP demands stricter identity verification. Over 15.7 million UNEP certificates were issued through GosKlyuch in the first eight months of 2026.
Access Under Control: Experts to Discuss SSO Risks, Legacy System Migration and AI Agent Permissions
On November 26, 2026, at 11:00, a webinar titled 'Managing access to corporate systems: how to bring order and reduce risks' will bring together leading Russian information security professionals. Participants will examine how organizations can control user permissions when integrating new applications while maintaining support for legacy systems. The discussion will cover excessive privileges, accounts of former employees, and contractor access, highlighting common mistakes that enable attackers to compromise corporate environments using legitimate credentials. A dedicated segment will address access management challenges during import substitution, including architecture selection and criteria for choosing between unified platforms and specialized solutions. Experts will also analyze bypass techniques for SSO and MFA, the impact of authentication service outages, and pre-deployment validation steps. Additional topics include the privileges of AI agents within corporate systems and regulatory requirements for centralized access control, with measurable outcomes such as faster rights revocation and reduced manual operations.
Russia Mandates Pre-Installation of RuStore App Store on Smart TVs from 2027
The Russian government has signed a decree that will make pre-installation of the domestic RuStore application marketplace mandatory on all Smart TVs starting in 2027. The Ministry of Digital Development confirmed that the new rules integrate RuStore into the existing mechanism for compulsory software pre-installation on television devices. The ministry must submit an updated list of required applications by March 1, 2027. Officials state that RuStore will guarantee access to Russian services on televisions and enable distribution of applications that are currently unavailable in Google Play and Google TV. Use of the store remains voluntary for end users. Similar pre-installation requirements have already applied to Android smartphones and tablets since 2023 and will extend to iOS and HyperOS devices from September 2025.