Rules and User Agreement

1. Agreement and definitions

1.1. CF Ranking is the name of the project and application. In these Rules, “Operator” means the person responsible for operating the project and publishing the application. This Agreement does not claim registration of a trade mark or a separate legal entity. Support email: support.cfranking@gmail.com. Email for personal data enquiries: support.cfranking@gmail.com. Persons authorised by the Operator to manage the project and perform moderation are referred to as the administration.

1.2. CF Ranking provides tools for organising matches, rankings, tournaments, team communication, support requests and purchases available to the user. CF Ranking is not the developer of Standoff 2; rights in the game belong to the respective rights holders.

1.3. A user is an individual who has created their own account. A CF Ranking account and a Standoff 2 game account are separate accounts, linked by the Standoff 2 ID provided. Each individual must use only one CF Ranking account.

1.4. A league is a competition format with defined eligibility criteria. A match is a game whose identifier, participants, map and conditions are recorded in the application. A party is a group of users searching for a match together. A game lobby is a match room in Standoff 2. The host is the participant responsible for creating and configuring the lobby. The captain performs the team selection and map selection actions prescribed by the procedure. A rehost is the recreation and restart of a lobby under subsection 4.3. AFK means a player's absence from active participation in a match. KD is the ratio of kills to deaths.

1.5. A cooldown is a temporary restriction of specific account functions. An account or service ban is a temporary or indefinite termination of access on the grounds set out in sections 8–9. Disqualification means exclusion from a particular competition and is not equivalent to a ban on the entire account.

1.6. The Agreement is provided to the user before registration. Acceptance requires a separate action in the application interface. Acknowledging the Privacy Policy does not replace consent to data processing where consent is required. Additional purchase or event terms are provided before the user confirms the relevant action.

1.7. The rules apply equally to all users, including partners, public project representatives, paying users and staff participating in matches. Individual arrangements must not disadvantage other participants or exempt anyone from fair play requirements.

1.8. Mandatory provisions of applicable law take precedence. Event-specific terms specify the format, deadlines and prizes but do not override user rights, security rules or appeal procedures. Where special terms conflict with the general rules, they apply only to the extent expressly identified and made available before participation begins.

1.9. A sanction may be imposed for an established act or omission constituting a breach under this Agreement. Unsubstantiated suspicion, personal dislike, lawful criticism and submission of a complaint are not independent grounds for sanctions. The examples in section 9 explain the offences and do not permit arbitrary extension of prohibitions by analogy.

1.10. Periods are calculated in calendar hours and days unless expressly stated otherwise. Sanction decisions and event terms must specify the exact date, time and time zone; an omitted time zone is interpreted in the user's favour. Technical match timers are displayed in the application.

1.11. The minimum age for CF Ranking registration is 12. Users under 18 require their legal representative's consent to the contract and to actions for which such consent is required by applicable law. Clause 6.6 of the Privacy Policy sets additional conditions for consent-based data processing. Match participation separately requires compliance with the Standoff 2 terms; stricter age limits imposed by law, the game or a particular prize event remain applicable. The CF Ranking registration age does not replace store age ratings or permit circumvention of third-party restrictions.

1.12. CF Ranking is an international project open to users from any country worldwide. Citizenship or country of residence alone is not grounds for refusing participation. Individual functions are provided subject to mandatory applicable law and distribution platform rules. This Agreement does not select the law of a particular country on an exclusive basis or restrict mandatory user rights. Where a specific function requires a restriction, its grounds and scope are disclosed before registration, purchase or participation in the relevant event.

2. Registration, accounts and security

2.1. On registration, the user must provide their own Standoff 2 ID and create a unique public nickname and login credentials. An email address is mandatory only for functions that require it for performance. Identifiers belonging to another person, known to be inaccurate or obtained unlawfully must not be used.

2.2. Match eligibility does not depend on the age of a CF Ranking account. Experience and device requirements are set out in section 3.

2.3. Accounts must not be bought, sold, gifted, rented, shared for match participation or placed under another person's control to alter rankings or obtain advantages. Requesting support to restore access does not constitute an account transfer.

2.4. Additional accounts must not be created or used to evade sanctions, obtain weaker opponents, claim repeated bonuses, self-refer or re-enter an event with restricted participation. A user who accidentally registers twice must contact support before playing matches. One primary account is designated following review.

2.5. A shared IP address, network or device does not by itself establish misuse of multiple accounts. Reviews must consider shared family connections, gaming centres, public networks and other substantiated circumstances.

2.6. Users must protect passwords, session tokens and access links, refrain from publishing them and report compromise without delay. Support does not request passwords, CVV codes, one-time banking codes or third-party service passwords.

2.7. Where account compromise is suspected, the administration may temporarily restrict high-risk actions, revoke sessions and request proportionate evidence of account ownership. A security restriction does not establish that the user committed an offence.

2.8. Actions performed through an account are assessed in light of the evidence. Confirmed compromise, a malfunction or third-party actions do not conclusively establish the account holder's fault; results of unfair matches may nevertheless be corrected.

2.9. Logging out, reinstalling the application or changing devices does not cancel achievements, purchases or match history. Paid service periods and sanctions continue to run under their applicable terms. Account deletion is governed by the Privacy Policy and section 15 of these Rules.

2.10. The linked game ID must correspond to the user's account. Support corrects an incorrect link after verifying ownership. A correction must not transfer another person's statistics, cancel existing sanctions or circumvent eligibility criteria.

2.11. Users must report incorrectly credited goods, points or funds to support and must not spend disputed credits after receiving notice of a review. Corrections are based on transaction logs and explained to the user.

2.12. Support, appeals, purchase enquiries and the exercise of personal data rights remain available while gameplay functions are restricted. If the account is inaccessible, the user may contact the Operator using the published contact details.

3. Leagues, devices and eligibility

3.1. General requirements

3.1.1. The baseline experience requirement is at least 300 hours in Standoff 2. Users with less experience may request an individual eligibility review. The reasons for the decision are recorded; purchasing admission to bypass the review is prohibited.

3.1.2. Before entering matchmaking, players must check their game version, connection stability, device power, voice communication availability and ability to meet recording requirements. Objective limitations must be reported to support in advance.

3.1.3. Users must accurately disclose their device and control method when requested for eligibility or verification. Devices may be changed between matches within league rules. Only one gaming device may be used during a match; a necessary replacement must be agreed with moderation and must not involve a substitute player.

3.1.4. The prohibitions on cheats, macros, action automation and interference with the game apply to all devices. Permission to use a device does not permit circumvention of the Standoff 2 rules.

3.2. Unified Default League

3.2.1. Mobile and PC users participate in one unified Default League, with shared matches, rankings, settings and disciplinary rules. There is no separate PC league.

3.2.2. Default League permits smartphones, tablets, PCs, emulators and external input devices, including keyboards and mice, subject to the game rules and sections 6–7. The type of permitted device is not, by itself, grounds for cancelling a match or imposing a sanction.

