Legal

Terms of Use

Access conditions, rules of conduct and enforcement measures. They apply to every account without exception.

Last updated: 23.08.2026

These Terms set out how the Rockstar client may be used, how you interact with the administration and support, and which violations lead to which measures. Acceptance of these Terms is a condition of access: registering an account, paying for a subscription or launching the client means you have read the Terms, understood them and accepted them in full. If you disagree with any provision, do not use the client and do not pay for a subscription.

1. General provisions

1.1. These Terms govern the relationship between the administration of the Rockstar project (the “Administration”) and any user who has obtained or requested access to the client (the “User”).

1.2. The Terms apply regardless of how the subscription was purchased (the website, the RollyPay payment system, the FunPay marketplace), the selected plan, the subscription length and how long the account has existed.

1.3. The Terms supplement the License Agreement and the Public Offer. Conduct and discipline are governed by these Terms, payment and provisioning of access by the Public Offer, and the scope of software rights by the License Agreement.

1.4. Being unaware of the Terms, or not having actually read them, does not release the User from responsibility for breaching them.

1.5. The Terms apply to all project resources: the website, the account area, the support service and the official communities.

2. Account and access

2.1. One User corresponds to one account. Registering additional accounts to circumvent restrictions, bans or promotional conditions is prohibited.

2.2. Accounts and subscriptions are non-transferable. Selling, renting, exchanging, gifting and sharing an account is prohibited.

2.3. The User is solely responsible for keeping their login, password and linked email secure. Any action taken through the account is deemed an action of its owner.

2.4. Access may be bound to the User's hardware (HWID). Resetting the binding is performed by support and is limited in number and frequency.

2.5. The User must report any account compromise to support immediately. A report submitted after a violation has been committed from the account does not remove responsibility for that violation.

2.6. The Administration may request proof of account ownership (payment details, the linked email, support history) and may decline any account operation until such proof is provided.

2.7. Losing control of an account is not a ground for lifting the measures applied: the owner remains responsible for actions taken through the account.

3. Subscription and its term

3.1. A subscription is activated the moment payment is confirmed and runs continuously until the paid term expires.

3.2. The term is counted in calendar days and does not depend on whether the User actually used the client. Unused days are not carried over, paused or compensated.

3.3. If a purchase is made while a subscription is active, the new term is added to the current expiry date.

3.4. Scheduled maintenance, releasing updates, adapting the client after game updates and short-term unavailability of individual features do not automatically extend the subscription term.

3.5. In the event of prolonged downtime caused solely by us, the Administration may grant compensation in the form of an extension of the subscription term. Its form, amount and the fact of granting it are determined by the Administration; no monetary refund is issued in this case.

3.6. Freezing, transferring and splitting a subscription between accounts is not available.

4. Refunds

4.1. The client is a digital product. Access is granted immediately after payment is confirmed, therefore the service is deemed rendered at the moment access is provided.

4.2. No refund is issued if the client has been successfully launched on the User's account at least once. This applies regardless of how long it was used, how much of the subscription term remains, the reason for the request and the payment method.

4.3. The launch is evidenced by the licensing system's service records: the license issuance event, the account identifier, the hardware identifier and the time of launch. Such records are treated as sufficient and final proof.

4.4. Before the first successful launch, a refund request is reviewed individually. A refund is possible where access cannot be provided for reasons attributable solely to us and the problem is not resolved within a reasonable time.

4.5. No refund is issued where the account is banned for breaching the Terms, or where access is terminated by decision of the Administration due to the User's bad faith.

4.6. Choosing the wrong plan, buying by mistake, changing plans and losing interest in the product are not grounds for a refund.

4.7. Purchases made through the FunPay marketplace are additionally governed by that marketplace's rules. Opening a dispute there does not create a right to a refund beyond this section.

4.8. Attempting to obtain a refund by reversing the payment (chargeback) while access has in fact been provided is treated as bad faith and results in a permanent ban of all linked accounts.

