What data the agent sees
Personal data is information that identifies a person: name, phone, address and order history. An agent sees it in three places: in chats, in the CRM and in 1C, the Russian accounting system, and in the logs of its own work.
Start with an inventory. Write down which fields the agent reads, which it writes and where it sends them. A booking agent needs a name, a phone number and the visit time; it does not need a passport.
The fewer fields an agent sees, the less leaks after an error or an attack. In our builds, the agent gets a separate account in the CRM and 1C with rights only for its own process.
Mark health data and biometrics separately. 152-FZ has its own articles for them, and such projects do not start without a lawyer.
Where to store and process data
Under Part 5 of Article 18 of 152-FZ, the personal data of Russian citizens is collected and stored in databases in Russia. For an agent, this means chats, client cards and logs.
If the text of messages with a name and a phone number goes to a foreign model, that is a cross-border transfer. Since 1 March 2023, the operator files a notice with Roskomnadzor, the Russian data regulator, before such a transfer (Part 3 of Article 12).
The practical path is an open model on your own server or at a hosting company in Russia. Then the data does not leave the country, and you can replace the model without rebuilding the agent.
Since 1 September 2026, 243-FZ on AI technologies has been in force. The Government sets the cases where sovereign and national models must be used, so check that list before each new project.
Where the data physically sits and what to ask about foreign services is covered in the article on 152-FZ and AI agents. Which data you may give a model is described on the page about the law and data.
The processing order for the contractor
Your company is the personal data operator: you collect client data and decide why. A contractor that builds and supports the agent processes the data on your order.
Under Part 3 of Article 6 of 152-FZ, the order must contain the list of personal data, the list of actions with it, the purposes of processing, a duty of confidentiality and the protection requirements of Article 19.
Before you sign, compare the order with the inventory from the first section. If the contractor writes “all CRM data” and the agent needs a name and a phone number, narrow the list.
The operator, that is you, is responsible to the client for the contractor’s actions (Part 5 of Article 6). The contractor is responsible to you, so the data processing section of the contract is not a formality.
Ask about the models too: through which outside services the text of messages passes, and whether there is a contract with them. The answer “we will find out” means it is too early to sign.
Consent and notice
If the client’s consent is needed, it is drawn up separately from other documents the client signs or confirms (Part 1 of Article 9). A line about consent inside a contract or a user agreement does not meet this requirement.
An agent in a messenger also collects data. Before its first question about a name and a phone number, it gives a link to the processing policy and, where needed, to the consent.
Before processing starts, the operator notifies Roskomnadzor of its intention to process personal data (Part 1 of Article 22). The exceptions are narrow, for example processing without automation, and an agent automates processing by its very nature.
If the data goes abroad, you need a second notice, about the cross-border transfer, and it is filed before the transfer.
Decisions without a person
Article 16 of 152-FZ bans decisions based only on automated data processing that have legal consequences for a person or otherwise affect their rights.
The exceptions are the person’s written consent or a case directly set by federal law. Even then, the operator must explain how the decision is made and let the person challenge it.
For an agent, this is a boundary. The agent does not decide on its own to refuse an installment plan, a refund or a job: it prepares the data and passes the decision to an employee.
We work the same way: the agent does not sign documents, make payments or negotiate, and it hands hard cases to an employee together with the history. All six rules are collected on the page about data security.
A 10-point checklist
1. There is an inventory of the fields the agent reads, writes and passes on.
2. The agent has a separate account with rights only for its own process.
3. The agent’s chats, cards and logs are stored in databases in Russia.
4. You know which outside services and models the text of messages passes through.
5. The notice to Roskomnadzor about data processing was filed before launch, and if data goes abroad, the cross-border transfer notice was filed too.
6. The personal data policy is published, the agent links to it, and consent, where needed, is a separate document.
7. The contract with the contractor contains the processing order: the list of data, actions, purposes, confidentiality and protection.
8. A person makes the decisions that have legal consequences for the client.
9. The agent’s actions are logged, and an administrator can revoke access in a minute.
10. The contract records what happens to the data and access when it ends.
If even one point is not met, postpone the launch. A repeat leak costs a legal entity 1% to 3% of revenue, but not less than $300,000 and not more than $6 million, so each point is cheaper than the fine. General agent protection, from permissions to logs, is described on the page about agent security.