3.2.3. Changing devices does not require a league transfer or alter rankings, existing restrictions or disciplinary history. Recording requirements for PC play and external input devices are set out in subsection 7.3.

3.2.4. Default League participation is free. Reaching level 10 in Default League makes a user eligible for free Qualification League access, subject to its requirements. Access may alternatively be purchased under section 11. Both routes are subject to the same device, fair play and continued eligibility requirements.

3.3. Qualification League

3.3.1. Qualification League matches permit only smartphones with a screen diagonal of no more than 7 inches. Tablets, hybrid devices, PCs, emulators and virtual environments are not permitted.

3.3.2. Electronic external controllers, including keyboards, mice, gamepads, joysticks and similar devices, are prohibited. Mechanical triggers without built-in electronics or automation are permitted.

3.3.3. Device types are verified under section 7. Concealing a device, substituting the device shown or falsifying its specifications constitutes a separate offence.

3.3.4. Continued eligibility requires a KD of at least 0.95 and at least 30 registered matches in each 30-day period from admission or purchase of access. Only confirmed matches within the relevant period are counted; cancelled and incorrectly registered matches are excluded.

3.3.5. If the standard is not met at the end of the period, access may be terminated with the calculation provided and an opportunity to correct errors. Widespread project outages and match unavailability are taken into account when extending the period. For paid access, the standard must be disclosed before purchase; refunds are governed by section 11.

3.3.6. The three highest-placed participants in the final Qualification League ranking become eligible for Test Pro League, subject to its admission requirements. Purchasing a paid service does not guarantee a particular competitive result.

3.4. Test Pro and Pro League

3.4.1. Test Pro and Pro are subject to the smartphone, screen size, emulator and external device restrictions in clauses 3.3.1–3.3.3.

3.4.2. Test Pro requires a KD of at least 1.05 and at least 30 registered matches in each 30-day period from admission to Test Pro. Calculation, error correction and outage adjustments follow clauses 3.3.4–3.3.5. Failure to meet the standard results in termination of Test Pro access by a reasoned decision.

3.4.3. Additional Pro performance requirements apply to the period for which they were published. Poor performance is not grounds for exclusion without a defined eligibility criterion or a proven offence.

3.4.4. Where a prohibited device is used in Qualification, Test Pro or Pro, only affected matches are cancelled and eligibility for that league is reviewed. The user remains able to use that device in Default League after applicable restrictions expire.

4. Match preparation, play and results

4.1. Matchmaking and lobby creation

4.1.1. By confirming participation, a player undertakes to remain available, complete player and map selection and finish the match. Reserving a place without intending to play, circumventing matchmaking restrictions or changing the roster outside the prescribed procedure is prohibited.

4.1.2. The application determines team rosters, sides and the map. Creating a party does not confer a right to demand a rehost or alter the published roster without authorisation. Player substitution, transfer of control and undeclared participants are prohibited.

4.1.3. All players must join the game lobby within 5 minutes after the final roster is published. Within the same period, the host must create the lobby and invite the assigned players using their game IDs. The host must verify the roster and settings before starting.

4.1.4. A match consists of two teams of five players. The map, number of rounds and settings must comply with the match card and Appendix A. The server region is stated on the card before participation is confirmed. The host must use that region; changes are permitted only under the established procedure, with participants notified before the match begins.

4.1.5. If a participant leaves during player or map selection, the remaining participants must stay connected to the lobby until the stage is cancelled or restarted in the application. Leaving and re-entering matchmaking to force a change of opponents is prohibited.

4.1.6. Before the match starts, each participant must report any apparent roster, map or settings error. A participant who knowingly exploits an error is responsible for that conduct; the designated host is responsible for configuration, taking account of the actions available to them.

4.2. Match conduct

4.2.1. Deliberate inactivity, absence for three or more consecutive rounds, intentionally assisting one's own team's defeat, obstructing teammates, disclosing team plans to opponents, deliberately dropping the bomb to disrupt play and changing sides without authorisation are prohibited.

4.2.2. Poor statistics, a tactical mistake, limited experience or an isolated failure do not by themselves constitute sabotage. Intent is established from conduct in the match context and supporting evidence.

4.2.3. Adding spectators to gain an advantage, transferring control, playing against one's own account, fixing outcomes, deliberately losing for a reward or distributing wins among associated participants is prohibited.

4.2.4. Initiating or knowingly supporting a player's removal from a match is prohibited unless the match procedure expressly permits it. Sanctions apply to identified participants in the offence. Membership of the same team does not establish that every player took part.

4.2.5. Participants must remain connected to the team's voice room and able to hear its messages. Playing without voice connectivity or with headphones switched off for three or more rounds is prohibited. Between 22:00 and 08:00 local time, players may refrain from using their microphone while remaining able to hear the team. Necessary accessibility exceptions are agreed without disclosing a diagnosis to other players.

4.2.6. If connection latency (ping) exceeds 150 ms for three consecutive rounds, the player must notify the team and moderation. An individual fault is assessed in light of its effect on the match. Widespread outages, confirmed service unavailability and other circumstances beyond the player's control exclude automatic sanctions.

4.2.7. Incompatible Standoff 2 updates are subject to temporary restrictions published in the application. These must not be circumvented even if a device has the latest version available to it. Compatibility restrictions do not create a separate PC league.

4.2.8. The broadcaster determines the delay applied to their stream. An absence of delay does not permit other participants to obtain information from the stream for a competitive advantage. Such use of a stream (stream sniping), prohibited spectator assistance and transmission of information otherwise unavailable to a participant are prohibited.

4.3. Rehosts and cancellation

4.3.1. A rehost is permitted for an objective reason: a client malfunction, an assigned player's absence, incorrect settings or another confirmed technical obstacle to properly starting the match. The reason must be announced in chat and evidence retained.

4.3.2. A rehost for ordinary technical reasons is permitted until the red timer in the third round expires. Results of rounds played before the rehost are not carried over to the recreated match. Disagreement with team rosters, losing the opening rounds or wishing to form a party is not grounds for a rehost.

4.3.3. If the number of rounds is incorrect, the match may be cancelled at any stage and must not be registered in the incorrect format. Other settings errors must be reported before the specified third-round cutoff; ordinary technical cancellation is unavailable after that point. Confirmed cheats, roster substitution and result falsification are reviewed regardless of the cutoff.

4.3.4. No more than two rehosts are permitted in total for both teams. If the match still cannot begin in accordance with clause 4.1.4, it is deemed not to have taken place and is not registered. Fictitious rehosts to change the roster or evade a sanction are prohibited.

4.3.5. Cancelling a result corrects the competitive outcome and does not automatically sanction all participants. In sabotage cases, a match is cancelled only where the offence is proven to have materially affected the result. AFK alone is not an unconditional ground for cancellation.

4.4. Results and identification

4.4.1. The result screenshot must be submitted through the application and enable verification of the final score, rosters, map and match completion time. If the game does not show the time, match data must confirm it. Missing information must not be added by editing the image.

