Version dated 16 September 2026. It applies upon publication and acceptance in the manner set out in this agreement.
1. Parties and subject matter of the offer
1.1. RIZZ TRADE Limited Liability Company / “RIZZ TRADE” LLC, registered in the Republic of Uzbekistan on 15 September 2025, registration entry 2944991, TIN 312432714, offers to enter into an agreement for use of its own Cicora software service on the terms of this public offer. Address for correspondence: Republic of Uzbekistan, Tashkent, Mirabad District, Abdulla Avloniy MFY, Nukus Street, Building 3. Email: support@cicora.ai. Telephone: +998 90 051 48 40. It is referred to below as “Cicora,” the “Provider,” or “we.”
1.2. This agreement is entered into with an individual or organisation accepting this offer, referred to below as the “User” or “Customer.” A person accepting the terms on behalf of an organisation confirms that they are authorised to enter into the agreement, create a workspace, order features and incur the associated charges. A person without that authority must not purport to bind the organisation.
1.3. The subject matter of the agreement is the grant of rights to use Cicora software and the provision of related digital services: processing requests, routing them to models, managing context and files, using available tools, recording usage, and providing results. The specific scope is determined by the selected product, plan, model, mode, and order.
1.4. RIZZ TRADE is the provider of its own software service. The Cicora server-side system provides authentication, routing, processing algorithms, access management, and usage accounting. We may engage technology providers to perform individual computing operations. This does not change the party to the agreement with the User and does not mean that we accept payment on a provider’s behalf as a payment intermediary.
1.5. Purchasing Cicora does not mean purchasing another company’s personal account, subscription, or API key. Names of third-party models are used to identify technology available within the service and do not imply a partnership, representation, or endorsement unless that relationship is expressly confirmed.
2. Definitions
2.1. “Service” means the software interfaces, the cicora.ai website, available applications and Cicora APIs, and the functions included in an order. “Account” means a User account. “Workspace” means an account or organisational environment in which access rights and a shared budget may be allocated. “Administrator” means a person granted the workspace-management powers shown in the interface.
2.2. “Input Materials” means requests, messages, instructions, files, images, audio, video, code, data, and other materials supplied by or on behalf of the User. “Results” means responses and other materials generated when a request is performed. Input Materials and Results together are “Content.” Third-party content obtained from external sources may have a separate rights holder.
2.3. “Model” means a selected computational model or specialised function. “Model Provider” means a person providing the technology or its execution. “Route” means a configuration for performing a request, including the model, provider, mode, region, and data-processing settings. One model identifier may have several Routes with different prices, availability, and data rules.
2.4. “Order” means a confirmed selection of a product, term, price, currency, applicable terms, and payment method. “Subscription” means access for a defined paid period with the capabilities and limits provided by the plan. “Pay as you go” means payment for actually measured usage. “Balance” and “Credits” mean an internal accounting of prepaid service volume; they do not mean a bank account, payment wallet, or a right to settle with third parties.
2.5. “Model Terms” means the binding rules, licences, and restrictions of the relevant Model and Route. “Consumer” means an individual purchasing the Service for purposes to which applicable law gives consumer protection. “Business Customer” means a person using the Service for business or professional purposes. The name of a plan does not by itself remove a status granted to a Consumer by law.
3. Agreement documents and their order of precedence
3.1. The agreement consists of this offer, the confirmed Order, the applicable version of pricing, the Billing and Credit Rules, the Refund Rules, the Acceptable Use Rules, and the Feature Terms. Section 11 of this offer sets out the rules for use of Models; the Model and Provider Policy Directory helps identify the terms applicable to a particular Route.
3.2. The Privacy Policy describes the processing of personal data. It is not a blanket consent to every form of processing and does not replace separate consent where required by law. The Business Data Terms apply, within their scope, to processing under documented instructions from a Business Customer.
3.3. Mandatory law prevails in the event of conflict. Next in priority are an individually agreed written Order or agreement; the special terms of a particular feature for that feature; and this offer and the incorporated rules. Model Terms determine binding limits on use of the relevant technology, but do not themselves replace the price promised to the User by Cicora or remove RIZZ TRADE’s requirements in respect of its own service.
3.4. An individual amendment is effective only if accepted by authorised parties in a retained written or electronic form. Terms unilaterally added by a Customer to a payment instruction, purchase order, or other document do not amend the agreement without our express acceptance.
3.5. Documents are published in the language versions available through the language selector. The version and language displayed on acceptance are retained for an Order. Translation differences are resolved in light of the meaning of the agreed terms and the User’s mandatory rights; an unread version in another language is not used to expand the User’s obligations covertly.
4. Entering into the agreement and electronic evidence
4.1. Before placing an Order, the User may review the terms, description, price, usage-measurement rules, access period, and applicable restrictions. For a paid Order, acceptance is expressed by expressly confirming the relevant terms and completing the specified payment action. Merely visiting a public page does not authorise a charge.
4.2. The User checks the Order and corrects errors before confirming it. After successful payment or another agreed basis for activation, a retained confirmation is created. It must identify the parties, product, period, amount, currency, and accepted terms. Electronic confirmations, transaction records, and accounting documents are used to perform the agreement and review requests.
4.3. The parties acknowledge that electronic messages, notices, payment-provider confirmations, and Service logs may be used as evidence to the extent permitted by law. Such records are not conclusive: the User may submit evidence of an error or other documents. A technical record of a browser redirect does not replace confirmation of payment.
4.4. No physical medium is provided for electronic delivery of software. Activation confirmation and actual use are recorded by the electronic system. The absence of a signed paper acceptance certificate does not by itself mean that a digital service was not provided where its provision is evidenced by admissible evidence; mandatory accounting and consumer documents are provided where required by law.
5. Age, authority, and account information
5.1. The minimum age for access is 13, or a higher age set by applicable law, the Model Terms, or a separate feature. If approval from a legal representative is required for independent entry into an agreement, data processing, or payment, it must be obtained before the relevant action. A higher age threshold of a particular Route prevails for that Route.
5.2. At registration, the User provides current and accurate information sufficient for the Account and Order. The User must not impersonate another person, create a fictitious organisation, conceal mandatory country information, or use another person’s payment data without lawful permission. Changed contact and billing data must be updated promptly.
5.3. We may request proportionate confirmation of authority, Account ownership, rights to materials, payment, or use of a restricted feature. A request is limited to what is needed for the specific review. Passwords, CVV values, bank codes, and other secrets must not be sent by ordinary email. If a necessary review cannot be completed, the affected action may be suspended within the limits of law.
6. Account and API-key security
6.1. Personal sign-in data may not be shared in a manner that makes several people appear to be one User. Collaborative work takes place through the provided roles and accounts. The User takes reasonable measures to protect passwords, devices, sessions, and its own Cicora keys and reports a compromise to support@cicora.ai.
6.2. An API key operates within the granted rights and budget. The Customer controls its placement in applications, access by developers and contractors, revocation, and replacement. A secret key must not be published in open-source code, given to unauthorised persons, or used when it belongs to another person without permission. Lawful API integration into the Customer’s own product does not create a right to resell a Cicora Account or Technology Provider keys.
6.3. Until we receive notice, we may rely on properly authenticated Account actions, subject to our obligation to maintain reasonable security and to rules governing challenges to unauthorised transactions. This clause does not make the User responsible for a proven error by Cicora and does not remove mandatory payment protections.
6.4. Where there is a security threat, we may revoke a key, end sessions, verify the owner, or temporarily limit functions. We seek to keep measures to the necessary scope. Restoration does not automatically remove lawful restrictions imposed by a Model Provider.
7. Workspaces and corporate accounts
7.1. The workspace owner and appointed Administrators manage only the rights provided by the product: members, available Models, budgets, keys, policies, and Content within the relevant role. Administrator powers are disclosed when a person joins; a corporate email address alone does not give an organisation unconditional access to personal history.
7.2. Where transfer of an Account into a corporate environment is available, the User receives the applicable notice before administrative control is transferred. The organisation must have a basis to manage its members’ data and inform them of its policies. It determines the lawfulness of its instructions and the use of Results in the organisation’s activities.
7.3. An authorised purchaser may order functions and incur charges only within its granted authority. The organisation is responsible for use ordered by authorised persons and controls member rights. Removing a member ends that member’s access but does not necessarily delete data or accounting records lawfully belonging to the organisation.
7.4. Access for an affiliate, customer, or contractor is permitted only by a method authorised by the plan. A separate legal entity does not become a party to the agreement or an independent licensee merely because it has a common domain, owner, or project.
8. Software licence
8.1. To the extent of rights available to us, for the term of paid access or permitted free use, we grant a limited, non-exclusive right to use Cicora functionality through the provided interfaces and APIs. No exclusive rights, source code, or trademark rights are transferred.
8.2. The licence is limited by the purpose, volume, geographic availability, number of users, and technical limits of the selected product. The Service does not grant a right to copy or distribute server software, rent out an Account, provide unauthorised sublicensed access, or create a false appearance of official representation of Cicora.
8.3. An API authorised by the plan may be integrated into the Customer’s own applications and processes. The Customer must comply with requirements for end users, the Model, key security, and data processing. Such integration differs from transferring provider accounts or covertly reselling access in breach of applicable licences.
8.4. Published terms for the relevant component apply to a downloadable client, SDK, extension, or other component. Components under an open-source licence retain that licence and its mandatory notices; this agreement does not reduce rights expressly granted by that licence. The presence of separate open-source components does not make the entire platform open-source software.
8.5. Updates may modify or replace components for security, compatibility, and product development. The User is not required to grant rights that are not needed to use an update. When an access right ends, use of protected components ends to the extent provided by the agreement and law; data-export rights permitted by law remain available.
9. Service capabilities, limitations, and changes
9.1. The description and plan comparison define the purchased product. The name of another company’s function does not mean that an equivalent Cicora function is available. A Subscription does not promise third-party consumer applications, enterprise certificates, dedicated capacity, or an SLA unless a confirmed Order expressly provides it.
9.2. Model availability and performance depend on the mode, context volume, tools, infrastructure status, and availability of Technology Providers. A stated maximum context window is not necessarily entirely available for the User’s text: some of it may be used by instructions, tools, history, and system processing.
9.3. We may develop the interface, correct errors, address vulnerabilities, replace technical components, and discontinue obsolete functions. A material reduction of an already paid obligation is addressed under applicable law and the Refund Rules. An ordinary update does not create a right to recalculate a completed request retrospectively or reduce purchased volume.
9.4. Technical maintenance and temporary unavailability do not by themselves promise compensation under a non-existent SLA. Requirements arising from actual non-provision or defective provision of a paid service nevertheless remain. Trial, beta, and preview functions are expressly labelled and governed by special terms; a stable paid product is not retrospectively labelled beta.
10. Subscriptions, usage, and prepayment
10.1. Individual subscriptions are available as Plus ($20), Pro ($50), 5× ($100), and 20× ($200) at monthly prices according to the pricing page. For comparable modes and measurement periods, the 5× and 20× plans provide respectively 5× and 20× the usage volume of the Plus ($20) plan. Pro has the enhanced level described in the product. These multipliers do not multiply money held in an Account.
10.2. Subscription limits, a separately paid API Balance, and bonuses are distinct. A Subscription is valid for the stated period; consumption depends on the Model, context, response, files, tools, and other disclosed parameters. No particular number of messages or identical cost of different requests is guaranteed. Limits and their refresh time are shown when selecting and using a plan.
10.3. API Pay as you go is charged from the relevant Balance for actual usage. If the Balance is insufficient, a new paid request may be rejected or stopped under the disclosed procedure. A hidden credit facility, debt, or automatic budget overrun does not arise merely because a request has started.
10.4. Before confirmation, the product price, applicable taxes, billing currency, and final amount are displayed. Models are subject to the published catalogue and the rules of the relevant Route. Different tools and media may be billed by tokens, image, character, request, second, minute, hour, or another disclosed measure. The absence of a displayed rate does not mean that use is free.
10.5. Additional rules for measurement, reservation, adjustments, and the lifetime of units are set out in the Billing and Credit Rules. No type of Balance gives a right to interest income, currency exchange transactions, transfers to other Users, or payments to third-party sellers.
11. Model Terms and technology Routes
11.1. This section is part of the agreement, not merely an information page. Each Model may be used only within the binding terms of its provider and the selected Route. Links, provider information, and available restrictions are shown in the API catalogue and the Model Terms Directory. The list is not limited to three brands.
11.2. Before making a request, the User checks the purpose and permitted use of the Model for its task, commercial-use terms, country or organisation restrictions, available functions, and rules for handling materials. If the User does not accept a binding Model Term, the User must not send a request through that Route and may select another permitted option.
11.3. A Business Customer and a developer who provides its own product to end users through the Cicora API undertake to pass on applicable rules to those users and obtain required consent and a lawful basis for processing before a request. To the extent permitted by law, the Customer is responsible for its integration and authorised users; it may not expand rights beyond the Model licence.
11.4. A Model may have several providers and versions. Automatic routing, fallback, selection of regional execution, training, or storage apply only within disclosed settings and binding restrictions. A fallback Route must not be used to bypass an agreed budget, a prohibition on data transfer, or an unavailable territory.
11.5. A change in rules, withdrawal of a Model, a change in provider availability, or a provider’s binding requirement may result in restriction of the relevant Route. Material consequences for an active paid product are notified in the manner required by law; completed operations do not become new purchases at changed rates.
11.6. We may not override a Model developer’s binding licensing, export, age, or other restrictions. Circumventing blocks or safeguards, falsifying country or identity, or using a proxy or VPN to obtain prohibited access is forbidden. A permitted network-security tool is not prohibited merely because it is used, provided that it is not used for such circumvention.
11.7. To meet binding requirements, we may request reasonably necessary information about rights to materials, consent, authority, country, mode, or end use. If information required for a specific Model is not provided, use of that Model may be restricted. This does not create a right to demand unrelated information about all Customer activities.
11.8. Technical classification of a region, request class, or compatibility may contain errors. The User may ask for review. This qualification does not relieve Cicora of its own obligations and is not permission knowingly to send a request through an unsuitable Route.
11.9. Cicora’s procurement agreement with a provider does not make that provider a party to the User’s agreement with RIZZ TRADE. RIZZ TRADE is responsible, to the extent established by law, for its interface, charges, price disclosure, and contractual obligations to the User.
12. API integrations and end users
12.1. The API must be used in accordance with published documentation, authentication, limits, and permitted parameters. The Customer is responsible for the correctness of its integration, verification of responses, retry logic, and dependencies. Undocumented methods must not be used to bypass pricing, security, or Model Terms.
12.2. Automation of requests that is authorised through the API is not prohibited scraping. It is nevertheless prohibited to extract protected materials or non-public interface information in bulk, interfere with other customers’ operations, circumvent limits, or obtain infrastructure access beyond the provided API.
12.3. Idempotency, timeouts, streaming, and confirmation of completion must be taken into account in an integration. Re-sending a new request does not guarantee an identical response and may create a separate chargeable processing operation; a retry caused by Cicora’s own error is considered under the adjustment rules. Request identifiers enable matching of usage and Results.
12.4. A Customer serving its own users remains responsible for its product, its representations, permissions, data processing, and decisions made based on Results. It must not promise its users undisclosed Cicora warranties or represent itself as an authorised representative of RIZZ TRADE without a basis.
13. Input Materials and rights in Results
13.1. The User retains its rights in Input Materials. The User grants a limited permission to receive them, store them in the selected mode, reproduce them in the workflow, make technical transformations, transfer them to necessary providers, and generate a response solely to perform, protect, and support the Service and comply with law.
13.2. The User confirms that it has the necessary rights, consent, and lawful basis to submit materials, including personal data, images and voices of other persons, protected works, and organisational information. Availability of material on the internet does not always mean that it may be reused or sent to a Model.
13.3. As between the parties, rights in a Result that belong to Cicora and can be transferred are granted to the User to the fullest extent permitted by applicable law and the Model licence. This does not transfer third-party rights, create protectability where it does not exist, or remove special restrictions on a particular type of Result.
13.4. Results may be identical or similar for different users. The agreement does not grant exclusivity in a general style, idea, facts, common elements, or independently created content. Third-party content from search, a connected source, or a tool remains subject to applicable rights and terms of use.
13.5. The User assesses the lawfulness of publishing and commercially using a Result. Generating a Result does not by itself confirm the absence of third-party trademarks, rights in a depicted person, the permissibility of advertising, or compliance with a software-component licence.
14. Files, history, and publication
14.1. Files are accepted in formats, sizes, and quantities supported and indicated in the interface or API. We may reject a corrupted, dangerous, incompatible, or prohibited file and limit actions that threaten infrastructure. Any right to review is limited to security, performance, and legal-compliance purposes.
14.2. Selecting a file for a request instructs us to use the necessary content on the relevant Route. It is not a general permission to publish all files in the Account. The storage mode, member access, deletion, and backups are governed by the data policy and settings of the relevant function.
14.3. The processing service is not a guaranteed archive or the User’s sole backup. Important source materials and Results should be retained independently. Data-protection obligations and mandatory rights in the event of Cicora’s own error remain unaffected.
14.4. If a function permits creation of a public link or publication of Content, an agent, a template, or another object, the User selects the relevant action before publication. Permission covers only publication and display of the selected object to the relevant audience. Recipients may retain material available to them; revoking a link does not always remove their independent copies.
14.5. Public posting does not grant us exclusive rights in personal Content or turn non-public conversations into advertising material. Other uses require a separately disclosed basis. The User is responsible for rights in published material and for the absence of unlawful content.
15. Feedback and Cicora rights
15.1. Suggestions for improvement voluntarily submitted as feedback may be used to develop the Service without an obligation to pay compensation unless otherwise separately agreed. This clause does not permit us to call all personal Content feedback or use it for an undisclosed purpose.
15.2. The platform, its software components, design, documentation, and marks remain with their respective rights holders. Neither payment for a Subscription nor use of a Result transfers rights in Cicora code or branding. Use of marks must not create a false impression of authorship, affiliation, or endorsement.
15.3. A report of suspected intellectual-property infringement is handled under the IP Complaint Procedure. We review sufficiently specific information, take into account explanations from the affected party, and comply with applicable legal requirements. Knowingly false notices or counter-notices are not permitted.
16. AI accuracy and responsible use
16.1. Generative systems produce probabilistic Results and may make errors, omit context, use outdated information, or give unexpected responses. We do not promise that every response will be true, unique, or suitable for the User’s particular purpose.
16.2. Reasonable review is required before using a Result, especially before publication or use in relation to other persons. An AI Result must not be presented as a verified professional opinion or human work where that would be misleading or unlawful. Required labels for synthetic content must be retained.
16.3. A general-purpose Service does not become a licensed medical, legal, financial, or other regulated professional service. Material decisions about employment, credit, insurance, housing, education, health, and other human rights must not be made solely on the basis of an unverified AI response in breach of applicable requirements.
16.4. These limitations apply to the relevant use and do not promise complete control of every Result. Detailed general and model requirements are set out in the Acceptable Use Rules. They do not remove Cicora’s responsibility for promised functionality, its own charges, or remedies required by law.
17. Prohibited conduct and checks
17.1. Illegal conduct, infringement of intellectual and personal rights, exploitation of children, fraud, unauthorised access, malicious software, interference with infrastructure, dangerous use, and circumvention of binding restrictions are prohibited. The full categories and conditional Model rules are set out in the Acceptable Use Rules.
17.2. A User must not attempt to obtain non-public source code, secrets, model weights, or data of other users through reverse engineering, extraction, or circumvention of technical measures, except to the extent expressly permitted by mandatory law or an applicable open-source licence. Permitted security research is conducted under an agreed programme if such a programme is offered; general API access does not itself authorise attacks.
17.3. The User must not disable provided safeguards, falsify metrics, abuse bonuses, create fictitious accounts to evade limits, or help third parties breach these rules. Using Results to train another model is subject to data rights and binding restrictions of the selected technology; a provider prohibition is not removed merely because the call was made through Cicora.
17.4. To the necessary extent, automated and human review, blocking of an individual request or file, restriction of a function, retention of evidence related to an incident, and lawful reporting to a competent authority may occur. Checks do not mean that all Content is continuously read by humans. Their purposes and legal bases are described in the Privacy Policy.
18. Confidentiality
18.1. Confidential Information means non-public information disclosed in connection with the agreement and identified as confidential or reasonably confidential by its nature: private Content, business information, technical materials, terms of an individual Order, and security and access information.
18.2. The receiving party uses Confidential Information to perform the agreement and protect the relevant rights, maintains reasonable confidentiality, and permits access only to persons who need it and are subject to an applicable protection obligation. Where a contractor is engaged, only the necessary portion of information is transferred, subject to the agreement, Model Terms, and data-protection law.
18.3. The restrictions do not apply to information that becomes public without breach by the recipient, was lawfully known to it earlier, was lawfully received from an independent third party, or was independently developed without use of the disclosed Confidential Information. An exception must have a basis and is not presumed merely from similarity of information.
18.4. Where disclosure is mandatory under a lawful request, it is limited to the required scope. Where permitted, the disclosing party is informed of the request and given a reasonable opportunity to protect the information. This clause does not require breach of a non-notification order or obstruction of a lawful investigation.
18.5. When the lawful basis ends, information is returned, deleted, or retained to a limited extent for mandatory accounting, claim protection, security, and backup cycles. Confidentiality obligations continue for lawfully retained information. Personal-data rules prevail in their field.
19. Third-party services, tools, and actions
19.1. The Service may include external sources, search, connected tools, applications, and links. Where the User enables such a function, the User must review its purpose, data recipient, and necessary permissions. Enabling it does not automatically grant access to all Account data.
19.2. Performing an external action at the User’s instruction, such as sending information or changing an object in a connected system, may be subject to additional confirmations and the rules of that system. The User verifies material actions before they become final where confirmation is available. A generated instruction must not be represented as independently granted human authority.
19.3. Cicora does not control every term or piece of content of an external site and does not promise its continuous operation. However, engaging a provider to perform Cicora’s own paid obligation does not automatically remove RIZZ TRADE’s responsibility to the User. Data from a third-party source and its intellectual-property rights are governed by the relevant terms.
20. Personal data and business processing
20.1. Processing of Account, payment, security, requests, and support is described in the Privacy Policy, Cookie Rules, and Data Controls. This public offer does not replace particular consent required for optional processing.
20.2. A User submitting data of other persons must have an applicable basis. A Business Customer is responsible for the lawfulness of its instructions, notices to data subjects, and permissions for transfer. This does not mean that Cicora is automatically never an operator or controller of data: the role is determined by the particular operation and applicable law.
20.3. Processing under an organisation’s instructions is governed by a separate contractual business-data layer. The existence of a general privacy text does not establish special agreements for medical data, international transfers, or other regulated processing. Information must not be submitted where the binding terms of the selected Route have not been met.
20.4. Information about retention of requests, files, and technical logs differs by function and provider. The terms “confidential,” “no training,” or “ZDR” are not universal promises for every Route. The User may choose only actually available modes with disclosed boundaries.
21. Payment, renewal, and price changes
21.1. Payments are made only through a bank, provider, or app store actually offered for the Order. Check the merchant, amount, and currency. Questions about provision of the Service are addressed to RIZZ TRADE; questions about an unauthorised card transaction may also be addressed to the card issuer.
21.2. Automatic renewal and automatic top-up require separate express authorisation stating the period or threshold, amount or calculation, and method of cancellation. Saving a payment instrument does not by itself authorise any later charge. The User may withdraw authorisation for future payments by the provided method.
21.3. Upon ordinary cancellation, a Subscription is not renewed and remains available until the end of the already paid period, unless a refund or other lawful termination takes place. A plan change does not create an automatic credit, discount, or pro-rata refund; the terms of a particular change are shown before confirmation.
21.4. Failed payment may result in a new Order not being activated, renewal stopping, or paid functions being limited. Confirmed payments and legal claims already accrued are considered separately. A repeated payment notice is not grounds to credit or charge one transaction again.
21.5. A new price applies to new Orders and requests after disclosure. A future Subscription price change is notified in advance as required by law and the agreement, with an opportunity to cancel the next renewal. An erroneous price does not create a right to charge a different amount covertly: proper disclosure and consent are required before performance of a corrected Order, or the erroneous transaction is cancelled as required by law.
21.6. Domestic sales in Uzbekistan and international sales use the applicable currency and tax arrangements. A foreign reference price does not by itself authorise domestic currency linkage. All mandatory information about the final price is given before the Order is accepted; the User’s bank conversion is governed by that bank’s terms.
22. Refunds and mandatory remedies
22.1. As a general rule, payments for Subscriptions and prepaid usage are non-refundable except for the specific grounds in the Refund Rules, mandatory applicable law, and an individual approval. An unused limit or a wish to stop using the Service does not by itself create an unconditional right to a cash refund.
22.2. Confirmed errors and duplicate charges, unauthorised payments, non-provided or materially defective service, termination of a paid service by Cicora without User breach, statutory withdrawal rights, and app-store procedures are considered separately. The Refund Rules state the relevant grounds and request process.
22.3. Ordinary cancellation of future renewal differs from withdrawal from an agreement already concluded. A Consumer retains applicable withdrawal rights, digital-service guarantees, and statutory time limits. A record that service started early is not a universal waiver of all rights.
22.4. A refund through the original transaction takes account of the law and the actual payment route. Recovery from a bank does not create a right to recover the same amount again from Cicora. Contacting support does not remove the right to contact a bank, regulator, or court.
23. Term and termination of the agreement
23.1. The agreement remains in effect from acceptance within the scope of granted access and necessary settlements. The User may stop use, cancel renewal, and request Account deletion. These actions have different consequences; deletion of an external app-store subscription is managed in that store.
23.2. We may suspend a particular function, Model, key, Workspace, or Account in the event of a material breach, a justified security threat, fraud, infringement of rights, a binding demand of law or a provider, unpaid charges, or inability lawfully to continue service.
23.3. Where possible and proportionate to the circumstances, we notify the User of the basis and give an opportunity to cure a breach. Urgent protection, a lawful prohibition on notice, or a risk of continuing harm may require action without advance warning. The opportunity to appeal through support@cicora.ai remains to the extent permitted by law.
23.4. Final termination of a paid service without breach by the User is accompanied by settlement of the unprovided prepaid part, including where continuation of the Service becomes impossible because a provider withdraws or a legal restriction applies. Replacement of an individual Route that preserves the agreed material capabilities does not by itself mean that the entire Service has been terminated. The consequences of a material reduction are determined by the Order, the Refund Rules, and mandatory law. Where a breach is proven, unused balance does not automatically become refundable, but it also may not be taken contrary to mandatory law.
23.5. On termination, rights to continued use end and the relevant keys and sessions are revoked. Accrued payment claims, confidentiality, rights and data-protection obligations, applicable liability limits, and dispute procedures survive. Documents and data lawfully retained are not destroyed merely because an Account is closed.
23.6. If a storage function or data access ends, export, deletion, and other rights are exercised under applicable law, the agreement, and the actual capabilities of the function. This clause does not create a right to indefinite free storage after the Service ends.
24. Warranties and limits of promises
24.1. We provide the described software service within the agreed Order and applicable mandatory requirements. Beyond mandatory warranties and expressly agreed written promises, the Service is provided in the state and scope actually available. We do not promise the absence of all errors, absolute security, uninterrupted availability of every Model, or a particular commercial outcome.
24.2. Neither a demonstration of a Result nor a marketing example replaces the terms of an Order or guarantees an identical response to another request. Questions of regulated activity, licences for materials, and final verification of a decision remain with the person using the Result, within the law.
24.3. A Route temporarily disabled by a provider or a network failure does not automatically amount to a breach of a particular Cicora contractual obligation. This qualification does not exclude liability for Cicora’s own fault, concealed non-conformity with the promised product, or mandatory Consumer remedies.
25. Limitation of liability
25.1. To the maximum extent permitted by law, we are not liable for indirect or consequential loss, lost profits, lost savings, or commercial opportunities arising from use of the Service. This limitation does not exclude loss or remedies that mandatory law prohibits from being excluded or limited.
25.2. Where a limitation is permitted, the aggregate contractual liability of RIZZ TRADE for related claims does not exceed the greater of: the amount actually paid for the service to which the claim relates during the twelve months preceding the relevant event; or the equivalent of USD 100. A different limit may be agreed individually in a B2B agreement.
25.3. The limit does not apply to liability that cannot be limited, including wilful misconduct, fraud, injury to life or health in cases provided by law, mandatory personal-data requirements, and non-excludable Consumer rights. It does not turn a refund required by law into a discretionary payment by the Service.
25.4. The User takes reasonable steps to mitigate loss, preserve necessary evidence, and notify us of an error. This does not shorten a statutory limitation period or require the User to waive rights against a bank or court.
26. Third-party claims in business use
26.1. This section applies to a Business Customer to the extent permitted by law; it does not impose a hidden obligation on an ordinary Consumer to reimburse any Cicora costs. The Customer is responsible for the lawfulness of its Content, instructions, product, and acts of authorised users.
26.2. If a third-party claim arises from the Customer’s Content that breaches law or the agreement, missing required permissions, or unlawful operation of its integration, the Customer shall, at its expense and to the extent permitted by law, defend RIZZ TRADE and reimburse documented reasonable defence costs, including legal fees, as well as amounts awarded and approved settlements attributable to its breach. Reimbursement does not cover Cicora’s own culpable act or circumstances unrelated to the Customer.
26.3. RIZZ TRADE shall notify the Customer of the claim without undue delay and provide reasonably necessary assistance at the Customer’s expense; delayed notice relieves the Customer only to the extent it demonstrably prejudices the defence. The Customer shall appoint qualified counsel reasonably acceptable to RIZZ TRADE and keep it informed of material steps. RIZZ TRADE may participate through its own counsel at its own expense; if the Customer fails to provide a timely defence or a material conflict of interest arises, RIZZ TRADE may arrange the necessary defence and recover proportionate costs under clause 26.2. Any settlement that admits a violation by RIZZ TRADE, imposes a payment or other obligation on it, or fails to provide a complete release from the relevant claim requires its prior written consent. Neither party may assume obligations on behalf of the other without authority; consent shall not be unreasonably withheld or delayed.
26.4. Special protection from intellectual-property claims relating to the Results of a particular Model or Technology Provider is not automatically provided. It applies only if expressly included in an individual Order and the corresponding rights are available in the contractual chain. This does not remove RIZZ TRADE’s liability for its own infringement of exclusive rights.
27. Circumstances beyond reasonable control
27.1. A party is not liable for non-performance to the extent caused by proven circumstances beyond its reasonable control where applicable law permits such relief, including an emergency event, a binding prohibition by a competent authority, a large-scale communications-infrastructure failure, or another comparable event.
27.2. An ordinary lack of funds, a party’s own security breach, or any contractor error does not automatically constitute force majeure. The affected party notifies the other party of a material impediment where possible and takes reasonable measures to mitigate its consequences. The unprovided paid portion and statutory termination rights are addressed separately.
28. Governing law and dispute resolution
28.1. This agreement is governed by the law of the Republic of Uzbekistan, while preserving mandatory rules and Consumer remedies applicable to the particular User. The choice of law does not deprive a Consumer of access to a court or authority that mandatory law protects in the Consumer’s country.
28.2. To raise a dispute, a party may send a claim to support@cicora.ai or to the postal address above, stating the circumstances, Order, evidence, and requested remedy. We consider it within the applicable statutory period. A pre-litigation procedure is mandatory only to the extent required by applicable law or a lawful individual agreement.
28.3. For a business dispute, unless law or a separate agreement provides otherwise, the competent court at the location of RIZZ TRADE is used. The agreement does not automatically impose foreign mandatory arbitration, a class-action waiver, or a requirement that a Consumer not go to court.
28.4. A request does not prevent urgent protective measures, performance of a binding regulator request, or protection of rights through a bank. Statutory time limits are not shortened by a general support-convenience clause.
29. Notices, changes, and assignment
29.1. Legal and service notices are delivered through the stated email address, Account, Order confirmation, or another agreed method. The parties keep contact information current. Marketing messages have a separate legal basis and opt-out option; accepting this agreement does not mean subscribing to marketing.
29.2. Changes are introduced for security, legal, technological, or product-development reasons. A new version is published with a date; material changes are notified in advance to the extent required by law, with an opportunity not to accept new terms and to stop the relevant future use. Completed operations are not recalculated retrospectively.
29.3. Continued use after proper notice constitutes acceptance only to the extent permitted by law; separate consent is requested where required. Removing a link to an earlier text does not change the provable terms of an earlier Order.
29.4. The User may not assign an Account or contractual rights and obligations to a third party in breach of plan restrictions or without necessary consent. Transfer of RIZZ TRADE’s business or reorganisation is permitted by law subject to requirements for notice, personal data, and preservation of acquired rights; it does not permit arbitrary deterioration of a Consumer’s position.
30. Final provisions and contacts
30.1. The parties are independent persons. The agreement does not create a partnership, employment relationship, authority to accept payment for a Model Provider, or authority to represent the other party without a separate basis.
30.2. Failure or delay in exercising a right is not a waiver of that right. Invalidity of an individual provision does not invalidate the remaining provisions if the agreement can operate without it; an invalid term is applied or replaced only to the lawful extent, without reducing the User’s mandatory rights.
30.3. This agreed package and the confirmed Order constitute the agreement of the parties for the relevant product. Marketing statements are taken into account to the extent provided by law; a completeness clause does not exclude mandatory liability for a misleading description.
30.4. Any additional rights of a Technology Provider as a third-party beneficiary apply only where required by an applicable licence and disclosed for the Route. The agreement does not give an indeterminate class of persons an independent right to charge the User or manage the User’s Account.
30.5. Support, payment, refunds, content complaints, and personal-data requests: support@cicora.ai, +998 90 051 48 40. Provider: RIZZ TRADE Limited Liability Company / “RIZZ TRADE” LLC, TIN 312432714, registration entry 2944991 dated 15 September 2025, OKED 62010. Address: Republic of Uzbekistan, Tashkent, Mirabad District, Abdulla Avloniy MFY, Nukus Street, Building 3.