Novosibirsk · Russian-qualified counsel Recognised by Pravo-300 · Best Lawyers · Kommersant
Corporate & Regulatory

Navigating Federal Law 152-FZ personal data requirements in Russia against insolvency estates: a step-by-step overview

Elena Pavlova · September 2026 · 11 min read

Dealing with Russian insolvency estates triggers 152-FZ personal data duties. A step-by-step compliance guide for in-house counsel. Make an enquiry.

Unlike the EU General Data Protection Regulation, which applies primarily by virtue of where data subjects are located, Federal Law No. 152-FZ applies by virtue of where processing occurs and, critically, where data is stored. For a foreign company that is acquiring assets, reviewing creditor claims, or conducting due diligence against a Russian insolvency estate, this distinction is consequential. The personal data of employees, counterparties, debtors, and individual creditors that passes through an insolvency process in Russia is regulated under Russian personal data legislation from the moment it touches a Russian information system or a Russian-domiciled database. Inattention to Federal Law 152-FZ at the point of engagement with a Russian estate has, in practice, created regulatory exposure that persists long after the underlying insolvency matter closes.

What to prepare before engaging with a Russian insolvency estate

Before initiating any engagement with an insolvency administrator or reviewing estate documentation, in-house counsel should assemble the following:

This checklist is not exhaustive. Its purpose is to establish a baseline before review of estate materials begins and before any personal data received from the insolvency administrator is stored, transmitted, or processed outside Russia.

For in-house counsel managing a Russian subsidiary or creditor claim that involves access to personal data held by a Russian insolvency estate, early compliance review is preferable to remediation under regulatory pressure. Make an enquiry: info@vetrovpartners.com |

Step 1 — Map what personal data the insolvency estate holds

The first step is a data-mapping exercise. An insolvency estate in Russia typically holds a significant volume of personal data across multiple categories. The debtor company's employee records, payroll data, and pension contributions contain personal data in the strict sense under Russian personal data legislation. Contracts with individual counterparties, personal guarantees executed by directors, creditor claims filed by natural persons, and court submissions naming individuals all fall within the scope of Federal Law 152-FZ if they are processed in Russia.

A foreign company reviewing estate documentation as a creditor, potential acquirer, or litigation counterparty becomes engaged with this data from the moment it receives, copies, stores, or transmits documents containing personal data of Russian individuals. The correct approach is to treat the data-mapping exercise as a jurisdictional trigger analysis: for each category of document received, identify whether it contains personal data of Russian individuals, how that data will be stored and by whom, and whether any onward transfer outside Russia is contemplated.

This analysis is the foundation on which all subsequent compliance decisions rest. Shortcuts taken at this stage typically surface as notification gaps or transfer-restriction violations when Roskomnadzor conducts its review.

Step 2 — Determine whether your company qualifies as a personal data operator under Russian law

Under Russian personal data legislation, an entity that independently or jointly with others determines the purposes and means of processing personal data is a "personal data operator." The concept is functionally similar to the "data controller" concept in European data protection law, but the jurisdictional trigger differs. A foreign company that instructs a Russian insolvency administrator to compile a data set, directs the storage of personal data in a Russian system, or makes decisions about which data subjects' information to review and retain is, as a general rule, acting as a personal data operator for Russian law purposes.

The classification matters for two reasons. First, personal data operators are subject to Roskomnadzor's supervisory jurisdiction regardless of their place of incorporation. Second, the notification obligations, data subject rights regime, and cross-border transfer rules under Federal Law 152-FZ all attach at the operator level. A foreign company that incorrectly characterises itself as a mere "recipient" of estate documentation, rather than as an operator engaged in processing, risks assuming compliance obligations it has not prepared to meet.

The threshold for classification as an operator under current Roskomnadzor interpretive guidance is relatively broad. In practice, any active decision-making role in relation to personal data received from a Russian estate is likely to be sufficient.

Step 3 — Register with Roskomnadzor and establish an internal processing framework

Personal data operators are required to notify Roskomnadzor of their processing activities before processing commences. For foreign companies engaging with a Russian insolvency estate, this notification requirement applies where the company qualifies as an operator and where Russian nationals' personal data is being processed. The notification is submitted through Roskomnadzor's official portal and must specify the categories of personal data being processed, the purposes of processing, the legal basis, the categories of data subjects, the retention periods, and the identity and location of any processors acting on the operator's behalf.

The timeline for completing notification and establishing the required internal documentation framework varies in practice. As a general rule, in-house counsel should allow several weeks from the point at which the operator classification is confirmed to the point at which a compliant framework is in place. This includes time for drafting or adapting internal data processing policies, executing data processing agreements with the insolvency administrator or any Russian service provider, and completing any required record-of-processing documentation.

For companies that have existing Russian subsidiaries or branch offices, it is worth confirming whether those entities have already filed Roskomnadzor notifications that could be extended or amended to cover the processing associated with the insolvency engagement. Processing activities that fall outside the scope of an existing notification cannot be treated as covered by it. A separate or amended notification is required.

For in-house counsel with existing compliance frameworks in Russia who need to assess whether an insolvency-related engagement triggers new or amended Roskomnadzor notification obligations, the firm's data protection practice can provide a focused review. Request our practice review: info@vetrovpartners.com |

Step 4 — Navigate data-subject rights and cross-border transfer restrictions in an insolvency context

