...

Data subject requests under Russian law: how to verify the requester before you answer

The law gives an operator ten business days to answer, but does not say how to be sure the message came from the person themselves. Handing someone’s data to a stranger is a leak, and asking the requester for a passport scan “just in case” is excessive data collection. NeuroVision matches the requester’s document and face via a link and returns the result to your request-handling system.

Requester check result: document, passport, Liveness
10 days business days for the operator’s answer
7 days business days to correct and destroy data
30 days to stop processing after consent is withdrawn
from 29 ₽ the requester’s document and Liveness
Document Passport against the Ministry of Internal Affairs database Liveness Power of attorney (MRPOA) Request log

Data stored in Russia · Russian software registry no. 19972 · 152‑FZ

A data subject request under 152‑FZ: what may be demanded, how fast to answer and when to refuse

A data subject request is not a complaint to Roskomnadzor but an ordinary appeal to the operator, and the law sets its content, deadline and limits.

  • What a data subject may demand

    152‑FZ, Art. 14 parts 1 and 7

    Verify the requester

    Information

    • Confirmation that the operator processes the data; legal grounds and purposes; the list of data and its source
    • Processing and storage periods; persons processing data on the operator’s behalf; cross-border transfer

    Actions

    • Correct the data if it is incomplete, outdated or inaccurate
    • Block or destroy data obtained unlawfully or not needed for the stated purpose
  • What a request must contain and how fast to answer

    Art. 14 parts 3–5, Art. 20 parts 1–3, Art. 21 part 5

    Operator checklist

    Request

    • The number of the main identity document, issue date and issuing authority; details of the relationship with the operator (for example, contract number and date); the signature of the subject or representative, or an electronic signature

    Deadlines

    • Answer within ten business days, extendable by no more than five with a reasoned notice
    • Correcting and destroying unneeded data — within seven business days
    • Consent withdrawal — stop processing and destroy data within 30 days, unless a contract or law provides otherwise

    Repeat request

    • No earlier than 30 days later, if the answer was complete
  • When you may not answer or must refuse

    Art. 14 part 8, Art. 20 part 2, Art. 7, Art. 21 part 3.1

    Operator checklist

    Third-party rights

    • Access is restricted if it violates the rights and legitimate interests of other persons

    Refusal

    • A written, reasoned answer citing part 8 of Art. 14 or another law, within the same deadline

    Disclosure to a stranger

    • The law does not name a way to verify identity; the operator chooses it
    • If data went to the wrong person, this is unlawful disclosure: under part 3.1 of Art. 21 the operator notifies Roskomnadzor — within 24 hours of the incident and within 72 hours of the investigation results

Managing data subject requests: sixteen lines from the letter to closing the case

The tag shows who closes the line: NeuroVision, your request-handling system or the operator’s lawyer.

  • The request is registered and the date of receipt is recorded Your system
  • The type is defined: information, correction, destruction, consent withdrawal Operator’s lawyer
  • The request details are checked: document, basis of the relationship with the operator, signature Operator’s lawyer
  • A request in the account is separated from one sent by email: in the account the identity is already known Your system

  • The representative’s power of attorney is valid and covers the request (MRPOA) NeuroVision
  • For a paper power of attorney — a copy and confirmation from the principal The applicant’s document
  • The representative’s own document and face are checked the same way as the requester’s NeuroVision
  • A request from a lawyer or an organisation is backed by a basis Operator’s lawyer

  • The data is found across all systems and your processors Your system
  • Decision made: disclose, correct, destroy or refuse with reasons Operator’s lawyer
  • The answer went out on time and in the form in which the request came Your system
  • The requester check result is recorded in the request log (via API) NeuroVision
  • NeuroVision — the line is closed by a document, face or power-of-attorney check
  • Your system — the operator’s internal process; we do not replace it
  • Operator’s lawyer — the decision stays with you
  • The applicant’s document — a copy and confirmation from the principal

Account, support email, postal letter: where requests come from

Data subject requests arrive in different ways: from an account, to a shared mailbox, to a support chat, by letter. The sources differ, but the question is the same: is this the person themselves, and on what basis are they asking for data.

  • Cloud service and SaaS

    • Requests arrive at support and at a shared address
    • The user may have left, and the company may have changed owner
    • Disclosing a company’s customer data is a separate case
  • Online store and marketplace

    • Requests grow after mailings and third-party leaks
    • One person — several accounts
    • A request from a former buyer without logging in to an account
  • Subscription service and app

    • Consent withdrawal together with cancelling the subscription
    • A request from a different email
    • Payment and device data
  • Operator with branches and processors

    • A shared request-handling centre for a holding
    • The request is addressed to one legal entity while the data sits with another
    • A single check log
  • Lawyer and the person responsible for personal data processing

    • The decision to refuse and the reasoned answer are theirs
    • A trail is needed: who confirmed the identity, when and how
    • A check at Roskomnadzor’s request
  • Consent management platforms

    • The person gives consent to the processing of their data and face image themselves
    • Document and Liveness — when consent is given and withdrawn
    • The result with a date goes to the platform’s log; the platform manages the consent texts itself

