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

Cross-border data transfer restrictions from Russia in the mining and metals sector: what in-house counsel need to know

Elena Pavlova · January 2026 · 13 min read

Russian data transfer law creates sector-specific obligations for mining companies. A step-by-step guide for in-house counsel. Make an enquiry.

Unlike the GDPR framework familiar to most multinational legal teams, Russian personal data legislation does not treat cross-border data transfers as a secondary compliance step – it places them at the centre of the regulatory obligation. For in-house counsel at foreign mining and metals companies operating in Russia, this distinction carries practical weight: employee records, contractor databases, geospatial survey data associated with identified individuals, and health-and-safety files processed at Russian sites are all potentially subject to Russian cross-border data transfer restrictions before they can be routed to a group headquarters or shared with foreign joint venture partners. The regulatory framework applicable to these flows has tightened since amendments that took full effect in 2023, and Roskomnadzor's enforcement posture in the extractive industries has been increasingly attentive. This guide sets out the steps that in-house counsel at mining and metals companies need to take to assess exposure, establish a lawful basis, and maintain defensible documentation.

What to prepare before you begin

Before working through the steps below, gather the following materials. The adequacy assessment and authorisation process cannot proceed without them.

If your Russian entity's data flow map has not been audited in the past twelve months, the assumptions underlying your current compliance position may not reflect the regulatory position as it stands in 2026. Make an enquiry to discuss an initial data protection review: info@vetrovpartners.com |

Step 1 – Understand the legal basis: what Russian law requires from mining operators

Russian personal data law establishes a two-layer obligation for any cross-border transfer of personal data by a Russian operator. First, the operator – which includes a Russian legal entity that is part of a foreign corporate group – must conduct a pre-transfer adequacy assessment of the destination country. Second, unless the destination country is on a list of countries deemed to provide adequate protection (approved by Roskomnadzor and subject to revision), the transfer requires either the prior authorisation of Roskomnadzor or the establishment of an alternative lawful basis.

For the mining and metals sector, the practical significance of this framework becomes clear at the operational level. Personnel data – shift records, payroll information, occupational health records, qualification certificates – generated at extraction sites or processing facilities in Russia constitutes personal data of Russian data subjects regardless of where the employing entity is incorporated. When that data is uploaded to a group HR system hosted outside Russia, or transmitted to a foreign parent's health-and-safety platform, it crosses the border within the meaning of Russian data protection legislation.

The legislation also applies to data generated in connection with contractor and subcontract labour, which is pervasive in the mining sector. In-house counsel should not assume that data held by a third-party labour contractor is outside the Russian entity's regulatory perimeter: where the Russian entity determines the purposes and means of processing – as is common in large-scale extraction operations – it may be treated as the operator for regulatory purposes.

The Data Protection practice at Vetrov & Partners advises Russian and foreign companies on the structure of compliant cross-border transfer arrangements. For a detailed technical analysis of the legislative framework, see also our deep dive on cross-border data transfer restrictions from Russia.

Step 2 – Classify your data flows: which categories trigger cross-border transfer restrictions?

Not all data generated at a Russian mining site is subject to the cross-border transfer rules in the same way, and a workable compliance programme depends on accurate classification.

The primary category requiring attention is personal data of Russian citizens and residents. This includes, in a typical mining or metals operation: employee and contractor personnel files, occupational health screening records (which may also qualify as special-category biometric or health data and attract heightened obligations), payroll and tax reporting data, and any operational data that is linked to identifiable individuals – for example, access logs, vehicle movement records tied to named drivers, or safety incident reports naming the individuals involved.

A secondary category – which in-house counsel sometimes overlook – is personal data of individuals who are not employees of the Russian entity but whose data is processed by it: visitors to the site, members of affected communities where personal data is collected as part of environmental or social impact processes, and individuals whose data is processed in connection with land rights or resettlement arrangements.

Geospatial and geological data does not by itself constitute personal data under Russian law. However, when geospatial data is combined with personally identifiable records – for instance, survey data linked to named landowners or individuals interviewed in connection with subsoil licensing – the combined dataset may require treatment as personal data for transfer purposes.

The distinction between data that is subject to the cross-border transfer restrictions and data that falls outside them is not always self-evident in a mining context. A data mapping exercise conducted specifically with Russian law in mind – rather than adapted from a GDPR mapping template – is typically necessary to arrive at a reliable classification.

