DOZOR.BET

DOCUMENTS

Personal Data Processing Policy

How Dozor processes personal data: purposes, data, legal grounds, retention, recipients, transfers abroad, your rights and how to withdraw consent.

updated October 13, 2026

Contents

This is a translation. In case of discrepancies, the Russian version prevails.

This policy sets out the procedure and conditions for processing the personal data of users of the Dozor service and the measures taken to protect it. It is drawn up in accordance with Federal Law No. 152-FZ of 27.07.2006 “On Personal Data” (hereinafter the “Law”); terms are used in the meanings set by the Law.

1. General provisions

1.1. The personal data operator (hereinafter the “Operator”, “we”) is an individual applying the special tax regime “Tax on Professional Income” (a self-employed person, NPD):

Self-employed (Russia) Antonov Maksim Denisovich, Taxpayer ID (INN) 592012156078
Email: watch@dozor.bet
Support on Telegram: @dozor_manager

1.2. The policy applies to all personal data that the Operator receives from users of the dozor.bet website, the app.dozor.bet app and the service's Telegram bot (hereinafter together the “Service”).

1.3. The policy is published on this page in open access in fulfilment of Part 2 of Art. 18.1 of the Law.

1.4. Inquiries and requests on the processing of personal data are accepted at watch@dozor.bet.

The legal grounds are given under Part 1 of Art. 6 of the Law: the data subject's consent (item 1), performance of duties imposed on the Operator by law (item 2), performance of a contract to which the data subject is a party (item 5), the Operator's legitimate interest (item 7). The contract is the Terms of Use and Public Offer, the consent is the Consent to the Processing of Personal Data.

PurposeDataLegal groundRetention period
Sign-in and account managementEmail address; Telegram ID, username and name from TelegramConsent; performance of a contractAs long as the account exists
Operation of the Service according to your settingsScanner settings and notification rules, surebet journalPerformance of a contractAs long as the account exists
Payment and access recordsThe fact, date and amount of payment, plan, invoice ID at YooKassa or Trybit. The Operator holds no card or wallet detailsPerformance of a contractAs long as the account exists; self-employed receipts stay in “Moy Nalog” (the Federal Tax Service), payment records stay with YooKassa and Trybit under their rules
Account security, abuse protection, troubleshootingIP address, browser and device information, times of sign-ins and requests, errors; sign-in log (last 10 sign-ins)Operator's legitimate interestSign-in log: 180 days; sign-in session: up to 30 days; web server logs: about a week (rotation by size); application logs: no longer than 30 days (daily rotation); container system logs are limited by volume and overwritten as they fill
Service emails and notificationsEmail address, Telegram IDPerformance of a contractAs long as the account exists
Visit analyticsCounter cookie identifiers, IP address, browser and device information, page views, navigation, clicks, scrolling; on dozor.bet, a recording of on-page actions (Webvisor)Consent to analytics cookiesUnder the rules of Yandex Metrica and Google Analytics
Referral programReferral code, code of the person who invited you, information about invitees: sign-ups and payments through the linkPerformance of a contractAs long as the account exists
Support requestsThe text of the request and correspondence, the email address or Telegram account you write fromConsent3 years from the last request
Consent logDate and time, type and version of the document, your choice, IP address, browser informationCompliance with the law: the Operator must be able to prove that consent was obtained (Part 3 of Art. 9 of the Law)As long as the account exists
Database backupsEverything stored in the database, including the data listed above (account, payments, consent log with IP address)Operator's legitimate interest: restoring the Service after failuresUp to 6 months: daily copies are kept for 30 days, monthly copies for 6 months, then overwritten

Service messages are sign-in codes, confirmations of linking an email, and payment and subscription notifications. We do not send advertising mailings. The Service notifies you of surebets by sound and a browser notification; only subscription notifications arrive in Telegram.

The app.dozor.bet app runs only the Yandex Metrica counter without Webvisor: there is no recording of on-page actions there. Google Analytics runs only on dozor.bet.

3. Actions with data and methods of processing

3.1. The Operator performs the following actions with personal data: collection, recording, systematization, accumulation, storage, clarification (updating, changing), retrieval, use, transfer (provision), deletion, destruction.

3.2. Processing is carried out using automation tools (automated processing).

4. Place of storage and cross-border transfer

4.1. Data is stored on the servers of the hosting provider OVH SAS in France. Placing data on these servers is a cross-border transfer of personal data.

4.2. Google (USA) receives Google Analytics counter data only with your consent to analytics cookies.

4.3. Telegram receives data and passes it to the Operator when you sign in via Telegram and when you use the Service's bot; processing takes place on Telegram's infrastructure outside Russia.

5. Recipients

We do not sell your data. It is passed only to those without whom the Service does not work, and only to the extent needed for their task:

  • YooKassa (Russia): payment processing;
  • Trybit: cryptocurrency payment processing;
  • Unisender (Russia): delivery of emails with sign-in codes;
  • Telegram: sign-in via Telegram and subscription notifications;
  • Yandex (Yandex Metrica): visit analytics, only with your consent;
  • Google (Google Analytics): visit analytics for dozor.bet, only with your consent;
  • OVH SAS: hosting, servers in France.

Each recipient processes data under its own rules. Data is passed to government authorities only on a lawful demand.

6. Retention periods and destruction

6.1. Data is kept for the periods stated in the table in section 2 and is destroyed when they expire.

6.2. When consent is withdrawn or the account is deleted, data is destroyed in working systems within 30 days, and in database backups when the copies expire (up to 6 months); deleted accounts are not restored from backups. The exception is support requests: they are kept for the period in the table in section 2, 3 years from the last request. Payment records in the Service are kept as long as the account exists and are deleted along with it; self-employed receipts stay in “Moy Nalog” (the Federal Tax Service), payment records stay with YooKassa and Trybit under their rules.

7. Rights of the personal data subject

7.1. Under Arts. 14–17 of the Law you have the right to:

  • obtain information about the processing of your personal data;
  • demand that data be clarified, blocked or destroyed if it is incomplete, outdated, inaccurate, unlawfully obtained or not necessary for the stated purpose;
  • withdraw consent to processing;
  • appeal the Operator's actions or inaction to Roskomnadzor (the data protection authority) or in court.

7.2. How to exercise your rights:

  • in the “Account” section of the app: view and change the linked email and Telegram, end sessions on all devices, delete the account together with its settings and history;
  • by email to watch@dozor.bet: any request from item 7.1. State the email or Telegram account you use to sign in to the Service: we use it to find the account.

7.3. The Operator responds to a request within 10 business days of receiving it. The period may be extended by no more than 5 business days, with a reasoned notice of the reasons.

8. Cookies

The website and the app use necessary cookies (sign-in, session protection, language, referral tag, your cookie choice) and, only with your consent, the analytics cookies of Yandex Metrica and Google Analytics. The choice is made in the banner on your first visit and changed with the “Cookie settings” button. The full list, retention periods and the procedure for withdrawal are in the Cookie Policy.

9. Security

The connection to the Service is protected by HTTPS. Session cookies are inaccessible to page scripts and are bound to specific paths of the app. Access to servers and data is restricted and protected by keys. There is no absolute protection, so keep your email and Telegram access safe: it is equal to access to the account.

10. Age

The Service is intended for persons who are at least 18 years old. We deliberately do not collect data of persons under 18; if you learn of such an account, write to us and we will delete it.

11. Changes

We may update this policy. The new version is published on this page with the update date; we will notify you of material changes in the app or by email.