data security

The assistant sees only what the employee may see. And changes nothing without you

NeuronChat connects to your systems but never becomes their owner. Your system decides the permissions, a person confirms every change, and personal data is hidden before it reaches the model.

  • 01Your permissionsThe assistant acts on behalf of an employee and sees exactly what they see.
  • 02Changes after “Apply”The assistant itself never writes or sends anything.
  • 03Masked dataPhones, emails and documents are replaced with tokens before the model.

access

Who can do what through the assistant

The assistant does not get a master key. Every request comes from a specific person, and your system decides what to show them.

  • 01

    On behalf of the employee

    The system is told who is asking. No permission for a section — the assistant says so instead of working around it.

  • 02

    Reads at once, changes by button

    Creating a task, sending an email or adding a record is only proposed. You see a “what will change” card and press “Apply”.

  • 03

    Re-checked on apply

    Permissions are checked again between the proposal and “Apply”: revoke access and the action will not run.

  • 04

    Audit log

    Every call to a system is recorded: who, when, which action, how it ended. No chat texts or system responses.

  • 05

    You enable actions yourself

    When you connect your own system, reads are on and anything that changes data stays off until the owner enables it.

  • 06

    Access is revoked instantly

    The key is stored encrypted and never displayed. Revoke it on your side and access is gone.

masking

The model does not see personal data

Before text is sent to the model, personal data is replaced with tokens. In the answer the tokens are swapped back — you see normal text the model never saw.

what the customer wrote

My name is Anna Smirnova, phone +7 912 345-67-89, email anna@romashka.ru. Passport 4510 123456.

what the model received

My name is {name_1}, phone {phone_1}, email {email_1}. Passport {passport_1}.

  • phone numbers
  • email
  • full names
  • passport
  • tax ID (INN)
  • insurance number (SNILS)
  • date of birth
  • driving licence
  • address: house and flat

Masking is on by default and works in customer chat, in the assistant inside your systems and in the dashboard helper. In work systems the names of colleagues and customers are kept — without them the assistant cannot name the person responsible.

russian models

“Russian models only” mode

One switch for the whole account. While it is on, chats are processed only by Russian models — for any employee and under any failure.

  • Applies to everyone

    Customer-facing AI employees, assistants inside your systems and the dashboard helper.

  • No silent fallback

    If the Russian model is unavailable, the assistant refuses. The chat is not sent to a foreign model.

  • When to enable

    When the assistant handles personal data of customers or staff and it must stay in Russia.

storage

What we store and what we do not

We do not copy your database. The assistant requests only what is needed to answer a specific question.

We store

  • chats with the assistant — like chat history
  • the action log: who, when, what was called
  • access keys — encrypted only
  • the knowledge base you uploaded yourself

We do not store

  • a copy of your CRM, mail or accounting system
  • your systems’ responses in the action log
  • keys in plain text — even your admin cannot see them
  • action parameters with personal data: they are masked in the log

honestly

Where the protection ends

We do not promise the impossible. Here is what to know before connecting.

  • Masking is not magic

    It recognises data by format. A rare surname without context, a company name or a deal amount may reach the model as is.

  • Use the Russian mode for personal data

    If chats contain personal data, enable “Russian models only”. Masking then becomes a second line of defence, not the only one.

  • System data is not a command

    The assistant treats the text of an email or a request as data. An instruction inside an email is not executed, and any action still needs “Apply”.

152-fz

Working under the personal data law

You remain the operator of your data; we process it on your instruction and only to run the assistant.

Privacy policy
  • Documents

    Public offer, personal data policy, contract, invoices and acts for companies.

  • Company data is separated

    One account’s data is not available to another. Dashboard access is role-based: owner, admin, editor, operator, observer.

  • Russian models

    In “Russian models only” mode chats are processed by Russian models; foreign ones are not used for answers.

See it on your own data

Connect a test system and open the log: what the assistant requested, on whose behalf, and what reached the model.