5. Client protection and prohibited technical actions

5.1. The client contains technical measures protecting it against analysis, copying and tampering. Studying, circumventing, disabling and substituting them is prohibited.

5.2. The following are prohibited in particular: disassembly, decompilation, debugging, memory dumping, unpacking, patching and modifying client and loader files, intercepting and substituting network traffic and certificates, emulating the license server, and extracting keys and access tokens.

5.3. Submitting the client, its files, memory dumps, logs or any extracted code fragments to automated analysis systems is prohibited, including neural-network services, cloud reverse-engineering platforms, public sandboxes and mass-scanning services.

5.4. The protection measures record such attempts and send the Administration a technical report: the event type, the name and digital signature of the third-party process or module, the time of the event, the account identifier and the hardware identifier. The report is used solely to protect the product and to decide on access.

5.5. The protection measures operate within the boundaries of the client's own process and are observational and self-defensive in nature. They cause no grave or other harm to the User's computer: they do not damage, delete or encrypt the User's files, do not alter system settings, the registry or the bootloader, do not affect hardware or its firmware, do not install third-party software and do not persist in the system after the client exits.

5.6. The protection measures do not collect personal files, private messages, browser history, credentials for third-party services or any data unrelated to the client's operation and license protection.

5.7. A confirmed tampering attempt results in immediate termination of access with no refund. Repeated, organized or commercial attempts result in a permanent ban of all linked accounts.

5.8. This section also applies to unsuccessful attempts: responsibility arises from the act of tampering itself.

6. Distribution of client files

6.1. Publishing, forwarding, uploading for public access, selling or otherwise transferring client and loader files, keys and access tokens, or configurations containing license data, is prohibited.

6.2. Granting third parties access to your account is prohibited, including through shared sessions, remote desktop control and streaming the authorization process.

6.3. An account from which files were distributed is banned permanently. This applies both to deliberate transfer and to a leak through a compromised account, pursuant to clause 2.3 of these Terms.

6.4. Funds for the unused subscription term are not refunded where an account is banned under this section.

6.5. The Administration may demand removal of published material, approach the hosting platforms and use the recorded technical data to identify the source of the leak.

6.6. Publishing screenshots, video recordings and descriptions of how the client works is not distribution of files and is not restricted by this section, provided that no files, keys or protection-bypass methods are disclosed.

7. Operability and compatibility

7.1. The client is provided “as is”. We do not guarantee that it will work on an arbitrary hardware configuration, any operating system version, any game build, or alongside arbitrary third-party software.

7.2. Compatibility with anti-cheat systems, antivirus products, security and virtualization tools is not guaranteed, nor is stable operation on modified or non-standard systems.

7.3. Feature descriptions reflect the client's capabilities and are not an undertaking that the User will achieve any particular in-game result.

7.4. Inability to launch or use the client for reasons on the User's side (hardware, operating system, third-party software, network restrictions, actions of third-party services) is not a ground for a refund or for extending or transferring a subscription.

7.5. Support assists with diagnostics within reasonable limits but is not obliged to make the client operable on any given configuration.

7.6. The User bears the risks associated with using the client in third-party games and services, including any restrictions imposed by their administrators.

8. Communication and treatment of the team

8.1. Threats against the life, health, property or reputation of project staff — administrators, developers, moderators and support agents — or of their families are prohibited.

8.2. Insults, degrading treatment, harassment, discrimination on any ground and persistent provocative behaviour towards staff and other Users are prohibited.

8.3. Blackmail, extortion, pressure applied through third-party platforms, collecting and publishing staff members' personal data, and knowingly unfounded complaints to payment services, regulators and platform owners intended to harm the project are prohibited.

8.4. Flooding, spam, advertising third-party projects and mass messaging in project channels and in support requests are prohibited.

8.5. Demanding a response by way of pressure, threats or ultimatums is a breach of this section regardless of the merits of the request.