Step 3 – Establish a lawful basis for each transfer: what are the available routes?

Once the data flows are classified, the in-house counsel's task is to identify and document a lawful basis for each category of cross-border transfer. Russian law recognises several bases, and the appropriate route depends on the destination country and the nature of the data.

For transfers to EAEU member states – Belarus, Kazakhstan, Armenia, and Kyrgyzstan – the position is more straightforward: these countries are treated by Russian law as providing an adequate level of protection, and a specific Roskomnadzor authorisation is not required, provided the transfer is otherwise compliant with the processing rules applicable to the underlying data. Mining companies with operations across more than one EAEU jurisdiction should confirm their inter-entity data flows against this position, but the compliance burden is materially lower.

For transfers to non-EAEU countries – which typically means the EU or Switzerland for European groups, or the US, Canada, and Australia for Anglo-American mining groups – the framework is more demanding. Unless the destination country appears on Roskomnadzor's list of adequate countries, the operator must either obtain Roskomnadzor's prior authorisation before the transfer begins or rely on one of the statutory alternative bases. The alternative bases include: the explicit consent of each data subject (operationally demanding at scale and not well-suited as a primary basis for ongoing employment data flows); the necessity of the transfer for the performance of a contract to which the data subject is a party; or the necessity of the transfer for the protection of the vital interests of the data subject or third parties where consent cannot be obtained.

In practice, for routine HR and operational data flows from a Russian mining entity to a foreign parent, Roskomnadzor authorisation is the most reliable and defensible basis. The authorisation process requires the Russian entity to submit a notification to Roskomnadzor specifying the categories of data, the recipient, the destination country, the purposes and legal basis of transfer, and the protective measures in place. Roskomnadzor may respond with conditions or requests for additional information; transfers should not begin before authorisation is confirmed.

Note: Initiating a cross-border data transfer without the required Roskomnadzor authorisation – where authorisation is the applicable basis – exposes the Russian entity to administrative liability under Russian law. Enforcement action by Roskomnadzor can include mandatory suspension of the transfer and, in more serious cases, referral for further regulatory action. The reputational implications for a foreign parent company with publicly reported ESG commitments should not be underestimated.

Establishing the correct lawful basis for each cross-border data flow requires a fact-specific assessment. Firms managing multiple data streams across jurisdictions often benefit from instructing Russian counsel early in the process, before Roskomnadzor contact is initiated. Request our practice review: info@vetrovpartners.com |

Step 4 – Implement localisation and technical controls: sector-specific considerations for mining

Russian data protection legislation requires that personal data of Russian citizens be stored and primarily processed on servers physically located in Russia before any cross-border transfer. For mining and metals companies operating group-wide IT infrastructure – enterprise resource planning systems, workforce management platforms, health-and-safety incident management tools – this localisation requirement has direct implications for system architecture.

In the mining context, the localisation obligation commonly affects: the primary HR database for Russian site personnel; occupational health management systems where Russian employee health data is processed; payroll and compliance reporting systems; and, increasingly, IoT and wearable device data where individual workers are identified in the dataset. The group parent's tendency to centralise these systems on a single global instance hosted in the US, Ireland, or Germany does not extinguish the Russian localisation requirement: a Russian mirror or primary-instance configuration is required for the Russian data subjects' records.

For smaller Russian operating entities – junior partner subsidiaries in joint ventures, for example – this requirement can appear disproportionate relative to the operational scale. However, there is no exemption based on company size or employee headcount under Russian data protection legislation, and Roskomnadzor does not in practice distinguish between large and small operators in enforcement terms.

The technical controls that accompany the localisation requirement include: access controls limiting who within the foreign group can access the Russian-localised dataset; audit logging of any transfers out of the localised environment; and contractual arrangements with group IT service providers that clearly demarcate Russian data from the global data estate.

For detailed analysis of how Russian courts and Roskomnadzor have approached the localisation requirement in recent enforcement activity, see our note on Russian Supreme Court clarification on cross-border data transfers.

Step 5 – Document, review, and respond to regulatory scrutiny

