Personal Data Processing Policy
Version of 19 November 2026
This is an English translation provided for information only. The Russian version of this document is legally binding; in case of any discrepancy between the two versions, the Russian version prevails.
1. General provisions
This Policy sets out the procedure for processing and protecting the personal data of users of the “Scanner” website and software in accordance with Federal Law No. 152-FZ of 27 July 2006 “On Personal Data”.
The personal data operator is Индивидуальный предприниматель Липкина Лидия Александровна (Individual Entrepreneur Lipkina Lidiya Aleksandrovna; INN 524830916587, OGRNIP 326527500103167, address: 603159, Russia, Nizhny Novgorod, Volzhskaya naberezhnaya, 8/3 - 187) (the “Operator”). Contact for personal data processing matters: libscanner@yandex.com.
2. What data is processed, for what purposes and for how long it is stored
| Purpose | Data | Retention period | |
|---|---|---|---|
| Registration and access to the personal account | Email address; password — only as a hash (argon2id), the password itself is not stored; two-factor authentication secret, if enabled; account status, roles, dates of registration and of email address confirmation, information about failed login attempts | Until the account is deleted. An account whose email address has not been confirmed is deleted 30 days after registration if it has no orders or licenses | |
| Personal account login sessions, protection against unauthorized access | Session identifier (only its hash is stored in the database), browser information (user agent), IP address, dates of the start, last access and end of the session | 30 days after the session ends | |
| Placing and fulfilling orders, issuing invoices, accepting payment, accounting and tax records | Contents, amounts, dates and statuses of orders; the buyer’s invoicing details — name, INN (taxpayer identification number), KPP (tax registration reason code), OGRN (OGRNIP) (primary state registration number), address, bank details, surname, first name and patronymic of the head (individual entrepreneur) and of the accountant, telephone number, email address; payment information from the payment operators (YooKassa, Robokassa) — identifier, amount, status (without bank card data) | For the periods established by tax and accounting legislation. The most recently entered details, used to prefill the next invoice — until the account is deleted | |
| Automatic renewal of the Pro subscription — charging the next period without the user taking part, if the user agreed to it when paying or turned it on in the personal account | Identifier of the payment method saved with the payment operator (encrypted in the database), card name and last digits (for example, "Bank card *4444"), the agreed charge amount, the number of failed attempts in a row, attempt dates and the order of the last attempt | Until automatic renewal is turned off by unlinking the card, the subscription is revoked on a refund, or the account is deleted. Orders and payments of automatic renewal — as other orders | |
| Performance of the license agreement: issuing and verifying licenses, limiting the number of computers, transferring a license to another computer | License key (the database stores its hash and last characters). On activation and verification the program transmits: four SHA-256 hashes of the computer fingerprint — of the machine identifier, motherboard, processor and system disk (the serial numbers themselves are not transmitted), the computer name, operating system information, program version and license key. The server records the IP address of the last request, the dates of activation, last verification and unbinding, and the transfer history | Computer name and IP address — 6 months after the computer is unbound from the license; fingerprint hashes and other information — for as long as the license exists | |
| Downloading the distribution in the “Downloads” section: release statistics; marketing mailing — subject to separate consent | Which file was downloaded (product, version, file), date and time, IP address | IP address — 6 months; download record — 3 years | |
| Marketing mailing — only with separate consent (section 7) | Email address, download information, date and version of the consent; when news is published — a copy of the address in the mailing send queue (news_deliveries) with the dates it was queued and sent | Until consent to the mailing is withdrawn. The copy of the address in the mailing queue — 30 days after the email is sent; an email that could never be sent — 90 days after it was queued | |
| Replying to enquiries submitted through the feedback form | Name, email address, subject and text of the enquiry, IP address | IP address — 6 months; enquiry — 3 years, then deleted | |
| Answering questions asked in the website chat | Text of the messages, email address (if provided — for an email about the reply), the website page where the conversation started, language, IP address; for a logged-in user — the link between the conversation and the account. A question may be answered by the AI assistant, or the assistant may prepare a draft reply for the Operator; if the assistant does not know the answer, the Operator gets the question. For this, the text of the conversation — without email addresses, telephone and bank card numbers, which are replaced with placeholders — is transferred on the Operator’s instructions toООО «Яндекс.Облако» (Yandex.Cloud LLC, Yandex AI Studio service; INN 7704458262; OGRN 1187746678580; 16 Lva Tolstogo Street, premises 528, Moscow, 119021, Russia); the assistant’s messages in the chat are labelled “AI assistant” | IP address — 6 months; conversation — 12 months after the last message, then deleted (earlier — at the visitor’s request). The AI assistant service does not store the requests: request logging is disabled | |
| Confirming the fact of consent (Part 3 of Article 9 of Law 152-FZ) and of acceptance of the offer | Consent log: which consent (to personal data processing, to marketing mailing, acceptance of the offer), given or withdrawn, version of the text, date and time, IP address, browser information | While the consent is in effect and for 3 years after it is superseded by a new record (withdrawal or a new version). When the account is deleted, consents are withdrawn and the records are kept for 3 years; acceptance of the offer — as the contract | |
| “One month of Pro free” promotion and container trial keys: once per address, even after the account is deleted | Hash (SHA-256) of the email address of a deleted account that received the gift or a trial key, the product of the trial key, date of deletion | 1 year, then deleted | |
| Security: log of actions in the personal account and in administration | The action, who performed it and when, IP address; for sign-ins, also browser information | IP address and browser information — 6 months; sign-in records — 1 year | |
| Sending emails: email address confirmation, password reset, notifications about orders and licenses | Sending emails: email address confirmation, password reset, notifications about orders and licenses | Recipient’s email address and the content of the email in the sending queue; one-time links (email address confirmation, password reset) — only their hash is stored in the database; payment notifications from the payment operator | Emails — 30 days after sending; one-time links — 30 days after expiry; payment operator notifications — 1 year |
| Operation and security of the website, protection against abuse | Web server logs: IP address, browser information, address of the requested page, date and time | No more than 6 months (logs are rotated) | |
| Analysis of website traffic and improvement of the website (Yandex Metrica) — only with consent to analytics cookies (section 4) | Yandex Metrica cookie identifiers, IP address, browser and device information (device type, operating system, language, screen resolution), addresses of the pages visited and the referral source, date and time of the visit, actions on the pages: clicks, scrolling, pointer movements, session recording (Webvisor). Form fields containing personal data, the pages of the personal account and of administration, and the codes read or entered on the code reading and generation pages (results, summary, reconciliation with a delivery list, the input field and the generated code image) are not included in the session recording | Until consent is withdrawn, but no longer than 1 year. The _ym_uid cookie identifier is stored in the browser for up to 1 year; after consent is withdrawn, Metrica cookies are deleted from the website | |
| Statistics on the use of the online code reading and generation services on the website (the “Read DataMatrix” and “Create DataMatrix” pages) and of the links from the website to the “Сканер DataMatrix” chatbot in the MAX messenger by logged-in users: service development and user support | User identifier, date, type of service (reading or generating a code, going to the chatbot), number of uses per day (for reading, including how many times the code was not read) and the time of the last use. Decoded and generated code strings are not stored (except for the Pro plan scan history, below), uploaded images only if not recognized (below); use without logging in to the personal account is not counted | 1 year, then deleted | |
| Limiting the number of free code readings on the website | IP address (without logging in to the personal account) or user identifier and the times of readings — only in the server’s memory | No longer than 24 hours; deleted immediately when the server restarts | |
| Pro plan scan history: showing the user their decoded codes in the personal account | User identifier, date and time of reading, the decoded code string: GTIN and serial number for search, the full string with the verification code in encrypted form. Kept only while the Pro plan is active; images are not stored | 90 days, then deleted; the user can delete the history in the personal account at any time | |
| Reading DataMatrix codes on the website (the “Read DataMatrix online” page): improving recognition | Uploaded images in which no code was found or read — not linked to the user, their IP address or other data. Image metadata (EXIF: shooting location, device model and serial number, shooting time and other) is removed: the browser redraws the image before sending it, and the server removes the metadata before storing an unread image. An image in which a code was read is not stored | No longer than 1 year; no more than 500 MB in total (the oldest are deleted when this is exceeded) | |
| Access to the API (api.libscanner.com): checking the key, counting requests against the plan limits, showing the user their keys and usage in the personal account | User identifier; for each API key — the name given by the user, the beginning of the key, the hash of the key (the key itself is not stored), permissions, the times it was created, last used and revoked; the number of requests per day by type (reading, generating a code, parsing a string) and outcome. Submitted images and code strings, and the codes in the responses, are not part of this record | A key — until it is revoked and for 1 year after that; request counts per day — 1 year; on account deletion — immediately | |
| Reading codes through the API on the free plan: improving recognition | Submitted images in which no code was found or read — not linked to the user, their key, IP address or other data; image metadata (EXIF) is removed before storing. An image in which a code was read is not stored. On paid API plans images are not stored at all; an image given by a link (image_url) is downloaded only for the time of processing the request | No longer than 1 year; no more than 300 MB in total (the oldest are deleted when this is exceeded) | |
| Reading DataMatrix codes in the “Сканер DataMatrix” chatbot in the MAX messenger: replying to the user who sent an image, and improving recognition | The user’s and the chat’s MAX identifiers, images sent by the user. The chatbot does not store the name, phone number or other MAX profile data; decoded code strings are not stored | An image in which a code was read is deleted immediately after the reply. Images in which no code was found or read are kept to improve recognition: no more than 500 MB in total (the oldest are deleted when this is exceeded) and no longer than 1 year. The user identifier is kept only in memory to limit the request rate, for no longer than 1 hour |
Bank card data is entered on the payment operator’s page (YooKassa or Robokassa) and is not transferred to the Operator. The Operator does not process special categories of personal data or biometric personal data.
3. Legal grounds
- Performance of a contract to which the personal data subject is a party, and entering into a contract at the subject’s initiative (clause 5 of Part 1 of Article 6 of Law 152-FZ) — account, sessions, orders, invoices, payments, licenses and activations, emails about orders and licenses.
- Performance of obligations imposed on the Operator by law, including tax and accounting legislation (clause 2 of Part 1 of Article 6) — orders, invoices, payments; the obligation to prove that consent was obtained (Part 3 of Article 9) — consent log.
- Consent of the personal data subject (clause 1 of Part 1 of Article 6) — enquiries submitted through the feedback form and questions asked in the website chat, download statistics, security logs; website traffic analysis with Yandex Metrica — only with consent to analytics cookies, which the visitor gives in the cookie notice on the website (section 4); statistics on the use of the online code reading and generation services and of the links to the MAX chatbot by logged-in users; reading codes in the MAX chatbot — the user gives consent by sending an image to the chatbot (a link to this policy is in the chatbot’s greeting); marketing mailing — only with separate consent (Part 1 of Article 18 of the Federal Law “On Advertising”).
4. Cookies
The website uses three categories of cookies and browser storage entries (localStorage, sessionStorage):
- necessary — the session identifier for logging in to the personal account, a security token against request forgery (CSRF), a record of the chosen cookie settings and, for those who have written in the website chat, the __Host-chat cookie with a random identifier by which the website shows the visitor their conversation (kept for 180 days) and a “conversation started” mark in browser storage (libscanner-chat); login, forms and the chat do not work without them, so they are always enabled;
- functional — remembering the selected color theme (light or dark); they are stored only in the browser, are not sent to the server and are used only if the visitor has allowed them;
- analytics — cookies and storage entries of the Yandex Metrica service (_ym_uid, _ym_d and others with the _ym prefix): visit statistics and recording of actions on the website (Webvisor) in order to improve the website. They are used only with the visitor’s consent: without it the Metrica counter is not loaded and no data is sent to Yandex. The contents of form fields containing personal data, of the pages of the personal account and of administration, and the codes read or entered on the code reading and generation pages are not included in the session recording. The same category covers the entries of the website’s own anonymous statistics: libscanner-visit (start of a visit, sessionStorage), libscanner-scan-days (the days on which codes were read in this browser, no longer than 90 days), libscanner-scan-purpose (the answer to “What do you scan codes for?”) and libscanner-pro-interest (following the link to the “Pro” plan). Only anonymous values are sent to the server for them — the referral source and device type, the ordinal number of the scanning day, the chosen answer — without a visitor identifier; the server stores only a daily count. These entries are also created and sent only with consent to analytics cookies.
The choice is made in the notice shown on the first visit and can be changed at any time via the “Cookie settings” link at the bottom of every page. If analytics cookies are declined, data collection stops, and Metrica cookies and the website statistics entries are deleted from the browser. No advertising cookies are used on the website.
5. Procedure and conditions of processing
- Processing includes the collection, recording, systematisation, accumulation, storage, clarification, retrieval, use, transfer (provision, access), blocking, deletion and destruction of personal data, using automated means.
- The recording, systematisation, accumulation, storage, clarification and retrieval of personal data of citizens of the Russian Federation are carried out using databases located in the territory of the Russian Federation. The website server and the database are located in the Russian Federation.
- No cross-border transfer of personal data takes place.
- Upon expiry of the retention periods set out in section 2, upon achievement of the purposes of processing or after withdrawal of consent, the data is destroyed unless its storage is required by law or for the performance of a contract.
6. Transfer to third parties and processing on the Operator’s instructions
Personal data is transferred to third parties, or processed by them on the Operator’s instructions, only to the extent necessary for the purposes of processing:
- ООО «ЯНДЕКС» (YANDEX LLC; 16 Lva Tolstogo Street, Moscow, 119021, Russia) — email service: sending emails to users (recipient’s address, content of the email);
- ООО «ЯНДЕКС» (YANDEX LLC; 16 Lva Tolstogo Street, Moscow, 119021, Russia) — Yandex Metrica web analytics service: visit statistics and recording of actions on the website (Webvisor) to the extent set out in section 2 — only with the visitor’s consent to analytics cookies. The data is stored on servers in the Russian Federation;
- АО «ИОТ» (IOT JSC; INN 7731399513; 42 Bolshoy Boulevard, bldg. 1, Skolkovo Innovation Centre, Moscow, 121205, Russia) — hosting provider from which the server in the Russian Federation is rented: hosting of the website and the database;
- ООО «Яндекс.Облако» (Yandex.Cloud LLC, Yandex AI Studio service; INN 7704458262; OGRN 1187746678580; 16 Lva Tolstogo Street, premises 528, Moscow, 119021, Russia) — AI assistant of the website chat: answering the visitor’s question or preparing a draft reply for the Operator from the text of the conversation with email addresses, telephone and bank card numbers removed. The data is processed on servers in the Russian Federation and is not stored after the reply (request logging is disabled); it is not used to train models;
- ООО «МАХ» (MAKH LLC, operator of the MAX messenger; INN 9714058267; 39 Leningradsky Prospekt, bldg. 79, Moscow, 125167, Russia) — operator of the MAX messenger: delivery of messages and images between the user and the “Сканер DataMatrix” chatbot. The data is stored on servers in the Russian Federation;
- ООО НКО «ЮМани» (YooMoney NCO LLC, YooKassa service; INN 7750005725; 82 Sadovnicheskaya Street, bldg. 2, Moscow, 115035, Russia) — payment operator: accepting online payments and generating the cash receipt (order number and amount, order contents, the buyer’s email address for sending the receipt). Card and other payment details are entered by the buyer on the YooKassa page and are not transferred to the Operator.
- ООО «РОБОКАССА» (ROBOKASSA LLC, Robokassa service; INN 5047063929; OGRN 1055009302215; 26 Stremyanny Lane, Moscow, 115054, Russia) — payment operator: accepting online payments, including with cards issued by foreign banks, and generating the cash receipt (order number and amount, order contents, the buyer’s email address for sending the receipt). The buyer enters card details on the Robokassa page; they are not transferred to the Operator. Robokassa processes the data it receives as an independent operator in accordance with its own personal data processing policy.
In addition, data is provided to government authorities at their request in cases established by law.
7. Marketing mailing
Emails with news about releases, updates and offers are sent only with separate optional consent, which can be given at registration or in the “Downloads” section of the personal account. The mailing uses the email address and download information. When news is published, each subscriber’s address is copied to the mailing send queue (news_deliveries): emails are sent gradually, and the queue survives a server restart. A queue entry is deleted 30 days after the email is sent or, if the email was never sent, 90 days after it was queued. You can opt out of the mailing at any time: via the “Unsubscribe” link in every email, in the “Downloads” section of the personal account, or by writing to libscanner@yandex.com. After consent is withdrawn, the mailing stops.
8. User rights
The user has the right to:
- receive information about the processing of their personal data (Part 7 of Article 14 of Law 152-FZ);
- demand that the data be clarified, blocked or destroyed if it is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose of processing;
- withdraw the consent to the processing of personal data and the consent to marketing mailing, and demand deletion of the account;
- withdraw the consent to analytics cookies (Yandex Metrica) via the “Cookie settings” link at the bottom of the page;
- appeal against actions or omissions of the Operator to Roskomnadzor (the Russian data protection authority) or in court.
A request is sent to libscanner@yandex.com from the email address specified at registration, or by post to the Operator’s address. The Operator replies within 10 working days of receiving the request; this period may be extended by no more than 5 working days with notice of the reasons. After consent is withdrawn, processing stops and the data is destroyed within 30 days, except for data that the Operator is required to retain by law or processes on another legal ground (performance of a contract).
9. Data protection
The Operator takes legal, organizational and technical protection measures: data is transmitted only over a secure connection (HTTPS); passwords, session identifiers and one-time links are stored as hashes; access is restricted; administrators’ actions are logged; data is deleted upon expiry of the retention periods.
If an unlawful or accidental transfer (provision, dissemination, access) of personal data that has resulted in a violation of the rights of data subjects is detected, the Operator notifies Roskomnadzor: within 24 hours — of the incident, its presumed causes, the possible harm, the measures taken and the contact person; within 72 hours — of the results of the internal investigation and of the persons whose actions caused the incident (if any) (Part 3.1 of Article 21 of Law 152-FZ).
10. Changes to the Policy
The Operator may amend this Policy. A new version takes effect upon publication on this page; the date of the version is shown at the top.