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

Procedural considerations in Federal Law 152-FZ personal data requirements in Russia

Elena Pavlova · January 2026 · 4 min read

Foreign companies must meet procedural requirements under Federal Law 152-FZ Russia. Key registration, consent, and localisation steps explained. Make an enquiry.

Foreign companies with Russian operations are subject to Federal Law 152-FZ on Personal Data regardless of where their legal seat is located. The operative rule is this: any entity that processes the personal data of Russian citizens — whether through a website accessible in Russia, a local subsidiary, a CRM system, or employment records for Russian-based staff — is a data operator under Russian law and must comply with the procedural requirements that status entails. Non-compliance exposes the entity to Roskomnadzor investigation, administrative penalties, and, in serious cases, mandatory website blocking.

What the rule requires

Under Russian data protection legislation, foreign companies acting as data operators face four principal procedural obligations.

First, notification. Before commencing processing activities, the operator must notify the Federal Service for Supervision in the Sphere of Telecom, Information Technologies, and Mass Communications — Roskomnadzor — of its status as a personal data operator. The notification is submitted through the Roskomnadzor online portal and must specify the categories of data processed, the processing purposes, the legal basis for processing, and the data retention periods. Omitting the notification is itself a basis for enforcement action, independent of any underlying compliance failure.

Second, data localisation. The initial recording, systematisation, accumulation, storage, clarification, and retrieval of personal data of Russian citizens must be performed using databases physically located in Russia. This applies to foreign operators as well as domestic ones. In practice, this requirement most commonly affects foreign companies that centralise HR or customer data on servers outside Russia without maintaining a Russian-resident copy. Routing data through a Russian data centre or engaging a certified Russian cloud provider are the standard approaches. The localisation obligation does not preclude subsequent transfer of the data abroad provided the localisation step occurred first.

Third, consent. Processing based on the data subject's consent requires that the consent be specific, informed, and capable of being withdrawn. Consent obtained through general terms and conditions that bundle data processing permissions with unrelated commercial terms is, under the prevailing regulatory interpretation, unlikely to satisfy the standard. Where consent is the chosen legal basis, operators should maintain a granular record of what was consented to and when, capable of being produced to Roskomnadzor on request.

Fourth, cross-border transfers. Transfer of personal data to a state that Roskomnadzor has assessed as providing adequate protection follows a streamlined procedure. Transfer to other states requires prior written notification to Roskomnadzor and, in many cases, contractual safeguards. The list of adequate states is maintained by Roskomnadzor and updated periodically; in-house counsel should verify current status before configuring data flows to any jurisdiction outside the EAEU.

Note: Failure to comply with the data localisation requirement is a distinct and separately penalised violation. Roskomnadzor may order blocking of the operator's web resources in Russia without prior judicial approval. For a foreign company whose Russian revenue depends on online customer access, this is a material operational risk, not merely a regulatory formality.

How it applies in practice

The procedural requirements above apply in layers that are not always apparent from a face-value reading of the legislation. In practice, in-house counsel managing Russian data compliance should attend to three points that frequently create issues.

The operator register notification must be kept current. Changes in processing scope, purposes, or the categories of subjects affected must be reflected by an updated notification. Companies that notified Roskomnadzor at initial market entry and have since expanded their Russian operations — adding employee data from a new Russian subsidiary, for instance, or integrating Russian customer records into a group-wide CRM — may find their existing notification no longer accurately describes actual processing activities. An outdated notification does not provide a defence against enforcement for processing that exceeds its scope.

Localisation documentation must be capable of demonstrating physical server location, not merely contractual commitment. During a Roskomnadzor inspection, the regulator may request confirmation that the localisation requirement is satisfied in fact, not just in the terms of a data processing agreement. Cloud arrangements in particular require careful review: a contract with a provider that routes data through Russian infrastructure is not the same as verified localisation. Operators should obtain and retain confirmation from their providers specifying the physical location of data at rest.

Consent records require a structured approach. Where the operator processes data of Russian-based employees, the consent framework must be adapted to the employment context. Russian data protection law treats employee data processing as a sensitive area, and some categories of employee data require explicit, written consent even where a general employment contract is in place. Foreign employers who rely on group-level consent templates not adapted for Russian law should treat this as a gap requiring correction.

For a broader analysis of the substantive obligations under Federal Law 152-FZ, including the full scope of data operator status and lawful processing grounds, see Federal Law 152-FZ: Personal Data Requirements in Russia and A Practical Guide to Federal Law 152-FZ for Foreign Companies.

The firm's Data Protection practice advises foreign companies on 152-FZ compliance, Roskomnadzor notification, and cross-border transfer frameworks.

If your Russian subsidiary or group-level data processing arrangements have not been reviewed against current 152-FZ requirements — 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