Foreign transport companies operating in Russia face tightening 152-FZ localisation obligations that conflict with GDPR transfer rules. Understand the gap. Make an enquiry.
Alert: GDPR and Russian Federal Law 152-FZ — bridging requirements in the transport and logistics sector Effective: 15 January 2026
Foreign transport and logistics companies processing personal data in Russia are subject to a dual compliance obligation: Russian Federal Law No. 152-FZ requires that personal data of Russian individuals be stored and primarily processed on servers physically located in Russia, while the GDPR continues to govern transfers of EU-resident personal data to Russia as a third country without an adequacy decision. Roskomnadzor has continued to prioritise enforcement in operationally intensive sectors, and transport and logistics operators — whose systems routinely move employee, customer, and cargo-handler data across jurisdictions — are among the sectors facing the sharpest tension between these two frameworks. Companies that have not reviewed their data flows since implementing their initial 152-FZ localisation measures should treat this as a prompt to do so.
Foreign transport and logistics groups with Russian subsidiaries or branch operations are directly affected. The exposure arises specifically where: (a) EU-side systems receive or retain copies of personal data originating in Russia, whether for HR, customs documentation, fleet management, or shipment tracking purposes; (b) cross-border data transfers to parent or affiliate entities in the EU are not covered by an adequate legal mechanism under the GDPR; or (c) localisation on Russian-based infrastructure is incomplete or relies on vendor arrangements that have not been reviewed for 152-FZ conformity. Companies operating under the EAEU framework should note that 152-FZ localisation obligations apply independently of EAEU data flow rules — the two regimes do not substitute for one another.
Recommended action:
Map all personal data flows between your Russian and EU operations, distinguishing data of Russian individuals (subject to 152-FZ localisation) from data of EU individuals (subject to GDPR transfer rules).Verify that Russian-side storage infrastructure meets current Roskomnadzor expectations — vendor contracts and subprocessor chains should be reviewed, not assumed compliant from an earlier audit.Assess whether cross-border transfers from Russia to EU affiliates are covered by a GDPR-compliant transfer mechanism and document the legal basis on both sides of the transfer.Instruct Russian-qualified counsel before amending cross-border data processing agreements, as contract changes that resolve a GDPR gap may inadvertently create a 152-FZ exposure, and vice versa.
For guidance on the intersection of GDPR and 152-FZ obligations specific to the transport and logistics sector, see the firm's data protection practice: Data Protection — Vetrov & Partners. Further analysis is available at GDPR and Russian Federal Law 152-FZ: bridging requirements.
Speak to our team — info@vetrovpartners.com |
— Elena Pavlova Associate, Vetrov & Partners vetrovpartners.com/pavlova/
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