Home

KADR Privacy Policy

Version of November 21, 2026

This policy explains what data is processed when you buy and use KADR, where it is stored, why, and for how long. Terms are as defined in the Terms of Use https://kadrapp.dev/en/terms.

This English version is a convenience translation. If it differs from the Russian text, the Russian text prevails.

1. Who is responsible

The data controller is the seller: the developer and copyright holder of KADR (the "Seller"). Data questions: the support bot @kadr_help_bot on Telegram.

2. In short

3. Data on your computer (not received by the seller)

What Where and how
Projects: scripts, voice-overs, images, videos, thumbnails, settings Program folders on your PC
API keys, passwords, tokens and sessions for third-party services (Google/YouTube, Meta/Instagram, ElevenLabs, Pexels, Pixabay, etc.) Locally, encrypted with Windows DPAPI (only your Windows account on this PC can decrypt them)
License key and computer code Locally; the key is verified in the software and, at least once every 14 days, on the seller's server (see below)
Program logs Locally
Error report Created only on your command — a zip archive on the Desktop. You decide whether to send it to the seller and can review its contents first

The software connects only to services you connect yourself (Section 6), to GitHub to check for updates, and — if you turn on cloud control — to the relay on Cloudflare. In addition, at least once every 14 days the software contacts the seller's server on Cloudflare to check that the key has not been revoked; it sends the key ID and a hash of the computer code.

4. Data processed by the seller

4.1. Purchase and key issuance (sales bot in Telegram)

Data Why
Telegram user ID, name and username (as provided by Telegram) Contacting you, issuing the key, support
Payment ID (Telegram Stars charge id or NOWPayments payment id), coin, amount, date, tier; crypto refund address if you sent one Sales and tax records, refunds
License data: key ID, tier, expiry, issue date, transfer history Issuing, renewing and transferring keys; enforcing transfer limits
Computer code — a SHA-256 hash of Windows and hardware identifiers; the identifiers themselves are not sent in plain form Binding the key to one computer
Messages with the bot and support; error reports you send yourself Support
Result of the subscription check for the @kadrapp_news channel (subscribed or not) and when it was checked; Telegram tells the bot on request Mandatory subscription for the sales bot and shop; only the latest result is kept

4.1.1. Bonus programs (if you take part)

Data Why
Who invited whom (Telegram IDs), invitation status Giving bonus days for friends
Hashes (SHA-256 with a secret salt) of a device tag and browser fingerprint from the check in the bot; the values themselves are not stored Protection against second accounts of the same person
Hash of the IP address from the check in the bot (SHA-256 with a secret salt) Only as a reference for the owner when reviewing bonuses manually; no blocks or refusals are based on IP
The link to your video and its public stats (views, likes, comments, channel name) Reviewing the video for the bonus

