Personal data
Personal data is not only a name and a phone number: an individual’s tax number and data from open registers count too. Sending them to a foreign service raises the question of cross-border transfer. The main problem, according to the author of a review the publication cites, is that most international providers of language models have no processing contract. Replacing names with tokens such as user_123 does not help if the link can be restored. Relatively safe options, according to the same publication: Russian cloud platforms with a contract, a model inside your own infrastructure, or anonymization before sending.
Access to foreign APIs
As of 29 September 2026, Russia is not on the list of supported countries of two large foreign providers. Since 9 July 2024 one of them has blocked API traffic from unsupported countries, and under its rules, access from unsupported countries, including through intermediaries, may lead to an account block. For a business this is an operational risk, not only a legal one: the channel can disappear any day.
Law 243-FZ
Since 1 September 2026 Russia has had a law on support for AI technology development: statuses of a sovereign and a national model, criteria from 1 March 2027, and a transition period for existing systems until 2032. From 1 March 2027 the government will be able to define cases where only such models are allowed. Our blog has an analysis for business.
Three classes of data
Public and anonymized data: any API. Personal and commercial data: a Russian cloud with a processing contract, or a local model. Source code, medical and credit documents, state secrets and critical information infrastructure: only a local setup. This is what a telecom operator, Moscow healthcare and an airport from this section’s cases did, and a developer chose an isolated setup on a Russian model. After source code leaked through a chatbot in 2023, a large electronics maker banned outside services and began building its own.