4.4.2. Altering statistics in an image, combining results from different matches, submitting another match's material, registering a result twice and concealing participant information needed for verification are prohibited. Unrelated personal data may be redacted after prior notification, provided the result is not distorted.

4.4.3. The profile nickname must allow the player to be unambiguously linked to their Standoff 2 ID. Until the result is registered, but for no longer than 24 hours after the match, the player must not change their game nickname without notifying support. System recognition errors are corrected on the evidence.

4.4.4. Result registration is suspended pending review where data is missing or inconsistent. Verified figures are restored from the case materials. Fictitious kills, deaths or assists must not be entered as a disciplinary measure. Deliberate falsification constitutes a separate offence.

4.4.5. A result is registered once it has been processed and displayed in the application. Corrections must identify the reason and affected figures. Match disputes are submitted under section 10.

5. Communication, profiles and user content

5.1. These rules apply to match chats, voice rooms, profiles, clan names and images, attachments, complaints, support requests and other content available through the application. Staff are subject to the same communication standards.

5.2. The language of participant communication is determined by match settings and the need to exchange game information the team can understand. Available support languages are listed in the application. Use of a particular language is not grounds for humiliation or discrimination. Using another language is not an offence in itself if it does not obstruct team coordination and complies with these rules.

5.3. Targeted insults, repeated provocation, humiliation, bullying, sexual harassment, stalking and circumventing communication restrictions to continue contact are prohibited. Non-directed profanity without humiliation, threats or chat disruption does not by itself result in a sanction.

5.4. Racist and other discriminatory attacks, promotion of violence, encouragement of suicide or harm, threats against a user or their close relations, blackmail and extortion are prohibited. Neutral references to family, religion or beliefs do not constitute an offence.

5.5. Pornography, sexual exploitation, sexual material involving minors, involving children in dangerous acts, graphic violence, trading prohibited items and instructions for committing crimes are prohibited. Such content is hidden without waiting for a repeat offence.

5.6. Publishing another person's address, telephone number, documents, private correspondence or intimate material without a lawful basis, threatening such disclosure and using another person's image to impersonate them are prohibited. Public availability of information does not authorise harassment or compiling dossiers for stalking.

5.7. Repeated messages that disrupt chat, audio spam, music playback and deliberate voice distortion that obstruct team communication are prohibited. Three identical messages within a short period may indicate such a breach. Technical retransmissions and necessary game messages are assessed in context.

5.8. Advertising, mass invitations, commercial offers and referral spam require prior authorisation. Links to evidence in support requests, official resources and necessary game materials are permitted. Malicious and phishing links are always prohibited.

5.9. Nicknames, avatars and descriptions must not breach clauses 5.3–5.8, simulate verification, impersonate staff or obstruct identification. The service prefix “!” and the labels Admin, Moderation and Support may be used only by authorised staff in an official capacity.

5.10. Deliberately copying a verified profile, using lookalike characters to deceive and displaying counterfeit badges are prohibited. A shared ordinary name does not itself establish deception. Contact details and advertising links are removed from nicknames, and the user is given an opportunity to choose a compliant nickname.

5.11. The administration may hide offending content, replace an impermissible nickname with a neutral one and restrict uploads or communication. The user is informed of the reason and appeal route. Dangerous content need not remain available pending voluntary correction.

5.12. Good-faith criticism of the project, a partner or a staff member, reporting misconduct and negative reviews are permitted. Sanctions apply to proven deception, threats, harassment and other defined breaches. A negative assessment is not itself grounds for a sanction.

5.13. Dangerous content may be reported through the application or the published support contact. The administration prioritises restricting access to dangerous material. Making a report does not authorise republication of the material in public chat.

5.14. Users retain rights in their content and grant the Operator a limited, non-exclusive permission to store, technically process and display it as necessary for the selected function, moderation and dispute resolution. Independent advertising use of a user's image requires a separate lawful basis.

6. Fair play and service security

6.1. Cheats, modifying game memory or files for an advantage, bypassing anti-cheat, automated aiming or recoil control, autoclickers and macros that perform gameplay actions in place of a person are prohibited. A program's name does not determine an offence: its functions and proven use or possession specifically as an offending tool are assessed.

6.2. Artificially degrading connectivity for an advantage, manipulating packets, latency or synchronisation, interfering with results, bypassing client restrictions and falsifying device or request data are prohibited.

6.3. Exploiting vulnerabilities, duplicating currency or items, bypassing limits, falsifying receipts, unauthorised access to others' accounts or data, malicious files, service overload and automated activity that disrupts the service are prohibited.

6.4. Users must report discovered vulnerabilities to support through a non-public channel, providing only the information necessary to substantiate them. Extracting others' data, continuing exploitation, demanding payment under threat of disclosure and supplying attack tools to third parties are prohibited. A good-faith vulnerability report does not itself result in sanctions.

6.5. Match fixing, third-party boosting of another person's account, deliberate rating reduction, win trading, fictitious matches, collusion for rewards, artificial manipulation of statistics, fake opponents and coordinated matchmaking to manipulate results are prohibited.

6.6. Knowingly assisting a person using prohibited tools, facilitating their use, distributing them or receiving an agreed benefit from an offence constitutes complicity. Being randomly assigned to a team with an offender or being unaware of concealed prohibited software does not establish complicity.

6.7. Phishing, fraudulent exchanges, fake support messages, offers to remove bans for payment, extorting access and payment fraud are prohibited. Staff must not demand personal transfers for reviewing a complaint or reaching a favourable verification outcome.

6.8. Bribing participants or staff, pressuring witnesses, destroying relevant evidence after receiving a preservation notice and knowingly false complaints are prohibited. A good-faith mistaken suspicion or insufficient substantiation of a complaint does not itself constitute an offence.

6.9. Cooldowns, bans and regional, eligibility or purchase restrictions must not be circumvented through another account, device, intermediary or fictitious information. A technical change of network or device without that purpose is not itself an offence.

6.10. Ordinary developer tools, alternative installers, a certificate, debugging, root access, jailbreak or an unlocked bootloader do not by themselves prove cheating. If a configuration conflicts with verifiable security requirements, its eligibility may be temporarily restricted until corrected, with the technical reason explained. This does not replace proof of an offence.

7. Anti-cheat: grounds, procedure and limits

7.1. Grounds and authority

7.1.1. A verification review may be conducted where there are specific indicators of an offence, a substantiated complaint, a verifiable result anomaly or a pre-announced eligibility check for prize recipients. The staff member records the grounds, match and scope in an in-app support case.

7.1.2. A verification request may be issued without arranging a time in advance where evidence from the current match needs to be preserved. The user is told who will conduct the review, what actions are required and the deadline. Unavailability and technical faults are considered before concluding that the user is evading verification.

7.1.3. Reviewers must act within their assigned authority, avoid conflicts of interest and record material actions and the outcome. A complaint concerning a staff member must be reviewed by another authorised staff member.

7.1.4. Before screen or voice recording begins, the user receives information about the purpose, scope, recipients, retention period and lawful basis for processing. Where separate consent is necessary, it is obtained before recording. Covert recording by staff and personal use of the material are prohibited.