4.1.2. Personal account (https://cloud.kadrapp.dev/account)

Data Purpose
Telegram user ID, name and username that the bot receives when you log in via the link Logging in, showing your keys, renewals and upgrades to Pro
Hash of the one-time login code (valid for 10 minutes) Linking the browser to your Telegram at login
Session hash in the database and the kadr_acc cookie in your browser (HttpOnly, Secure, limited to account addresses, 30 days) So you don't have to log in again; logging out deletes the session
Hash of the IP address (SHA-256 with a secret salt) and a 10-minute request counter Protection against brute force and overload; access to keys is never decided by IP

4.2. If you turn on cloud control (control bot and relay on Cloudflare)

Data Why
Hashes of link codes (one-time codes used to link the PC to your Telegram) Secure linking of the PC to your chat
Binding: Telegram chat ID ↔ your PC's ID in the relay Delivering commands and notifications to the right user
Command and notification content in transit: video titles, task status, cover thumbnails, command text Passing them between the PC and your Telegram

Command and notification content is kept only until delivered: it is deleted after delivery or after 24 hours, each user's queue is limited to 200 messages, and older messages beyond the limit are dropped. The relay does not keep an archive of your videos, covers or commands.

Cloud control is optional — the main features do not depend on it. You can unlink the PC with /unlink in the bot @kadr_remote_bot or with the button in the software; the binding is then deleted.

5. Processors

Processor Role Policy
Telegram (Telegram Messenger Inc. / Telegram FZ-LLC) Messenger, bots, Telegram Stars payments https://telegram.org/privacy
Cloudflare, Inc. Website, infrastructure for the sales, control and support bots, the relay, the payment page and key checks (Workers, storage) https://www.cloudflare.com/privacypolicy/
NOWPayments Cryptocurrency payments: amount, coin, payment status (the computer code and key are not shared with it) https://nowpayments.io/doc/privacy-policy
Google LLC (Google Fonts) Fonts on the cloud.kadrapp.dev pages (personal account, payment page, Telegram mini apps): your browser loads fonts from Google's servers, so Google sees your IP address. The kadrapp.dev website uses its own fonts and does not contact Google https://policies.google.com/privacy
GitHub, Inc. Distribution of the installer and updates (GitHub Releases). When checking for updates GitHub sees your IP address, as with any website request https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement

These companies may process data outside your country, including in the United States. Such transfers rely on standard contractual clauses or other mechanisms provided by law.

6. Third-party services you connect yourself

YouTube / Google Cloud, Instagram / Meta, Anthropic (Claude Code), OpenAI (ChatGPT Codex), Google AI Studio, Flow and Gemini, ElevenLabs, Pexels, Pixabay, Wikimedia Commons, Mixkit, Nexlev and others. The software contacts them directly from your computer, using your own accounts and keys. Data you send them (text, audio, images, videos, metadata) is processed under their own privacy policies and terms. The seller does not receive this data and is not responsible for its processing. The local Piper and Kokoro voices work without sending text to the internet.

7. Purposes and legal bases

Purpose Legal basis
Selling, issuing, renewing and transferring keys; support Performance of a contract (Terms of Use)
Delivering cloud control commands and notifications Performance of a contract — a feature you turned on
Payment records and keeping sales documents Legal obligation (tax and accounting)
Preventing abuse: key resale, bypassing transfer limits, repeated trials Seller's legitimate interest

We make no automated decisions with legal effects for you, other than the technical key check (term, tier, computer).

8. Retention

Data Period
Payment records 5 years
License data and transfer history Key term + 12 months; for lifetime keys — while the license is valid
Support messages and error reports you sent 12 months after the last request
Cloud control binding Until unlinked or 6 months of inactivity
Link code hashes Until the code is used or expires (30 days)
Command and notification content Until delivered, no longer than 24 hours
Hashes from the check in the bot (device, fingerprint, IP) 12 months
Invitations and video bonus requests While the bonus key is valid + 12 months
Personal account session Until logout or 30 days
Account login codes and IP hashes in request counters 1 day
Channel subscription check result While you use the sales bot; deleted on request

After the period ends, data is deleted or anonymized.

9. Your rights

You can request access to and a copy of your data, correction, deletion, restriction of processing, objection to processing based on legitimate interest, and data portability. If you are in the EU/EEA or the UK, you may also lodge a complaint with your national data protection authority.

Send requests to the support bot @kadr_help_bot on Telegram. We usually reply within 1–2 business days and complete the request within 30 days at the latest. Deletion may not be possible for data we must keep by law (payment records); after license data is deleted, the key can no longer be renewed or transferred.

10. Children

The software is not directed at people under 16. We do not knowingly collect their data; if we learn of such a case, we will delete it.

If you publish content for children, setting "Made for Kids" labels and meeting related platform requirements (for example, COPPA on YouTube) is your responsibility.

11. Security

No system is completely secure. If a serious incident affects your data, we will notify you through the bot where required by law.

12. Changes

A new version is published at https://kadrapp.dev/en/privacy with a date. We will announce material changes in the bot.

13. Contact

The developer and copyright holder of KADR Telegram support: @kadr_help_bot