MMOOZZGG.com

AI for lawyers

Cross-border data transfer to a foreign AI service: what Russian law requires

6 min read5 sources

Cross-border data transfer through AI starts the moment a lawyer pastes a contract or correspondence with a client’s name, passport and address into a foreign AI service. Since 1 March 2023, before such a transfer, the operator must file a notice with Roskomnadzor, Russia’s data protection regulator, under Part 3, Article 12 of 152-FZ, Russia’s personal data law. Below, step by step: when a prompt counts as a transfer, what the notice must contain, how this links to database localization and when it is simpler to run the model in Russia.

On this page · 4 sections

When a prompt is a data transfer

Clause 11, Article 3 of 152-FZ defines a cross-border transfer as a transfer of personal data to the territory of a foreign state, to a public authority, a foreign individual or a foreign legal entity. The law has no separate rule for chatbots.

If the service’s server and the company that processes the request are abroad, a foreign legal entity receives the text with the client’s data. It does not matter whether the text was pasted into the chat window, uploaded as a file or read by the service from email.

Three typical cases in a lawyer’s work:

1. A contract, a statement of claim or correspondence with surnames, passport data, addresses and phone numbers is pasted into a prompt.

2. Case materials are uploaded to the service: statements, minutes, powers of attorney, the client’s medical or bank documents.

3. The service is connected to the firm’s email or storage and reads incoming documents itself, including attachments.

A prompt without personal data does not fall under Article 12. A general question about how to interpret a rule, or a request to shorten the published text of a law, is not a data transfer.

In this setup, the operator is the firm or company where the lawyer works: it defines the purposes of processing and is responsible for where an employee sent the text. The roles of operator and processor are covered in detail in our article on AI and personal data.

The Roskomnadzor notice

Part 3, Article 12 of 152-FZ requires the operator to notify Roskomnadzor of its intention to make a cross-border transfer before it starts. This is a separate document: the notice of personal data processing under Article 22 does not replace it.

The procedure before the first data goes to a foreign service:

1. Get from the recipient information on its data protection measures and the conditions for ending processing (Part 5, Article 12). For a public chatbot, you will have to collect this from the service’s user agreement and privacy policy.

2. Assess how the recipient keeps data confidential and secure, and record the date of the assessment: it goes into the notice.

3. State in the notice the legal basis and purpose of the transfer, the categories and list of data, the categories of data subjects and the list of countries (Part 4, Article 12).

4. File the notice and wait: Roskomnadzor decides whether to ban or limit the transfer within ten working days (Part 9, Article 12).

If the recipient’s country is not on the list of states with adequate protection of data subjects’ rights, you may not transfer data before this period ends (Part 11, Article 12). Check the country against the list before you file the notice.

In practice, the notice is written for a specific service and specific data. A lawyer who chose a new chatbot and uploaded a case to it skips this procedure, and the firm will answer for it.

Database localization

A second rule works next to Article 12. Under Part 5, Article 18 of 152-FZ, the personal data of Russian citizens is collected and stored in databases in Russia, and a cross-border transfer notice does not cancel this duty.

For a firm whose lawyers work in a foreign chatbot, the risk is double. The dialog history with the texts of contracts and case materials is stored on the service’s server: in effect, an archive of documents with personal data abroad, and the firm controls neither how long it is kept nor who can access it.

What to check in the firm under this rule: where the request history of each AI service is stored, whether the firm can delete it, and who at the vendor has access to it. If the contract gives no answer, assume the firm does not control it.

For breaking the localization rule, a legal entity pays up to $72,000 under Part 8, Article 13.11 of the Code of Administrative Offenses. The size of fines for leaks is covered in our article on fines for personal data.

Not only personal data leaves with the text. Information about a case is protected by professional secrecy, and this question is covered on the page about attorney secrecy and AI.

The alternative: a model in Russia

The notice, the recipient assessment and the ten working days of waiting are needed while data goes abroad. If the model runs on the firm’s server or in a cloud in Russia, there is no cross-border transfer, and the Article 12 procedure does not start.

Law 243-FZ, in force since 1 September 2026, sets the same direction: the data of sovereign and national models is processed in Russia, and the government defines the cases where such models are mandatory.

What such a setup looks like for a law firm:

1. The model runs on the firm’s server or in a Russian cloud, and the prompt text does not leave the country.

2. Personal data is processed on servers in Russia under 152-FZ, and the text does not go to services without a data processing contract.

3. The system, data and access stay with the firm, and the model can be replaced without changing the process.

Which model to choose and what hardware to run it on is covered in our article on a local neural network for lawyers. The decision and the signature stay with the lawyer: AI prepares a draft and finds what is needed in the documents.

Sources and fact-checking

Checked by the editors on 16 October 2026.

  1. Brace Law Firm (brace-lf.com)
  2. ppt.ru, 26.07.2026 (ppt.ru)
  3. ConsultantPlus, 152-FZ “On Personal Data”, Article 3, 27 July 2006 (consultant.ru)
  4. ConsultantPlus, 152-FZ “On Personal Data”, Article 12, 14 July 2022 (consultant.ru)
  5. Data security in AI projects

Found a mistake? Tell us

Publications

How we protect data

  • Data in Russia

    We process personal data on servers in Russia under 152-FZ, Russia's personal data law. Message text does not go abroad or to services we have no contract with for processing on your behalf.

  • Rights only for its own process

    The agent has its own account in the CRM, the accounting system (1C) and the phone system. A sales agent only needs to create deals; it does not need to export the database or have admin rights.

  • Actions are visible

    Everything the agent does in your CRM goes into the CRM's log. Every change of rules is recorded in the support report, and you can roll it back in a minute.

  • Commands from messages are not carried out

    The agent's instructions forbid changing the rules at the request of an incoming message. If a client asks it to "forget the rules" or to send a list of clients, the request goes to a person.

  • People make the decisions

    The agent does not sign documents, make payments or negotiate. It hands complex and disputed cases to an employee together with the history.

  • The model can be replaced

    We choose the model for a process with regard to where it is deployed, and we can replace it without reworking the rules and connections.

After the rollout, the system, a perpetual license, the data and the access rights are yours. The agent's accounts are created in your systems, and your administrator can revoke any access in a minute.

Data security: all the rules
Contact us