Version dated 16 September 2026. These Terms supplement the Public Offer and Licence Agreement, the Acceptable Use Rules, the Privacy Policy, and the Model and Route Terms Registry.
1. When Feature Terms apply
1.1. A section of this page applies only to a feature that is actually enabled for the User in the interface, API documentation, or confirmed Order. Mentioning beta, an agent, connector, fine-tuning, publishing, voice, video, marketplace, cloud platform, medical use case, or another capability does not mean it is already available, certified, included in the Plan, or promised by Cicora.
1.2. Before first use of a specific feature, its product or Route card must show its purpose, required Input Materials, material data terms, available controls, known limits, usage-measurement method, and applicable Model rules. In case of conflict, Feature Terms govern that feature, but do not override mandatory law, a confirmed Order, or RIZZ TRADE’s duty to perform its own service.
1.3. A third-party Model, tool, or feature name does not transfer to the User a provider account, key, cloud product, certification, SLA, data residency, zero-data-retention, or commercial right of the provider unless it is expressly offered and confirmed for the selected Route.
1.4. Where the interface allows feedback, an Output rating, or an error report, that is voluntary. Cicora may use the feedback itself and context the User consciously attaches to it to fix an error, assess safety, or improve the relevant feature in accordance with the Privacy Policy. Feedback does not give Cicora a right to use the User’s entire private account history for another purpose.
2. Applications, downloadable components, and updates
2.1. If Cicora makes available an application, SDK, extension, package, container, or another downloadable component, the User receives a limited non-exclusive right to install and use it only with a permitted feature, on the User’s systems, and within the Order. The User may not copy, distribute, modify, lease, extract source code from, or sublicense the component except where expressly allowed by law or a separate licence.
2.2. A component may be updated for safety, compatibility, bug fixing, and product development. The interface or documentation will communicate material system requirements, end of support for a version, and an available update path where applicable. An update does not give Cicora a right to new kinds of data processing that are not needed for the component to operate.
2.3. Components under an open-source licence remain subject to that licence and its required notices. That licence applies to the relevant component where it grants greater rights than this page; it does not make the whole Service open source or transfer rights in the Cicora server-side platform.
3. Trial, beta, preview, and evaluation features
3.1. A feature is a trial feature only if it is expressly marked in the interface or documentation as trial, alpha, beta, preview, early access, or evaluation. A stable paid feature does not become beta retroactively because of an incident, Model change, or support difficulty.
3.2. Before enabling such a feature, Cicora discloses its experimental status, known material limitations, available support level, applicable data and retention terms, and a way to opt out where one is available. Beta may be changed, limited, or discontinued more quickly than a stable feature; this does not remove mandatory User rights or create a blanket liability exclusion that the law does not permit.
3.3. Beta is not intended for production, safety-critical, regulated, or other high-risk tasks unless the feature card and law expressly confirm otherwise. Beta is not a guaranteed SLA, independent audit, industry certification, special storage regime, or technical fitness for a particular purpose.
4. Files, attachments, and Content
4.1. The User may upload only files and materials needed for the task and for which the User has rights. To perform a request, Cicora may send the selected Model the file itself, extracted text, technical attributes, contextual excerpts, and other necessary data within the disclosed Route.
4.2. Permitted formats, size, number of files, analysis availability, and retention period are determined by the actual feature and shown before upload or in documentation. Rejection of a file, incomplete text extraction, a format error, or a context limit does not promise another processing method.
4.3. To protect the Service, checks may be applied for malicious code, technical compatibility, a breach of the Acceptable Use Rules, and compliance with law. A check does not guarantee a file’s safety, absence of rights infringement, or Output accuracy. The User must not upload secrets, third-party sensitive data, or material that the selected Route is not allowed to process.
4.4. Where a feature provides a library, project, history, or persistent file storage, the interface must show how to locate, manage, and delete the item. Where it does not, a one-request upload does not become a promise of permanent retention, immediate deletion, or backup in a particular country.
5. Search, browsing, and external sources
5.1. If search, browsing, retrieval, or another form of external-source access is enabled, the request, part of the request, and necessary technical parameters may be sent to that source to the extent identified by the feature. An external website, database, search provider, and its materials have their own terms, availability, licences, and privacy policy.
5.2. External information and Outputs may be incomplete, outdated, inaccurate, unavailable in a territory, or protected by third-party rights. The User must verify important facts, primary sources, dates, licences, and downstream use rights. A link, citation, or summary does not mean Cicora or a provider guarantees accuracy, endorses a source, or transfers its intellectual-property rights.
5.3. Search may not be used for mass extraction of restricted content, circumvention of a paywall, robots or contractual restrictions, collection of personal data, spam, or access to another person’s account. Lawful research of open sources, analysis of the User’s own database, and searching material that the User is entitled to use are not prohibited by themselves.
6. Connectors, applications, actions, webhooks, and agent actions
6.1. Connecting an external application, account, MCP connector, webhook, or action requires a separate act by the User or authorised Administrator. Before access is granted, the external recipient, requested permissions, categories of data transferred, persistence of access, method to disconnect, and the external service’s terms must be understandable.
6.2. The User is responsible for authority to connect an external account, select a scope, instruct an agent, and check the consequences of an action in an external system. A connector or action may not be enabled to bypass access rights, send another person’s data, make a hidden publication, send mass messages, make an unauthorised booking or purchase, change a file, or take another action without lawful authority.
6.3. Where a feature can take an action on the User’s behalf, the feature card or interface identifies whether a separate confirmation is required, the available scope, and where to view the result. The User must not assign an irreversible, regulated, or high-risk operation to that action without human review. Where an action feature is not enabled, this page does not create a right to send commands to external systems by another means.
6.4. Revoking a connection applies to future access within technical feasibility. It does not undo data lawfully already transferred to an external service or actions already carried out. Cicora is not responsible for the external application’s independent operation, but retains its duties for its own interface, Route disclosure, and data processing within its area of control.
7. Voice, images, and video
7.1. For an enabled voice, audio, image, or video feature, the User must have rights and, where necessary, consent for all uploaded or generated material. Particular care is required for a third party’s voice, face, appearance, name, identity, a child’s image, health data, or other sensitive data.
7.2. A feature may not be used to identify a person, create a biometric profile, infer sensitive characteristics, clone, or plausibly imitate a voice or likeness without the necessary lawful basis and consent. More restrictive terms of a particular Model apply only to that Model and are stated in the Model and Route Terms Registry.
7.3. Output rights, commercial-use availability, required labelling, restrictions on a separate audio file, likeness, and public distribution may differ between Routes. The User must check them before publication. Cicora does not promise uniqueness, lack of similarity, absence of third-party rights, or permission for every form of distribution.
7.4. If Cicora ever enables a public feed, remix, gallery, character, publication, or shared media link, publication must be preceded by a separate User choice and a clear rule about published Content, the licence to display it within the feature, audience, complaints, and deletion. Until that mode is enabled, these Terms do not grant a right to publicly use another User’s materials.
8. Code, software Outputs, and development
8.1. Code, configuration, command, library, or other technical Output may contain an error, unsafe dependency, third-party licence restriction, a similar fragment, or require adaptation. The User must perform review, testing, security analysis, licence review, and compliance checks before running, publishing, or shipping it.
8.2. An Output does not replace a security audit, legal licence review, code review, penetration test, or manufacturer support. Code may not be used for prohibited interference with a system, bypassing controls, licence infringement, or training or extracting a Model where the selected Route prohibits it.
8.3. A developer integrating Cicora into a product remains responsible for its UI, statements, data processing, user terms, AI disclosure, error handling, and decisions made by its end users. The developer must not state that its product is an official service of a Model provider where that status does not exist.
9. Context, Models, and automated routing
9.1. Context size, speed, queueing, concurrency, tool use, availability, and price depend on the specific Route. A stated maximum context window does not mean that all of it is available only to the User’s Input Materials: part may be occupied by system instructions, history, files, tools, safety processing, and Outputs.
9.2. Automated Model selection, fallback, processing region, retention, training, safety review, and logging are allowed only within the disclosed configuration, the Model Terms, and the User’s or organisation’s choice. Where an alternative path materially changes the data regime, territory requirement, price, or permitted task, Cicora must not silently use it instead of the agreed Route.
9.3. The User may obtain available information about the actual Route, usage measurement, and material data terms. We do not have to disclose secrets, keys, vulnerabilities, data of other customers, or information whose disclosure would breach safety, contract, or law.
10. Fine-tuning, custom models, and training programmes
10.1. Fine-tuning, training a user model, a custom model, an evaluation corpus, development-partner mode, or a research or training programme are separate features. They do not arise automatically from an ordinary file upload, chat history, feedback, or use of a base Model.
10.2. Before such a feature begins, a separate term or card must specify the Training Materials, purpose, data rights and consent, provider and Route, permitted data types, retention and deletion terms, Output use, price, access, duration, withdrawal option, and the effect of withdrawal on training already completed. Special-category data, health information, and children’s data may not be used in that mode without explicitly confirmed lawfulness and required safeguards.
10.3. Until the relevant feature is enabled and documented, the User does not receive a right to require training, separate storage, data localisation, model exclusivity, export of weights, or transfer of rights in a base Model.
11. Publishing, builder features, marketplaces, and external platforms
11.1. If Cicora permits a User to create and publish a user agent, template, application, extension, or another public object, its author is responsible for its instructions, description, connected actions, data, Content rights, compliance with the Acceptable Use Rules, and applicable Model Terms. Cicora may limit or remove the object for a breach, risk, complaint, end of the feature, or legal requirement.
11.2. Before publication, the interface will disclose who can view the object, what data may be available to a user of the object, what licence is required for display or distribution, and how to submit an IP complaint. Publication does not make Cicora an editor, co-author, employer, or guarantor of the author, and does not transfer rights in third-party materials to the author.
11.3. Distribution through an App Store, Google Play, cloud marketplace, or another external catalogue is governed by additional rules of that platform only after that distribution channel is actually launched. This page does not promise listing, moderation, support, refund, fee, territory, or data location of an external platform.
12. Regulated, sensitive, and high-risk use cases
12.1. The Service is not a medical device, diagnostic system, legal representative, payment organisation, investment adviser, insurance intermediary, employment or credit scoring tool, critical-infrastructure system, or guarantor of compliance with an industry standard. Use in such contexts is possible only with a lawful basis, required qualification, human control, technical measures, and permitted terms of the specific Route.
12.2. Protected health information, medical images for diagnosis, identity documents, biometric templates, banking secrets, state secrets, or other sensitive material may not be sent to an ordinary Route unless the feature card and applicable agreement expressly permit that processing. An interface warning does not replace a separate agreement, risk assessment, consent, safeguards, or legally required addendum.
12.3. If a separate feature for a regulated use case is launched, its role, permitted purpose, required checks, Output limitations, specialist requirements, data regime, incident contact, and applicable special terms must be published before use. Until then, this page does not promise HIPAA, medical, financial, educational, governmental, or other sector-specific suitability.
13. Changes, termination, and relationship with other terms
13.1. Cicora may develop, replace, limit, or discontinue a feature because of safety, law, technical compatibility, provider rules, or product development. A material change to an active paid obligation is governed by the Public Offer, the Order, and the refund rules; it does not justify changing a completed request retroactively.
13.2. Where a feature concerns an organisation’s personal data and RIZZ TRADE processes it under documented instructions of a Business Customer, the Business Data Terms also apply to the extent applicable. Mentioning a feature on a public page does not replace a separate B2B DPA where one is required.
13.3. Questions about a feature, its restriction, the selected Route, or data may be sent to support@cicora.ai or +998 90 051 48 40. Provider: RIZZ TRADE LLC, Republic of Uzbekistan, TIN 312432714, registration record 2944991 dated 15 September 2025, address: 3 Nukus Street, Abdulla Avloniy MFY, Mirabad District, Tashkent.