7.1.5. Only information relevant to the device, match and suspected offence may be requested. Passwords, banking codes, complete correspondence, access to cloud archives, unrelated photographs or inspection of all household devices must not be demanded without specific grounds.

7.1.6. Users may conceal unrelated personal information, request the reasons for a requirement and propose an equally effective, less intrusive verification method. Exercising these rights is not refusal to cooperate. A diagnostic report request must specify the necessary data and exclude information unrelated to the review.

7.1.7. Remote PC access requires a separate agreement through an in-app support case. Users must be able to observe the staff member's actions and end the session. Staff must not establish covert access, retain credentials or change unrelated settings. If verification cannot be performed safely, eligibility is restricted and an alternative method is used. This inability does not prove use of cheats.

7.1.8. A smartphone must be checked using a compatible method. A player who has no PC is not required to provide one. If a microphone or screen demonstration is unavailable for a valid reason, an accessible alternative is agreed.

7.2. Materials and user cooperation

7.2.1. After a specific evidence preservation request, users must not deliberately delete relevant recordings, alter files under review, substitute a device or falsify a report. An ordinary system reinstallation before such a request is not itself an offence or proof of cheating.

7.2.2. A requested screenshot and simultaneous game-screen video must be taken at a safe point in play: during the red preparation timer, with a weapon held and the view directed towards the opposing team's base. Actions intended to disrupt the current round must not be demanded.

Example of proper SS/MS compliance: this example shows the correct way to comply with an SS/MS request: the screenshot and/or screen recording must be taken during the red preparation timer, with a weapon in hand, and with the view directed toward the opposing team's base. This method is considered proper, safe for the current round, and not an interference with gameplay.

7.2.3. An ordinary request for this material may be made once per player per match; a further request is permitted after reconnection. An additional staff request requires a separate explanation and must not be used for harassment.

7.2.4. Material must be submitted through the support case within one hour after the request is received. If submission is objectively impossible, the player must explain why and retain the original; staff must set a proportionate additional deadline. Repeated failure to provide mandatory material may lead to an eligibility review under section 9.

7.2.5. Original recordings with timestamps and sufficient context are preferred. Extracts are acceptable if they do not conceal relevant circumstances. An AFK complaint must include recordings of three consecutive rounds; where file size is limited, separate extracts of up to 40 seconds from each round may be submitted with the full timing context identified.

7.2.6. A link to the material must be submitted through a restricted-access support case. Publishing verification material for harassment is prohibited. Passwords, access secrets and third-party information accidentally recorded must be removed from the working copy without altering the circumstances of the event under review.

7.3. Recording PC play and external input devices

7.3.1. In the unified Default League, PC or emulator players must record gameplay using an instant-replay buffer of at least 7 minutes or continuous recording. The recording software is not restricted to a particular graphics card manufacturer.

7.3.2. The recording must cover the game screen and transitions necessary to verify actions during the match. Continuous desktop recording outside the match is not required. A process list may be shown only to the extent relevant to the review; unrelated information must be concealed.

7.3.3. For a smartphone used with a keyboard and mouse, available screen recording or external video recording must be used. Where on-device recording is technically impossible, continuous external recording of at least 1080p is permitted, showing the screen, hands and input devices.

7.3.4. The material's filename must identify the match, round and author, for example: “Match 12345 — round 6:12 — player ID”. A naming error must be corrected and is not itself equivalent to a missing recording.

7.3.5. Players must retain required recordings for at least 48 hours after the match and, if notified of a dispute, until its conclusion within the notified retention period. Absence of a recording after the period expires, without a dispute notice, does not result in a sanction.

7.3.6. Knowingly false advance claims that recording is technically impossible are prohibited. A confirmed malfunction is assessed separately from deliberate destruction of evidence; eligibility may be restricted until a suitable recording method is configured.

7.4. Verification outcome

7.4.1. The outcome is recorded in the support case, identifying established facts, applicable provisions, conclusions, restrictions, periods and the appeal procedure. Reliance solely on an anti-cheat decision without explaining the factual grounds is insufficient.

7.4.2. Suspected misconduct, device incompatibility and confirmed use of cheats are assessed separately. An indefinite ban for cheating requires evidence of the offence. Temporary protective measures must comply with section 8.

7.4.3. Staff must not threaten users, demand payment, fabricate evidence, disclose private information or use access for personal purposes. Complaints about a review must be referred to a staff member independent of it under section 10.

7.4.4. A completed review recording is retained for complaints and appeals under the Privacy Policy. Users may obtain information concerning them, subject to protection of other people's data and specific offence-detection methods.

8. Restrictions and sanction principles

8.1. Types of measures

8.1.1. A corrective notice requires the user to amend a profile, correct information or stop a minor breach. The number of such notices is not an independent basis for an automatic ban.

8.1.2. A communication cooldown restricts the chats, posts and voice transmission specified in the decision to the stated extent. A gameplay cooldown restricts participation in a particular league. A global gameplay cooldown applies to all leagues. Each measure preserves access to appeals and data and purchase enquiries.

8.1.3. A protective suspension may be imposed to address an active risk or preserve a review for up to 72 hours, with reconsideration within 24 hours. A supervisor may extend it to 7 days by a reasoned decision stating the necessary actions and next review date. A longer restriction requires an established offence or a specific lawful basis notified to the user.

8.1.4. Rating corrections, cancellation of affected matches, removal of content and reversal of erroneous transactions remedy consequences. They do not substitute for sanctions and must not affect unrelated purchases or results without separate grounds.

8.1.5. A temporary account ban lasts for the period specified in section 9. An indefinite ban may be imposed for proven, particularly serious offences under the conditions stated there. It remains subject to internal review where there is an error or new evidence.

8.1.6. An eligibility restriction arising from objective non-compliance lasts until its cause is resolved. It must not be used as an indefinite disciplinary cooldown; the user must be informed of a verifiable condition for restoring access.

8.2. Repeat offences and proportionality

8.2.1. Section 9 specifies baseline periods for a first proven incident. Unless a particular offence specifies its own repeat-offence period, a second similar offence within 30 days of the preceding offence doubles the baseline temporary sanction; a third multiplies it by four. Separate incidents, rather than the number of complaints about one event, are counted.

8.2.2. For offences with a baseline gameplay cooldown of 24 hours, a third similar incident within 30 days results in 7 days. The next similar incident within 30 days after that restriction ends results in 30 days. This rule applies equally to all leagues.

8.2.3. Repeat-offence escalation is capped at 7 days for communication cooldowns, 30 days for league or global gameplay cooldowns and 90 days for temporary account bans. The number of minor offences alone cannot justify an indefinite ban. Such a ban requires grounds under subsection 9.4 or proven systematic circumvention of restrictions.

8.2.4. Offences are similar if they fall under the same offence provision or one of these groups: spam; abusive communication; non-attendance, leaving and AFK; lobby procedure violations; failure to provide mandatory material; result manipulation; or evasion of eligibility requirements. The decision must explain the classification. An incident outside the specified 30-day period is not counted towards the sanction multiplier.

