Procedure for Handling Complaints and Rightsholder Requests
1. Purpose of this document
1.1. This Procedure describes how to send the Company a request concerning an infringement of rights or prohibited content posted on the Millida platform, on shop storefronts, in the market, on the forum, in the rating and on servers hosted on the Company's infrastructure.
1.2. The Company is an information intermediary: it provides the technical means to post materials and does not carry out prior control of them. The Company takes reasonable measures on requests and is not liable for content posted by users, provided that it responds in good time.
2. Who may submit a request
2.1. A rightsholder or a person authorised by them — regarding infringement of exclusive rights and rights to means of individualisation.
2.2. Any person — regarding content that breaches the law or the Platform's Rules.
2.3. A data subject — regarding their data being posted without consent.
2.4. Authorised bodies — under the procedure established by law.
3. Requirements for a request
3.1. A takedown request is sent to support (t.me/MillidaTeamBot) and must contain: — information about the applicant: name or corporate name, contact details for a reply; — the grounds for the request: the particulars of the right (registration, contract, date and circumstances of creation) or a reference to the rule or provision being breached; — the exact address (link) of the disputed material; for a request concerning a game server — its address and a description of the infringement; — a description of the infringement and the measures requested; — confirmation of authority, if the applicant acts on behalf of a rightsholder; — a statement that the information is accurate and that the applicant believes in good faith that the posting is unlawful.
3.2. A request that does not contain the information listed is returned to the applicant with an indication of the deficiencies.
3.3. A knowingly inaccurate request sent in order to harm a competitor is an abuse of rights. The Company may refuse to consider further requests from such an applicant and pass the information to the affected person.
4. Review procedure
4.1. The Company confirms receipt of a request within 3 (three) business days.
4.2. The Company reviews a request within 10 (ten) business days. Where the infringement is obvious, where there is a security threat or upon the demand of an authorised body, access to the material is restricted immediately.
4.3. The Company notifies the User who posted the material of the request and gives them the opportunity to provide explanations within 5 (five) business days, except where notification is prohibited by law.
4.4. Following the review the Company may: restrict access to the material, delete it, restrict access to the account or the server, or refuse the request.
4.5. The applicant and the User are notified of the decision taken.
5. Counter-notice
5.1. A User whose material has been restricted may send a counter-notice with a justification of the lawfulness of the posting and supporting documents within 14 (fourteen) calendar days.
5.2. Where the lawfulness of the posting is confirmed, access to the material is restored.
5.3. Where the disagreement persists, the Company may keep the material restricted until the parties present a court decision that has entered into force.
6. Repeated infringements
6.1. The Company keeps a record of confirmed infringements. Upon systematic infringement of the rights of third parties, the Company ceases to serve the User and may refuse to allow new accounts to be created.
7. Vulnerability reports
7.1. Reports of vulnerabilities in the Company's services are sent to support. The Company asks that information about a vulnerability not be disclosed publicly until it is fixed and that it not be used to access other people's data.
7.2. Where a report is made in good faith, the Company takes no measures against the researcher and considers the possibility of a reward.
Amendments to this document
The Company may amend this document unilaterally. Amendments do not raise the price or shorten the term of a service the User has already paid for: the paid period is rendered at the price and for the term in force at the time of payment.
A new version is published on the website and takes effect 14 (fourteen) calendar days after publication, unless the version itself specifies a later date. Changes driven by legal requirements, decisions of authorised bodies or payment systems, or by the need to remove a security threat take effect immediately upon publication.
Registered Users are notified of material changes in their personal account and (or) at the email address stated in the account. Posting a notice in the platform interface also counts as notification.
A User who disagrees with the new version may, before it takes effect, stop using the relevant service. Any amounts already paid are refunded only in the cases and in the manner set out in the Refund and Chargeback Policy. Continuing to use the service after the new version takes effect means agreeing to it.
All previous versions are retained and available on request from support; rights and obligations that arose earlier are governed by the version in force when they arose.
Final provisions
Governing law. This document and the relations of the parties are governed by the substantive law of the Kyrgyz Republic, without regard to its conflict-of-law rules.
Pre-court claim procedure. Before going to court, a party must send a written claim through support. A claim is reviewed within 10 (ten) business days of receipt. The pre-court claim procedure is mandatory, except for disputes with a consumer User: for them a claim is recommended but is not a precondition for going to court.
Jurisdiction. Failing agreement, the dispute is to be heard by the court at the Company's location. A consumer User may also bring a claim before the court whose jurisdiction is established by consumer protection law, including the court at the User's place of residence.
Evidence. The parties may rely on records of the Company's information systems — operation logs, the ledger of funds movement, message and order history, the document acceptance journal — as evidence. The Company ensures the integrity of these records by recording their time, version and checksum. The User may submit any evidence, including screenshots. Evidence is assessed under the rules of the applicable procedural law.
Language of the contract. The contract is concluded in Russian. Where translations into other languages exist, the Russian text prevails.
Severability. If a particular provision is held invalid or unenforceable, the remaining provisions stay valid; the invalid provision is to be replaced by a valid one closest to it in meaning.
No waiver. The Company's failure to exercise a right does not mean waiving it and does not prevent exercising it later.
Assignment. The Company may transfer its rights and obligations under the contract to an affiliate or a successor upon reorganisation, having notified the User. The User may not transfer its rights under the contract to third parties without the Company's written consent.
Legally significant messages. The parties recognise the legal force of messages sent to the email address stated in the account, through the personal account and through official support channels. The User must keep contact details up to date; the risk of not receiving a message sent to outdated details lies with the User.
Entire agreement. This document, together with the other platform documents, constitutes the entire agreement of the parties on the subject matter and supersedes all prior arrangements.
Survival. The provisions on liability, indemnity, confidentiality, intellectual property, dispute resolution and financial obligations survive termination of the contract.
Company details: Market Link LLC, registration number 303671-3301-OOO, taxpayer number 01605202410603, Russian taxpayer number 9909692242, registered address: Kyrgyz Republic, Bishkek, Sverdlovsky district, 62 Kievskaya street. Support: t.me/MillidaTeamBot.