Privacy policy

Version dated 26 October 2026

1. Scope and controller

This policy governs data processing when using the website kadr.asinex.tech, the “Kadr: screen recorder and video editor” Chrome extension and the account service at api.kadr.asinex.tech. It applies to website visitors, extension users and people contacting support.

Controller: ASINEX Limited Liability Company, INN 9717192052, OGRN 1267700154402. Registered address: Premises 13P, Building 1, 17 Selskokhozyaystvennaya Street, Rostokino Municipal District, Moscow, 129226, Russia. Personal data contact: kadr@asinex.tech.

This policy takes into account Federal Law No. 152-FZ “On Personal Data” and Chrome Web Store requirements. It applies to Kadr. Consent for support enquiries is obtained separately when processing is based on consent. Controller contact and company details are available on a separate page.

2. What data Kadr processes

Recordings and projects on your device

At your request, the extension records video of the selected tab. If you enable the relevant features and grant browser permissions, tab audio, microphone and webcam are added. Recording segments, styling settings, caption text, teleprompter scripts and project information are saved for editing.

Auto zoom and action visualization process click coordinates and times, pointer movements, scrolling, navigation events and permitted control keys and shortcuts. The selected tab's address is checked; its title may be used as the project name. The extension does not collect your full browsing history. Ordinary typed text is not saved as a keystroke log. However, anything visible or audible in the recorded tab, including entered data, may appear in the video or audio itself.

Video, audio, captions and recording events are stored locally by the extension. Kadr does not send them to its server or an external speech recognition service. Export runs on your device. You control sharing the exported file with others.

Account and email sign-in

Sign-in is optional for recording and editing. When requesting a code, the server receives your email, interface language, client type and device name. Account records contain an identifier, email, preferred language, creation date, plan status, session information and sign-in and activity dates. Cryptographic derivatives of codes and tokens are stored on the server for verification. The one-time code is delivered by email; session tokens are stored on your device to keep you signed in.

Your IP address is processed during network connections and used to prevent abuse. Database rate limiters use hashed IP and email identifiers. Accounts do not synchronize local recordings between devices. Payments are not connected in the current version, and Kadr does not request bank card details.

Website visits and enquiries

When you access the website and API, the infrastructure receives your IP address, request date and time, resource address, response status and technical browser headers, including user-agent and referrer if provided. This information is needed to deliver pages, diagnose issues and protect the service. Support emails involve processing the sender's address, correspondence and attachments you choose to send.

The Kadr website has no registration or payment forms. Pressing Allow in analytics settings loads Yandex Metrica counter 113811435 with Session Replay, click maps and link tracking. It processes browser identifiers, IP address, device information, page URLs and referrers, views, clicks, scrolling and recorded website interactions. Session Replay reproduces interactions with a website page; it does not record your computer screen or extension activity. The extension does not use user data for advertising. Details of local storage and cookies are in a separate document.

3. Processing purposes and grounds

• Recording, editing, captions and export: performing functions requested by the user on their device. Browser permissions control camera and microphone access.
• Accounts and service emails: providing the sign-in function selected by the user and carrying out interactions at their initiative. A sign-in code is not an advertising mailing.
• Website analytics: assessing traffic, referral sources and page usability with Yandex Metrica based on a separate Allow choice. Declining does not restrict website access. Change your choice using Analytics settings at the bottom of the page.
• Support: reviewing and replying to enquiries and providing requested help; user consent applies where required by law.
• Security and reliability: preventing abuse, diagnosing issues and restoring service based on the controller's legitimate interests while respecting user rights and data protection obligations.
• Personal data enquiries: fulfilling obligations under applicable law.

Processing is limited to these purposes. It may include collection, recording, organization, storage, correction, use, providing access to necessary service providers, restriction, deletion and destruction. Automated and mixed processing are used.

Kadr does not request special categories of personal data or use images or voice to identify individuals. Users determine the contents of their recordings and whether they have grounds to record other people's data. Do not include information unnecessary for your task in enquiries or recordings.

4. Infrastructure and external services

