Cordice
Open Cordice (opens in a new tab)
← All legal documents

Vulnerability Disclosure Policy

Last updated: [PUBLICATION DATE]

Русская версия (имеет юридическую силу)

This is an English translation provided for convenience. The Russian and Uzbek versions are equally authoritative; the English version has no legal force.

This Vulnerability Disclosure Policy (the "Policy") sets out the procedure for reporting vulnerabilities in the Cordice Service to the Operator and the conditions under which security research on the Service is permitted. The Policy applies together with the Terms of Service. Any security research on the Service not conducted in accordance with the Policy is prohibited by the Terms of Service.

1. Terms and definitions

1.1. Operator means CORDICE LLC ("CORDICE" MChJ, OOO "CORDICE"), Republic of Uzbekistan, Tashkent, taxpayer ID (STIR) [STIR], registered address: [ADDRESS].

1.2. Service means the Cordice software system, including the web version, the mobile and desktop apps, the server side, the Bot API and the Operator's websites.

1.3. Researcher means a person conducting security research on the Service and/or sending a Report to the Operator.

1.4. Vulnerability means a flaw in the Service that allows the confidentiality, integrity or availability of the Service or of Users' data to be compromised.

1.5. Report means information about a Vulnerability sent by a Researcher to the Operator under section 3.

1.6. User means an individual who uses the Service under the Terms of Service.

2. General provisions

2.1. A Researcher who discovers a Vulnerability must report it to the Operator and must not exploit it.

2.2. Conducting research within the Policy or sending a Report constitutes the Researcher's acceptance of the Policy.

2.3. The Policy grants the Researcher no rights in respect of the Service other than those expressly provided in it, creates no employment, contractor or other contractual relationship between the Operator and the Researcher, and gives rise to no obligations of the Operator other than those expressly stated in it.

2.4. The Researcher is solely responsible for complying with the laws of the country where they are located and any other applicable law. The Policy is not a permission to perform actions prohibited by law.

3. How to send a Report

3.1. Reports are sent to [email protected]. The address is also listed in /.well-known/security.txt (RFC 9116).

3.2. A Report must contain a description of the Vulnerability, the steps to reproduce it, the addresses and apps affected, the version and the possible impact.

3.3. The Researcher may not make the disclosure of Vulnerability details, or refraining from publishing them, conditional on payment of a reward or any other consideration. Such conduct falls outside the Policy.

4. Scope

4.1. The following are within the scope of the Policy:

  • the Cordice apps (web, Android, iOS, desktop);
  • the hosts app.cordice.org, api.cordice.org, gw.cordice.org, crdc.xyz, u.cordice.online;
  • the Bot API and the Service side of Mini Apps.

4.2. The following are outside the scope of the Policy and may not be tested:

  • third-party services, including Cloudflare, LiveKit, Resend, Google and Apple — they have their own programmes;
  • neighbouring services hosted on the same hosting;
  • admin.cordice.org (the Operator's internal staff panel) — without the Operator's prior written permission;
  • third-party developers' Bots and Mini Apps on their side;
  • any other hosts and services not listed in clause 4.1.

5. Rules for permitted testing

5.1. Research is permitted only to the minimum extent necessary to confirm the existence of a Vulnerability.

5.2. For testing, the Researcher uses only their own accounts or accounts whose owners have given explicit consent.

5.3. If during research the Researcher gains access to other Users' data, they must immediately stop the relevant actions, must not store, copy or share such data, and must inform the Operator of this in the Report.

6. Prohibited actions

6.1. The Researcher may not:

  • access other people's accounts and data;
  • change or delete other people's data;
  • disrupt the Service, including by denial-of-service attacks, mass requests or spam;
  • use social engineering against Users or the Operator's employees and contractors;
  • physically interfere with hardware;
  • attack the targets listed in clause 4.2;
  • disclose Vulnerability details in breach of section 7.

7. Confidentiality

7.1. The Researcher may publish or otherwise disclose Vulnerability details to third parties once the Operator has fixed the Vulnerability or once 90 (ninety) days have passed since the Operator acknowledged receipt of the Report (clause 8.1), whichever occurs first.

7.2. If fixing the Vulnerability requires more time, the period set out in clause 7.1 may be extended by agreement between the Operator and the Researcher made in writing (including by email).

7.3. Disclosure of Vulnerability details before the Vulnerability is fixed and before the period set out in clause 7.1 has expired (taking into account any extension under clause 7.2) is permitted only with the Operator's written consent (including by email) and to the extent agreed with it.

7.4. The Researcher notifies the Operator of the publication date by sending a notice to [email protected] no later than 7 (seven) days before that date.

7.5. The Researcher may ask the Operator to confirm that the Vulnerability has been fixed or to consent to its disclosure by sending a request to [email protected]. Absence of a reply does not constitute consent to disclosure before the period set out in clause 7.1 has expired.

7.6. A publication of Vulnerability details must under no circumstances contain Users' data obtained during the research.

8. Actions of the Operator

8.1. The Operator acknowledges receipt of a Report within 3 working days.

8.2. The assessment of a Vulnerability and its severity, and the timing and method of fixing it, are determined by the Operator at its discretion. The Operator informs the Researcher of progress on the fix to the extent and in the manner determined by the Operator.

8.3. With the Researcher's consent, the Operator may, but is not obliged to, credit the Researcher in its acknowledgements.

8.4. Information contained in a Report may be used by the Operator without restriction and without payment of any reward to fix the Vulnerability and ensure the security of the Service.

9. Safe harbour

9.1. In respect of research conducted in good faith and in strict compliance with all provisions of the Policy, the Operator undertakes not to bring legal action against the Researcher and not to file complaints with public authorities, except where such a filing is mandatory for the Operator by law.

9.2. Clause 9.1 does not apply if the Researcher breaches any provision of the Policy.

9.3. The Policy does not bind third parties. The Operator does not guarantee that third parties, including Users, the Operator's contractors and the owners of the targets listed in clause 4.2, will not bring claims against the Researcher, and is not liable for such claims.

10. Rewards

10.1. As of the date of this version, no monetary reward for Reports is offered.

10.2. The Operator assumes no obligation to pay any reward. Any reward may be granted solely at the Operator's discretion and creates no obligation to grant one in future or to other persons.

11. Liability

11.1. The Researcher is solely responsible for their actions and their consequences, including actions outside the scope of the Policy.

11.2. To the extent permitted by law, the Operator is not liable for any losses of the Researcher connected with the research or with sending a Report. This provision does not limit the Operator's liability that cannot be limited by law, including for intentional breach.

12. Changes to the Policy

12.1. The Operator may amend the Policy unilaterally. A new version takes effect on publication unless it states otherwise and applies to research conducted after its publication.

13. Governing law

13.1. The Policy is governed by the law of the Republic of Uzbekistan. Disputes are resolved in the manner provided by the Terms of Service.

13.2. The Policy is drawn up in Russian and Uzbek; both versions are equally authoritative. The English version is a translation for convenience.

14. Contact

14.1. Vulnerability reports: [email protected].