The data-subject rights framework under Federal Law 152-FZ applies throughout an insolvency process. Individual data subjects — employees of the debtor, individual creditors, directors whose personal data appears in estate documentation — retain rights of access, correction, and erasure in respect of their personal data, subject to exceptions for data processed in connection with legal proceedings. An operator engaged with a Russian estate must have a documented mechanism for receiving and responding to such requests, even if the practical likelihood of receiving one is low.

The cross-border transfer question is typically the most operationally significant for foreign companies. Under Russian personal data legislation, the transfer of personal data of Russian nationals to a country that does not ensure an adequate level of data protection is, as currently interpreted by Roskomnadzor, subject to specific requirements. These include, as a general rule, that the transfer be covered by a written agreement between the operator and the recipient providing for equivalent protections, and that a prior assessment of the recipient country's data protection framework be documented. The list of countries that Roskomnadzor recognises as providing adequate protection is distinct from the EU adequacy decision list, and foreign companies frequently discover that a country they assumed to be "adequate" for Russian purposes is not on the Russian list.

For insolvency-related processing, the practical implication is that documents containing personal data of Russian individuals should not routinely be transmitted to the foreign company's home-country servers, review platforms, or litigation support systems without prior assessment of the cross-border transfer requirements. Where transfer is necessary, the applicable legal basis should be documented before the transfer occurs.

Step 5 — Manage onward disclosure to insolvency administrators, creditors, and courts

The final step in the compliance sequence involves the management of onward disclosures. In an insolvency matter, personal data flows in multiple directions: from the debtor company to the insolvency administrator, from the administrator to creditors, from creditors to their advisers, and from all parties to the Russian courts hearing the insolvency proceedings. Each of these flows is subject to Federal Law 152-FZ to the extent it involves a personal data operator processing personal data of Russian individuals.

A foreign company acting as a creditor must be able to demonstrate that its own processing of personal data received through the insolvency procedure is covered by an appropriate legal basis. Disclosure to external legal counsel, consultants, or financing parties requires the same analysis. Disclosure to a court does not require data-subject consent but does require that the disclosure be proportionate to the litigation purpose.

The insolvency administrator is, as a general rule, separately classified as a personal data operator in respect of the data held within the estate. This does not eliminate the foreign company's own obligations. Both entities may simultaneously hold operator status in respect of overlapping data sets. In-house counsel should not assume that the administrator's compliance framework covers the foreign company's processing. Separate documentation is required.

Foreign companies who have managed this compliance sequence correctly in similar matters have, in the firm's experience, avoided Roskomnadzor inquiries that arose from informal complaints by data subjects identified in estate documentation. The regulatory exposure for non-compliant operators is real, and it does not dissolve with the closure of the insolvency proceedings.

For further background on the Federal Law 152-FZ framework applicable to foreign companies operating in Russia more broadly, see the firm's analysis at Federal Law 152-FZ: Personal Data Requirements for Foreign Companies and the related legislative framework overview at Federal Law 152-FZ: A Legislative Framework Analysis. Matters involving insolvency procedure more generally are handled by the firm's Restructuring & Insolvency practice. A record of representative matters involving cross-border data and insolvency engagements is available at Matters.

For in-house counsel managing the compliance dimension of a Russian insolvency engagement, the regulatory timeline leaves limited margin for delay once processing has commenced. Discuss your matter in confidence: info@vetrovpartners.com |

Frequently asked questions

Q: How long does it take to register as a personal data operator with Roskomnadzor?

A: The formal process of submitting a notification to Roskomnadzor through its official portal is typically completed within a few working days once all required information has been assembled. However, the preparation of that notification — identifying the categories of data, purposes, legal bases, and processors — takes longer in practice, particularly for a foreign company with no existing compliance infrastructure in Russia. In-house counsel should allow several weeks for the full cycle from operator classification through to a documented, notification-compliant processing framework. Processing should not commence before notification is filed. A foreign company that begins reviewing estate personal data without first completing the notification sequence is, as a general rule, already in breach of its Russian personal data obligations.

Q: What documents must a foreign company prepare to comply with Federal Law 152-FZ when dealing with Russian insolvency estates?

A: The core documentation set includes a Roskomnadzor notification (or evidence of an existing notification that covers the processing in question), internal records of processing activities covering the insolvency engagement, a data processing agreement with the insolvency administrator or any other Russian-based processor, a documented legal basis for any cross-border transfer of personal data of Russian nationals, a data-subject rights response procedure, and a data retention and deletion schedule. Where the foreign company holds existing Russian personal data compliance documentation through a subsidiary or branch, that documentation should be reviewed to confirm it extends to the specific processing activities arising from the insolvency engagement. Extensions or amendments may be necessary.

Q: What happens if a foreign company fails to comply with personal data requirements during Russian insolvency proceedings?

A: Non-compliance with Federal Law 152-FZ can attract administrative sanctions imposed by Roskomnadzor following an inspection or in response to a complaint from a data subject. Sanctions are graduated depending on the nature and duration of the breach. In practical terms, a foreign company involved in Russian insolvency proceedings faces an additional risk: personal data compliance issues can become a lever for counterparties or the insolvency administrator to delay proceedings, challenge the admissibility of documentation, or attract regulatory scrutiny at a stage when the company is already under commercial pressure. The risk is not merely theoretical. Regulatory exposure for personal data operators who have not filed a Roskomnadzor notification does not diminish simply because the operator is foreign. Russian data protection legislation applies on the basis of processing location, not company domicile.

Practitioner note

This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.

Facing a matter like this?

Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.

Make an enquiry