RRTReal Russia TodayThings you won’t hear from propaganda-driven media
No matching stories on this page.
NewsUN General Assembly recognized Russia as ‘occupying power’

Russia’s developers navigate Nordic compliance

17 November 2026

Russia’s developers are increasingly constrained by Nordic privacy, security, and platform-economy compliance rules as they serve clients in the region. While Nordic regulators have sought to safeguard data flows, Russia’s evolving legal landscape is also shaping how developers must operate. The result is a two-sided regulatory burden.

Nordic pressure on Russian-linked data flows

Nordic authorities have been tightening their scrutiny of personal data transfers tied to Russian-owned businesses. Finland and Norway temporarily suspended data transfers from Yango, the ride-sharing subsidiary of Russia's Yandex, over concerns about the FSB's access to customer data in Russia under September 2023 reforms. The bans expired 30 November 2023, but Nordic regulators are still examining Yango's European data flows, including potential data processing on Ridetech International's servers in the Netherlands.

Russia's platform-economy law, which takes full effect 1 October 2026, will add another compliance layer for Russian-led businesses. The law requires platforms like Yango to clarify grounds for account suspension and establish pre-trial complaint processes. Developers will need to put in place the necessary procedures and tools to meet this requirement.

Russia’s domestic compliance rules

While Nordic regulators are focused on data security, Russia's legal regime is shaping how developers can legally operate. The country's first law on artificial intelligence, signed in 2026, comes into force 1 September 2026. Provisions on sovereign and national AI models, developer obligations, labeling of AI-generated content, and some government powers take effect 1 March 2027.

Under the AI law, sovereign and national models must be developed by Russian legal entities and hosted in data centers owned by Russian legal entities and free from foreign control. Developers of these models must ensure model security, define usage rules, and maintain technical documentation.

In addition, Russia's data localization rules require personal data of Russian citizens to be stored on servers inside Russia. This is in contrast to GDPR, which requires additional safeguards, including Standard Contractual Clauses, before personal data of EU residents can be transferred to Russia. As a result, developers serving both markets may need to implement data storage and transfer solutions that can flexibly cater to these differing compliance requirements.

Contracting and operating model

The combination of Nordic and Russian legal requirements is reshaping the contracting and operating model for developers in the region. For instance, agreements with a foreign legal element—covering projects listed across regional platforms like Spilloversikt—can be governed by foreign law at the parties' discretion. However, developers must ensure that source code, object code, and compilation tools are located in Russia, and that remote control of programs from abroad is not allowed.

As a result, developers are increasingly structuring their contracts and delivery teams to meet these requirements. This may involve setting up local entities, using local data centers, and building up local development and implementation capabilities. Developers may also need to put in place robust data protection and security controls, as well as compliance management processes, to meet both Nordic and Russian regulatory expectations.

Practical takeaway for businesses

As a result, businesses engaging with developers in Russia need to be aware of the potentially conflicting compliance requirements they may face. This includes understanding the data localization, security, and platform economy rules that will shape how developers can operate.

Businesses should assess their data storage and transfer needs, and put in place appropriate controls to comply with both Nordic and Russian regulations. They may also need to work with developers to ensure that contracts, team structures, and delivery processes are aligned with the relevant legal requirements.

In practice, this may mean implementing flexible data storage and transfer solutions, setting up local entities and data centers, and building up local development and implementation capabilities. Businesses should also consider putting in place robust compliance management processes to monitor and manage their compliance status over time.

Ultimately, navigating the Nordic and Russian compliance landscape will require a nuanced understanding of the relevant legal requirements, as well as a pragmatic approach to structuring contracts, teams, and delivery processes. By proactively managing these issues, businesses can continue to leverage Russian development capabilities while meeting their compliance obligations in the Nordic region.