A compliant cross-border data transfer arrangement under Russian law is not a one-time filing. It requires ongoing documentation maintenance and the institutional capacity to respond to Roskomnadzor inquiries or inspections, which in the mining and metals sector may also intersect with other regulatory interactions at the site level.

The documentation set that a Russian mining entity should maintain includes: the Roskomnadzor notification or authorisation confirmation; the internal data flow map and its update history; records of consent (where consent is a relied-upon basis for any specific transfer category); contractual arrangements with data processors and sub-processors, including group IT service providers; and records of data subject requests and how they were handled.

Roskomnadzor has the power to conduct both scheduled and unscheduled inspections of data operators. In the mining sector, these inspections may be triggered by a data subject complaint (for example, from a former employee or contractor), by a report from another regulator with whom Roskomnadzor co-ordinates, or as part of a sector-specific enforcement exercise. In-house counsel should ensure that the Russian entity's designated person responsible for personal data processing – a mandatory appointment under Russian law – is identified and that their contact details are current in the Roskomnadzor register.

Foreign parent companies should also be aware that Roskomnadzor's approach to foreign entities with Russian operations has become more assertive since 2023. The obligation to comply with Russian data protection requirements rests with the Russian legal entity, but group-wide compliance programmes that treat Russian requirements as an afterthought – rather than as a distinct regulatory stream – typically produce documentation gaps that are difficult to remedy once regulatory scrutiny begins.

The Data Protection and Regulatory & Licensing practices at Vetrov & Partners assist foreign companies in establishing compliant documentation frameworks for their Russian operations and in responding to Roskomnadzor inquiries. Our matters page contains further examples of the types of regulatory compliance mandates the firm has handled.

For in-house counsel managing the Russian data protection compliance of a mining or metals group, a structured compliance review with Russian counsel typically produces a clearer picture of residual exposure than an internal audit conducted under a different legal framework. Discuss your matter in confidence: info@vetrovpartners.com |

Frequently asked questions

Q: How long does the cross-border data transfer notification or authorisation process take in Russia?

A: The timeline depends on whether the transfer requires Roskomnadzor's prior authorisation or only notification. Where authorisation is required – as is typical for transfers to countries not on the adequacy list – Roskomnadzor should respond within a prescribed period, but in practice the process can extend to several weeks or longer where Roskomnadzor requests additional documentation or clarification. Companies should not treat the submission of the notification or authorisation request as the point from which the transfer may begin: the transfer should wait until authorisation is confirmed. In-house counsel managing a project with a defined data transfer deadline – for example, in connection with a group IT migration or a joint venture data room – should build regulatory lead time into the project plan. Attempting to initiate transfers before the process is complete exposes the Russian entity to the administrative consequences described above.

Q: What documents does a mining company need to file to establish a lawful basis for transferring personal data abroad?

A: The specific documents required depend on the basis being relied upon. For a Roskomnadzor authorisation, the submission must describe the categories of personal data to be transferred, the identity and location of the foreign recipient, the purposes of the transfer, the legal basis under Russian law, and the protective measures the operator has put in place. In addition, the Russian entity must be registered in the Roskomnadzor register of personal data operators; if this registration is not current or has never been completed, it must be addressed before the authorisation submission is filed. Where consent of data subjects is relied upon for a specific category of transfer, the consent records must demonstrate that consent was freely given, specific to the cross-border transfer, and informed – a standard that generic employment consent clauses typically do not meet. Russian counsel can review the adequacy of existing documentation before submission and identify gaps that would delay or prevent authorisation.

Q: What happens if a mining or metals company is found to have transferred data without the required authorisation?

A: Roskomnadzor has the authority to order the suspension of the unlawful transfer and to initiate administrative proceedings against the Russian legal entity. The consequences under Russian administrative law include financial penalties, which have increased since the 2023 amendments, and a mandatory remediation order. In more serious cases – particularly where the breach involved special-category data (health data, biometric data) or a large volume of data subjects – Roskomnadzor may refer the matter to other law enforcement bodies. For a foreign parent company, the Russian subsidiary's regulatory liability does not directly transfer, but the reputational and operational consequences of a suspended data transfer affecting, for example, a group HR or payroll system are immediate. Mining companies that discover a historic unauthorised transfer should seek Russian legal advice before self-disclosing to Roskomnadzor, as the approach to voluntary disclosure affects the likely regulatory outcome.

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