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

Developer Terms

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.

These Developer Terms (the "Developer Terms") set out the procedure and conditions for access to the Bot API and for the creation and operation of Bots and Mini Apps in the Cordice Service. The Developer Terms form an integral part of the Terms of Service and apply together with them and with the Privacy Policy and the Community Guidelines. Technical documentation is available at developers.cordice.org.

Key points

This summary does not replace the full text; in case of discrepancy, the full text applies.

  • A Bot or Mini App is the Developer's third-party service. The Operator does not create or review it and is not responsible for it; the Developer is fully responsible for it, including Users' data and payments.
  • The Developer collects only the data it needs, publishes its own privacy policy, deletes data on request and does not engage in bulk data collection.
  • A Token is equivalent to a password. Everything done with a Token is deemed done by the Developer.
  • Spam, deception, phishing, impersonating Cordice and circumventing restrictions are prohibited.
  • The Bot API may change at any time with no compatibility obligations. The Operator may disable a Bot and revoke a Token without giving reasons.
  • The Bot API is provided free of charge and "as is".

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. Developer means a User who has created a Bot or Mini App, obtained a Token or otherwise uses the Bot API, and also the person on whose behalf such User acts.

1.4. Bot means a program hosted on the Developer's servers, controlled by the Developer and interacting with the Service through the Bot API under a separate account, including an app created in the developer portal and installed in groups and Spaces.

1.5. Mini App means the Developer's website or web application opened within the Service interface.

1.6. Bot API means the programming interfaces of the Service for Bots and Mini Apps, including the interface compatible with the Telegram Bot API, the app platform interface (REST, WebSocket, events), webhooks, the initData mechanism, the developer portal developers.cordice.org, documentation, code samples and other materials made available by the Operator to Developers.

1.7. Token means a unique access key issued by the Operator for controlling a Bot through the Bot API, and any other credentials issued by the Operator to the Developer.

1.8. User means an individual who uses the Service under the Terms of Service, including one who interacts with a Bot or Mini App.

1.9. User Data means any information relating to Users, including personal data and Content, that a Bot or Mini App receives through the Service or directly from a User.

1.10. Other terms have the meanings given to them in the Terms of Service and the Privacy Policy.

2. Acceptance

2.1. The Developer Terms are a public offer by the Operator. Creating a Bot, obtaining a Token, calling the Bot API, publishing a Mini App or continuing to operate a Bot constitutes the Developer's full and unconditional acceptance of the Developer Terms in the version in force at the time of such action.

2.2. The Developer's electronic actions in the Service (pressing buttons, entering codes, sending requests to the Bot API using a Token) are recognised as a proper expression of the Developer's will. The Operator's records and logs are recognised as proper evidence of the Developer's actions unless proven otherwise.

2.3. If the Developer acts on behalf of a legal entity or another person, the Developer represents that they are authorised to accept the Developer Terms on its behalf; in that case such person is deemed the Developer, and the individual acting for it is jointly liable with it to the Operator to the extent permitted by law.

2.4. The Developer represents that they have the legal capacity required to accept the Developer Terms and are not subject to sanctions or export control restrictions preventing use of the Service.

3. Independent status of the Developer

3.1. Bots and Mini Apps are third-party services. They do not belong to the Operator and are not created, reviewed or endorsed by it unless the Operator expressly states otherwise. The Operator merely provides the technical means for a Bot or Mini App to operate in the Service and is not a party to the relationship between the Developer and Users.

3.2. The Developer participates in the Service solely as an independent party. The Developer Terms do not create any relationship of representation, agency, partnership, joint venture or employment between the Developer and the Operator.

3.3. The Developer may not present itself, its Bot or Mini App as the Operator, its representative or partner, or as a service endorsed by the Operator.

3.4. The Developer is solely and exclusively responsible for the Bot and Mini App, their operation, functionality and security, the Content they send, receive, store and display, and any transactions, payments and obligations towards Users — to the same extent as a User is responsible for their own account.

3.5. The Developer handles Users' enquiries and complaints relating to its Bot or Mini App itself and provides contact details in the Bot's description.

4. Availability

4.1. The Bot API, some of its functions, and individual Bots and Mini Apps may be unavailable to some Developers and Users, in some apps of the Service or in some territories, depending on technical limitations, legal requirements, economic and other factors.