8.2.5. Intent, actual harm, duration, benefit obtained, age, confirmed malfunction, voluntary cessation and assistance in remedying consequences are considered. Mitigation must be explained. An increase beyond the baseline and prescribed escalation is permitted only under an expressly defined more serious offence.

8.2.6. Multiple gameplay cooldowns for the same act in one incident must not be added together; the most precise offence provision applies. Communication and gameplay may be restricted together where independent offences in each area are proven, with grounds and periods stated separately.

8.2.7. Sanctions apply to the proven offender. A team result may be cancelled because of one player's conduct, but individual bans on others require evidence of their participation or knowing assistance.

8.2.8. A sanction starts at the time specified in the notice; protective suspension already served for the same function is credited. Undisclosed extensions, restarting a period on login and retroactive sanctions under new rules are prohibited.

8.2.9. The decision must identify the event, applicable clause, material evidence, baseline period, repeat offences considered, final period, affected functions and appeal procedure. Erroneous restrictions are removed and affected figures corrected.

8.2.10. Purchasing removal of disciplinary sanctions, preferential treatment in an appeal or deletion of disciplinary history is prohibited. An amnesty does not replace correction of an error and may operate only under publicly defined criteria.

9. Offences and baseline sanctions

The periods below apply together with section 8. “Removal” means removal of offending material, not the account. Escalation does not turn corrective notices into a cumulative warning system.

9.1. Communication and profiles

9.1.1. Repeatedly posting duplicate or unrelated messages after being instructed to stop: a 1-hour communication cooldown; offending messages are removed.

9.1.2. Deliberate extraneous sounds, audio spam or disruption of voice communication: voice transmission restricted for 1 hour. An accidental fault must first be given an opportunity to be corrected.

9.1.3. An isolated targeted insult or deliberate provocation: a 6-hour communication cooldown. Losing a match does not justify abusive language.

9.1.4. Insults against close relations, degrading sexual remarks or repeated personal harassment: a 24-hour communication cooldown; systematic bullying falls under clause 9.1.5.

9.1.5. Organised bullying, discriminatory attacks or encouragement of violence or self-harm: communication and global gameplay cooldowns of 7 days each. A credible safety threat is assessed under clause 9.4.5.

9.1.6. Unauthorised advertising or mass invitations: removal and a 1-hour communication cooldown. Fraudulent advertising falls under subsection 9.4.

9.1.7. Persistent demands for money or items after refusal: a 6-hour communication cooldown. A single ordinary request without pressure is not extortion.

9.1.8. An impermissible nickname, contact details within it or imitation of an official designation without fraud: replacement and a 1-hour communication cooldown. An ordinary technical error must first be given an opportunity to be corrected.

9.1.9. An offensive or prohibited avatar, description or clan name: removal and a 24-hour communication cooldown. Particularly dangerous material falls under clause 9.4.6.

9.1.10. Knowingly impersonating a specific player or staff member: removal of the impersonating content and a 7-day global gameplay cooldown; theft of access or property falls under clause 9.4.2.

9.1.11. Knowingly false information about project terms intended to deceive players: a 24-hour communication cooldown. Substantiable criticism and good-faith mistakes do not constitute this offence.

9.1.12. Circumventing a contact restriction to continue harassment: communication and global gameplay cooldowns of 7 days each. Repeated organised bullying may result in a 30-day temporary ban.

9.2. Eligibility and match organisation

9.2.1. Failure to attend within 5 minutes after roster assignment, leaving during player or map selection or unjustifiably refusing to start a confirmed match: a 24-hour gameplay cooldown in the relevant league.

9.2.2. Incorrect settings, late lobby creation or failure to invite assigned players attributable to the host: a 24-hour gameplay cooldown. Treatment of the result is governed by subsection 4.3.

9.2.3. An unjustified rehost, a false cancellation reason or deliberately exceeding the rehost limit: a 24-hour gameplay cooldown.

9.2.4. Leaving for three or more rounds or being AFK without a substantiated valid reason: a 24-hour gameplay cooldown. Proven intent to disrupt the match falls under clause 9.3.1.

9.2.5. Playing without mandatory voice connectivity or with headphones switched off for three or more rounds: a 24-hour gameplay cooldown, subject to any agreed accessible alternative.

9.2.6. Continuing to participate with a connection known to be unusable or circumventing published compatibility restrictions: a 24-hour gameplay cooldown. A widespread project outage does not result in a sanction.

9.2.7. Using a device not permitted in Qualification, Test Pro or Pro without concealment: a 24-hour gameplay cooldown in that league and suspension of eligibility until compliance; the affected result is reviewed.

9.2.8. Deliberately concealing a prohibited device or substituting it during verification: a 7-day gameplay cooldown in the relevant league, cancellation of affected matches and eligibility review. Evidence forgery is assessed separately under clause 9.4.4.

9.2.9. Changing gaming devices during a match without authorisation, thereby obstructing verification: a 24-hour gameplay cooldown. Transferring control to another person is treated as player substitution.

9.2.10. An incorrect game ID or nickname preventing registration: registration suspended until correction. Knowingly using another person's ID or deliberately concealing a participant results in a 7-day gameplay cooldown; substitution of the account holder falls under clause 9.4.3.

9.2.11. Changing a nickname before result registration in breach of clause 4.4.3 or repeatedly submitting a result known to be unusable after receiving an explanation: a 24-hour gameplay cooldown. Technical rejection of a screenshot without fault does not result in a sanction.

9.2.12. Failure to provide mandatory material within the notified deadline without a valid reason: a 24-hour gameplay cooldown and verification of readiness for the next match. A repeat incident justifies further review but does not automatically prove cheating.

9.3. Competitive integrity offences

9.3.1. Deliberate sabotage, assisting one's own team's defeat, obstructing teammates or disclosing team plans to an opponent: a 72-hour gameplay cooldown and correction of any result materially affected.

9.3.2. Initiating or knowingly supporting prohibited removal of a player from a match: a 72-hour gameplay cooldown for each identified participant in the offence.

9.3.3. Obtaining a competitive advantage by viewing an opponent's stream, receiving prohibited spectator assistance or using other external information: a 7-day global gameplay cooldown and review of affected results.

9.3.4. Deliberately exploiting a game error for an advantage without system interference: a 7-day global gameplay cooldown and result correction. Hacking and system vulnerability exploitation fall under clause 9.4.1.

9.3.5. Match fixing, win trading, deliberate rating reduction or third-party account boosting: a 30-day global gameplay cooldown, reversal of proven benefits and disqualification from the affected competition. A repeated organised incident results in a 90-day ban. Establishing an ongoing scheme to evade restrictions results in an indefinite ban supported by a reasoned decision.

9.3.6. Creating an additional account for an advantage or bonuses: a 30-day global gameplay cooldown on the primary account and closure of the improper additional account. A registration error without exploitation of an advantage is resolved under clause 2.4.

9.3.7. Deliberately manipulating the queue, roster or opponents without fixing the outcome: a 7-day global gameplay cooldown and result review. Collusion falls under clause 9.3.5.

