Before you make an avatar, “animate” a photo or clone a voice, make sure the materials were uploaded by their owner. NeuroVision checks the document and live presence and matches the face against the materials for the likeness. For API access — a check of the company and its representative; for data labellers — one person per account.
Consent of the likeness owner is confirmed by the owner · 152‑FZ
There is no law that obliges an AI service to verify its users — even the AI law adopted in summer 2026 does not require it. But a person's face and voice are protected by the Civil Code and the personal data law, and the service will answer for someone else's likeness in a model.
Civil Code of the Russian Federation, Art. 152.1; draft law No. 718834‑8 (Art. 152.3 of the Civil Code) — not adopted.
152‑FZ, Part 1 of Art. 9 (as amended by 156‑FZ), Part 1 of Art. 11; 572‑FZ, Art. 15.
Law of 26.07.2026 No. 243‑FZ, Arts. 9, 10 (from 1 March 2027); 149‑FZ, Part 10 of Art. 8; Administrative Offences Code, Art. 13.55.
There is no need to verify everyone who comes in to try a neural network. Verification is needed where the service opens access to someone else's face or voice, to large limits or to money.
The likeness owner goes through user verification right in your AI service, from a phone or computer. You receive confirmation that the materials for the avatar or clip were uploaded by the same person who signed the consent.
The likeness owner signs the consent as a separate step and photographs the passport with the camera. Full name, date of birth and document number arrive as fields without manual entry, and anti-fraud flags a photo of a screen, a printout and traces of editing.
The person goes through Liveness: a photo, a screen, a mask and video stream substitution are rejected. The selfie is checked for signs of a deepfake, face-swap and full generation, and the face is compared with the photo in the document.
The face from the photos and video frames that the person uploaded for the likeness is compared with their face from the session. A match — the likeness is created; no match — the service stops it pending review. The decision and consent are stored with the session number.
What exists and what does not
The image is protected by Art. 152.1 of the Civil Code; the voice is not yet: the draft law on Art. 152.3 has not been adopted since 2024. So the basis is the personal data law and the contract with the voice owner. The more precise the contract, the fewer disputes about what consent was given for.
Consent to a voice clone is given by the owner themselves, not by a studio, an agent or the user who brought the recording. The service makes sure it is them: the owner goes through a KYC session, and the service links the voice recording and the signed consent to the session number.
Purposes separately: speech synthesis, model training, commercial use, advertising. The term, the territory, who else will get access to the model, and the withdrawal procedure. Training on recordings without a direct indication in the contract is a frequent cause of disputes between voice actors and clients.
The owner has the right to withdraw consent to personal data processing. The service needs a clear procedure: switch off the voice, stop payments and delete the session data. A withdrawal should also be accepted from the verified owner — so that a stranger does not “withdraw” the likeness on their behalf.
The level of verification grows with the risk of the feature. A free chat does not require a passport, while the avatar of a real person and a payment to a contractor do. This is a guide for a conversation with a lawyer, not a legal opinion; the rules are as of October 2026. How to protect personal and biometric data in KYC — in a blog article.
Verification answers the question “who is this user and is it their face in the materials”. What they then generate is a matter of your service's usage policy, filters and moderation.
NeuroVision works with the document and the face. We do not recognise a voice clone by sound — we confirm the identity of the person who gives consent, and linking the recording to the session is done by the service.
The check proves that the consent was signed by the likeness owner. The text of the consent and licence, the purposes, terms and withdrawal procedure are prepared by your lawyer.
Under 243‑FZ, the ability to mark AI-created material is provided by the platform. The label and its format are on the service's side.
How Liveness tells a live person from a deepfake, a mask and a virtual camera — on the page “Deepfake protection in verification”.
The decision to let a user into a feature or to stop a likeness is made by the service: NeuroVision provides the result of each check and the session number.
Photos of a blogger or a former colleague
A user uploads photos of a blogger or a former colleague and makes a “talking head” for advertising or blackmail. What helps is the owner's Liveness and matching the face in the uploaded photos with the face from the session — a mismatch stops the likeness.
A recording from an open video
A voice recording is taken from a publicly available video and passed off as one's own, to train a model and make calls “on behalf of” a person. What helps is the voice owner's consent after their KYC session: without a verified owner, the clone is not created.
Hundreds of registrations on virtual numbers
Hundreds of registrations collect free limits or resell access to the model, including to those for whom it is closed. For large limits and the API — company by INN, sanctions lists and the representative's document.
One account — a different contractor
An account passes the check as one person, while tasks are done by another — or one person runs ten accounts for payouts. What helps is one account per document number, repeat Liveness before payment and self-employed status.
A virtual camera or an emulator
Instead of a camera, a generated video is fed in through a virtual camera or an emulator. What helps is Liveness, which rejects video stream substitution, and deepfake signs on the selfie — learn more.
152‑FZ
Consent — before the likeness
The avatar owner adds a new voice or new photos — Liveness and face matching against the new materials again. The account may have changed hands.
For a labeller or a likeness author — Liveness and self-employed status before transferring money. This shows that the money goes to the person who passed the check.
An API client's head or representative has changed — a company check and the new representative's document before the keys are renewed.
A person reports that an avatar was made without their consent — the likeness is stopped, and the complainant goes through a KYC session so that the service can match their face against the materials.
If an avatar or clip is made from someone else's photos, claims will be brought not only against the user but also against the service that distributed the image. The owner's confirmed consent is the main argument.
A citizen has the right to demand that an image distributed online without consent be deleted and further distribution be prohibited
Copies bearing such an image are seized and destroyed by court decision
Violation of personal non-property rights gives the right to monetary compensation
The amount is determined by the court; for a defamatory clip, protection of honour and business reputation is added
Processing without consent or without separate consent — a fine for the organisation
The amount is under the current version of Art. 13.11 of the Administrative Offences Code; a repeat violation costs more
Authorising users by means other than those permitted by law
For a legal entity — 500,000 to 700,000 ₽ from 7 July 2026
The set is assembled for the feature: an avatar needs Liveness and face matching, an API client — a company check, a labeller — self-employed status.
The document with no manual entry
Document fields, anti-fraud and a check against the Ministry of Internal Affairs database.
The document is recognised from a photo: 16,000+ types from 195+ countries and territories, fields arrive without retyping. Included in the “Document” package.
from 16 ₽
Learn moreSigns of a photo of a screen, a printout, a pasted-in photo and traces of editing. Included in the “Document” package.
in the package
Learn moreThe authenticity and validity of a Russian passport through the interagency interaction system. It catches expired, replaced, lost and invalid documents and verifies that the passport was issued to this particular person.
5 ₽ / check
Learn moreDetermining the tax number from the passport data. It unlocks the checks that need precise identification of the person — with no namesakes.
5 ₽ / check
Learn moreLiveness and face matching
Live presence, deepfake signs and face comparison.
A check that a live person is in front of the camera: a photo, a screen, a mask and video stream substitution are rejected. Included in the “Document + Liveness” package.
from 29 ₽
Learn moreThe selfie is checked for signs of a deepfake, face replacement and full generation.
in the package
Learn moreThe face in the document photo is compared with the face in the selfie in the same session.
in the package
Learn moreThe face from the session is compared 1:1 with the face in the photos and frames uploaded for the avatar or clip.
on request
Learn moreOrganisation and representative
Access to the API and increased limits.
Company status, head and founders — as part of the KYB scenario.
on request
Learn moreA check of the head and founders against selected registers and lists.
5 ₽ per register
Learn moreScreening against the consolidated lists of OFAC (USA), the European Union, the United Kingdom and the UN. Every match carries a similarity score and a flag if it was triggered by an alias.
5 ₽ / check
Learn moreInternational screening for politically exposed persons and their associates, international sanctions lists, regulator measures and negative media publications. For citizens of Russia — by foreign passport or full name and date of birth.
36 ₽ / check
Learn moreLabellers and experts
The contractor's status and clearance before payment.
Confirmation of registration as a payer of professional income tax.
5 ₽ / check
Learn moreScreening against the list of people involved in extremist activity or terrorism. A mandatory check under 115-FZ.
5 ₽ / check
Learn moreA search of the federal database of people wanted by the police. Filtered by the full date of birth — results with no namesakes.
5 ₽ / check
Learn moreA check on a foreign national against the register of controlled persons that the police have kept since February 2025: people who have lost the legal grounds to stay in Russia. Russian citizens do not need the check — by law they are not in the register.
5 ₽ / check
Learn moreNo subscription fee: you pay for the sessions and checks performed. One KYC session is one person with all the steps of the scenario.
from 16 ₽ per session
Document recognition and anti-fraud, date of birth and document number as fields — for labellers and features without a face. Database checks — 5 ₽ each.
Document with anti-fraud, Liveness, deepfake and face-swap signs, comparison of the face with the document. At 10,000 sessions a year — 33 ₽; the price falls as volume grows.
on request
Company by INN as part of the KYB scenario, head and founders — 5 ₽ per register, international screening — 36 ₽, representative — a “Document + Liveness” session.
Prices follow the price matrix on the publication date. Test access — 1 month.
Verification is built into the step where the user creates a likeness, requests limits or a payout, and the scenario is changed in the personal account without development.
Payment only for sessions performed; the data retention period is set in the scenario.
An AI service needs a check that will not put off an honest user and will withstand a dispute with the owner of the likeness.
Document, Liveness, face matching against the materials and organisation checks work through one API and one session. For each likeness you have a session number and the result of each check.
There is no need to assemble a solution from several vendors and reconcile their responses.
The retention period is set in the scenario, and data is deleted on request.
Concepts that come up when an AI service works with the faces and voices of real people.
Deepfakes, Liveness and protection of biometric data — in our blog.
By the risk of the feature. For free limits, sign-in by phone or Gosuslugi is enough. Before creating an avatar or voice clone — document, Liveness and face matching against the materials; before API access — a check of the company and its representative; before paying a labeller — Liveness and self-employed status.
No. Law No. 243‑FZ of 26 July 2026 on supporting AI technologies does not require users to be identified. Sign-in requirements are set by the Information Law: phone, Gosuslugi, the Unified Biometric System or a Russian authorisation system.
Yes. A citizen's image may be made public and used only with their consent (Art. 152.1 of the Civil Code). If the face is used to establish identity, it is also biometric data — written consent under 152‑FZ is required.
There is no separate article on the voice in the Civil Code as of October 2026: draft law No. 718834‑8 on Art. 152.3 has not been adopted. A voice recording is protected by the personal data law, so the voice owner's consent and a contract are needed even now.
No, we do not analyse the voice. We confirm the identity of the person who gives consent to the clone: document, Liveness and face in one session. The service links the voice recording and the consent to the number of that session.
Ask them to go through a KYC session: document, Liveness and selfie. Then the face in the uploaded photos and video frames is compared with the face from the session. No match — the likeness is stopped pending review.
Stop the likeness, invite the complainant to go through a KYC session and match their face against the materials. If the consent was signed by another person, delete the likeness and the data. The owner's confirmed consent is the service's main argument in a dispute.
Yes. Liveness rejects a photo, a screen, masks and video stream substitution, and the selfie is checked for deepfake and face-swap signs. In detail — on the deepfake protection page.
By INN: company status, head and founders, sanctions lists and, if necessary, international screening. The representative who receives the keys goes through a “Document + Liveness” session.
The document number and date of birth arrive as response fields — check them against your contractor database before the first task. Before payment, ask for a repeat Liveness and check the self-employed status.
The retention period is set in the check scenario; indefinite storage is enabled separately. Session data can be deleted on request — this matters if it holds photos and videos from which a likeness is made. The support mode and communication channels are fixed in the contract.
A “Document + Liveness” session — from 29 ₽, “Document” — from 16 ₽, database checks — 5 ₽, no subscription fee. Test access — 1 month.
Tell us what your service does — API, generation, voice, avatars or labelling — and how many users go through verification per month. We will build a scenario for each feature and give you test access.
Can't put your request into words? Book a call and our team will contact you at a convenient time
Book a callThe company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.
Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.