4.2. The availability of the Bot API, Bots and Mini Apps may change at any time. The Operator is not obliged to give advance notice, explain the reasons or pay compensation.

5. Licence, rights and branding

5.1. Subject to the Developer's compliance with the Developer Terms and the Terms of Service, the Operator grants the Developer a limited, revocable, non-exclusive, non-transferable, non-sublicensable, royalty-free licence to use the Bot API solely to create, operate and maintain Bots and Mini Apps running in the Service, for the term of the Developer Terms.

5.2. The Developer owns the rights in the code of its Bot and Mini App and in the Content they publish. The Operator owns all rights in the Service, its code, functionality, the Bot API, protocols, infrastructure, documentation and the Cordice names and marks; rights not expressly granted by clause 5.1 are reserved to the Operator.

5.3. The Developer may not decompile, reverse engineer or otherwise attempt to obtain the source code of the server side of the Service, circumvent technical limitations of the Bot API, or provide third parties with access to the Bot API other than through the Developer's own Bot or Mini App, except where such restrictions are expressly prohibited by law.

5.4. Branding. A Bot and a Mini App must have their own name and design. The trademarks, logos, names and other marks of Cordice, and marks confusingly similar to them, may not be used in the name, description, image, advertising or design of a Bot or Mini App, other than to state that the Bot or Mini App runs in the Service. If, in the Operator's opinion, a Bot or Mini App may be perceived as belonging to or affiliated with the Operator, the Operator may require the design to be changed and apply the measures provided for in section 14.

5.5. The Developer grants the Operator a royalty-free, non-exclusive licence to use the name, image, description and functionality of the Bot and Mini App for their display, distribution and operation in the Service, including the Service's search, catalogues and selections, and to refer to them in materials about the Service, for the period they are available in the Service. Inclusion of a Bot or Mini App in selections and catalogues, and its removal from them, are at the Operator's discretion.

5.6. Where the Operator makes software or tools available under separate licences, including open source licences, the terms of such licences apply to the extent they conflict with the Developer Terms, and only in respect of the relevant software.

5.7. The licence under clause 5.1 terminates automatically when the Developer Terms terminate and may be revoked by the Operator under section 14.

6. User Data

6.1. Data shared. The data that Bots and Mini Apps receive from the Service is set out in section 2.12 of the Privacy Policy. The Developer acknowledges that a Bot in a private chat receives the messages a User sends to it and the User's public profile, and that a Bot added to a group or installed in a Space may receive every message in that group or Space within the rights and event subscriptions granted to it. A Mini App receives from the Service signed launch parameters (initData): the User's identifier, name, @username and language, the type of chat it was opened from, and the start parameter. A Mini App does not receive from the Service the User's phone number, email address, location, or access to the camera and microphone; the clipboard can be read only after the User's permission.

6.2. Additional data. The Developer may request other data from Users only with their knowledge and consent. Misleading Users in order to circumvent the Service's restrictions on access to data is prohibited.

6.3. Privacy policy. If a Bot or Mini App stores any User Data, the Developer must publish its own publicly accessible privacy policy and link to it in the Bot's description. The policy must disclose what data is collected, how and why it is collected, retention periods and how data is deleted. The Developer's policy may not conflict with the Developer Terms and the Service's Privacy Policy. The Operator does not review the Developer's policy and is not responsible for its completeness or observance.

6.4. Retention and deletion. Unless longer retention is required by law, the Developer must delete User Data:

  • at the User's request or when the User deletes the chat with the Bot — within 30 days;
  • when it is no longer necessary for the operation of the Bot or Mini App;
  • when the Bot or Mini App ceases to operate in the Service, except data the User has expressly agreed may be retained, for as long as that consent remains in effect;
  • on a lawful request from an authorised body or at the Operator's request.

6.5. Minimisation and no bulk collection. The Developer collects and processes only the data necessary for the operation of the Bot or Mini App and does not keep group messages unless they are used for the Bot's function. Data voluntarily provided by a User may be used for other purposes only if the User is clearly informed and gives explicit, revocable consent.

6.6. The Developer is prohibited from, including but not limited to:

  • selling, renting or transferring User Data to third parties for advertising or to data brokers;
  • profiling Users from their messages, or linking Cordice accounts with other data without the User's consent;
  • bulk collection of messages, profiles and member lists, including for building datasets and training neural networks;
  • obtaining sign-in codes, passwords, payment details or documents by deception.