8.6. Breach of this section results in an account ban without prior warning, without a refund and without any right to have access restored.

9. Criticism and feedback

9.1. The User is entitled to criticize the client, its features, quality, price, updates and level of support openly. A negative assessment is not in itself a breach of the Terms.

9.2. Criticism is protected by these Terms provided it is objective and truthful: based on facts, drawn from actual use and, on request, capable of being substantiated (client version, time, description of the situation, a screenshot or recording).

9.3. The following constitute a breach and enjoy no protection: knowingly false statements, invented accusations, forged correspondence and evidence, attributing to the client actions it does not perform (including claims of damage to a computer, theft of payment data, mining or malicious code), and spreading such claims in order to damage the project's reputation.

9.4. The manner matters: blunt but substantive assessment is acceptable; personal attacks and insults directed at staff are dealt with under section 8 of these Terms.

9.5. The Administration does not impose restrictions for a negative review as such, does not condition support on its removal and does not require a change of rating in exchange for service.

9.6. The Administration may respond publicly to public criticism, including by presenting technical data refuting the statements made, to the extent that this does not disclose the User's personal data.

10. Support service

10.1. Support operates through requests submitted in the account area and the official project channels. Other means of contact are not official and answers obtained through them have no effect.

10.2. Support is not obliged to answer instantly. Requests are handled in order of receipt and according to complexity; the indicative response time is up to 24 hours, and up to 72 hours during periods of high load, game updates and new build releases.

10.3. The absence of an instant reply is not a refusal of service, a breach of obligations, or a ground for a refund, subscription extension or compensation.

10.4. Duplicate requests, demands for an “immediate” answer and pressure on staff slow down processing and may result in restricted access to support.

10.5. The User must provide accurate information and supply the details requested. Requests lacking the necessary information, and requests the User leaves unanswered, may be closed.

10.6. Support may decline to advise on matters beyond the client's operation: configuring third-party software, circumventing third-party service restrictions, recovering third parties' accounts, and questions whose answer would reveal the product's protection methods.

10.7. Support replies are informational and do not alter these Terms, the License Agreement or the Public Offer.

11. Enforcement and decisions of the Administration

11.1. For a breach of the Terms the Administration may apply one or more measures: a warning, restricted access to support and project channels, suspension of the subscription, revocation of the subscription, an account ban, refusal of further service and refusal to accept further payments.

11.2. The Administration may revoke a subscription or suspend or terminate access to the client at its own discretion, where it considers this necessary, without prior notice and without stating a reason.

11.3. Such a decision may be based on, among other things, suspicion of a breach, a risk to the security of the product or other Users, indications of fraud, bad faith, and circumstances making further service undesirable. The Administration is not obliged to disclose the sources, details or criteria of the decision, as that would reveal the product's protection methods.

11.4. A decision to apply measures is final. An appeal is possible only through the support service; the Administration is not obliged to reconsider the decision, to correspond about it or to provide evidence.

11.5. Measures applied in connection with a breach of the Terms are not accompanied by a refund or compensation for the unused subscription term.

11.6. Where access is terminated at the Administration's initiative in the absence of any breach by the User, the Administration may grant compensation for the unused term; its form and amount are determined by the Administration.

11.7. Attempts to circumvent imposed measures — registering new accounts, changing hardware and identifiers, buying access through intermediaries and third parties — constitute a separate breach and result in a ban of all linked accounts.

11.8. The severity of a measure is determined by the Administration in light of the nature of the breach; applying a lighter measure in one case creates no obligation to apply it in others.

12. Amendments to the Terms

12.1. The Administration may amend these Terms unilaterally.

12.2. The current revision is published on the website and takes effect upon publication unless the revision itself states another date.

12.3. Continued use of the account and the client after a new revision is published constitutes the User's acceptance of it.

12.4. The date of the effective revision is stated at the beginning of the document. Keeping track of changes is the User's responsibility.