The subject’s identity in a request: three steps from the letter to the decision

The check is built into the reply email or support chat: the requester completes it on a phone, and the lawyer receives the result in the request-handling system.

Step 1

Send the requester a link

A one-time check link goes out in the reply email or chat. The requester opens it on a phone: they do not need to register, and you do not need to ask for a passport scan in the correspondence.

A check link in the reply email
Step 2

Document, passport and face

The service recognises the document, checks it for forgery, matches the passport against the Ministry of Internal Affairs database and runs Liveness: the selfie is compared with the photo in the document. One session — one person.

Checking the requester’s document and face on a phone
Step 3

Decision and a log entry

The result arrives in your system: “passed”, “failed” or “not enough data”, with no copy of the document in the correspondence. Then the lawyer decides: disclose the data, ask for more information or refuse with reasons.

Check result in the request log

Someone else’s data goes to a stranger, too much is asked of the requester, a deadline is missed: four losses for the operator

  • 01

    Disclosure to someone who only claimed to be the subject

    A letter from a “customer” asks to export their data. The email address matches the one in the database, but the mailbox may have been hacked. Disclosure to a stranger is unlawful disclosure: the operator notifies Roskomnadzor within 24 hours and within 72 hours.

  • 02

    A passport scan “for safety”

    Support asks for a passport in reply. The operator now holds a passport copy it does not need to answer, and one more data set to protect. The law requires the volume of data to match the purpose of processing.

  • 03

    A representative without authority

    A lawyer or a “relative” asks for data under a power of attorney that nobody checked. If the power of attorney turns out to be invalid, the operator answered someone it had no right to.

  • 04

    A missed deadline

    While they discussed how to verify the requester, ten business days passed. The law allows an extension of five days only with a reasoned notice, while a check via a link takes minutes.

Requester check

Document, face and power of attorney in a single check. The answer follows the law; the decision is yours.

What the requester check confirms and what stays with the operator’s lawyer

NeuroVision answers one question: is this the right person. What to do with their data is the operator’s decision. A request register, answer templates and search for a subject’s data are not our part. We will connect the check result to your request-handling system via API.

  • The applicant’s identity

    Document, passport validity, the face in the selfie and Liveness. The result goes to the request log without a copy of the document.

    • NeuroVision
  • The representative’s authority

    A power of attorney and an MRPOA are checked separately; the representative’s document and face — with the same checks as the requester’s.

    • NeuroVision
  • Searching for and disclosing data

    Finding data across your systems, building an export, deleting, sending the answer in the required form — the operator’s internal processes.

    • Operator
  • Decision and refusal

    The answer, a reasoned refusal, an extension of the deadline and a notice to Roskomnadzor — decided by the lawyer or the person responsible for personal data.

    • Operator’s lawyer

A request from a representative, lawyer or company: power of attorney, MRPOA and other people’s requests

  • A representative under a power of attorney

    Paper. A copy of the power of attorney and confirmation from the principal.

    Electronic (MRPOA). Checking validity and scope of authority in the service.

  • An advocate or a law firm

    Basis. The request is backed by a power of attorney or a warrant.

    Document. The lawyer’s identity is checked from a document, their status — from information you are entitled to request.

  • A requesting organisation

    Company. A check by Tax ID: status, director, founders.

    Employee. The employee’s MRPOA or a power of attorney from the director.

  • Requests from government bodies and courts

    A different procedure. This is not a data subject request: a body’s demand is answered under Art. 20 part 4 or the law on that body.

    Not checked as a requester. An identity check of a person does not apply here.

The law allows a request from the subject’s representative. The operator is entitled to know on what basis they act.

A request based on consent to a digital likeness — verification in AI services. Regaining access to your own account — access recovery.

Requester and representative checks: catalogue and prices

Each check is enabled separately. You pay for completed requests. The result is “passed”, “failed” or “not enough data”; the decision to disclose or refuse is made by the operator. All checks are in the section AML checks.

The applicant’s document

Document fields without manual entry and forgery protection.

  • Recognition

    Russian passport and documents of 195+ countries and territories

    The document is recognised from a photo and the fields arrive without retyping: match them against the request details.

    from 16 ₽ per document

    Learn more
  • Anti-fraud

    A photo of a screen, editing, pasting

    Signs of a photo of a screen, a printout, editing and a pasted-in photo. Included in the document check.

    included in the document check

    Learn more
  • Police · SMEV

    Passport validity

    The 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 more