9.3.8. Unauthorised repeat registration of an already recorded match or bypassing registration to manipulate statistics: a 72-hour gameplay cooldown; erroneous records are corrected.

9.3.9. Concealed receipt of assistance from an offender with proven knowledge of the offence: the same sanction as for knowing participation in the relevant scheme, with the individual's contribution and benefit explained.

9.4. Serious offences and security

9.4.1. Proven use of cheats, interference with the game, service hacking, data theft, a malicious attack or anti-cheat circumvention: an indefinite ban and reversal of proven affected results and unlawful credits.

9.4.2. Fraud, phishing, account theft, extortion, falsified payments or misappropriation of others' items: an indefinite ban; restitution of disputed property is determined from verified transactions and applicable law.

9.4.3. Playing through another person's account, transferring control to alter rankings or obtain advantages, or selling or renting an account: a 30-day ban and cancellation of affected results. A repeat offence results in a 90-day ban. Systematic account trading or evasion of an existing ban results in an indefinite ban.

9.4.4. Forging material evidence, deliberately destroying material after a preservation request or bribing a staff member or witness: a 30-day ban; a repeat incident results in a 90-day ban. Proven fraud or concealment of prohibited tools is subject to the relevant grounds for an indefinite ban.

9.4.5. A credible threat of physical violence, blackmail involving personal information or publication of data for harassment: immediate cessation of dissemination and a 30-day ban. An established serious threat, repeated harassment or extortion results in an indefinite ban.

9.4.6. Sexual exploitation of minors, dissemination of such material or preparation of a violent crime through the service: immediate hiding of the material and an indefinite ban. Information is preserved and disclosed to competent authorities only as prescribed by law.

9.4.7. Evading an existing ban or global gameplay cooldown through another account: termination of the circumvention and a 30-day ban; a repeated or organised scheme results in an indefinite ban. A shared network without other evidence is insufficient.

9.4.8. Deliberate refusal of a proportionate review where an accessible alternative has been offered and no objective obstacle exists: gameplay eligibility suspended until verification is completed, with reconsideration under clause 8.1.3. An indefinite cheating ban requires independent evidence of cheating.

9.4.9. Artificially increasing referrals, balances, bonuses or payments through rule violations: a 30-day global gameplay cooldown and reversal of related improper credits. A proven systematic fraud scheme results in an indefinite ban.

9.4.10. Knowingly presenting another person's payment instrument as one's own, forging a receipt or fraudulently obtaining repeated reimbursement for one transaction: a 30-day ban; proven financial fraud falls under clause 9.4.2. A good-faith refund request or bank enquiry is not an offence.

9.5. Support requests and staff misconduct

9.5.1. Mass repetitive requests intended to obstruct support: duplicate requests restricted for 24 hours, while retaining one active case and access to urgent security and data matters.

9.5.2. A knowingly false complaint without forged material: a 24-hour communication cooldown. Insufficient evidence from a good-faith complainant is not grounds for a sanction.

9.5.3. Threats, bullying and insults in a support case are assessed under the general rules; staff status does not itself increase the sanction.

9.5.4. A staff conflict of interest, unjustified refusal to consider evidence or procedural violation: removal from the case and independent reconsideration of the decision. The Operator determines personnel measures.

9.5.5. Bribery, data theft, falsification of a review or a staff member's use of access for personal purposes: immediate revocation of official access, preservation of evidence and the applicable general sanctions. An unlawful decision is corrected irrespective of personnel measures.

10. Complaints, evidence and appeals

10.1. Complaints are submitted through the application. If the account is inaccessible, the published support contact must be used. Users are encouraged to provide the match ID, time, participant, circumstances, relevant clause and original materials. Failure to cite a clause number is not itself grounds for rejection.

10.2. A match result complaint should be submitted within 24 hours after completion to help ensure recordings remain available. Later submission is not itself grounds for rejection; the reasons for delay and availability of evidence are considered. Reports of fraud, threats, data leaks and erroneous bans are accepted irrespective of this recommended period.

10.3. Requests are registered. The target for an initial response is 72 hours and for a reasoned decision in an ordinary case, 7 calendar days. Where further review is needed, the user receives the reason for extension and a new date, normally no later than 14 days. Statutory consumer and personal data response periods take precedence.

10.4. Immediate security threats, account compromise and dangerous content receive priority. Application support is not an emergency service; immediate threats to life must be reported to local emergency services.

10.5. Recordings, screenshots, match logs, transaction details and other verifiable information are accepted. Automated alerts, a single witness account or statistical anomalies are evaluated together with the other evidence. A disputed final decision must be capable of human review.

10.6. A user whose conduct is under review must have an opportunity to explain and challenge the information. The administration discloses the substance of material evidence. Third-party personal data and specific detection methods may be withheld, with the reason stated.

10.7. A request must not be rejected solely because the other party is a paying user, a personal acquaintance or has previously had a good-faith disagreement with staff. The language used is not grounds for rejection where translation is reasonably available. A staff member with a conflict of interest must refer the matter to another authorised person.

10.8. An appeal must be submitted within 30 days after notification of the decision. A missed deadline may be reinstated for a valid reason. Obvious errors and significant new evidence may be considered later; internal deadlines do not restrict access to courts or supervisory authorities.

10.9. An appeal is considered by a staff member who did not participate in the challenged decision. If no such staff member is available, the Operator conducts the review. The target period is 7 days, or 14 days where a justified extension is notified to the user.

10.10. Appealing does not increase the sanction and requires no payment. A new, independent offence may be reviewed separately. Duplicate submissions concerning the same matter are merged with the original without loss of material.

10.11. If a sanction is overturned, restrictions are removed, the erroneous decision record is corrected and affected rankings, eligibility and paid service rights are restored to the extent technically and legally possible. Where restoration is impossible, the user receives reasons and information about an alternative remedy.

10.12. The final internal decision concludes the internal procedure but does not remove the right to seek judicial protection or contact a regulator, payment provider or legally designated dispute resolution body.

11. Purchases, paid services and refunds

11.1. Access and ordering

11.1.1. Default League and Pro League participation is free; Pro performance eligibility requirements remain applicable. Qualification League access may be obtained free upon reaching Default League level 10 or purchased. Payment does not waive device, experience or continued eligibility requirements.

11.1.2. Before payment, the offer card must disclose the seller, total price and currency, taxes and mandatory charges, service content, access period, activation time and termination and refund terms. Where a subscription is offered, the billing interval, automatic renewal, trial period and cancellation method must be stated separately. Undisclosed automatic renewal is prohibited.

11.1.3. The Qualification continued eligibility requirements in clauses 3.3.4–3.3.5 are provided immediately before purchase. Access advertised as unconditional must not be terminated for an undisclosed KD or activity requirement. Readmission arrangements and service duration must be stated in the offer before payment.

