When AI processes personal data
Under point 1 of Article 3 of 152-FZ, personal data is any information about a person who can be identified directly or indirectly. Legal documents hold a lot of it: the parties and signatories of a contract, employees in a labor dispute, debtors, heirs, witnesses.
Under point 3 of Article 3, processing is any action with such data, automated or not: collection, recording, storage, retrieval, use and transfer. Uploading a contract to a neural network counts as several actions at once, and a model’s answer with the same names counts as one more.
A test for a lawyer before uploading:
1. The text names a person who can be identified by name, position, address or document number.
2. The text leaves the systems of the firm or the client: it goes to someone else’s cloud or a foreign server.
3. There is no processing agreement with whoever receives the text.
If the first two points are true, this is processing with transfer. If the third is true as well, the transfer happens without the processing agreement that Part 3 of Article 6 of 152-FZ requires. Document anonymization before sending removes the first point.
Localization and foreign services
Part 5 of Article 18 of 152-FZ requires that the collection and storage of personal data of Russian citizens take place in databases located in Russia. A foreign service cannot be the first database that receives information about a client.
Hence the order: documents first enter the firm’s systems in Russia, and only then may some of them go further under the rules for cross-border transfer. For breaking localization, under Part 8 of Article 13.11 of the Code of Administrative Offenses, a legal entity faces a fine of up to $72,000.
Foreign services raise a second question: not all of them sign a processing agreement with a Russian firm, and without one the transfer does not fit Part 3 of Article 6. The terms and availability of large services in Russia are covered on the page on the law and data in the Sovereign AI section.
Notice of cross-border transfer
Under point 11 of Article 3 of 152-FZ, a cross-border transfer is a transfer of personal data to the territory of a foreign state, to a public authority, a person or a legal entity. A document sent to a service with servers abroad falls under this definition.
Since 1 March 2023, the operator files a notice with Roskomnadzor, Russia’s data protection regulator, before such a transfer starts (Part 3 of Article 12 of 152-FZ). The notice is filed before the transfer, not after a lawyer’s first request in a chat.
What to check in the firm:
1. Whether lawyers use foreign AI services with client documents, including from personal accounts.
2. Whether a notice has been filed and whether it lists the countries and recipients.
3. Whether the actual transfer matches the firm’s personal data processing policy.
How to file the notice and what to put in it is covered in the article on cross-border data transfer.
Fines
After Law 420-FZ, the fine under Article 13.11 of the Code of Administrative Offenses depends on what exactly was violated. For a legal entity, as amended on 4 August 2026:
1. Processing without written consent where it is required: $3,600–$8,400 (Part 2).
2. Breaking localization: up to $72,000 (Part 8).
3. Roskomnadzor not notified of a leak: $12,000–$36,000 (Part 11).
4. A leak: $36,000–$60,000, 5–10 million or 10–15 million, depending on the number of people affected (Parts 12–14).
5. A repeat leak: 1–3% of revenue, but not less than $240,000 and not more than $6 million (Part 15).
Part 10 adds a fine of $1,200–$3,600 if the operator did not notify Roskomnadzor of its intent to process personal data. A firm that has not yet filed such a notice should start there.
Abroad, vendors are fined too: on 20 December 2024, the Italian data protection authority fined OpenAI 15 million euros over data processing in the training of ChatGPT. The first cases in Russian courts are covered in the article on personal data fines.
How to set up processing lawfully
A lawful setup for a firm takes five steps, and none of them requires giving up AI.
1. For each document flow, define who the operator is and on what legal basis the processing happens.
2. Keep the documents and the model in Russia: on the firm’s own server or in a Russian cloud. Then there is no cross-border transfer, and the requirement of Part 5 of Article 18 is met.
3. With a contractor who sets up or maintains the AI, sign a processing agreement under Part 3 of Article 6: the list of data, the actions, the purposes, confidentiality and protection requirements.
4. Anonymize documents if they go to an outside service, and describe this in the personal data processing policy.
5. Update the policy and the notice to Roskomnadzor if AI changes the set of actions with data or the circle of recipients.
How this works in our projects is described in the “How we protect data” block below and on the page on data security.