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

Navigating GDPR and Russian Federal Law 152-FZ: bridging requirements in the oil and gas sector: a step-by-step overview

Elena Pavlova · February 2026 · 10 min read

Oil and gas companies processing personal data under both GDPR and Russian 152-FZ face dual obligations. Step-by-step compliance guide. Make an enquiry.

Unlike the GDPR, which treats data localisation as an exception rather than the rule, Russian Federal Law No. 152-FZ on Personal Data treats it as a baseline obligation for any operator collecting personal data of Russian citizens — including foreign companies with Russian operations. For oil and gas majors operating across Russia, Europe, and beyond, this creates a structural compliance problem: the two regimes share surface-level vocabulary — consent, lawful basis, data subject rights — but diverge materially on localisation, transfer mechanisms, and regulatory notification. The gap between them is not a technicality. It is a source of live regulatory exposure that in-house counsel managing Russian upstream, midstream, or downstream assets need to plan for systematically.

What to prepare before you begin

A gap analysis between current data flows and the requirements of both regimes is essential before any compliance programme is designed. The following checklist identifies the minimum information your team needs before proceeding to the five steps below.

If your compliance baseline is incomplete or you are uncertain whether current transfer arrangements satisfy Russian law — make an enquiry: info@vetrovpartners.com |

Step 1 — Establish the regulatory perimeter: which data flows trigger 152-FZ?

The first task is definitional. Russian Federal Law 152-FZ applies to any operator — domestic or foreign — that processes personal data of Russian citizens. For oil and gas companies, this catches a wider population than many in-house counsel initially assume. The term "personal data" under Russian law includes not only names and identification numbers but also biometric data used in field access control systems, location data generated by personnel tracking in remote operations, health and safety records, and — under the 2022 and subsequent amendments to 152-FZ — a broader set of "special categories" that now broadly corresponds to the GDPR's Article 9 sensitive data list.

The practical perimeter for a typical upstream or midstream operator includes: all Russian-employed personnel (direct employees and contractors on Russian soil); subcontractors whose personal data is processed as part of HSE or licensing obligations; and third-party individuals whose data enters group-level systems via Russian-sourced inputs. The GDPR perimeter, by contrast, is triggered by the location of the data subject or the establishment of the controller — creating an overlap zone where the same processing activity is simultaneously subject to both regimes. Identifying this overlap zone precisely is the output of Step 1.

Geo-signal note: operators registered or licensed in Russia — even as a branch or representative office rather than a standalone legal entity — are treated as operators under Russian law and fall within 152-FZ's scope regardless of where their parent is incorporated.

Step 2 — Satisfy the localisation requirement without breaking GDPR transfer obligations

The localisation obligation under 152-FZ requires that the initial collection and primary storage of personal data of Russian citizens occurs on servers physically located within Russian territory. This is a hard statutory requirement, not subject to contractual override. It applies regardless of the lawful basis under which the data is processed. For oil and gas groups running centralised, often cloud-hosted, data infrastructure, this creates immediate architectural tension with GDPR-compliant data flows, which assume free movement of data within the EEA and rely on standard contractual clauses (SCCs) or adequacy decisions for transfers outside it.

The bridging approach that Russian-qualified practitioners and major operators have converged on involves a two-tier architecture: a Russian-located primary database (the "local layer") — whether hosted by a Russian cloud provider or a dedicated on-premise server within the Russian entity — that holds the canonical copy of Russian citizens' personal data; and a shadow or replicated dataset that feeds group systems after the localisation requirement is satisfied. This architecture does not eliminate the need for GDPR-compliant transfer mechanisms: the replication itself constitutes a transfer under GDPR, and standard contractual clauses between the Russian entity and the EEA-based group parent remain necessary.

Note: Failure to localise Russian citizens' personal data is one of the most actively enforced obligations under 152-FZ. Roskomnadzor has demonstrated a willingness to impose website-blocking measures on non-compliant operators, an outcome that would materially disrupt digital operations in Russian fields. The penalty and blocking regime was strengthened by amendments that took effect in 2024. Operators who have not yet implemented a localised primary database should treat this as a priority action, not a medium-term project.

Step 3 — Align consent and lawful basis documentation across both regimes

Consent under 152-FZ is more formalistic than under GDPR. Russian law requires written consent in most circumstances involving sensitive personal data and certain employment contexts — a paper or electronic signed record, in the Russian language, specifying the categories of data, the processing purposes, and the operator's identity. GDPR, by contrast, permits a wider range of lawful bases (legitimate interests, contractual necessity, legal obligation) that effectively reduce reliance on consent for many employment-context processing activities. The practical problem for oil and gas operators is that employment data — the most voluminous personal data category in field operations — sits at the intersection of both regimes, and the lawful bases do not map cleanly.

The recommended approach is to build a dual-column processing register: one column recording the 152-FZ basis (consent, statutory obligation, or contract performance), the other recording the GDPR basis for the same processing activity. Where 152-FZ requires written consent and GDPR permits a non-consent lawful basis, both requirements must be satisfied simultaneously — the consent document serves the Russian requirement, while the non-consent basis serves the GDPR record. This dual-column register also forms the documentary basis for responding to data subject access requests under both regimes, which, while procedurally different, share overlapping substance.