11.1.4. Payment for league access grants only the rights expressly stated in the offer. It does not guarantee a win, a particular ranking, successful verification, a cash prize or a skin awarded as a competition reward, and does not exempt the user from sanctions. This does not limit the obligation to deliver a specific item purchased from the store. CF Ranking does not guarantee income or investment returns.

11.1.5. An order requires an explicit user action. The confirmation must state the subject, price, date, transaction identifier and applicable terms in a form the user can retain. A technical error must not require repeat payment before the first transaction is checked.

11.1.6. A gift purchase requires the correct recipient identifier. The recipient, item or service transferred and error-correction procedure must be stated before payment. Fulfilment does not remove the payer's mandatory refund rights or protection against unauthorised transactions.

11.1.7. CF Ranking does not offer paid cases, roulette or purchases of random prizes. A separate free prize event may be held only under rules published in advance and in compliance with platform terms and applicable law.

11.2. Cybercoins and store goods

11.2.1. Cybercoins are CF Ranking internal accounting units. Users earn them through confirmed participation in the project and may also purchase them. Available earning methods, package price and number of units are disclosed before the relevant action.

11.2.2. Cybercoins may be exchanged for goods and in-game skins offered in the store. Before order confirmation, the card must specify the selected item, cybercoin price, availability, transfer terms and applicable restrictions. The selected item must not be replaced with a random item.

11.2.3. The balance displays credits, spending and adjustments. The origin of purchased and earned units is retained for refunds and dispute resolution. Accounting errors are corrected against a verifiable transaction, with notice to the user; arbitrary deductions are prohibited.

11.2.4. Cybercoins are internal accounting units and do not confer rights under a bank account or deposit. These rules do not provide for direct conversion of cybercoins into money. Users retain their rights to receive paid goods, have orders fulfilled and obtain refunds where required by law.

11.2.5. Transfers of cybercoins between users and external sales are permitted only where an expressly provided function and published terms allow them. Transferring an account to circumvent this restriction is prohibited.

11.2.7. Future store price changes do not alter an already confirmed order. If an item is withdrawn before fulfilment, an agreed replacement or restoration of the deducted units with their original classification must be offered. Mandatory monetary claims remain unaffected.

11.2.8. Published rules determine match completion requirements, participation rewards and grounds for withholding a reward. Properly earned units must not be cancelled because of an unrelated offence. Credits for proven falsified matches are corrected together with the results.

11.3. Withdrawal and service defects

11.3.1. Consumers retain statutory rights to withdraw from a distance contract, have digital product defects remedied, obtain a price reduction and terminate the contract. There is no blanket prohibition on refunds for all purchases.

11.3.2. Where a right to withdraw from a distance contract applies, the standard period is 14 days; its commencement and possible extension depend on applicable law and proper provision of information. Separate withdrawal instructions and a model form with the seller's details are provided before payment.

11.3.3. For digital content not supplied on a tangible medium, early loss of the withdrawal right is possible only when all statutory conditions are met, including separate prior consent to immediate performance, acknowledgement of the loss of the right and provision of the required contract confirmation. Acceptance of general terms alone does not replace these steps.

11.3.4. Services and digital services are governed by the conditions applicable to their legal category. Starting to use a service does not itself extinguish all withdrawal rights. Payment for a part already performed following withdrawal is permitted only in the cases and to the extent allowed by law.

11.3.5. A withdrawal notice may be sent to the seller's published contact, identifying the order and clearly stating the intention to withdraw. Use of the model form is optional. Where a platform store processed the payment, its refund procedure is also available; the user need not waive lawful claims against the responsible seller.

11.3.6. If paid access is not provided, a charge is duplicated or there is a material defect, the user should contact support with the order number. Proper correction is offered first where provided by law, without excluding other remedies. Service-attributable outages are considered when extending access or calculating a refund.

11.3.7. A disciplinary restriction does not itself justify cancellation of all purchases, monetary claims or cybercoins. Consequences for a particular service depend on performance, the reason for termination, proportionality and applicable law. Unrelated claims and mandatory refund rights remain unaffected.

11.3.8. A refund of a verified transaction is accompanied by cancellation of the corresponding unused item or credit to prevent double recovery. Automatic deductions from other funds, arbitrary penalties and allegations of fraud solely for contacting a bank are prohibited.

11.3.9. If the service closes, users must be notified in advance of arrangements for completing paid services, using balances and submitting claims. A change in the rules does not itself discharge outstanding obligations relating to paid rights.

12. Prizes, skins, referrals and special events

12.1. General reward terms

12.1.1. Cash prizes and skins may be offered in different leagues and events; they are not limited to Qualification League. The availability, amount and method of receiving a reward are specified on the season or event card before participation begins.

12.1.2. Event rules must identify the organiser, eligible territories and ages, deadlines and time zone, free and paid admission conditions, winner selection and tie-breaking procedures, prize composition and value, number of recipients, fees and claim and fulfilment deadlines. Terms that disadvantage participants must not be applied retroactively.

12.1.3. A free route into a league does not automatically mean that selling access to a competition with valuable prizes is permitted by law or an application store. Functions are provided only in permissible territories and formats; technical payment availability does not establish that a mechanism is permitted.

12.1.4. Competition prizes, goods exchanged for cybercoins and referral rewards are accounted for separately. Buying cybercoins is not an entry for a cash prize. Buying league access does not create an entitlement to a prize without meeting the published competitive conditions.

12.1.5. The organiser must secure the announced prize pool before the event begins. If the event is cancelled, the reason, refund arrangements for related payments and fulfilment of accrued obligations must be published. Delivery of an announced prize must not depend solely on the organiser's discretion.

12.2. Result verification and cash payments

12.2.1. Results are marked provisional until verification is complete. Results and prize places are verified within 14 calendar days after the event ends. A specific dispute may justify extension to 30 days, with reasons and notice to affected participants.

12.2.2. Participants must provide necessary payment details through the designated secure channel. Requests are limited to information needed to identify the recipient, make the payment and perform mandatory checks. A document request must state its purpose, required data, recipients and retention period. Unrelated information may be concealed unless disclosure is legally required.

12.2.3. Payments to minors are arranged with their legal representative's involvement to the extent required by law. Any stricter event age requirement must be announced before participation, not after a win.

12.2.4. The payment period must be stated before the event and must not exceed 180 calendar days after its official end, except where payment is legally prohibited or there is a documented recipient-caused delay. Administrative verification is included in that period and does not restart it. A shorter stated period takes precedence.

12.2.5. If details are incomplete, the recipient receives a list of missing information and instructions for correction. Performance is suspended only while payment is objectively impossible. Once the cause is resolved, the recipient is notified of the payment date. Indefinite discretionary extensions are prohibited.

12.2.6. Fees or deductions are permitted only where lawful and disclosed before the prize entitlement arises; a calculation must be provided. Participants fulfil their own tax obligations, and the organiser fulfils its applicable accounting and withholding obligations.

12.2.7. Payment to a third party requires verification of authority and legality; this does not prevent a minor's legal representative from acting. Assignment of a claim is governed by applicable law and event terms within lawful limits.

