User Agreement — LEGACY privilege terms

User AgreementLast updated 17.07.2026

This is an informational translation. The authoritative version is in Russian and is governed by the laws of the Russian Federation.

Terms of the Agreement

1.1. This Agreement is an integral part of the public offer of the LEGACY project (https://legacy.sx/oferta) and supplements it with respect to the privileges listed in the title.
1.2. Capitalised terms not defined herein shall have the meanings established by the offer: the Contractor, the Customer, the Project, the Website, the Catalogue, the Account, the Steam Identifier, LC, the Digital Feature, the Project Rules.
1.3. By activating any of the privileges named in the title, the Customer confirms that they have read and unconditionally accept the terms of this Agreement, the public offer and the Project Rules.
1.4. In matters not governed by this Agreement, the terms of the offer shall apply. In the event of a discrepancy between this Agreement and the offer on matters expressly described herein, this Agreement shall prevail.

Definition of a Privilege

2.1. A privilege (MODER, ADMIN, MASTER, PLATINUM, TITAN) is a Digital Feature that expands the set of actions available to the Customer on the game servers of the Project, including actions affecting the gameplay of other Customers.
2.2. The scope of functions of each privilege, its term and its price are determined by the description in the Catalogue as of the moment of activation. The Customer reviews the description prior to payment (clause 4.7 of the offer).
2.3. A privilege is bound to the Customer’s Steam Identifier, may not be transferred to another person and may not be moved to another Identifier.
2.4. Privileges are ranked by the increasing scope of available functions in the following order: MODER, ADMIN, MASTER, PLATINUM, TITAN. A privilege is deemed higher in relation to any privilege listed before it and lower in relation to any privilege listed after it.
2.5. The ranking of privileges established by clause 2.4 determines only the scope of functions and the procedure for their application among Customers (clause 5.2). It does not create any relationship of subordination between Customers, does not give rise to any obligations of one Customer towards another and does not affect the scope of the Customer’s rights under the offer.
2.6. Holding a privilege does not exempt the Customer from the Project Rules and the offer, does not grant any advantage in the resolution of disputes and does not protect against the measures provided for in Section 6.

What a Privilege Does Not Include

3.1. The activation of a privilege does not create an employment relationship between the Parties, does not constitute hiring or appointment to a position and does not give rise to any official duties of the Customer towards the Contractor.
3.2. The Contractor does not assign any work or services to the Customer, does not give them tasks, does not establish working or rest hours for them, does not supervise their activity and does not pay them anything.
3.3. The Customer uses the privilege at their own discretion and in their own interest. They are not obliged to be present on the Project servers, to monitor the conduct of other Customers, to react to their violations or to apply any measures to them. The Customer’s inaction does not in itself constitute a breach of this Agreement.
3.4. The conditions of Section 4 are the conditions on which the Customer retains the privilege, and not obligations the performance of which the Contractor is entitled to demand. The sole consequence of their non-observance is the measures set out in Section 6 in relation to the privilege itself and to access to the Project.
3.5. This Section reflects the true intent of the Parties. The Parties proceed on the basis that their relationship is limited to the Contractor’s provision of a paid service for the activation of a Digital Feature.

Conditions for Retaining a Privilege

4.1. The Customer retains the privilege for as long as they use it in accordance with the following conditions.
4.2. When applying to another Customer a measure that affects their gameplay, the Customer states a truthful reason and does not misrepresent the circumstances of what occurred.
4.3. The reason for the measure applied or for a summons to a check is communicated to the person concerned by voice in the in-game chat.
4.4. Only the software tools published by the Contractor on the Website are used for checks. Third-party tools are not used.
4.5. The Customer is a member of the official Discord server of the Project, and their display name in Discord matches their in-game name.
4.6. The Customer responds within 24 (twenty-four) hours to a request from the Project Staff made in connection with the use of the privilege. The Contractor is entitled to treat the absence of a response as a refusal to provide explanations and to resolve the matter on the basis of the information available.
4.7. The Project Staff are the persons engaged by the Contractor to ensure the operation of the Project and to resolve disputes. The composition of the Staff is determined by the Contractor.

Prohibited Use of Privileges

5.1. Using the functions of a privilege for entertainment, out of personal animosity or without a reason provided for by the Project Rules.
5.2. Applying measures to a Customer holding a privilege of the same or a higher level than that of the person applying them (clause 2.4). Measures are applied to a Customer with a lower-level privilege on the general grounds provided for by the Project Rules.
5.3. Publicly discussing the actions of other privilege holders otherwise than in the manner established by the Project Rules.
5.4. Disclosing information obtained in connection with the use of a privilege, including information about other Customers and about the Project Staff.
5.5. Using additional Accounts for actions performed by means of a privilege.
5.6. Transferring a privilege, access to it or any related credentials to another person, as well as any attempt at such a transfer.

Measures

6.1. In the event of non-observance of the conditions of Section 4 or the commission of the acts listed in Section 5, the Contractor is entitled to apply any of the following measures proportionate to the circumstances:
— a warning;
— temporary deactivation of the privilege;
— permanent deactivation of the privilege without refund of amounts paid;
— restriction of access to the Project and inclusion in the list of persons permanently denied access (clause 10.7 of the offer).
6.2. The choice of measure belongs to the Contractor. The prior application of a more lenient measure does not deprive the Contractor of the right to apply a stricter one in the event of a repeated occurrence.
6.3. The grounds for inclusion in the list of persons permanently denied access to the Project are established by clause 10.7 of the offer. The following additionally serve as such grounds:
— the deliberate mass application of measures to other Customers without grounds;
— fraudulent acts committed using a privilege;
— the transfer of a privilege to a third party or an attempt at such a transfer;
— systematically provoking conflicts and treating other Customers abusively.
6.4. The Customer’s admission of the circumstances of a violation is taken into account by the Contractor along with other information. It does not replace the verification of such information if the Contractor has grounds to doubt the reliability of the admission.
6.5. The procedure for lifting a permanent restriction is determined by clause 10.8 of the offer.

Refund Rules

7.1. Deactivation of a privilege on the grounds set out in Section 6 does not entail a refund of amounts paid, including where the paid term has not yet expired.
7.2. The Parties have agreed to regard non-observance of the conditions of Section 4 and the commission of the acts listed in Section 5 as a material breach of the terms of the contract by the Customer.
7.3. The refund procedure in all other cases is established by Section 8 of the offer and is not altered by this Agreement.
7.4. Any change by the Contractor to the set of functions of a privilege or to its price does not apply to a privilege already activated by the Customer until the end of the paid term.

Disputes, Amendments, Miscellaneous

8.1. Disputes arising out of this Agreement are resolved in the manner established by Section 15 of the offer.
8.2. The Contractor is entitled to amend this Agreement unilaterally. The new version is published on the Website with an indication of its date and comes into force no earlier than 7 (seven) calendar days after publication. Continued use of the privilege after the amendments come into force constitutes consent to the new version.
8.3. The invalidity of an individual provision of this Agreement does not affect the validity of the remaining provisions.
8.4. Legally significant correspondence is conducted by email: support@legacy.sx.
8.5. Details of the Contractor:
Individual entrepreneur Arseniy Alekseevich Bardachev
INN: 616620944595
OGRNIP: 326619600168508
Website: https://legacy.sx
Email: support@legacy.sx

Terms of the Agreement

1.1. This Agreement is an integral part of the public offer of the LEGACY project (https://legacy.sx/oferta) and supplements it with respect to the privileges listed in the title.

1.2. Capitalised terms not defined herein shall have the meanings established by the offer: the Contractor, the Customer, the Project, the Website, the Catalogue, the Account, the Steam Identifier, LC, the Digital Feature, the Project Rules.

1.3. By activating any of the privileges named in the title, the Customer confirms that they have read and unconditionally accept the terms of this Agreement, the public offer and the Project Rules.

1.4. In matters not governed by this Agreement, the terms of the offer shall apply. In the event of a discrepancy between this Agreement and the offer on matters expressly described herein, this Agreement shall prevail.

Definition of a Privilege

2.1. A privilege (MODER, ADMIN, MASTER, PLATINUM, TITAN) is a Digital Feature that expands the set of actions available to the Customer on the game servers of the Project, including actions affecting the gameplay of other Customers.

2.2. The scope of functions of each privilege, its term and its price are determined by the description in the Catalogue as of the moment of activation. The Customer reviews the description prior to payment (clause 4.7 of the offer).

2.3. A privilege is bound to the Customer’s Steam Identifier, may not be transferred to another person and may not be moved to another Identifier.

2.4. Privileges are ranked by the increasing scope of available functions in the following order: MODER, ADMIN, MASTER, PLATINUM, TITAN. A privilege is deemed higher in relation to any privilege listed before it and lower in relation to any privilege listed after it.

2.5. The ranking of privileges established by clause 2.4 determines only the scope of functions and the procedure for their application among Customers (clause 5.2). It does not create any relationship of subordination between Customers, does not give rise to any obligations of one Customer towards another and does not affect the scope of the Customer’s rights under the offer.

2.6. Holding a privilege does not exempt the Customer from the Project Rules and the offer, does not grant any advantage in the resolution of disputes and does not protect against the measures provided for in Section 6.

What a Privilege Does Not Include

3.1. The activation of a privilege does not create an employment relationship between the Parties, does not constitute hiring or appointment to a position and does not give rise to any official duties of the Customer towards the Contractor.

3.2. The Contractor does not assign any work or services to the Customer, does not give them tasks, does not establish working or rest hours for them, does not supervise their activity and does not pay them anything.

3.3. The Customer uses the privilege at their own discretion and in their own interest. They are not obliged to be present on the Project servers, to monitor the conduct of other Customers, to react to their violations or to apply any measures to them. The Customer’s inaction does not in itself constitute a breach of this Agreement.

3.4. The conditions of Section 4 are the conditions on which the Customer retains the privilege, and not obligations the performance of which the Contractor is entitled to demand. The sole consequence of their non-observance is the measures set out in Section 6 in relation to the privilege itself and to access to the Project.

3.5. This Section reflects the true intent of the Parties. The Parties proceed on the basis that their relationship is limited to the Contractor’s provision of a paid service for the activation of a Digital Feature.

Conditions for Retaining a Privilege

4.1. The Customer retains the privilege for as long as they use it in accordance with the following conditions.

4.2. When applying to another Customer a measure that affects their gameplay, the Customer states a truthful reason and does not misrepresent the circumstances of what occurred.

4.3. The reason for the measure applied or for a summons to a check is communicated to the person concerned by voice in the in-game chat.

4.4. Only the software tools published by the Contractor on the Website are used for checks. Third-party tools are not used.

4.5. The Customer is a member of the official Discord server of the Project, and their display name in Discord matches their in-game name.

4.6. The Customer responds within 24 (twenty-four) hours to a request from the Project Staff made in connection with the use of the privilege. The Contractor is entitled to treat the absence of a response as a refusal to provide explanations and to resolve the matter on the basis of the information available.

4.7. The Project Staff are the persons engaged by the Contractor to ensure the operation of the Project and to resolve disputes. The composition of the Staff is determined by the Contractor.

Prohibited Use of Privileges

5.1. Using the functions of a privilege for entertainment, out of personal animosity or without a reason provided for by the Project Rules.

5.2. Applying measures to a Customer holding a privilege of the same or a higher level than that of the person applying them (clause 2.4). Measures are applied to a Customer with a lower-level privilege on the general grounds provided for by the Project Rules.

5.3. Publicly discussing the actions of other privilege holders otherwise than in the manner established by the Project Rules.

5.4. Disclosing information obtained in connection with the use of a privilege, including information about other Customers and about the Project Staff.

5.5. Using additional Accounts for actions performed by means of a privilege.

5.6. Transferring a privilege, access to it or any related credentials to another person, as well as any attempt at such a transfer.

Measures

6.1. In the event of non-observance of the conditions of Section 4 or the commission of the acts listed in Section 5, the Contractor is entitled to apply any of the following measures proportionate to the circumstances:
— a warning;
— temporary deactivation of the privilege;
— permanent deactivation of the privilege without refund of amounts paid;
— restriction of access to the Project and inclusion in the list of persons permanently denied access (clause 10.7 of the offer).

6.2. The choice of measure belongs to the Contractor. The prior application of a more lenient measure does not deprive the Contractor of the right to apply a stricter one in the event of a repeated occurrence.

6.3. The grounds for inclusion in the list of persons permanently denied access to the Project are established by clause 10.7 of the offer. The following additionally serve as such grounds:
— the deliberate mass application of measures to other Customers without grounds;
— fraudulent acts committed using a privilege;
— the transfer of a privilege to a third party or an attempt at such a transfer;
— systematically provoking conflicts and treating other Customers abusively.

6.4. The Customer’s admission of the circumstances of a violation is taken into account by the Contractor along with other information. It does not replace the verification of such information if the Contractor has grounds to doubt the reliability of the admission.

6.5. The procedure for lifting a permanent restriction is determined by clause 10.8 of the offer.

Refund Rules

7.1. Deactivation of a privilege on the grounds set out in Section 6 does not entail a refund of amounts paid, including where the paid term has not yet expired.

7.2. The Parties have agreed to regard non-observance of the conditions of Section 4 and the commission of the acts listed in Section 5 as a material breach of the terms of the contract by the Customer.

7.3. The refund procedure in all other cases is established by Section 8 of the offer and is not altered by this Agreement.

7.4. Any change by the Contractor to the set of functions of a privilege or to its price does not apply to a privilege already activated by the Customer until the end of the paid term.

Disputes, Amendments, Miscellaneous

8.1. Disputes arising out of this Agreement are resolved in the manner established by Section 15 of the offer.

8.2. The Contractor is entitled to amend this Agreement unilaterally. The new version is published on the Website with an indication of its date and comes into force no earlier than 7 (seven) calendar days after publication. Continued use of the privilege after the amendments come into force constitutes consent to the new version.

8.3. The invalidity of an individual provision of this Agreement does not affect the validity of the remaining provisions.

8.4. Legally significant correspondence is conducted by email: support@legacy.sx.

8.5. Details of the Contractor:
Individual entrepreneur Arseniy Alekseevich Bardachev
INN: 616620944595
OGRNIP: 326619600168508
Website: https://legacy.sx
Email: support@legacy.sx