6.7. Developer's status regarding data. With respect to User Data, the Developer is an independent operator (controller) of personal data. The Operator does not process such data on the Developer's behalf and is not its processor. The Developer itself determines which personal data laws apply to it, including the laws of the countries where the Users of its Bot are located and, where applicable, Regulation (EU) 2016/679 (GDPR), and itself complies with their requirements: legal bases for processing, consents, data subject requests, cross-border transfers and data localisation.

7. Security and credentials

7.1. A Token is confidential information equivalent to a password and is intended solely for the operation of the Developer's Bot. The Developer must not publish a Token or disclose it to third parties other than its own employees and contractors, for whose actions it is responsible.

7.2. If a Token is leaked or a leak is suspected, the Developer must reissue it immediately using the tools of the Service. The Operator stores a Token only as a hash and cannot recover or re-send it.

7.3. All actions performed using a Token are deemed performed by the Developer, regardless of how the Token came into the possession of the person performing them, unless the Developer proves that the Token was obtained by a third party as a result of a breach by the Operator.

7.4. At a minimum, the Developer must:

  • protect User Data with reasonable organisational and technical measures and operate the Bot and Mini App in a secure environment;
  • accept webhooks only over HTTPS, verify the signature or secret header of incoming requests from the Service, and verify the initData signature in Mini Apps;
  • take into account that data coming from client apps may be forged, and protect the Bot and Mini App against such data;
  • promptly remedy leaks, security incidents and malfunctions that put Users at risk;
  • notify Users of a breach of their data in the manner required by applicable law.

7.5. The Operator is not liable for the consequences of the Developer's failure to meet security requirements, including a leak of User Data held by the Developer.

8. Code of conduct

8.1. The Developer uses the Bot API in good faith and in the interests of Users. The Bot, the Mini App, their name, description and Content must comply with the Terms of Service and the Community Guidelines.

8.2. Content. The Developer is responsible for all Content published by its Bot or Mini App, including moderation of user-generated Content accessible through the Bot or Mini App. The Operator may, but is not obliged to, intervene in the moderation of such Content.

8.3. Bot operation. A Bot:

  • does not message a User first without an action on the User's side (a command, a button press, a subscription) and does not send spam or unsolicited messages;
  • observes the rate limits set by the Operator and does not circumvent them, including by using several Tokens or other persons' Tokens;
  • does not pretend to be a human where this misleads Users;
  • in a group, acts within that group's rules and the rights granted to it by the Space Owner; the Space Owner is responsible for adding the Bot to the Space and for the rights granted to it;
  • uses the rights granted to it (administrator rights and the like) only for the purposes for which they were obtained; the Developer informs Users in advance of any material change to the Bot's functions.

8.4. Prohibited. The Developer may not use a Bot, Mini App or the Bot API for, including but not limited to:

  • violating the law or the rights and legitimate interests of Users and third parties;
  • impersonating (directly or indirectly, including through name and design) Cordice, the Operator, its staff or any other person who has not authorised the Developer to do so;
  • misleading Users about the functions and results of the Bot, in particular: pyramid schemes, artificial inflation of metrics, phishing, asking for passwords and sign-in codes, presenting an illegal product as legal;
  • distributing malware;
  • offering, selling, advertising or facilitating trade in prohibited or specially regulated goods and services, including drugs, weapons, forged documents, and pirated Content;
  • spreading violence, threats, hate speech, harassment, or personal data and images of persons without their consent;
  • circumventing blocks, restrictions, moderation and decisions of the Operator, including by creating new Bots or accounts;
  • automating user accounts ("self-bots") or using unofficial clients to get around restrictions;
  • building services with the Bot API that depart significantly from its intended purpose (for example, using the Service as file storage for an external website);
  • disrupting the Service, creating excessive load, or searching for vulnerabilities without following the Vulnerability Disclosure Policy.

9. Mini Apps

9.1. A Mini App is the Developer's website opened within the Service. A Mini App may not imitate the Service interface, the sign-in screen, system dialogs, or notifications of the Service, the operating system, the browser or third parties.

9.2. The interface elements of a Mini App must work properly (in particular, pop-up windows must be closable) and must not prevent use of the Service.

9.3. Attempts to obtain a User's phone number, email address, location, or access to the camera or microphone by deception are prohibited.