12.2.8. Prohibited tools, match fixing or result falsification may lead to cancellation of the related prize place by a reasoned decision. An unrelated communication offence does not justify an arbitrary payment reduction. Fault must not be presumed for the whole team. Correction of a team result and individual sanctions are assessed separately.

12.2.9. Reallocation of places and prizes following disqualification must be specified before the event. Only the disputed part is withheld pending resolution; undisputed obligations must be fulfilled. Payments made in error or obtained fraudulently are recovered through lawful procedures without unauthorised access to user funds.

12.3. Delivery of in-game skins

12.3.1. Before confirming an exchange, the user receives details of the selected skin, cybercoin price, transfer method, recipient game ID, delivery period and applicable restrictions. Providing an in-game item does not guarantee its resale or a particular market value.

12.3.2. Transfers may use only methods permitted by the Standoff 2 rights holder and applicable law. CF Ranking does not request game account passwords or use account transfers to deliver skins. Use of the game's items does not itself make the rights holder a party to CF Ranking's obligations.

12.3.3. The maximum fulfilment period for a confirmed request is 90 calendar days from submission with the correct game ID. A shorter period stated on the card takes precedence. Requests are registered on submission; initial verification is included in the total fulfilment period.

12.3.4. A recipient error or in-game transfer restriction must be reported with an explanation of the available remedy. If an order cannot be fulfilled, an agreed replacement or cancellation of the exchange and restoration of deducted units is offered. Statutory claims concerning purchased units remain unaffected. Unilateral substitution of a lower-value item is prohibited.

12.3.5. Completion is confirmed by a verifiable transaction or receipt. Users may challenge an incorrect confirmation. An external price change after proper delivery does not itself constitute a defect in the fulfilled order.

12.4. Referrals and free promotions

12.4.1. Before referral programme participation, the required invitee actions, reward amount, restrictions, crediting period and rejection grounds must be published. Registration alone creates no payment entitlement where other published conditions remain unfulfilled.

12.4.2. Self-referrals, fictitious accounts, purchased artificial activity, misleading advertising and spam are prohibited. A single IP address does not prove an offence. Referrers are not responsible for every subsequent offence by an invitee without a proven connection to programme abuse.

12.4.3. A confirmed referral reward is delivered within the programme's stated period and no later than 90 calendar days after the conditions are met and required details supplied. Internal verification is included in that period. Errors and refusals may be appealed under section 10.

12.4.4. A deadline for confirming receipt of a prize, including a 48-hour deadline, applies only if clearly stated in advance and properly notified to the participant. Valid obstacles are considered; missing an internal deadline does not automatically extinguish mandatory consumer rights.

12.4.5. Referral programme changes apply to actions taken after they enter into force. Rights accrued under previous terms are preserved. Publication of a winner's name, photograph or promotional testimonial requires a separate lawful basis and must not be an undisclosed payment condition.

13. Rights, intellectual property and liability

13.1. Users receive a personal right to use available application functions within this Agreement. Rights in CF Ranking's code, design and original materials remain with the respective rights holders. This does not restrict lawful quotation, security research or other statutory exceptions.

13.2. Standoff 2, Apple, Google and other referenced names belong to their respective owners. CF Ranking does not claim an official partnership, endorsement or sponsorship without separate confirmation. The CF Ranking Agreement does not replace the game's own terms of use.

13.3. Users are responsible for the lawfulness of material they upload to the extent of their fault and applicable law. Permission granted to the project is limited to storing, displaying and processing material for the selected function, complaint handling and protection of rights. Separate advertising use outside those purposes requires an independent lawful basis.

13.4. Copyright infringement or unlawful content may be reported through the application or support, identifying the material, grounds and a reply contact. Substantiated reports are handled promptly. The author receives reasons for the measure and an opportunity to object unless notification is legally prohibited.

13.5. The administration maintains service security and functionality, corrects errors and provides support and updates to the extent required by law. Planned maintenance is announced in advance where circumstances permit. Changes to stated essential characteristics of a paid service must comply with statutory conditions and user rights.

13.6. Uninterrupted availability of the third-party game, communications networks and application stores is not guaranteed. This does not exclude CF Ranking's liability for its own breaches or selection of service providers, or restrict mandatory consumer rights. Following an outage, results and periods are restored using available data, with the decision explained to the user.

13.7. Liability for intentional misconduct, gross negligence, death, injury to health or bodily integrity, fraud, an expressly given guarantee and other mandatory cases is not limited. For ordinary negligence in breaching a material contractual obligation, liability may be limited to typical foreseeable loss only to the extent permitted by law.

13.8. This Agreement does not restrict mandatory remedies, personal data rights or access to courts. It does not impose liability for third-party claims irrespective of the user's fault.

13.9. Force majeure is considered only to the extent it actually affects performance. The affected party must notify the other party of the impediment and take reasonable steps to mitigate its consequences. Technical difficulty alone does not discharge a monetary obligation.

13.10. If a provision is invalid, the corresponding statutory rules apply. The remaining provisions remain effective to the extent permitted by law. An invalid term must not be automatically replaced with the term most favourable to the administration.

14. Platform terms

15. Changes, termination and notices

15.1. The current rules are available in the application before registration and in account settings. Users may retain a copy. Material changes are notified with a description and effective date. The general advance notice period is at least 14 days.

15.2. Changes necessary to comply with law, address a security threat or correct an obvious technical error may take effect before the general notice period expires. Their scope is limited to necessary measures, and users are told why urgent implementation is required. New disciplinary grounds do not apply to earlier conduct that was not prohibited when it occurred.

15.3. Changes to paid services, data processing and contractual terms require separate consent where required by law. Silence or continued use is not treated as consent in all cases. Changes affecting user rights must preserve statutory withdrawal and refund options.

15.4. Users may end participation and request account deletion. If a subscription exists, cancellation and account deletion are separate actions. Before deletion, users receive instructions for stopping future charges.

15.5. Administrative termination of access requires stated grounds, user notification and an appeal opportunity, except for permissible urgent security measures. It does not cancel outstanding monetary obligations, statutory refunds, data protection duties or handling of previously submitted requests.

15.6. Legal notices are sent to the Operator using the details in clause 1.1. This Agreement does not impose exclusive jurisdiction that deprives consumers of statutory protection. If a dispute is subject to mandatory out-of-court resolution, or the Operator has agreed to participate, information about the competent body and procedure is provided to the extent required by law.

15.7. Match notifications and decisions are posted in the application. Push notifications are an additional channel and delivery is not guaranteed. Material decisions remain available in a form accessible to the user. An alternative delivery channel is provided where the account is banned.

Appendix A. Game lobby settings

A.1. The table establishes standard lobby settings. The map and number of rounds permitted by the format are specified on the match card before launch. Changes to event format are published in advance. The host must apply the prescribed settings. Unless stated otherwise, the same value applies to both teams.

A.2. Test Pro uses Pro settings. If a Standoff 2 update changes parameter names or availability, the administration publishes the corresponding settings before matches are formed. A technical inability to set an unavailable parameter is not grounds for sanctioning a player.