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

Strategic notes on GDPR and Russian Federal Law 152-FZ: bridging requirements in the technology and software sector for cross-border practitioners

Elena Pavlova · May 2026 · 5 min read

Technology companies in Russia face overlapping GDPR and 152-FZ obligations. Key compliance divergences for in-house counsel. Make an enquiry.

Foreign technology companies processing personal data of Russian users operate under two distinct regulatory regimes simultaneously: the EU General Data Protection Regulation and Russian Federal Law No. 152-FZ on Personal Data. The two frameworks share surface-level similarities — lawful basis requirements, data subject rights, documented accountability obligations — but diverge materially on localisation, cross-border transfer mechanisms, and the role of the national regulator. For in-house counsel managing compliance across both systems, the divergences create operational friction that is rarely resolved by applying one framework's logic to the other.

What the dual framework requires

Both GDPR and 152-FZ impose a documented legal basis for processing personal data of individuals within their respective territorial scopes. For a technology or software company serving users in Russia, this means that a single processing activity — user account creation, behavioural analytics, cloud-based storage — may require parallel justification under two different legal systems that do not map onto each other.

The localisation obligation under 152-FZ has no direct GDPR equivalent. Russian legislation requires that, when collecting personal data of Russian citizens, the initial recording, systematisation, accumulation, storage, and modification of such data must take place on servers located within the Russian Federation. This applies regardless of where the company is incorporated or where its primary infrastructure sits. GDPR, by contrast, does not restrict where within the EEA data must be physically stored, provided adequate safeguards govern any transfer outside it.

Cross-border transfer rules create a further structural divergence. GDPR permits transfers to third countries on the basis of adequacy decisions, standard contractual clauses, binding corporate rules, or other recognised mechanisms. Russian law operates a separate cross-border transfer notification and authorisation regime administered by Roskomnadzor, the Federal Service for Supervision of Communications, Information Technology and Mass Media. A transfer that is lawful under GDPR standard contractual clauses does not automatically satisfy 152-FZ cross-border transfer requirements. Companies that have relied exclusively on GDPR transfer mechanisms for their Russia-facing operations have, in practice, found themselves non-compliant with the Russian procedural requirements.

Note: Roskomnadzor retains the authority to block access to digital services and platforms operating in Russia where 152-FZ obligations are not met. Enforcement has been exercised against technology companies — including those operating internationally — and the procedural pathway from investigation to access restriction can move quickly once a formal inquiry is opened. In-house counsel should not treat localisation and cross-border transfer obligations as aspirational — they are enforceable conditions of market access.

How this applies in the technology and software sector

Technology and software companies face a set of compliance pressure points that are distinct from those encountered in other sectors. Three patterns recur most frequently in practice.

The first concerns cloud infrastructure and SaaS architectures. A company offering software-as-a-service to Russian enterprise clients will typically process end-user personal data through shared cloud infrastructure hosted outside Russia. Under 152-FZ, the initial processing of Russian citizen data must occur on Russian-hosted servers. Where the SaaS architecture does not permit data segregation by geography, structural remediation — not policy remediation alone — is required. Documenting an intent to localise is not a substitute for actual localisation.

The second concerns data subject rights fulfilment. Both GDPR and 152-FZ provide data subjects with rights to access, correction, and deletion. The timelines differ: the Russian framework prescribes specific response periods that may be shorter than those to which a company's global privacy operations team is accustomed. Relying on GDPR-calibrated response workflows to handle requests from Russian data subjects creates compliance gaps that Roskomnadzor assessments have historically identified.

The third concerns consent architecture. Russian law has specific requirements for the form and content of consent to personal data processing — including, in certain contexts, requirements for written consent that GDPR's broader flexibility around freely given, specific, informed, and unambiguous consent does not replicate. Consent banners and privacy notices designed to satisfy GDPR will not, without amendment, satisfy 152-FZ consent requirements across all processing categories.

Mapping these three dimensions requires a compliance gap analysis that treats the two frameworks as independent systems, identifies the points of divergence, and sequences remediation steps by regulatory risk. The Data Protection practice at Vetrov & Partners conducts this analysis as a structured engagement, producing a documented compliance matrix specific to the client's technology stack and user base.

For companies that have recently reviewed their compliance position under GDPR following legislative amendments affecting the Russia-facing data transfer framework, the companion analysis at Legislative amendments affecting GDPR and Russian 152-FZ compliance sets out the current regulatory position in detail. The broader framing of bridging requirements across both frameworks is addressed in GDPR and Russian Federal Law 152-FZ: bridging requirements.

What to do

Three actions are typically the starting point for in-house counsel managing this compliance intersection.

Conduct a data-flow audit specific to Russian user data. Map where personal data of Russian citizens is collected, initially processed, and subsequently transferred. Identify any flows that traverse the localisation obligation without a compliant Russian-hosted processing step.Review cross-border transfer documentation for Russia-specific compliance. Confirm that any transfer of Russian citizen data to servers outside the Russian Federation has been notified to and authorised by Roskomnadzor under the applicable Russian procedure — not simply covered by a GDPR transfer mechanism.Audit consent and data subject rights procedures for 152-FZ conformity. Verify that consent language, form requirements, and response timelines satisfy Russian legislative standards independently of GDPR compliance.

For in-house counsel overseeing a Russian subsidiary or a Russia-facing technology product, the regulatory exposure from non-compliance with 152-FZ is a market-access risk, not merely a procedural one. Early-stage gap analysis, before a Roskomnadzor inquiry is opened, preserves the widest range of remediation options.

To discuss your company's compliance position under Russian Federal Law 152-FZ — make an enquiry: info@vetrovpartners.com |

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