9.4. The Developer is solely responsible for the content, availability and security of the Mini App and for the third-party services it uses.

10. Payments and regulated activities

10.1. As of the date of this version, the Service provides no built-in payment functions for Bots and Mini Apps. The Operator may introduce them in the future; the terms of their use will be published separately and apply from publication.

10.2. If the Developer accepts payment on its own website or through third-party payment systems, the Developer is the seller (provider) and is solely responsible for performing its obligations to Users, for compliance with payment, tax, consumer protection and fiscal requirements, for refunds and support, and for paying taxes.

10.3. The Operator is not a party to such transactions, does not accept or hold funds on behalf of the Developer or Users, does not guarantee performance of obligations and does not handle claims relating to them. Payment disputes are resolved between the User, the Developer and the payment system.

10.4. If a Bot or Mini App is used for giveaways, contests, lotteries, fundraising, selling goods or any other activity subject to special legal requirements, all risks associated with such activity, including fines and other sanctions, are borne by the Developer.

11. Compliance with laws

11.1. The Developer must ensure that the Bot and Mini App, their name, design, Content and functions comply with the laws of the country where the Developer is located and of the countries where they are available, and with the rules of app stores and other third parties applicable to the Developer.

11.2. A Bot or Mini App must not infringe the rights of third parties or enable Users to infringe them.

11.3. The Operator requires compliance with the law but does not verify it and is not liable for violations committed by the Developer.

12. Agreements between the Developer and Users

12.1. The Developer may set its own terms of use for its Bot or Mini App. Such terms apply solely between the Developer and the User; the Operator is not a party to them and bears no obligations or liability under them.

12.2. The Developer's terms may not amend or limit, and may not conflict with, the Developer Terms, the Terms of Service and the Service's Privacy Policy. In case of conflict, the Operator's documents apply.

13. Bot API changes and limits

13.1. The Operator may, at its discretion, set, change and enforce limits on request rates, data volumes, the number of Bots and other technical restrictions. Requests exceeding the limits are rejected by the Service.

13.2. The Operator may at any time and without notice change the Bot API and the ways in which Users find and interact with Bots and Mini Apps, including but not limited to:

  • changing, suspending or discontinuing individual methods and functions or the Bot API as a whole;
  • introducing new functions, rules and restrictions as a result of which a Bot or Mini App stops working or becomes obsolete, including where the Developer has already received payment for it from Users;
  • restricting individual Users' access to the Developer's Bots and Mini Apps.

13.3. The Operator assumes no obligations as to backward compatibility, support periods for earlier versions or advance notice periods. The Operator may, but is not obliged to, announce material changes in advance where possible, at developers.cordice.org or by other means of its choice.

13.4. The Bot API is provided in trial operation (alpha). Failures, unavailability, data loss, and changes to or removal of functions may occur. The Developer is itself responsible for the availability of its Bot and Mini App and their compatibility with the Bot API.

13.5. Updates not retrieved by a Bot are kept by the Service for a limited time and in a limited number (as of the date of this version, up to 24 hours and no more than 10,000 updates per Bot) and are then deleted; an update that could not be delivered to a webhook after several attempts may be deleted. The Operator is not liable for updates lost for these reasons.

14. Measures and termination

14.1. The Operator may, at its discretion, at any time, temporarily or permanently, without prior notice and without giving reasons unless reasons are required by law:

  • restrict, suspend or disable a Bot or Mini App, entirely or for some Users;
  • revoke or cancel a Token;
  • remove a Bot or Mini App from the Service or exclude it from search and catalogues;
  • restrict or block the Developer's account and the Spaces associated with the Bot;
  • revoke the licence granted by clause 5.1.

14.2. Grounds for such measures may include, in particular, breach of the Developer Terms or the Terms of Service, User complaints, a threat to the security of the Service or Users, or requirements of law or public authorities. This list of grounds is not exhaustive.

14.3. The Operator is not obliged to review, monitor or moderate Bots and Mini Apps. Taking measures against one Bot creates no obligation to take them against other Bots.

14.4. Measures under this section are applied without compensation to the Developer for direct or indirect losses. The Developer may appeal a measure via [email protected]; consideration of an appeal does not guarantee that it will be upheld.

14.5. The Developer may stop using the Bot API at any time by deleting its Bots and Mini Apps using the tools of the Service. The Operator may at any time terminate the Developer Terms with respect to a Developer or discontinue the Bot API in whole or in part, including in certain territories or for certain Users. The Operator does not guarantee the continued operation of the Bot API.