• Cloud.ru: hosting the account service and backups on infrastructure in Russia. Backups include account and session data; local videos and projects are not included.
• Yandex Metrica (YANDEX LLC): website analytics and Session Replay after visitor consent. Data is sent to Yandex infrastructure and processed under the Yandex privacy policy and Metrica terms. Counter code is included only on the website; extension recordings, email and tokens are not sent to it.
• REG.RU: email infrastructure for delivering sign-in codes and support correspondence. The recipient's email provider also receives the address and content during delivery.
• Hugging Face and its delivery infrastructure: downloading speech recognition model files when using captions. These network requests reveal your IP address and technical request information to the service. Kadr does not send audio, video, caption text or account email with these requests. The external service processes requests under its privacy policy; its infrastructure may be located outside Russia.
• Chrome Web Store: the extension is installed and updated through Google's store under its rules. The website links to the store but does not embed its trackers or widgets.

Service provider access is limited to what is needed to provide functions and operate infrastructure. Disclosure to authorized authorities is permitted only on legal grounds. We do not sell user data, share it with advertising platforms or data brokers, or use it to assess creditworthiness or issue loans.

5. Retention periods

• Local projects: until deleted by the user or cleared by the browser. Downloaded files remain where you saved them and are deleted separately. The browser manages the recognition model cache.
• Account: while used to provide the service, until deletion following a verified request or until the processing purpose ends, unless law requires otherwise.
• Sign-in code: valid for 10 minutes. Expired code request records are removed by a scheduled task that runs hourly while the service is running.
• Session: up to 30 days; the access token is valid for 15 minutes. After revocation or expiry, server session and token records are removed by the next hourly cleanup.
• Analytics choice: saved in localStorage for 180 days, after which the website asks again. Metrica cookie lifetimes depend on their purpose; examples are in the cookie document. Retention of collected statistics and Session Replay recordings is governed by Yandex service settings and rules. Declining prevents future counter loading but does not itself delete previously shared data; contact the controller about its processing.
• Technical logs: used for diagnostics and security and replaced during rotation. Website container logs are limited to two files of up to 5 MB each. This is a size limit, not a fixed number of days.
• Backups: hourly snapshots for 48 hours and daily snapshots for 14 days are retained locally. Separate storage retains the latest 8 snapshots and daily snapshots for 14 days. Cleanup follows successful verification of a new backup; older backups may be retained longer if backup operations fail.
• Support enquiries: until the interaction is completed. In the absence of another legal basis, data must be deleted within 30 days of achieving the processing purpose or withdrawing consent where processing is based on it. Evidence of compliance with legal obligations may be retained for legally prescribed periods.

6. Your rights and data deletion

You may request information about processing, correction, restriction, cessation of processing or deletion of data, withdraw consent where processing relies on it, and contact Roskomnadzor or a court.

To delete your account, email kadr@asinex.tech with the subject “Delete Kadr account” from the address associated with the account. For other enquiries, use the subject “Personal data”. We will verify the requester's connection to the data and handle the request within statutory time limits. Do not send a password or one-time code. If additional identification information is needed, we will explain what is needed and why.

Account deletion is handled on request; the current version has no separate deletion button. Data is removed from the live database subject to applicable legal obligations. Backups are considered when fulfilling requests: they are not used for routine account operations; if restoration is necessary before backups are updated, completed deletion requests must be reapplied before returning the service to operation.

Users delete local projects in the extension. Deleting an account does not delete projects from the device, and uninstalling the extension does not delete the server account. Kadr has no remote access to your local recordings.

7. Protection and access restrictions

API connections use HTTPS. Codes and tokens are verified using cryptographic derivatives, and access to servers and backups is restricted. Offsite backups are encrypted. Rate limits, session revocation and restoration checks are used.

Employee access to user data is permitted for help explicitly requested by the user with permission for the specific data, for security or to comply with law. Employees cannot access local recordings unless the user sends them to support. We do not use recordings to train models.

8. Chrome Web Store requirements

Use of data obtained through Google and Chrome APIs complies with the Chrome Web Store User Data Policy, including Limited Use requirements. Data is used only for Kadr's stated functions and related support, security and reliability tasks.

9. Policy changes

The current version is published on this page with its update date. When new processing purposes or functions require consent, the necessary information and consent are provided before that processing begins. Visiting the website alone does not constitute consent to advertising or optional analytics.