How much it costs to check one requester

No subscription fee. The price is per session. Test access — on request.

  • Document

    from 16 ₽ per session

    Enable

    Document recognition, anti-fraud; the passport check against the Ministry of Internal Affairs database — separately, 5 ₽.

  • Most popular choice

    Document + Liveness

    from 29 ₽ per session

    Enable

    Document, the face in the selfie, matching with the photo in the document.

  • Requester and representative

    on request

    Leave a request

    Plus database checks, an organisation check, MRPOA, a log and an export for audit.

The calculator is on the pricing page. Service price matrix.

A form on the site, a link in the reply email, an API for the request-handling system

The check fits wherever you receive requests: the request page in the account, the support reply email or your request-handling system.

A form on the site

A verification step appears on the data subject request page: the requester uploads a document and completes Liveness without leaving for another site. Web SDK.

  • Web SDK
  • Link
  • REST API
  • Docker
  • Webhooks

Test access — on request

You pay for completed sessions, with no subscription fee.

Why operators with a high volume of requests verify requesters with NeuroVision

An operator with a high volume of requests needs a way to be sure the writer is the person themselves that does not turn into correspondence and passport copies.

Requester verification without a scan in the correspondence

The requester completes the check via a link, and the lawyer receives the result: “passed”, “failed” or “not enough data”.

The decision to disclose data stays with the operator.

Document Liveness MRPOA API

Minutes instead of correspondence

The requester completes the check via a link, and the lawyer receives a ready result.

No extra copies

The document is needed for matching, not for the archive: the check result goes to the log.

One mechanism for the requester and the representative

Document, face and power of attorney are checked in one system.

Data in Russia

Cloud or on-premises installation, 152‑FZ, Russian software registry no. 19972.

A data subject request glossary: operator, identity document, reasoned refusal, representative

A short guide to the concepts of the personal data law that appear in data subject requests.

Data subject
The individual the data relates to.
Data subject
Operator
The organisation that determines the purposes and scope of data processing.
Controller
Data subject request
An appeal demanding information about processing, or correction, blocking or destruction of data.
Data subject request
Identity document
A document proving identity, whose number and issuing authority are stated in the request.
Identity document
Reasoned refusal
A written answer citing the law under which access is restricted.
Reasoned refusal
Consent withdrawal
A subject’s statement asking to stop processing their data; processing must stop within 30 days.
Consent withdrawal
Representative
A person who acts on the subject’s behalf under a power of attorney.
Representative
Unlawful disclosure
Giving data to someone with no right to it; leads to a notice to Roskomnadzor.
Unlawful disclosure

Questions about verifying requesters in data subject requests

The law names the request details: the document number, issue date and authority, details of the relationship with the operator, and a signature. It does not set a verification method, but data must not be given to a stranger: access is restricted if it violates third-party rights (part 8 of Art. 14). So the check is needed to the extent the risk of the request requires.

The document details are stated in the request itself. Asking for a passport copy in the correspondence is not advisable: the volume of data must match the purpose of processing (part 5 of Art. 5). A check via a link matches the document at the moment of the request, and the result goes to the log.

Ten business days, extendable by no more than five with a reasoned notice (part 3 of Art. 14, part 1 of Art. 20). Correcting and destroying unneeded data — within seven business days (part 3 of Art. 20).

Stop processing and destroy the data within 30 days, unless a contract or law sets another period (part 5 of Art. 21). Before destroying, confirm that the withdrawal comes from the subject themselves.

Yes, if access is restricted by law: for example, it violates third-party rights (part 8 of Art. 14). The refusal is written and reasoned, within the same deadline (part 2 of Art. 20).

No. We verify the requester and the representative and pass the result to your request-handling system. The request register, data search and the text of the answer stay with the operator.

A power of attorney and an MRPOA are checked separately, and the representative’s own document and face — with the same checks as the requester’s. For a paper power of attorney — a copy and confirmation from the principal.

Such a service is a representative: check its authority separately, like any representative, and the person’s own document and face — with the same checks as for a requester. Before destroying data, confirm that it is the person who demands it, and not an intermediary acting on its own initiative. Whether to accept such a request and to what extent is decided by the operator and its lawyer.

From 16 ₽ per document, from 29 ₽ together with Liveness, and the passport check against the Ministry of Internal Affairs database — 5 ₽. No subscription fee.

We will build a requester check for your request-handling system

Tell us how many requests you receive and where they come from. We will show the requester check on your scenario.

Can't put your request into words? Book a call and our team will contact you at a convenient time

Book a call

The 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.