Foreign companies in Russia face dual obligations under GDPR and 152-FZ. This guide maps the data localisation bridge for counsel. Make an enquiry.
Unlike the GDPR, which applies on the basis of establishment or targeting of EU data subjects regardless of where data is stored, Russian Federal Law 152-FZ imposes a territorial storage obligation: personal data of Russian citizens must initially be collected and recorded using databases physically located in Russia. For in-house counsel at a foreign company with a Russian subsidiary, a local distribution network, or Russian-resident employees and customers, this creates a genuine dual-compliance burden. Neither framework acknowledges the other, yet both apply simultaneously to a significant share of ordinary commercial data processing. Understanding where the obligations overlap, where they diverge, and how to structure a defensible position under both is the practical starting point for any compliance programme.
Before working through the steps below, gather the following materials. Attempting to build a localisation or transfer architecture without this baseline will produce a document that does not reflect actual data flows.
If you are unsure whether your current data inventory is sufficient for a 152-FZ compliance review, our Data Protection practice can assist — make an enquiry: info@vetrovpartners.com |
The territorial scope of 152-FZ is determined primarily by the data subject's citizenship or residence status, not by the location of the company processing the data. A foreign company that collects personal data from Russian citizens through a website, a mobile application, or a Russian subsidiary is subject to the localisation requirement, even if the company itself is incorporated outside Russia and has no physical presence there.
The central obligation is this: when personal data of Russian citizens is collected, the initial recording, systematisation, accumulation, storage, and retrieval must take place using databases located in Russia. Subsequent cross-border transfer to foreign systems is not prohibited outright, but it must follow from a primary Russian database, and the Russian version must remain current and accessible to Roskomnadzor on request.
For in-house counsel, the practical question is not whether 152-FZ applies in the abstract but which specific processing activities trigger the localisation requirement. The following categories routinely give rise to compliance obligations for foreign companies: HR data for Russian employees (payroll records, employment files, performance data); customer and end-user databases that include Russian-resident individuals; CRM and marketing systems that target Russian-resident contacts; and e-commerce platforms that process Russian shipping and payment data.
Processing that involves only legal entities and does not capture natural-person data does not engage 152-FZ. Similarly, anonymised or aggregated data that cannot identify an individual is outside the personal data definition. These distinctions matter when scoping the localisation programme and should be documented explicitly.
Once the applicable processing activities are identified, the next task is to ensure that the primary database for each is hosted in Russia. This does not require a self-owned data centre. The principal options are a Russian cloud provider (several major providers operate ISO 27001-certified facilities in Russia), a colocation arrangement with a Russian hosting company, or use of an existing Russian subsidiary's IT infrastructure, subject to appropriate processor agreements.
Three technical configurations are commonly used to satisfy the localisation requirement while maintaining integration with global systems. The first is a Russian-primary, global-mirror model: the primary database resides in Russia; a replicated copy is maintained offshore for global business continuity. The second is a data segregation model: Russian-resident personal data is held in a separate, Russia-hosted partition of an otherwise global system. The third is a dedicated Russian instance: a standalone deployment of the company's core HR, CRM, or ERP platform, hosted in Russia and not integrated with the global instance.
Each configuration carries different operational and compliance implications. Counsel should ensure that the chosen architecture is documented in the RoPA, that processor agreements with the Russian hosting provider meet both 152-FZ requirements (including security measures and data subject rights provisions) and GDPR Article 28 requirements, and that the data flow mapping accurately reflects the direction of replication — Russian database first, offshore copy second.
A recurring issue in practice is the use of global SaaS platforms — HR information systems, marketing automation tools, and customer support platforms — that do not offer a Russia-hosted deployment option. In those cases, the company must either migrate to a Russia-compliant alternative for the affected data categories, implement a technical gateway that creates a Russia-hosted record before data enters the global system, or document a legal basis for transfer as discussed in Step 3.
This is the section most likely to create tension between the two frameworks. Under GDPR, transfers of personal data to Russia are transfers to a third country without an EU adequacy decision. The available mechanisms are Standard Contractual Clauses (SCCs), Binding Corporate Rules, or — in limited circumstances — derogations under Article 49. Under 152-FZ, cross-border transfer of Russian citizens' personal data is permitted subject to notification to Roskomnadzor and the requirement that the destination country provides an adequate level of personal data protection (with a positive list maintained by Roskomnadzor), or alternatively, on the basis of the data subject's consent or the performance of a contract to which the data subject is a party.
The result for a company processing Russian-resident data is that two transfer analyses run in parallel. For data flowing from the EU into Russia (for example, where EU-based group HR systems receive data from a Russian subsidiary), GDPR governs the outbound transfer from the EU and Russian law governs what happens once the data reaches Russia. For data flowing from Russia to the EU or elsewhere, 152-FZ governs the outbound transfer from Russia and GDPR governs its receipt and further processing in the EU.
Companies in EAEU member states — Kazakhstan, Belarus, Armenia, and Kyrgyzstan — benefit from a slightly different position under Russian regulatory practice: Roskomnadzor has historically treated EAEU member states as providing adequate protection, which simplifies the cross-border transfer analysis for intra-EAEU flows. Foreign companies with group structures spanning EAEU jurisdictions should map these flows separately.
The practical approach is to implement SCCs for GDPR purposes and ensure that the 152-FZ transfer notification is on file with Roskomnadzor for each relevant destination country. Where the destination country appears on Roskomnadzor's positive list, no additional 152-FZ consent is required. Where it does not, data subject consent or a contractual necessity analysis is required. Documentation of both analyses should be consolidated in a single transfer impact record that can be produced to either regulator.
For companies managing parallel GDPR and 152-FZ transfer obligations across multiple group entities, an integrated compliance review can identify gaps before either regulator does — make an enquiry: info@vetrovpartners.com |
Roskomnadzor is the federal supervisory authority responsible for enforcement of 152-FZ. Its principal enforcement tools include scheduled and unscheduled inspections, mandatory notification requirements, administrative proceedings before courts, and — for persistent or serious non-compliance — requests to Roskomnadzor's own blocking authority, which permits it to seek restriction of access to websites and online services that violate the localisation requirement.
Penalties for 152-FZ non-compliance were substantially increased by legislative amendments that took effect in the period 2022–2024. The penalty regime now distinguishes between first and repeat violations, with repeat violations attracting significantly higher fines. The most serious category — failure to localise personal data of Russian citizens in Russian databases — carries per-violation fines for legal entities that, at current levels, represent a meaningful compliance cost even for large organisations. Counsel should obtain current penalty figures from a Russian-qualified practitioner before completing a risk assessment, as the schedule has been amended several times and figures in published English-language sources are frequently outdated.
The notification obligations that foreign companies most commonly overlook are: the obligation to notify Roskomnadzor of the commencement of personal data processing before processing begins (not after); the obligation to notify of any cross-border data transfer to a country not on the positive list; and the obligation to notify of personal data breaches within the statutory timeframe, which is materially shorter than the GDPR's 72-hour window.
Under Russian insolvency legislation, data obligations of a Russian subsidiary do not automatically transfer to the parent on liquidation — but the subsidiary's regulatory record, including any outstanding enforcement correspondence, will be visible to Roskomnadzor in any future inspection of a successor entity or related company. This makes clean-up of legacy notification gaps a worthwhile investment before any corporate restructuring.
Foreign companies holding Russian personal data assets should be aware that failure to localise, if detected, does not produce an immediate blocking order in most cases — Roskomnadzor's standard practice is to issue a non-compliance notice and require remediation within a defined period. However, the remediation period is short, and the regulator has demonstrated a willingness to escalate to blocking proceedings where remediation does not occur. This enforcement trajectory reinforces the case for proactive compliance rather than reactive remediation.
Achieving a compliant baseline is the beginning, not the end, of the programme. Both 152-FZ and GDPR impose ongoing obligations that require embedded compliance processes rather than one-off documentation exercises.
Under 152-FZ, the company must maintain a current and accurate privacy notice in Russian (or in a language accessible to Russian data subjects) that reflects actual processing activities, storage locations, and transfer arrangements. Data subject rights requests — access, rectification, erasure, and objection — must be handled within the statutory timeframes. Internal records of processing, including the register of personal data processing systems, must be updated whenever the scope, purpose, or technical architecture changes. Processor agreements with Russian vendors must be reviewed on renewal and when vendors change their own sub-processors or hosting arrangements.
Under GDPR, the transfer mechanisms in place for Russia-bound transfers must be reviewed against any updates to the SCC framework or changes to the legal and regulatory environment in Russia. Data Protection Impact Assessments (DPIAs) may be required for high-risk processing activities involving Russian data subjects, including large-scale profiling, systematic monitoring, and processing of special category data.
The point where the two frameworks most usefully converge is accountability documentation. A consolidated data processing register that maps each processing activity to its legal basis under both 152-FZ and GDPR, its storage location, its transfer mechanism, and its data subject rights procedure gives in-house counsel a single reference document that is responsive to inspections under either regime. Maintaining this register in both Russian and English reduces the friction of dual-regulator engagement.
Finally, the regulatory landscape for data localisation in Russia continues to evolve. The period 2022–2026 has seen multiple amendments increasing penalties, expanding Roskomnadzor's inspection and blocking powers, and introducing new breach notification requirements. In-house counsel at foreign companies with Russian operations should treat their 152-FZ programme as a living compliance document and schedule an annual review with Russian-qualified data protection counsel.
To review or establish a 152-FZ compliance programme aligned with your GDPR obligations, contact our Data Protection practice — make an enquiry: info@vetrovpartners.com |
Q: How long does it take to achieve full 152-FZ compliance for a foreign company that is starting from scratch?
A: For a foreign company with an established Russian subsidiary and identifiable data flows, a baseline compliance programme — covering system localisation, Roskomnadzor notification, privacy notices, and transfer documentation — typically takes three to six months to implement, depending on the complexity of the IT architecture and the number of third-party processors involved. Companies relying on global SaaS platforms that require migration or technical adaptation will find that the technical component, rather than the legal one, determines the timeline. The legal documentation can generally be prepared within four to six weeks once the technical architecture is confirmed.
Q: What documents does a foreign company need to have in place to satisfy both 152-FZ and GDPR data localisation requirements?
A: At a minimum, a defensible dual-compliance position requires: a data processing register that maps each activity to its legal basis under both frameworks; processor agreements with Russian-based hosting providers that meet both Article 28 GDPR and 152-FZ security requirements; Roskomnadzor notification filings for processing commencement and cross-border transfers where required; Standard Contractual Clauses or equivalent GDPR transfer mechanism for data flowing between Russia and the EU; a Russian-language privacy notice accessible to Russian data subjects; and an internal data breach response procedure that addresses both the GDPR 72-hour notification window and the shorter Russian statutory timeframe. These documents should be maintained in both Russian and English.
Q: What happens if a foreign company's global SaaS providers cannot offer Russia-hosted infrastructure?
A: If a global provider cannot offer a Russia-hosted deployment, the company has three principal options. First, it can migrate the relevant data categories — typically Russian employee and customer data — to a Russia-compliant alternative provider. Second, it can implement a technical gateway that creates a Russia-hosted primary record before data enters the global system, satisfying the initial recording requirement under 152-FZ while maintaining global system integration. Third, in limited circumstances, it can document a legal basis for processing outside Russia under 152-FZ — such as data subject consent or contractual necessity — though this approach is narrower in scope than localisation and carries enforcement risk if applied broadly. The preferred approach depends on the volume of Russian-resident personal data involved and the technical feasibility of each option in the specific system environment. Russian-qualified data protection counsel should assess the risk exposure before the company commits to option three.
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