Step 4 — Complete and maintain Roskomnadzor notification — does prior registration protect you?

Operators must notify Roskomnadzor of their status as personal data operators before commencing processing. The notification form requires disclosure of: the categories of data processed; the processing purposes; the legal basis; the data retention periods; the identity of any processors engaged; and — crucially for oil and gas operators — whether personal data is transferred outside Russia and, if so, to which countries and under which transfer mechanism. The notification is not a one-off exercise: material changes (new processing purposes, new transfers to foreign entities, changes to processor arrangements) require updated notification. Oil and gas operators undergoing corporate restructurings, asset acquisitions, or group-level IT migrations face a specific risk of notification lapse during transition periods.

Prior notification does not immunise an operator against enforcement. Roskomnadzor conducts both scheduled and unscheduled inspections, and the inspection framework was broadened following amendments in 2022 and 2024. What prior, accurate notification does provide is a documented compliance record that, in practice, reduces inspection frequency and — where a violation is found — may be taken into account in penalty assessment. For operators who have never filed, or who filed initial notifications that no longer reflect current processing activities, rectification is a matter of some urgency. The firm has Data Protection resources specifically directed at bringing operator notifications into current-state compliance.

For in-house counsel managing Russian data protection compliance across a group, we offer a structured practice review. Request our practice review: info@vetrovpartners.com |

Step 5 — Establish an ongoing compliance and incident response framework: what does a workable programme look like?

The final step moves from project to programme. A one-time gap analysis and localisation fix does not constitute a compliance programme — both 152-FZ and GDPR are living frameworks, subject to amendment, regulatory guidance, and enforcement decisions that materially affect the obligations of operators in practice. For oil and gas companies, the specific challenge is that data processing activities are operationally intensive and change frequently: field expansions, contractor rotations, HSE platform migrations, and group IT transitions each generate new data flows that require compliance assessment.

A workable programme for an operator in this sector typically rests on four pillars. First, a designated internal responsible person for personal data processing under 152-FZ (a statutory requirement for operators processing certain categories of data — the role is functionally analogous to a DPO under GDPR but has distinct Russian legal characteristics). Second, a documented data flow map that is reviewed and updated no less than annually and at every material operational change. Third, a defined incident response protocol that satisfies the notification timelines of both regimes — 152-FZ requires notification to Roskomnadzor of breaches within 24 hours of detection, a materially tighter window than the 72-hour GDPR standard. Fourth, a training programme for field and administrative personnel who handle personal data in Russian operations, calibrated to the categories of data and processing activities specific to their roles.

For the legislative context underlying this framework — including recent amendments to 152-FZ that affect operators in Russia — see our legislative update Legislative Amendment Affecting GDPR and Russian Federal Law 152-FZ. For a comparative doctrinal analysis of the two regimes, see Comparative Analysis: GDPR and Russian Federal Law 152-FZ. For matters involving regulatory compliance obligations across other Russian-law frameworks, the firm's Regulatory & Licensing practice provides complementary coverage.

Foreign companies with existing Russian operations may also wish to review the firm's Matters portfolio for sector-relevant examples of how compliance mandates of this nature have been handled in practice.

Frequently asked questions

Q: How long does it take to bring a Russian oil and gas operation into full compliance with 152-FZ?

A: There is no fixed statutory timetable, and timelines vary materially depending on the scale of the operation and the current state of its data infrastructure. In practice, operators who are starting from a basic compliance baseline — with no localised database and no current Roskomnadzor notification — should plan for a minimum of three to six months to complete the localisation architecture, file a compliant notification, and document the dual-regime processing register. Larger operators with complex IT infrastructure and cross-border transfer arrangements commonly take longer, particularly where group-level IT governance requires sign-off at multiple levels. The notification itself can be filed within days; the underlying data infrastructure work is typically the critical path item.

Q: What documents must a foreign oil and gas operator maintain to demonstrate 152-FZ compliance?

A: The core documentation set includes: a current Roskomnadzor notification that accurately reflects all processing activities; a processing register mapping each category of personal data to its legal basis under 152-FZ; written consent forms (in Russian) for processing activities that require consent under Russian law; data processing agreements with all processors engaged in Russian operations; records confirming the location of primary databases on Russian territory; and documentation of any cross-border data transfers, including the legal mechanism relied upon (typically, written consent for transfers to non-adequate countries). In practice, Roskomnadzor inspectors will review the notification first and then request the underlying documentation — operators whose records are current and internally consistent are better placed to manage inspection outcomes.

Q: What happens if an oil and gas company fails to localise personal data on Russian servers?

A: Non-localisation is the most seriously enforced violation under 152-FZ. Roskomnadzor has the authority to block access to the operator's information systems within Russia — a measure that has been applied to both consumer-facing services and, increasingly, corporate data infrastructure. In addition to blocking, administrative penalties apply and were materially increased by amendments taking effect from 2024. For an upstream operator, a block affecting field management or HSE platforms could create immediate operational disruption. Separately, non-localisation may trigger obligations under Russian labour law and licensing conditions that treat personal data of field personnel as subject to specific handling requirements. The consequence is not merely a compliance fine — it is a potential operational event.

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