Privacy and Personal Data Policy

1. General provisions

This Policy describes the processing of personal data and other user information in CS2 Team Finder.

The Policy applies to the website, web application, Telegram bot, Telegram Mini App, and other related service features.

For users in the Russian Federation, personal data is processed with due regard to Federal Law No. 152-FZ “On Personal Data”.

2. Data controller

Personal data controller:

individual Igor Sergeevich Kulgachev, taxpayer identification number (INN): 920157528798.

Email for personal-data inquiries:

hello@cs2teamfinder.ru.

3. Categories of data processed

3.1. Account

The service may process email, password hash, internal user ID, account status, language, registration and sign-in dates, authentication-method details, and the versions of documents accepted.

3.2. External sign-in methods

When external authentication is used, the service may process the user ID held by the relevant provider, provider name, email and display name if supplied by the provider, account-linking information, and technical parameters of the OAuth process.

The data involved depends on the specific integration.

3.3. Player profile

The service may process nickname, age or age range, region, country, languages, in-game roles, maps, skill level, schedule, gaming goals, description, communication preferences, and visibility settings.

3.4. Gaming services

When the relevant features are used, the service may process Steam ID and Steam profile details, FACEIT ID, nickname, level, ELO and statistics, as well as gaming information obtained through Leetify or other explicitly connected sources.

3.5. Telegram

The service may process Telegram ID, username, display name, Telegram account-linking details, and data needed for the Telegram bot, Mini App, and notifications.

3.6. Coach profiles and reputation

If the feature is available, the service may process a coach’s biography, experience, specializations, photo, links, ratings, reviews, and related information.

3.7. Teams and collaboration

The service may process information about teams, rosters, member roles, vacancies, applications and invitations, praccs, calendar events, tasks, strategies, notes, attachments, and other materials created through team features.

3.8. Communication and moderation

If chats are available, the service may process messages, sending and reading times, blocking details, and complaints.

When reviewing a complaint, the service may process its text, information about the user or content concerned, administrative comments, and the decision made.

3.9. Project support

When the project-support feature is used, the service may process the chosen support method, amount or description of the value transferred, transaction status and time, an external transaction or payer identifier, and other parameters received from the relevant provider.

For a manual request, the user may provide a description, proof of the transaction, and other necessary information.

3.10. Notifications

The service may process email and Telegram notification preferences, delivery data, event type, and notification recipients.

If a team configures an external webhook, the relevant information may be sent to the address specified by the team.

3.11. Technical data

The service may process IP address, user-agent, request date and time, technical identifiers, logs, error details, security events, and information about user actions.

Browser storage technologies, including localStorage and sessionStorage, may be used for the web application.

3.12. Analytics

With the relevant consent and if analytics is enabled in the current configuration, the service may collect information about use of the website.

In particular, the service technically provides for the use of Yandex Metrica, including features for analyzing visits and interactions with the interface.

An additional product analytics tool may also be used if enabled in the current configuration.

Optional analytics technologies must be used in accordance with the user’s choices in cookie and analytics settings.

4. Purposes of processing

Data may be used to create accounts, authenticate users, maintain profiles, operate search and recommendations, form teams, organize praccs and other team processes, enable user communication, operate calendars and tasks, display reputation, connect with Telegram and gaming services, send notifications, process project support, prevent abuse, moderate content, provide technical support, maintain security, perform analytics, and improve the service.

5. Legal bases

Depending on the specific operation, processing may be based on the user’s consent, the need to perform the Terms of Use, compliance with a legal obligation, or the exercise of lawful rights and interests of the controller or third parties where permitted by law.

If separate consent is needed for particular processing, it is requested separately.

Consent to optional marketing messages and optional analytics must not be inferred solely from the creation of an account.

6. Visibility of data to other users

Some data is intended for interaction between users within the service and may be available to other users depending on the selected feature, role, and visibility settings.

This may include nickname, avatar, gaming statistics, roles, maps, goals, schedule, region, language, description, Steam/FACEIT information, and reputation elements.

The available fields depend on current backend rules and the user’s settings.

Users should not put information in public fields or fields available to other users if they do not want to disclose it to the relevant audience.

7. Data obtained from external services

Data may be obtained from Steam, FACEIT, Leetify, Telegram, VK ID, Yandex ID, and other services only within an available integration and a scenario chosen by the user.

Third-party services independently determine how they process data on their side under their own documents.

8. Browser storage

localStorage, sessionStorage, and cookies may be used for the application to work.

In particular, localStorage may hold application authentication data, the user’s cookie and analytics choices, language, and temporary technical information needed for certain authentication processes.

sessionStorage may hold short-lived information needed to continue a user flow within the current browser session.

Further details are provided in the Cookie and Browser Storage Technologies Policy.

9. Analytics systems

With user consent and the relevant configuration, Yandex Metrica may be connected.

It may receive technical information about a visit, page URLs, referral source, browser, device, and user actions on the website.

If additional features such as Webvisor or clickmap are activated, interactions with a page may be analyzed.

Additional product analytics is used only when actually enabled in the configuration and permitted by the user’s choice, where consent is required.

10. Data sharing

Data may be transferred to or made available to third parties to the extent needed for the relevant feature.

Recipients may include infrastructure and hosting providers, email infrastructure providers, Telegram, Steam, FACEIT, Leetify, VK ID, Yandex ID, analytics services, and services that a user or team connects independently through a webhook.

URLs posted or transferred through particular service features may be checked by an external link-security service if that integration is enabled.

The service does not sell users’ personal data.

11. Cross-border transfer

Some external services may be located outside the Russian Federation or process data using foreign infrastructure.

Cross-border transfers are carried out only in compliance with applicable legal requirements and necessary organizational procedures.

The actual list of countries and recipients depends on the services the controller really uses.

12. Retention

Data is retained no longer than needed for the stated processing purpose, unless a different period is set by law or by a lawful necessity of the controller.

Retention periods vary by data category.

After account deletion is initiated, the account may remain recoverable for a period set by the service.

After final deletion, the account and related data subject to deletion under the service’s technical model are deleted.

Some information may be retained after account deletion, for example data needed to review complaints, maintain security, keep technical logs, confirm project-support transactions, protect the parties’ rights, or comply with the law.

When an account is deleted, the link between certain project-support records and the internal account may be removed, while some transaction or external identifiers within the record may remain for the period needed for the relevant purpose.

Deletion from the active system does not mean immediate deletion from every backup, if backups are used. They must be deleted or overwritten according to the backup retention cycle established by the controller.

13. Data security

The controller takes technical and organizational measures aimed at limiting unauthorized access, securing accounts and infrastructure, and controlling administrative access.

However, absolute security of information transfer and storage on the internet cannot be guaranteed.

14. User rights

Where provided by law, users may obtain information about processing of their data, request its correction, restriction, deletion, or destruction, and withdraw consent previously given.

To make a request, write to hello@cs2teamfinder.ru.

Optional analytics consent may also be changed or withdrawn through the website’s cookie settings.

Withdrawing permissions from an external provider may additionally require action in the settings of Steam, Telegram, VK ID, Yandex ID, or another service.

15. Minors

CS2 Team Finder sets a minimum age of 13 for using the service.

If applicable law requires a parent’s or another legal representative’s participation or consent, a minor may use the service only if that requirement is met.

A user below the specified minimum age must not create an account.

16. Policy changes

The Policy may be updated when service features, processing methods, or legal requirements change.

The current version is published on the website.

If changes require renewed user consent, the service may request it through the interface.

17. Contact

hello@cs2teamfinder.ru.