Mining and metals companies operating across the EU and Russia face simultaneous GDPR and 152-FZ obligations that conflict in practice. Make an enquiry.
Foreign mining and metals companies operating simultaneously in the European Union and Russia carry a compliance burden that few other sectors match in complexity. Following amendments to Russia's personal data framework that took effect progressively since 2022, multinational operators in the sector face a regulatory landscape in which the requirements of the EU General Data Protection Regulation and Federal Law No. 152-FZ on Personal Data do not merely differ at the margins — they conflict in structure, enforcement logic, and remediation timeline. For an in-house team managing Russian processing operations alongside EU-facing data flows, understanding where the two regimes genuinely converge and where they pull in opposite directions is the prerequisite for any workable compliance architecture.
At first glance, the two instruments appear to share common ground. Both establish the lawfulness of processing as a foundational principle, require a defined legal basis for collecting and using personal data, and impose obligations on controllers to implement organisational and technical safeguards. Both address the rights of data subjects — access, erasure, correction — and both impose requirements on parties who process data on behalf of a controller. For a multinational mining group, this surface convergence can be reassuring. It should not be.
The divergence becomes apparent at the structural level. The EU framework operates on a risk-based, accountability-driven model: the controller determines its compliance approach, documents it, and defends it to a supervisory authority and, increasingly, to data subjects via litigation. The Russian framework operates differently. Federal Law No. 152-FZ establishes prescriptive obligations — notification to Roskomnadzor, database localisation within Russian territory, and defined conditions for cross-border transfer — that are not subject to the same degree of contextual calibration. A controller cannot substitute a risk assessment for a mandatory registration. In the mining and metals sector, where operational data flows are dense — workforce management systems, contractor databases, payroll, health and safety records, environmental monitoring with individual attribution — this structural gap creates simultaneous exposure under both regimes.
The core obligation under Russian data protection law for any entity processing personal data of Russian citizens is the localisation requirement: primary databases must be physically located on servers situated within the territory of the Russian Federation. For a mining group with a European parent and centralised HR or payroll infrastructure, this is not a formality — it requires either a local data store or a certified Russian cloud provider solution, with the European system receiving only a copy or a downstream feed.
Beyond localisation, the law requires notification to Roskomnadzor before processing commences. Mining and metals operators frequently discover, during compliance reviews, that legacy systems established at the time of acquisition or joint venture formation were never registered. Under the amendments that strengthened enforcement powers and introduced administrative — and, for repeated or large-scale violations, criminal — liability, this gap carries material regulatory risk. Roskomnadzor has the authority to inspect processing operations, issue binding instructions, and, where non-compliance is established, seek inclusion of non-compliant operators in the register of violators, which carries practical consequences for continued operation.
The sector's particular data profile amplifies this exposure. Mining operations generate personal data categories that attract heightened regulatory attention: biometric data used in access control at mine sites, health data collected under occupational safety obligations, and geolocation data associated with individual workers operating in remote or hazardous environments. Under the Russian framework, these categories require explicit consent or a specific legal basis beyond the standard grounds applicable to ordinary personal data, and that basis must be documented and retained in a form accessible to Roskomnadzor inspectors.
For in-house counsel assessing the scope of 152-FZ obligations across a Russian mining or metals operation, the regulatory timeline leaves limited margin for a phased approach — make an enquiry: info@vetrovpartners.com |
Cross-border transfer under Federal Law No. 152-FZ is one of the most practically challenging areas for foreign-owned mining and metals groups. The law permits transfer of personal data to foreign territories, but conditions this on a prior assessment of whether the receiving country provides an adequate level of protection — a concept that exists in both the EU and Russian frameworks but is applied differently and with reference to different country lists.
Russia maintains its own list of countries considered to provide adequate protection. Importantly, EU member states appear on this list, but adequacy under the Russian framework does not mean that a transfer from Russia to an EU entity can proceed without further formality. The controller must ensure that the cross-border transfer notification to Roskomnadzor covers the specific countries and purposes involved, and that the contractual basis for the transfer addresses the protections required under Russian law — not only the safeguards required under the GDPR for transfers leaving EU territory.
For a mining group structured with a Dutch or German holding entity receiving consolidated HR data from a Russian subsidiary, this creates a layered requirement: the Russian operation must comply with the localisation rule (data stored in Russia), the transfer notification rule (Roskomnadzor notified of the cross-border flow), and the contractual safeguard rule (the intra-group agreement must satisfy Russian law standards). At the same time, the EU holding entity receiving that data must ensure that the transfer from Russia is lawful under the GDPR — including, where applicable, compliance with any applicable transfer mechanism or adequacy decision from the European side. As of mid-2027, there is no formal EU adequacy decision for Russia, which means that EU-side transfer mechanisms must be relied upon independently of the Russian-law position.
The practical consequence for mining sector operators is that a single intra-group data flow — employee records moving from a Siberian subsidiary to a European headquarters — simultaneously engages Russian notification requirements, Russian contractual standards, and EU transfer mechanism obligations. These do not cancel each other out; they stack.
"The assumption that an intra-group data agreement designed for GDPR compliance will also satisfy Roskomnadzor's requirements for cross-border transfer is one of the most common — and costly — misapprehensions we encounter in the sector." — Elena Pavlova, Associate, Vetrov & Partners
The mining and metals sector has data protection characteristics that distinguish it from most other industrial sectors in ways that directly shape compliance design. Three are particularly significant.
First, the workforce profile. Large-scale mining operations — whether in the Siberian Federal District, the Ural region, or the Russian Far East — employ substantial numbers of workers, many of whom are subject to collective bargaining arrangements, shift-based rotation schemes, and detailed health monitoring. The personal data generated by these arrangements is both voluminous and sensitive. Health records, including pre-employment medical assessments and ongoing occupational health data, fall into a protected category under Russian law and require a specific legal basis distinct from ordinary processing.
Second, access control and biometric data. Mine site security systems, particularly at facilities processing strategic minerals or operating under licensing conditions that impose security requirements, routinely rely on biometric identification — fingerprint or facial recognition systems at entry points. Biometric data is separately categorised under Federal Law No. 152-FZ and subject to additional restrictions. In practice, this means that a standard group-wide biometric access control rollout requires a Russia-specific legal analysis before deployment, not merely an extension of the EU-facing privacy impact assessment.
Third, contractor and supply chain data. Mining operations involve extensive contractor networks — drilling companies, logistics providers, equipment maintenance firms. Where personal data of contractor employees is processed by the mining company — whether for site access, health and safety compliance, or payment processing — the question of data controller versus data processor status arises under both frameworks. The Russian framework's concept of data processing on assignment (analogous to the processor relationship) has specific formal requirements that differ from the GDPR's processor agreement model. A standard EU data processing agreement will not, without amendment, satisfy the Russian requirements.
Firms advising multinational mining and metals clients with Russian operations will frequently need confirmed local Russian counsel before the compliance architecture can be finalised — make an enquiry or contact us on | info@vetrovpartners.com
The starting point for any bridging compliance programme in the mining and metals sector is an accurate data mapping exercise that is conducted against both frameworks simultaneously, not sequentially. A GDPR-first approach — common among European-headquartered groups — will produce a records-of-processing-activities document that is not calibrated to the Russian notification and localisation requirements and will miss the sector-specific categories that attract heightened scrutiny under Russian law.
A workable mapping exercise for a dual-framework environment identifies, for each processing activity: the legal basis under both regimes (which may differ), the storage location relative to the Russian localisation requirement, the cross-border transfer pathway and its bilateral compliance requirements, and the data subject rights mechanism applicable in each jurisdiction. For mining sector operations, this mapping should extend to contractor data and biometric systems as distinct processing streams.
Once the map is established, the principal structural decision is the localisation architecture. For groups using centralised European data platforms, the most common compliant model involves a federated database structure: a Russian-territory instance that holds the primary dataset for Russian citizen data, with defined synchronisation or transfer protocols to the European system. Cloud-hosted solutions using certified Russian providers can satisfy the localisation requirement, subject to verification that the provider's certification and data centre locations are current — an area in which the market has evolved quickly and due diligence should be recent.
Contractual alignment is the third element. Intra-group data processing agreements require amendment to address Russian law standards. Contractor agreements require a Russia-specific data processing annex. Employee notices and consent frameworks — where consent is the applicable legal basis — require Russian-language versions that satisfy the specificity and voluntariness requirements of the Russian framework, which differ from the GDPR's consent standards in material respects.
Finally, governance. Roskomnadzor enforcement has become more active, and the introduction of criminal liability for large-scale or repeated violations means that the risk profile of non-compliance has shifted from administrative penalty to personal liability for responsible officers. For the general counsel of a mining group with significant Russian operations, this shift in the enforcement environment is the most consequential development of recent years. Building an internal compliance function that can demonstrate ongoing compliance — not merely a historical audit — is increasingly what regulators expect.
For structured advice on designing a 152-FZ and GDPR bridging programme for a Russian mining or metals operation — including data mapping, localisation architecture, and Roskomnadzor notification — make an enquiry: info@vetrovpartners.com |
Q: Does a foreign mining company with a Russian subsidiary have to comply with Federal Law No. 152-FZ even if all data processing decisions are made at the European parent level?
A: Yes. The Russian data protection law applies on the basis of the location of processing, not the location of the controller's headquarters. If personal data of Russian citizens is collected or processed within Russia — which is the case for any subsidiary employing Russian workers, engaging Russian contractors, or operating Russian site access systems — the obligations of Federal Law No. 152-FZ apply to that processing regardless of where group-level decisions are made. The European parent's GDPR compliance programme does not substitute for Russian law compliance. In practice, this means the Russian subsidiary must maintain its own notification to Roskomnadzor, its own localised database structure, and its own data subject rights mechanism, even where the group operates a centralised HR or payroll platform.
Q: What is the data localisation requirement under Russian law and does it apply to all personal data or only to Russian citizens' data?
A: The localisation requirement under Federal Law No. 152-FZ applies to personal data of Russian citizens and requires that the initial recording, systematisation, accumulation, storage, clarification, and retrieval of that data be carried out using databases located within the territory of the Russian Federation. It does not apply to personal data of non-Russian citizens unless processed on Russian territory in the context of activities directed at Russian data subjects. For a mining group with an internationally mobile workforce, this means that the localisation obligation applies to the Russian citizen portion of the workforce dataset specifically, though in practice, operating a segmented database by citizenship carries its own complexity. After the initial recording in a Russian database, onward transfer to a foreign database is permitted, subject to the cross-border transfer notification requirements.
Q: How does Roskomnadzor enforce the localisation requirement, and what are the practical consequences of non-compliance?
A: Roskomnadzor enforces the localisation requirement through scheduled and unscheduled inspections, documentary requests, and complaints from data subjects or third parties. Where a violation is established, the regulator may issue a binding instruction to bring operations into compliance within a specified period, impose administrative penalties, and — in cases of repeated or large-scale violations — refer matters for criminal investigation. The most visible enforcement mechanism is inclusion in the register of violators, which can result in access to the operator's services being blocked within Russia — a consequence that, for a mining operation dependent on Russian government licensing and counterparty relationships, is operationally significant. Under the enforcement amendments in force as of mid-2027, the penalty regime has become meaningfully more severe than it was at the time of the original localisation requirement's introduction.
Q: Can a standard GDPR data processing agreement with an intra-group processor also satisfy the Russian law requirements for a data processing assignment?
A: Not without amendment. The Russian framework's model for processing personal data on assignment differs from the GDPR processor model in several respects: it requires the assignment to be documented in a specific form, imposes direct obligations on the assignee that differ from those imposed on GDPR processors, and does not provide for the standard sub-processing chain mechanism in the same way. A standard EU data processing agreement — even a well-drafted one based on European standard contractual terms — will typically not address the Russian-law specific requirements for the assignment relationship, the cross-border transfer conditions, or the data subject rights mechanism applicable under Russian law. For a mining group operating an intra-group shared services model, the practical solution is a dual-layer agreement: a GDPR-compliant processor agreement governing the EU-side relationship, and a Russia-law compliant processing assignment agreement governing the Russian subsidiary's engagement with the shared services entity.
Q: Does the mining and metals sector face any additional sector-specific data protection obligations under Russian law beyond the general requirements of Federal Law No. 152-FZ?
A: Yes, in two principal respects. First, mining companies operating facilities classified as hazardous industrial sites are subject to occupational safety legislation that imposes mandatory health monitoring and record-keeping obligations for workers. The data generated by this monitoring — medical examinations, injury records, fitness-for-work assessments — constitutes health data, which is a protected category under the Russian framework requiring a distinct legal basis and heightened security measures. Second, operations involving strategic minerals or certain defence-adjacent supply chains may be subject to sectoral licensing conditions that impose access control requirements — often biometric — for site entry. Biometric data is separately regulated under the Russian framework, with specific conditions for its collection, storage, and use. Neither of these sectoral obligations is addressed in a standard GDPR compliance programme, and both require Russia-specific legal analysis before system deployment.
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