Back

Data and privacy

Information used for sign-in, licensing and support. The controller’s legal identity is not published in this version; this service description does not replace a complete set of controller documentation.

Version dated 3 October 2026

Questions, support and requests: @exfador

1. Scope and contact

This document describes data handling on coxerhub.com and through @COXSTARS_BOT. Contact @exfador on Telegram for data questions and requests. Telegram, marketplaces and external services connected by users have their own data terms.

Publication of this text and browsing do not constitute separate consent to every data operation. Where consent is required, it must be specific, informed and obtained separately from other accepted documents. Contract performance and legal obligations may provide independent legal grounds.

2. Data and sources

The service uses information provided by users, confirmed Telegram sign-in and website or plugin operation:

  • Telegram ID, first and last name and username when supplied through sign-in; account role, registration and login times.
  • Available products, licenses, validity periods, access grants and revocations, protected representations of keys and device bindings.
  • Allowed IP addresses and networks, their labels, technical request addresses or shortened representations, license checks and denials.
  • Protected session identifiers, browser information, security events, two-factor settings and action logs.
  • Notification and consent preferences, account messages and Telegram delivery attempts.
  • Support requests and payment or diagnostic information supplied by users. Do not send unnecessary information or access secrets.

3. Purposes and legal grounds

Account and order information identifies users, provides agreed access, enables available downloads and supports users. IP addresses and device bindings enforce license limits. Technical events help prevent guessing attacks, abuse and unauthorized access.

Request records enable responses, claims handling and protection of lawful rights. The legal ground depends on the operation: contract formation or performance, a statutory duty, a permissible legitimate interest respecting user rights, or separately obtained consent.

Sign-in does not give the website your Telegram password or access to your entire private correspondence. Messages you send to the bot or support are available to their recipient.

4. Cookies and browser storage

Cookies support sign-in sessions, request protection and your selected theme. Browser local storage avoids repeatedly displaying the same notifications. Blocking or deleting this technical data may prevent sign-in or protected actions from working.

The current interface does not integrate advertising trackers or third-party visitor analytics. New tools require assessment of the data, legal grounds and necessary information or consent.

5. Notifications and advertising

License grants and revocations, purchased-plugin updates and service information may appear in the account and be delivered through Telegram according to preferences. Telegram delivery requires an available bot chat and may fail if the bot is blocked.

Advertising requires prior separate consent and must not be a purchase condition. Withdraw through settings or by contacting @exfador. Service messages must not bypass an advertising opt-out. Unsubscribing from advertising does not cancel a license.

6. Recipients, hosting and backups

Administrative and support access is limited to what the respective tasks require. Project infrastructure is hosted with Aeza. Telegram handles sign-in and message delivery, receiving the necessary chat identifiers and outgoing message content.

Database backups support recovery. The current process sends an encrypted archive through Telegram to the project owner’s private chat, with the password stored separately. The archive may include account and license data. Encryption does not remove legal requirements concerning recipients, retention or transfers.

The controller must verify infrastructure locations and the permissibility of cross-border operations. This version does not claim that all processing takes place exclusively in Russia or that required Roskomnadzor notices have been filed. Disclosure to authorities requires a legal basis and is limited to the necessary scope.

7. Retention and protection

Active account, license and obligation records are needed during the relevant relationship. Once a purpose is fulfilled, data must be deleted, anonymized or retained only on an independent lawful basis, such as mandatory records or a dispute. A past sign-in does not establish indefinite retention of all data.

Current technical cleanup periods are 180 days for account notifications, 30 days without updates for IP denial records and 24 additional hours after expiry for login requests. Expired sessions and single-use authorizations are removed by background processing. These periods do not mean that account, audit and backup data disappear together.

Access controls, protected connections, protected identifier and key storage, session controls and backups are used. Absolute prevention of leaks is not promised. Deletion must account for copies and backup restoration; applicable periods and lawful retention grounds are explained on request.

8. Your rights and requests

Users may request processing information, correction, restriction or deletion where justified, withdraw consent and complain to Roskomnadzor or a court. Send @exfador the request and enough information to identify the account safely, without unnecessary documents or access secrets.

Each request follows its statutory deadline. Withdrawing consent ends operations based solely on that consent; an independent legal ground may permit continued retention, which must be explained. Deleting information necessary for identification and licensing may prevent further account use; consequences are clarified before the request is executed.

New purposes, recipients or methods require updated information and, where necessary, fresh consent. Changing this text does not itself expand previously granted consent.

Related documents