14.6. On termination, the Developer must stop using the Bot API and Tokens and fulfil the obligations to delete User Data under clause 6.4.

14.7. Sections 3, 6, 7, 10–12, 15–18, 20 and 21, and other provisions which by their nature should survive, remain in force after termination of the Developer Terms.

15. Disclaimer of warranties

15.1. The Bot API and the Service are provided "as is" and "as available". To the extent permitted by law, the Operator gives no express or implied warranties regarding the Bot API, the data obtained through it, the documentation and client apps, including as to availability, uninterrupted and error-free operation, backward compatibility, fitness for a particular purpose, preservation of data and meeting the Developer's expectations.

15.2. The Operator does not guarantee any revenue, number of Users or continued availability of a Bot or Mini App in the Service.

16. Limitation of liability

16.1. To the extent permitted by law, the Operator is not liable for:

  • indirect losses, lost profits, unrealised payments, or loss of data, Content, goodwill or customers;
  • the consequences of any change, suspension, unavailability or discontinuation of the Bot API;
  • the consequences of measures taken under section 14;
  • the actions of Users when using a Bot or Mini App, including the Content they post, spam and abuse, and the actions of Space Owners and other third parties, including those who have obtained a Token; the Operator is not obliged to monitor or stop such actions;
  • failures of communication networks, third-party services and equipment, attacks and other circumstances beyond the Operator's reasonable control.

16.2. The Bot API is provided free of charge. Accordingly, the Operator's liability to the Developer in connection with the Bot API is excluded to the extent permitted by law. Where the Operator's liability cannot be excluded, its aggregate amount is limited to the sum actually paid by the Developer to the Operator in the 12 months preceding the event giving rise to the claim.

16.3. Nothing in this section limits or excludes the Operator's liability that cannot be limited or excluded by law, including for intentional breach of obligations, or limits the inalienable rights of consumers.

17. Indemnity

17.1. The Developer shall indemnify the Operator, its members, employees and contractors against all losses, fines, penalties and expenses (including legal costs) arising from claims, demands, investigations and proceedings by Users, third parties or public authorities caused by the Developer's Bot or Mini App, their Content, the processing of User Data, payments, or breach of the Developer Terms, the Terms of Service or the law by the Developer, its employees and persons acting on its behalf.

17.2. The Operator may conduct its own defence against such claims; the Developer shall provide the Operator with reasonable assistance. This section supplements the indemnity provisions of the Terms of Service.

18. Force majeure

18.1. The Operator is released from liability for failure to perform or improper performance of obligations caused by force majeure and other circumstances beyond its reasonable control, including natural disasters, power and communication network failures, failures and discontinuation of services of hosting, communication and other providers, attacks on infrastructure, decisions and actions of public authorities, blocking and access restrictions.

19. Changes to the Developer Terms

19.1. The Operator may amend the Developer Terms unilaterally. A new version takes effect on publication unless it states otherwise.

19.2. The Operator may notify Developers of material changes by means of its choice, including at developers.cordice.org. Continued use of the Bot API or operation of a Bot after a new version takes effect constitutes acceptance of it.

20. Relationship between documents and final provisions

20.1. Matters not governed by the Developer Terms are governed by the Terms of Service. In the event of conflict between them regarding Bots, Mini Apps and the Bot API, the Developer Terms prevail. The Operator's documents prevail over the Developer's own terms and policies.

20.2. If any provision of the Developer Terms is held invalid, it applies to the maximum extent permitted by law, and the remaining provisions remain in force.

20.3. Failure by the Operator to exercise any right does not constitute a waiver of it.

20.4. The Developer may not assign rights or transfer obligations under the Developer Terms without the Operator's written consent. The Operator may assign its rights and obligations to a third party.

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

21. Governing law and disputes

21.1. The Developer Terms are governed by the law of the Republic of Uzbekistan.

21.2. A mandatory pre-trial claim procedure applies before going to court. The period for responding to a claim is 30 days from its receipt.

21.3. Disputes not settled through the claim procedure are subject to the court at the Operator's location (Tashkent), unless otherwise required by mandatory provisions of law.

22. Contact

22.1. Bot API questions: [email protected]. Vulnerability reports: [email protected], under the Vulnerability Disclosure Policy.