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

Cross-border data transfer restrictions from Russia in the transport and logistics sector: key developments in 2026

Elena Pavlova · February 2026 · 9 min read

Russian data transfer rules tightened in 2026, imposing new compliance obligations on transport operators with foreign data flows. Make an enquiry.

Following amendments to Russian personal data legislation that took effect in stages since 2022 and continued to generate enforcement activity through early 2026, foreign companies operating in Russia's transport and logistics sector face materially different compliance obligations than they did three years ago. The cross-border transfer of personal data — covering driver records, customer details, freight documentation, and telematics — now requires prior notification, and in many cases prior authorisation, from Roskomnadzor, Russia's data protection supervisory authority. For in-house counsel at multinationals running logistics operations in Russia, understanding what has changed and what remains uncertain is not optional: Roskomnadzor's enforcement posture has hardened, and the sector's data flows are among the most operationally complex to restructure.

§ I. What has changed in cross-border data transfer rules under Russian law?

The regulatory framework governing cross-border data transfers from Russia is set out in Russian personal data legislation — Federal Law No. 152-FZ — as amended. The practical turning point came with the 2022 amendments, which replaced the previous regime's more permissive default with a two-stage mechanism: operators must first notify Roskomnadzor of an intended cross-border transfer, providing details of the recipient country, the categories of data, the legal basis for the transfer, and the measures in place to protect data subjects. They must then await confirmation from Roskomnadzor before proceeding.

Before the 2022 amendments, Russian operators and their foreign affiliates commonly relied on a simplified approach: ensuring that the recipient country appeared on the list of states deemed to provide adequate protection, or obtaining contractual commitments from the foreign recipient. That framework provided reasonable commercial predictability. The post-2022 position is structurally different. Transfers to countries not on the approved list — which includes European Union member states, the United Kingdom, and the United States — require an assessment of whether Roskomnadzor will authorise the transfer, and that assessment has produced inconsistent outcomes across sectors.

For the transport and logistics sector, the 2026 picture involves two overlapping developments. First, Roskomnadzor has continued refining its interpretation of which data categories generated in logistics operations constitute personal data requiring full compliance — including, as has become the prevailing approach, certain telematics and geolocation records linked to individual drivers. Second, enforcement scrutiny of logistics operators specifically increased through 2025 into 2026, with inspections targeting companies whose data architectures route Russian-originated driver, customer, and freight-booking data to group IT systems based outside Russia.

A material carve-out applies for transfers to EAEU member states — Kazakhstan, Belarus, Armenia, and Kyrgyzstan — and, under most current interpretations, to other CIS member states. These destinations do not require the same authorisation procedure, which is operationally significant for logistics operators whose primary cross-border flows run along established EAEU trade corridors.

§ II. Which foreign companies in transport and logistics are most affected?

The compliance burden does not fall uniformly across the sector. In-house counsel should map their Russian entity's data flows against three primary exposure categories.

The first category covers international freight forwarders and road haulage operators with consolidated logistics management systems. These businesses typically process personal data of Russian-resident drivers and warehouse staff in centralised platforms hosted in the EU, Switzerland, or the United States. Under the current Russian rules, each data category flowing to those platforms requires an active notification on file with Roskomnadzor, and categories transmitted without authorisation expose the Russian operating entity to regulatory action.

The second category covers passenger transport operators — including rail, coach, and aviation ground handling companies — that transmit booking and passenger identification data to parent group systems outside Russia. Roskomnadzor has consistently treated passenger identification data as a high-sensitivity category, and the combination of volume and personal identifiability has made passenger transport operators a focal point for enforcement.

The third category — one that has attracted less commentary but presents real operational risk — covers third-party logistics providers and platform-based freight marketplaces that aggregate Russian driver data in cloud environments located outside Russia. These operators often do not hold Russian legal entity status themselves, processing data through a foreign principal structure. The question of which entity bears the compliance obligation in that structure has not been definitively resolved by Russian courts or by Roskomnadzor's published guidance, and the prevailing approach in practice has been to treat the Russian-resident data controller as the primary obligated party.

For all three categories, the data localisation requirement — which predates the 2022 amendments and requires that personal data of Russian subjects be initially collected and stored on servers physically located in Russia — remains fully in force and is enforced separately from the cross-border transfer regime. Compliance with localisation does not substitute for compliance with the transfer notification and authorisation procedure.

For in-house counsel managing a Russian logistics subsidiary whose data architecture routes personal data outside Russia, mapping current flows against Roskomnadzor's notification register is the logical first step before the authority initiates contact.

If your company operates in Russia's transport or logistics sector and processes personal data with cross-border flows, our team can assist with a compliance review — make an enquiry: info@vetrovpartners.com |

§ III. What should foreign companies do now?

The compliance steps are sequential and time-sensitive. Russian personal data legislation does not provide a grace period for operators who discover a notification gap during an inspection — the obligation attaches at the point the cross-border transfer commences.

The first step is a data flow audit scoped to Russian-resident individuals. This means identifying all categories of personal data collected by the Russian entity, the jurisdictions to which that data flows (including intermediary processors), and the legal basis asserted for each transfer. For logistics operators, this exercise commonly surfaces data flows that predate the current regulatory framework and were never formally assessed against the 2022 requirements.

The second step is to file or update notifications with Roskomnadzor for each transfer where a notification has not been lodged, or where the notification on file does not accurately describe current data categories or recipient countries. The notification is a live document — changes in the transfer scope require an updated filing, not merely an internal record update.

The third step, where notification alone is insufficient for the transfer to proceed — typically because the recipient country is not on the approved list and the data category is sensitive — is to assess whether to seek authorisation or to restructure the transfer. Restructuring options include migrating the relevant data processing to a Russian-based system, appointing a local data processor, or limiting the categories transmitted to the foreign system to those for which authorisation is more straightforwardly available. Each option has different cost, timeline, and contractual implications that require legal and technical assessment in parallel.

The fourth and most frequently neglected step is to review existing agreements with foreign affiliates and third-party processors to confirm that the contractual basis for data transfer remains consistent with current Russian regulatory requirements. Many agreements concluded before 2022 contain cross-border transfer clauses that no longer accurately reflect the applicable procedure.

Open questions remain on two points. The scope of Roskomnadzor's interpretive guidance on telematics data in the logistics context has not been set out in a formal instrument — the prevailing approach rests on inspection outcomes and informal guidance, and operators should not assume consistency across circuits. Additionally, the intersection of Russian personal data obligations with transport-specific regulatory frameworks — including requirements under Russian transport safety legislation for the retention and transmission of driver working time data — has not been formally harmonised, and operators face the possibility of conflicting obligations that require case-by-case legal analysis.

"The transport and logistics sector sits at the intersection of operational data intensity and regulatory scrutiny — companies that have not revisited their cross-border data flows since 2022 are carrying a compliance gap that Roskomnadzor is increasingly equipped to identify." — Elena Pavlova, Associate, Vetrov & Partners

Frequently asked questions

Q: What specifically changed in Russian rules on cross-border data transfers, and when did the change take effect?

A: The substantive change came with amendments to Federal Law No. 152-FZ that took effect in stages from September 2022. The amendments replaced an approach that permitted cross-border transfers to "adequate" countries without prior regulatory engagement, with a mandatory two-stage procedure: first, notification to Roskomnadzor setting out the recipient country, data categories, legal basis, and protective measures; second, a waiting period before the transfer can commence. Transfers to countries not on Roskomnadzor's approved list — which includes most Western jurisdictions — require a positive assessment from the authority. The 2022 amendments have been operative for several years, but enforcement activity and interpretive guidance continued to develop through 2025 and into 2026, meaning that operators who filed notifications in 2022 may need to review whether those filings remain accurate.

Q: Which transport and logistics operators are most at risk of Roskomnadzor enforcement action over cross-border data transfers?

A: Enforcement risk is highest for three operator profiles: international freight forwarders and haulage companies with centralised IT systems outside Russia that process Russian driver and operational data; passenger transport operators transmitting identification and booking data to foreign group systems; and platform-based freight marketplaces aggregating Russian driver data in foreign cloud environments. Risk is compounded when the operator has not filed a notification with Roskomnadzor, when the notification on file does not accurately describe current data flows, or when no formal cross-border transfer assessment has been conducted since 2022. EAEU-bound transfers — to Kazakhstan, Belarus, Armenia, and Kyrgyzstan — carry a lower procedural burden and are generally outside the authorisation requirement.

Q: What practical steps should in-house counsel take now to assess and address a Russian cross-border data transfer compliance gap?

A: Four steps, in sequence. First, conduct a data flow audit scoped to Russian-resident individuals, identifying all data categories, destination jurisdictions, and transfer legal bases. Second, file or update notifications with Roskomnadzor for each transfer not currently covered by an accurate notification. Third, assess — with legal and technical input — whether any transfers require formal authorisation or whether restructuring (local processing, limiting categories transmitted, or appointing a Russian processor) is the more practical route. Fourth, review existing agreements with foreign affiliates and processors to ensure the contractual basis for transfer is consistent with current Russian requirements. The Data Protection practice at Vetrov & Partners can assist at each stage.

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