LYNX AI User Agreement

Version v5.5 dated 11 October 2026.

Provider: LYNX AI limited liability company (LYNX AI LLC), Tax ID (STIR) 313122838, registered address: Republic of Uzbekistan, Tashkent city, Chilanzar district, Qozirobod MFY, Choʻponota koʻchasi, 10b-uy. Website: https://lynx-ai.uz/. Platform: https://crm.lynx-ai.uz/. Contact address: contact@lynx-ai.uz. Phone: +998 33 769 69 09. Registration details are set out in the Provider Details (in Uzbek).

This Agreement sets out the terms on which the Service is accessed and used.

1. Terms and subject matter

1.1. "Service" means the LYNX AI software products made available through the website, the account dashboard and the supported connections. Depending on the account type, the plan and the Order, the Service may include:

(a) text agents that respond to enquiries and perform configured actions in connected channels;

(b) voice assistants and the Lynx Voice speech features;

(d) knowledge bases, quality assessment of conversation recordings and analysis of dialogs;

(e) features for creating and processing text, audio and other materials;

(f) the application programming interface (API) and integrations with other programs.

The specific features, channels and restrictions are determined by the Order. A reference to a product category does not mean that all of its features are provided.

1.2. "Client" means a person who has accepted this Agreement on registration and, in the case of paid access, also an Order, either personally or through an authorised representative. "Business Client" means a Client that uses the Service for business, professional or other organisational activity. "Consumer" means a Client who is an individual and acquires access for personal needs not connected with making a profit. The name of a plan and the account type do not restrict the mandatory rights of a Consumer. "Client Users" means persons to whom the Client has granted access to its account or workspace. "Interlocutors" means persons who interact with the Client's agents, bots, voice assistants and channels. The Provider does not enter into contractual relations with Interlocutors in connection with the Client's use of the Service; interaction with them is conducted on behalf of the Client, and the Client is responsible to them for the content and consequences of such interaction. The obligations that the law imposes on the Provider as a person processing data on instruction remain in force.

1.3. "Client Materials" means messages, files, recordings, instructions, knowledge bases and other materials provided by the Client or received for it through connected channels and programs. This definition does not transfer the rights of other persons to the Client and does not replace any required permissions. "Output" means text, audio, an image, an analytical conclusion or other material created by the Service for the Client. "Agent" (assistant) means a software function that handles enquiries and performs actions permitted by the Client. "Integration" means a connection of the Service to a channel or another program chosen by the Client. "Order" means the access terms displayed and confirmed when ordering: the selected features, plan, price, term, usage units, usage volume and restrictions. "Enterprise" means an individual contract or supplementary agreement concluded between the Provider and a Business Client by signing a single document, including with an electronic digital signature, or by exchanging electronic documents signed by authorised persons of the parties. Enterprise terms cannot be agreed through correspondence with support or sales staff, in a chat or orally. "Meta Channels" means WhatsApp, Messenger and Instagram connected to the Service through the official application programming interfaces of the Meta group of companies ("Meta"). "Platform Data" means information that the Provider receives from Meta in the operation of Meta Channels, including user identifiers and profile information, the content of messages and attachments, delivery and read information and access keys, as well as information derived from them. The term "Balance Units" has the meaning given to it in the Public Offer (section "Price and payment").

1.4. The Service is provided through the following account types:

(a) a "Personal Account" is opened for an individual to use the features designated for this account type in the plan description. The owner of a Personal Account is deemed a Consumer unless, when placing an Order, the owner stated that access was being acquired for business or other professional activity;

(b) a "Team Account" is opened for a legal entity or an individual entrepreneur for business or other professional activity after the application has been approved in accordance with clause 2.4. The person submitting the application represents the status of the organisation or individual entrepreneur, that person's authority and the use of the Service for those purposes. The owner of a Team Account, as well as a Client who, when placing an Order, provided the Tax ID (STIR) of an organisation or individual entrepreneur or requested an invoice made out to an organisation, is a Business Client;

(c) Enterprise terms are provided to a Business Client under a written contract. Connection of voice assistants to the Client's own PBX and communication channels, individual availability levels and other individual terms are provided only under Enterprise terms.

The features of each account type are stated in the plan description.

1.5. The scope of access is determined by the plan and the Order. An announcement of a future module does not establish its release date or its inclusion in the current plan. The designation "24/7" describes the assistant's automated mode of operation. Individual availability levels, support timeframes and other additional obligations apply only under Enterprise terms. The Service is not intended for contacting emergency services, sending emergency alerts or obtaining urgent assistance.

2. Conclusion of the contract

2.1. This Agreement is accepted on registration by ticking a box that is not pre-ticked or by another explicit action that is recorded, after access has been provided to the current version and the documents forming part of it. Acceptance covers the terms of use, the applicable terms of the selected features and the mandatory data processing and security rules within their respective scope. Registration and use of the Service are permitted only to persons who have reached the age of 18; on registration, the user confirms having reached that age. No access arrangement is provided for persons under 18. If the Provider becomes aware that an account has been opened by a person under 18, the Provider may suspend access and terminate the contract; the price of unused paid access and of unused paid Balance Units is refunded to the person who made the payment or to the legal representative in the manner set out in the Public Offer. A representative of an organisation confirms that they are authorised to act on its behalf.

2.2. Registration and free testing do not create an obligation to pay for a plan. A paid Order is placed under the Public Offer after the scope of access, price, currency, period, limits and the terms of additional charges and renewal have been displayed.

2.3. The Provider retains the accepted version and the information necessary to confirm the conclusion of the contract.

2.4. Team Account features are provided after the Provider has reviewed the application. The Provider may request information on state registration, the Tax ID (STIR) and the applicant's authority. The Provider may refuse to approve an application or to conclude a new contract if the information in the application is inaccurate or unconfirmed; if the declared activity or scenario is contrary to the Acceptable Use Policy or to the terms of the platform to be connected; if a contract with the applicant was previously terminated by the Provider in connection with a breach that has not been remedied; if granting access creates a threat to the security of the Service or there is no technical possibility of providing the requested features; or if required by law. The applicant is notified of the decision through the account dashboard or at the email address of the account; the reason for a refusal is given unless this is contrary to law or creates a security threat. Until the application is approved, only Personal Account features are available, and payment for Team Account features is not accepted.

2.5. The contract between the Provider and the Client consists of this Agreement, the Public Offer and the Order (for paid access), the Lynx Voice Supplemental Terms (where Lynx Voice is used), the Data Processing Agreement (where data is processed on the Client's instruction), the Acceptable Use Policy and the Security Policy, as well as Enterprise terms, if concluded. The Privacy Policy and the Cookie Policy apply within their respective scope. In case of discrepancy between the documents, they apply in the following order of precedence: Enterprise terms, to the extent expressly stated in them; the Data Processing Agreement, on matters of processing on instruction; the Lynx Voice Supplemental Terms, on matters of Lynx Voice; the Order, as regards the selected features, price, term, limits and usage units; the Public Offer, on matters of paid access; this Agreement; other documents. An Order placed outside Enterprise terms selects parameters provided for in the Public Offer and does not amend the general terms of the contract. An invoice establishes the price, the composition of the Order and the payment details and does not by itself amend other terms of the contract. Mandatory rules of law apply irrespective of this order of precedence.

2.6. The Acceptable Use Policy, the Security Policy, the Privacy Policy and the Cookie Policy apply to all users and plans within the relevant features and actual processing. Where data is processed on the Client's instruction, the Data Processing Agreement forms part of the contract regardless of the plan and does not require a separate purchase or signature. Enterprise terms may specify or strengthen measures and safeguards but do not override these documents, mandatory requirements of law or the rights of data subjects. The application of new versions is governed by section 11. Acceptance of the contract does not replace separate consent where such consent is required by law. Access is not provided without acceptance of the applicable contractual terms; refusal of optional processing does not restrict features for which it is not needed.

2.7. The parties acknowledge that registration, acceptance of a version of the contractual documents, confirmation of an Order, a recurring charge authorisation and other actions performed in the account dashboard after logging in with the Client's credentials, or through the API using an access key issued to the Client, are electronic documents originating from the Client and are equivalent to paper documents bearing a handwritten signature. Acceptance of a version or an Order through the API is permitted if the relevant text was provided before such action. On behalf of an organisation, such actions are performed by the account owner and by administrators to whom the Client has granted the relevant authority; their actions are deemed actions of the Client. Information automatically recorded by the Service, including information on registration, acceptance of versions, the number and checksum of the version displayed, confirmation of Orders and of charge authorisations, logins to the account, actions of users, agents and access keys, usage volume and notices sent, reflects the facts recorded in it unless proven otherwise. Information on registration, acceptance of versions, confirmation of Orders, recurring charge authorisations, usage volume and notices sent is kept by the Provider unaltered for the term of the contract and for three years after its termination, unless the law requires its earlier destruction. Information on logins to the account and on actions of users, agents and access keys is kept for the periods established by the Privacy Policy (section "Retention and destruction"), and information relating to a claim or dispute that has been raised is kept until the claim or dispute is resolved. At the Client's request, the Provider provides an extract from the information kept. The Client may challenge an incorrect record.

3. Rights to software and materials

3.1. The Service is provided by way of remote access to the Provider's software, which runs on computing resources used by the Provider. Copies of the Provider's computer programs, models and databases are not transferred to the Client, except for the Client Components. "Client Components" means the program code of the web widget, libraries and program code samples for connecting to the API of the Service, as well as documentation, which the Provider makes available to the Client for embedding in its website, application or other program.

3.1.1. During the access period, the Client may use the Service for its intended purpose through the interfaces provided and the API provided for by the plan, within the features, number of users and limits of the Order.

3.1.2. For the access period, the Provider grants the Client a simple (non-exclusive) licence to the Client Components. The licence includes the right to reproduce the Client Components and to place them on the Client's websites and in its applications and programs to the extent necessary to connect to the Service, as well as to adapt them for such connection. The licence is valid in the territory of all states in which use of the Service is not prohibited by law. The Client may give access to the Client Components to persons performing connection work commissioned by the Client, without the right for those persons to grant sublicences. The remuneration for the licence is included in the access price; under free access, the licence is granted free of charge.

3.1.3. The exclusive rights to the software, models, interfaces, documentation, agent templates, databases and other results of intellectual activity forming part of the Service, including their updates and modifications, belong to the Provider or to third parties that have granted the Provider the right to use them. Rights not expressly granted to the Client under the contract are not granted to the Client. Source code, models and internal documentation are not transferred to the Client. Rights to the results of individual work are determined by Enterprise terms.

3.2. Rights to Client Materials remain with the Client and with the persons who provided such materials to it. For the performance of the contract, the Client grants the Provider a simple (non-exclusive) licence, free of charge, to use Client Materials in the following ways:

(a) reproduction, including recording in computer memory, storage and making backup copies;

(b) adaptation, including speech recognition, translation, summarisation, format conversion, converting text to speech and creating Outputs on the basis of Client Materials;

(d) communicating them to Interlocutors and other recipients whom the Client designates in the settings of agents, channels and Integrations.

3.2.1. The licence is granted solely for providing the Client with the features it has selected, carrying out its lawful instructions, ensuring the security of the Service and preventing abuse, and performing the Provider's obligations established by law. The licence does not give the Provider the right to publish Client Materials on its own initiative, to use them in its advertising, to transfer them to third parties for those third parties' own purposes, or to use them to train artificial intelligence models, except in the case provided for in clause 5.4; in respect of Platform Data, such use is excluded entirely.

3.2.2. The licence is valid in the territory of the Republic of Uzbekistan and of other states in which computing operations are performed in accordance with the Privacy Policy and the Data Processing Agreement, for the term of the contract and, after its termination, for the period necessary to complete processing, carry out the Client's request for export, destroy the data in the established manner and perform the Provider's obligations established by law.

3.2.3. The Provider may grant the right to use Client Materials to persons engaged by it to perform the contract, within the limits and for the purposes specified in clause 3.2.1. The Provider is liable for the actions of such persons as for its own.

3.2.4. Deletion of an item of Client Materials in the Service or at the Client's request terminates the licence in respect of that item, except for copies whose retention is permitted by law, for the period and in the manner provided for in the Privacy Policy.

3.2.5. The licence does not replace consents and other grounds for processing personal data contained in Client Materials. Such processing is governed by the Privacy Policy and the Data Processing Agreement.

3.3. The Provider does not claim any rights in Outputs. If an exclusive right in an Output arises in favour of the Provider, it passes to the Client in full at the moment the Output is created; the payment for such transfer is included in the access price, and under free access the transfer is free of charge. The Client may use an Output in any manner not prohibited by law, subject to the restrictions of the selected feature of which the Client was notified before the Output was created.

3.3.1. An Output created automatically without human creative contribution may not be an object of copyright. The Provider does not guarantee that an Output is protected by law, is unique or does not infringe the rights of third parties, except where an infringement is caused by the actions of the Provider. Similar or identical Outputs may be created for other users; the Client's rights in its Output do not extend to the Outputs of other users.

3.3.2. Rights in an Output do not include rights in the software, models, standard voices, templates and other components of the Service by means of which the Output was created.

3.4. The Client ensures that it has the rights to the materials provided and to use them in the chosen manner. Processing a recording, reproducing another person's voice and using a person's identity require the permissions provided for by law.

3.5. The Client may use lawful Outputs in its products, present its agents to Interlocutors under its own name and designations subject to clause 5.3, and connect users through the API provided for by the plan. A person who configures the Service at the request of another person does so in that person's account or on the basis of that person's authority. Resale of access to the platform itself, providing the platform to third parties as a stand-alone product and providing it under another brand are permitted only under Enterprise terms.

3.6. The Client must not perform, and must not permit third parties to perform, any of the following actions:

(a) circumventing payment, limits, technical protection measures and access controls;

(b) copying, modifying and distributing components of the Service, except for the Client Components within the limits of clause 3.1.2;

(c) decompiling, disassembling and otherwise examining the code of the Provider's programs, except where the law permits a person lawfully in possession of a copy of a program to decompile it without the right holder's consent in order to achieve interoperability with other programs, subject to the conditions established by law and after the Client has requested the necessary interoperability information from the Provider;

(d) extracting system instructions, parameters and other internal information of the Provider's models, agents and templates, including by means of queries aimed at disclosing them; instructions that the Client has itself set for its agents are not such information;

(e) systematically extracting Outputs or other data of the Service in order to create, train or improve artificial intelligence models, programs or databases that compete with the Service;

(f) accessing the Service by automated means other than through the API provided for this purpose;

(g) extracting data of other users and interfering with the operation of the Service.

3.7. The Client may send the Provider comments, ideas and proposals about the Service ("Suggestions"). The Provider may use Suggestions free of charge to develop its products, without any obligation to implement them. To the extent that a Suggestion is a protected work, the Client grants the Provider a simple (non-exclusive) licence, free of charge, to reproduce it, adapt it and incorporate it into the Provider's products in the territory of all states for the term of the exclusive right, with the right to grant such right to persons engaged by the Provider for development. This clause does not apply to Client Materials, personal data or protected materials of third parties. Public use of the Client's name, logo or materials requires the Client's permission.

3.8. The Client may use the name LYNX AI, the names of models and features of the Service, logos and other designations of the Provider only to state truthfully that it uses the Service. Without the Provider's written consent, the Client must not include these or similar designations in the names of its products, domain names or accounts and must not state that its products or agents are created, endorsed or guaranteed by the Provider. Access to the Service does not grant any other rights to the Provider's designations.

3.9. The Client may conduct comparative tests of the Service for its own needs subject to clause 3.6 and the Acceptable Use Policy. The results of such tests may be published if the date of the tests, the plan, features and settings used, and a methodology sufficient to verify the results are stated. Tests must not create a load exceeding the limits of the Order.

3.10. The Provider may use depersonalised technical information about the operation of the Service, including load indicators, errors and aggregated statistics on the use of features, to ensure the operation and security of the Service and to improve it. Such information does not include the content of the Client's messages, audio recordings and documents, or Platform Data.

4. Account and authority

4.1. The Client is responsible for the accuracy of account information, the protection of credentials and access keys, and the granting and revocation of access. Actions of Client Users within the authority granted to them are deemed actions of the Client. For a Business Client, actions performed using an API access key issued to it are deemed actions of the Client until the key is revoked in the account dashboard or until the Provider receives a notice that the key has been compromised, unless it is proven that the key became available to other persons as a result of the Provider's breach of its security obligations. No fee is charged for usage made with a Consumer's key after the Provider receives a notice that the key has been compromised or after the key is revoked in the account dashboard. In other disputes concerning unauthorised access, the circumstances of the event and the actions of both parties are taken into account.

4.2. A workspace administrator manages access and sees data within the organisation's settings. The Client ensures that monitoring of its employees is lawful and that the necessary notice is given. When access is restored or transferred, where there are reasonable doubts as to authority, or where a mandatory requirement of law so provides, the Provider may request the necessary confirmation of identity, authority and account ownership. Disputed operations may be suspended pending verification. The scope of the information requested must correspond to the purpose of the verification.

4.3. The Client determines the agent's tasks, the information available to it, permitted actions, message recipients, spending limits and the procedure for confirming operations. An agent may respond to an enquiry, or run on a schedule or upon a configured event, without a new instruction for each action. Enabling such a scenario constitutes an instruction to perform the operations provided for in it within the established limits. An agent is not an independent party to the contract or a representative with authority of its own. Entering into transactions, payments, irreversible deletion and other material actions require human confirmation by an authorised person, except for specific lawful scenarios separately enabled by the Client with established limits. Mandatory requirements concerning representation, banking operations and human oversight continue to apply.

4.4. Before launch, the Client checks the instructions, the information used, the range of recipients, permitted actions and the procedure for handing an enquiry over to a staff member. During use, the Client monitors the operation of the agent and suspends an erroneous or suspicious scenario. The content of a file, message or website received does not extend the agent's authority. For a Business Client, actions of an agent within the authority configured by the Client, including actions triggered by the content of incoming messages, files or websites, are deemed actions of the Client unless it is proven that the event was caused by the Provider's breach of its own security obligations. In relations with a Consumer, liability is determined by the circumstances of the event and the breach of obligations by each party.

4.5. The Client independently determines its offers, prices, transaction terms, recipients and the content of communications. Use of the Service does not make the Provider a party to the Client's transactions and does not entitle the Client or its agent to assume obligations on behalf of the Provider. The Provider's own obligations to the Client remain in force.

5. Use of artificial intelligence

5.1. Outputs may contain errors, including speech recognition errors, and inaccurate information. The Client verifies material facts, rights of use and the suitability of an Output for its purpose. Generation of a response does not constitute the provision of a medical, legal or other professional opinion. An agent's responses are generated on the basis of the instructions, knowledge base and other information provided by the Client. For a Business Client, the consequences of decisions it takes on the basis of Outputs, and of agent responses that are consistent with the information and settings provided by the Client, are borne by the Client in the absence of a breach by the Provider of its obligations.

5.2. Taking decisions that have legal significance and affect the rights of a person solely on the basis of conclusions of artificial intelligence is not permitted. The Client ensures appropriate human oversight and compliance with other mandatory requirements.

5.3. The Client ensures that every Interlocutor, before the substance of the enquiry is discussed, is clearly informed that a software assistant is interacting with them and, where recording is enabled, also of the conversation recording and its processing, including automatic transcription and assessment. In a voice dialog, the notice is spoken at the beginning of the conversation; in a text channel, it is contained in the greeting or in the channel description available to the Interlocutor before the assistant's first response. The Client may change the wording of the notice while preserving its meaning, but must not disable or distort it. The assistant must not claim to be a human or deny its automated nature in response to an Interlocutor's question. The disclosure requirements of this clause do not apply to messages that an employee of the Client has reviewed and sent in their own name. The Client itself obtains the consents required for recording, data processing and sending messages, and keeps evidence of obtaining them for the period of use and for at least three years after it ends. The Provider does not check whether Interlocutors' consents and notices exist and is not liable for the consequences of their absence unless the Provider itself is in breach. It is prohibited to mislead an Interlocutor as to the person on whose behalf the interaction is conducted, or to use a synthetic voice or another person's identity for deception.

5.4. The Provider does not use Client Materials, the content of messages, audio recordings and documents processed on the Client's instruction to train or improve artificial intelligence models. Such use is permitted only under Enterprise terms and with the consent of the data subjects for that purpose. Platform Data is not used to create, train or improve artificial intelligence models, regardless of any permission of the Client. Processing of a message by a model in performing the Client's task is not model training.

5.5. Assessments of the quality of dialogs and of employees' work, assessments of an Interlocutor's interest, classification of enquiries and other automated conclusions of the Service ("Automated Assessments") are of an auxiliary nature. The Client must not take, solely on their basis, decisions on hiring, disciplinary liability, termination of an employment contract or changes in remuneration, or decisions to provide an individual with goods, works, services, credit or other benefits or to refuse them. Before such a decision is taken, an authorised employee of the Client checks the Automated Assessment against the original recording and other information and considers the objections of the person concerned.

5.5.1. Before applying Automated Assessments to its employees, the Client notifies them of this in the manner established by law and ensures that they are able to obtain explanations and raise objections.

5.5.2. The assessment criteria are determined by the Client. The Provider is not a participant in decisions taken by the Client using Automated Assessments; this does not release the Provider from liability for breach of its own obligations.

6. Integrations, external channels and communications

6.1. The Client connects only accounts and data that it is entitled to manage, complies with the rules of connected platforms and obtains the necessary permissions for messages, recording and data transfers. The Provider uses the permissions granted for the selected feature. The Client may disconnect an Integration and revoke access.

6.2. The operation of an Integration depends on the platform's rules, the region, the account and the available connection. Changes may require a feature to be restricted or disabled. Where paid access is materially affected, clauses 8.2 and 9.8 apply. Whether a scenario is permitted in a particular channel is determined by the rules of that channel. Meta's rules do not permit WhatsApp to be used to provide access to artificial intelligence as the primary function of the channel, including a general-purpose digital assistant unrelated to the Client's goods, works and services.

6.3. Under the contract, access is provided to software and computing functions. The Provider is not a telecommunications operator or provider, does not provide communication services, does not allocate, sell or resell subscriber numbers, communication channels or carriage of traffic, and does not provide access to telecommunications networks, including the telephone network. The Client's own PBX and communication channels belong to the Client or are used by it under its contracts with a communications operator, which the Client concludes and pays for independently. The Service is connected to the Client's own PBX and communication channels only under Enterprise terms and the Lynx Voice Supplemental Terms. The "processing minute" unit serves to account for software processing and is not a unit of communication services.

6.4. If the Client independently connects a third-party program, model or channel under its own contract with its owner, the Client's relations with that owner are governed by separate terms. Before connecting, the Client checks the access being granted and whether the data transfer is permissible. This rule does not release the Provider from its obligations regarding built-in features and persons engaged by the Provider itself to perform the contract. Webhook recipients, the Client's own programs, models and other systems that the Client connects to the Service at its own choice and under its own contract with their owners act on behalf of the Client and are not persons engaged by the Provider. Data is transferred to such systems on the Client's instructions, and the Client ensures the lawful ground for such transfer.

6.5. The Provider's obligations to ensure the operation of the Service are performed within the software and computing infrastructure used by the Provider, up to the transfer of a message, audio stream or other data to an external channel or to the Client's system, and from the moment they are received from such channel or system. Internet access of the Client and Interlocutors, the operation of the networks and services of communications operators, of the Client's own PBX, communication channels and other equipment, and the operation of messengers, social networks and other platforms that the Client connects under its own contract with their owner ("External Channels") are outside the scope of the Provider's obligations. Interruptions, delays, restrictions and failures of External Channels, including those caused by decisions of their owners, communications operators or state bodies to restrict or slow down networks and resources, do not constitute non-performance of the contract by the Provider unless they are caused by the Provider's breach of its obligations. The Provider assists the Client, within the means available to it, in restoring the operation of an External Channel. The rule in this clause does not apply to persons engaged by the Provider to perform the contract; the Provider is liable for their actions in accordance with section 10.

6.6. Messengers, social networks, customer relationship management systems, the Client's own PBX and communication channels, payment and other services connected by the Client are provided by their owners on their own terms, which the Client accepts independently and complies with as in force from time to time. In a connected service, the Provider performs operations on behalf of and on the instructions of the Client within the permissions granted. The Client connects third-party services by the methods provided for in the Service and must not give the Provider the passwords to its accounts in third-party services unless the Service provides for such a method of connection. The Client's accounts on Meta platforms and on other platforms whose rules prohibit sharing credentials with third parties are connected only through the official application programming interfaces and the permissions granted through them; passwords to such accounts are not given to the Provider. The Client creates, stores and replaces access keys and other connection credentials in accordance with the requirements of the owner of the relevant service and the Security Policy.

6.7. Meta Channels are provided only to Business Clients for communication with their customers and other persons in connection with the Business Client's business, professional or other organisational activity; Meta Channels are not connected to a Personal Account. The Client's accounts, Pages, phone numbers and business accounts on Meta platforms belong to the Client. The Provider obtains access to them within the permissions that the Client grants in the manner established by Meta and does not restrict the Client's direct access to them. Revocation of permissions or disconnection of a channel stops the relevant features.

6.8. When using a Meta Channel, the Client complies with Meta's terms and rules applicable to that channel as in force from time to time, including the Meta Platform Terms, the Meta Developer Policies, Meta's and WhatsApp's terms for the WhatsApp Business Platform, the WhatsApp Business Messaging Policy, the Meta Commerce Policies, the Instagram Terms of Use and the community rules of the relevant platform. The Client accepts these terms directly in its relations with Meta. Where Meta so requires, the Client accepts the Meta Platform Terms in the manner specified by Meta. A change in Meta's terms does not amend the contract between the Client and the Provider; its effect on the availability of features is determined by clauses 6.2 and 8.2.

6.9. By connecting a Meta Channel, the Client instructs the Provider to use Meta's application programming interfaces on the Client's behalf to receive and send messages and to manage message templates and channel settings within the selected features and the permissions granted. The Client represents that it holds the rights and consents necessary to transmit Client Materials through the Meta Channel on Meta's terms. The Provider processes Platform Data only to carry out this instruction, in accordance with the Data Processing Agreement and the Acceptable Use Policy.

6.10. The Provider may immediately restrict or terminate the Client's access to a Meta Channel at Meta's request, and also where there are reasonable indications that the Client has breached Meta's terms or the Acceptable Use Policy (section "Meta Channels"), if such breach may result in restriction of the access of the Provider or other clients to the Meta platform. The Provider informs the Client of the grounds where this is permitted by law and Meta's rules. If the restriction is not caused by a breach on the part of the Client, clause 8.2 applies.

6.11. Meta independently reviews accounts and message templates, sets limits, restricts or blocks accounts, numbers and Pages, and sets fees for messages. The Provider is not liable for such decisions of Meta or their consequences unless they are caused by the Provider's breach of its obligations, and assists the Client, within the means available to it, in challenging them. Message fees are charged by Meta to the Client under Meta's rules and are not included in the price of the Service unless otherwise stated in the Order.

6.12. At Meta's request, the Provider may provide Meta with information about the Client that has connected a Meta Channel and about its contact person, as well as information on the processing of Platform Data, to the extent provided for by Meta's terms and in compliance with the requirements of personal data legislation.

7. Data and confidentiality

7.1. Data processing is governed by the Privacy Policy. The Data Processing Agreement also applies to processing on the Client's instruction, regardless of the plan. The Client ensures the lawfulness of the transfer and of its instructions. The Provider performs the obligations relating to its role. The rules on protection, use, storage and destruction of data apply throughout the processing; termination of access or of the contract does not cancel continuing obligations.

7.2. Each party uses the other party's non-public information to perform the contract and gives access to it only to persons who need it and are bound to maintain confidentiality. The exceptions cover publicly available information, information lawfully obtained independently and mandatory disclosure under law. The other party is notified of a forthcoming mandatory disclosure where this is permitted by law and practicable.

7.3. Storage, export and destruction are carried out taking into account the purpose of processing, the settings, the contract and the law. Mandatory destruction of personal data may not be delayed solely because of the Client's outstanding debt.

8. Operation and changes of the Service

8.1. The Provider ensures the agreed functionality and remedies confirmed faults in accordance with the contract and the law. The Provider may engage third parties to perform the contract, remaining responsible for its obligations and complying with data processing requirements. Additional individual levels of availability, redundancy and support are established only by Enterprise terms. Without such terms, no particular commercial result, absolute accuracy and uniqueness of Outputs or continuous error-free operation is guaranteed. Limitations of free features are communicated before use; clause 8.5 applies to Test Features. Mandatory statutory guarantees remain in force.

8.2. The Provider may update the Service. The Provider notifies the Client of a material reduction of paid functionality at least thirty calendar days in advance, except where an immediate change is required by law, by the rules of a connected platform or to eliminate a security threat; the Client may agree on a replacement or withdraw from the affected Order with a refund of the fee for the part not provided. Discontinuation of a feature for all Clients is carried out under clause 9.9. Planned maintenance is accompanied by notice where practicable; urgent protective measures may be applied immediately.

8.3. To ensure stable operation and prevent abuse, the Provider may set limits on request frequency, concurrent operations and the size of materials processed. Ordinary limits are stated in the plan, the feature description or the Order. Temporary protective limits are permitted where systems or data are under threat. Their introduction does not give the right to charge unagreed additional fees or arbitrarily reduce the paid volume; where paid access is materially reduced, clause 8.2 and the Public Offer apply.

8.4. The names of models and features of the Service, including Lynx Spark, Sage, Pulse, Apex, Lynx Velvet and Lynx Radar, designate software functions that the Provider provides under its own name. Such functions may use software components, models and computing resources of third parties made available to the Provider under contracts with them. The Provider is responsible to the Client for the features of the Service. The names of persons engaged by the Provider are disclosed in the cases and to the extent provided for by law.

8.5. Features designated in the Service as test or preview features ("Test Features") are provided for familiarisation and evaluation. The Client is informed of the status of a Test Feature before it is enabled. No availability levels are set for Test Features, and the Provider may change or discontinue them, notifying the Client where practicable. A fee for a Test Feature is charged only if it is expressly stated before connection; if a paid Test Feature is discontinued, the fee for the period not provided is refunded. Outputs of Test Features are not used for material decisions without human review. The Privacy Policy and the Data Processing Agreement apply in full to data processed in Test Features.

8.6. A Business Client informs the Provider of an interruption in operation or another defect of the Service within thirty calendar days from the moment it became aware or should have become aware of it, stating the time of the event, the affected feature and the information available. In determining the extent of the Provider's liability, account is taken of the fact that late notice deprived the Provider of the opportunity to remedy the defect in good time and to reduce its consequences.

9. Breaches, suspension and termination

9.1. The Client must comply with the law, the contract and the Acceptable Use Policy. The following are prohibited: use of the infrastructure for unlawful activities, fraud, malware, unauthorised access, unlawful mass messaging and infringement of third-party rights.

9.2. The Provider may suspend performance of its obligations in whole or in part by restricting a particular access key, Integration, scenario, agent, channel or the account as a whole, in the following cases:

(a) non-payment or partial payment of an Order by the due date;

(b) breach by the Client of this Agreement, an Order or the Acceptable Use Policy;

(c) reasonable indications of unauthorised access, fraud, sending of messages without the recipients' consent or another threat to the security of the Service, data or third parties;

(d) a demand of the owner of a connected platform, a communications operator or a competent state body relating to the Client or its scenario;

(e) failure by the Client to provide, within the set period, confirmations requested in accordance with the contract.

The restriction applies to the part of the Service whose restriction is sufficient to eliminate the ground; if it is sufficient to restrict a particular key, Integration, scenario, agent or channel, the account as a whole is not restricted.

9.3. In the cases specified in sub-clauses (a), (b) and (e) of clause 9.2, the Provider, before suspension, sends the Client a notice stating the ground and the period for remedying it, which is at least three working days for non-payment and at least five working days in other cases. In the cases specified in sub-clauses (c) and (d), and also where a breach has resulted or may result in restriction of the access of the Provider or other clients to a connected platform, the restriction is introduced immediately and the notice is sent no later than the next working day, unless notification is prohibited by law or by a demand of a competent authority.

9.4. Access is restored no later than the next working day after the ground has been eliminated. Suspension on grounds that arose through the fault of the Client does not extend the paid period and does not entail recalculation of the fixed fee for that period.

9.5. The Provider may retain the necessary information about a breach and cooperate with competent authorities on lawful grounds. The period, scope and disclosure of such information are determined by law and the purpose of its retention. The Client must cease the breach and assist in establishing the circumstances within its authority. A restriction may be challenged by sending a request to contact@lynx-ai.uz; where there is no ground for the restriction, access is restored. A breach does not automatically entail retention of the entire unused advance payment.

9.6. The Provider does not carry out a preliminary legal review of each material, scenario or action of the Client unless such an obligation is provided for by law or the contract. Technical processing, security checks or the provision of access do not mean approval of the lawfulness of the Client's materials and actions. This clause does not cancel the obligations of the Provider, established by law and the contract, to respond to breaches.

9.7. The Provider may unilaterally withdraw from the contract in whole or as regards the affected feature by sending a notice to the Client, if:

(a) a ground for suspension that arose through the fault of the Client has not been eliminated within thirty calendar days;

(b) within twelve months, the Client has again committed a breach that served as a ground for suspension;

(c) the Client has materially breached the Acceptable Use Policy, the terms of a connected platform or the requirements of law when using the Service, including by committing fraud, distributing malicious code, gaining unauthorised access to data of other persons or using the Service for activities prohibited by law;

(d) payment is more than thirty calendar days overdue;

(e) the Client has provided inaccurate information about itself or its authority that is material to the conclusion or performance of the contract;

(f) infringements of third-party rights to materials, voice or image have been confirmed in relation to the account on more than one occasion.

Withdrawal on these grounds is deemed to be caused by the culpable actions of the Client. The contract is deemed terminated or amended from the date specified in the notice. An unused monetary prepayment is refunded less the Client's debt and the Provider's documented losses; in relation to a Consumer, deductions are made only in the cases and in the manner established by law.

9.8. If provision of a feature becomes impossible as a result of termination or change of access to a connected platform by decision of its owner, a requirement of law, an act of a state body or other circumstances for which the Provider is not responsible, the Provider's obligation terminates to the corresponding extent. The Provider notifies the Client within a reasonable time and refunds the fee for the unused period of the affected feature or, at the Client's choice, provides an equivalent volume of another feature.

9.9. The Provider may discontinue a feature for all Clients by notifying them at least thirty calendar days in advance. Discontinuation takes effect at the end of the paid period of the affected feature. If the paid period ends later than three months after the notice, the Provider, at the Client's choice, provides the affected feature or an equivalent volume of another feature until the end of that period, or refunds the fee for the unused period. Orders for the affected feature are not renewed after the notice.

9.10. The Client may withdraw from the contract at any time by disabling renewal and sending a notice through the account dashboard or to contact@lynx-ai.uz. The consequences of withdrawal for the paid period are determined by the Public Offer (section "Suspension, termination and refunds").

9.11. Free access may be changed or terminated by the Provider with at least thirty calendar days' notice, and in the event of a breach or a security threat, in the manner set out in clauses 9.2 and 9.3. A free account with no login and no use for twelve months may be closed after a notice sent to the email address of the account at least thirty calendar days in advance; the data of such an account is destroyed in the manner provided for in the Privacy Policy.

9.12. The Client represents that neither the Client nor the persons controlling it are persons subject to restrictive measures that prevent the provision of the Service to them or the making of settlements with them under the legislation of the Republic of Uzbekistan or decisions binding on the Provider. If a person engaged by the Provider to perform the contract, or a payment organisation, refuses to serve the Client because of restrictive measures applicable to them, the Provider may restrict the affected features. The Client is refunded the fee for access not provided, and the other features continue to be provided in the same scope, if this is technically possible.

9.13. The parties' obligations relating to payments, confidentiality, protection and destruction of data, liability and dispute resolution survive termination of the contract until they are performed.

10. Liability

10.1. Each party is liable for non-performance or improper performance of its obligations. The Client is responsible for the lawfulness of its materials, scenarios, instructions and messages, and for the actions of Client Users and of agents within the authority it has configured. The Provider is not liable for the Client's independent actions in the absence of a breach by the Provider itself. In relations with a Business Client, the Provider is liable where it is at fault and is deemed not at fault if it proves that it took all measures within its power to perform the obligation properly. The Provider is liable for the actions of persons engaged by it to perform the contract as for its own.

10.2. In relations with a Business Client, the Provider compensates only actual damage caused by breach of its obligations. Lost profit, including lost income and loss of customers, transactions and business reputation, and the costs of switching to another product are not compensated. Damage from loss of or damage to data is compensated within the limits of the reasonable costs of restoring the data from the latest backup copy of the Provider or the Client.

10.3. The Provider's aggregate liability to a Business Client for all claims relating to the contract and based on events occurring within twelve consecutive months does not exceed the amount of payments made by the Client for the affected feature in the three months preceding the first of such events. If that amount is less than the price of one monthly period of access to the affected feature, the limit is equal to the price of one monthly period. Where payment is made for a period longer than one month, the price of a monthly period is determined pro rata to the price of the paid period. For a one-off Order, the limit is equal to the price paid for that Order. If no separate price is set for the affected feature, the price of the plan or Order that includes it applies. If the law establishes a lower limit of liability for the relevant obligation, that limit applies.

10.4. Refunds of erroneously charged amounts and of fees for access not provided are made in addition to the limit set by clause 10.3 and do not reduce it. The same loss is not compensated twice; amounts refunded or set off in connection with an event are counted towards compensation of the losses resulting from it.

10.5. The limitations in clauses 10.2 and 10.3 do not apply to liability for intentional breach of an obligation, for harm caused to life or health, or in other cases where the law does not permit liability to be limited by agreement of the parties. If the law establishes for the relevant obligation an amount of liability that cannot be reduced by agreement of the parties, that amount applies. Increased liability of the Provider may be established only by Enterprise terms.

10.6. For features provided free of charge and for Test Features, the Provider is liable to a Business Client only for intentional breach and for harm to life or health.

10.7. In relations with a Consumer, the Provider's liability is determined by law. The limitations established for a Business Client do not apply to a Consumer; a Consumer may claim compensation for losses in the manner and amount provided for by law.

10.8. A Business Client compensates the Provider for losses caused by claims brought against the Provider by third parties, including Interlocutors, right holders, owners of connected platforms, communications operators and competent authorities, if such claims are directly caused by the Client's breach of its obligations under the contract or of the requirements of legislation, in particular by:

(a) the unlawful content of Client Materials and of messages sent under its scenarios;

(b) the absence of the necessary consents of Interlocutors, or of notice to them of interaction with a software assistant, of conversation recording and of data processing, as well as the absence of a lawful ground for entrusting the processing of data to the Provider;

(d) breach of the terms and rules of a connected platform;

(e) breach of the requirements for the use of the Client's own PBX and communication channels, including failure to protect them against unauthorised use;

(f) unlawful actions of Client Users and of agents within the authority configured by the Client, and actions performed using access keys issued to the Client, which under the contract are deemed actions of the Client.

Compensation covers amounts recovered from the Provider under a decision of a court or another competent authority or paid under a settlement agreed with the Client, as well as documented reasonable costs of legal assistance, expert examination and compliance with orders of authorities. This provision does not apply to claims caused by the Provider's own breach and does not impose on the Client administrative fines imposed on the Provider.

10.9. Within ten working days of receiving a claim, the Provider notifies the Client of it and provides the information it has about the claim. The Provider conducts the defence itself; the Client may take part in it at its own expense and must provide the necessary information and documents. Admission of a claim or a settlement at the Client's expense requires the Client's consent, which the Client may not unreasonably withhold. Compensation is paid within ten working days of receipt of the Provider's demand with supporting documents. The Provider's failure to meet the notice period reduces the compensation only to the extent that it deprived the Client of the opportunity to defend itself.

10.10. In relations with a Business Client, the statutory penalties established for business contracts for delay, non-performance or improper performance of obligations to provide services, including for failure to provide services and for provision of services of inadequate quality, do not apply to the Provider to the extent that the law permits a different arrangement to be established by contract. The statutory penalty for late payment by a Business Client applies in the amount established by law. Penalties that the law does not permit to be excluded or reduced, including for late refund of funds, remain in force. Other contractual penalties are established only by Enterprise terms. Payment of a penalty does not release a party from performing the obligation.

10.11. A party is released from liability for non-performance or improper performance of an obligation if it proves that this was caused by force majeure, that is, by extraordinary circumstances that could not be prevented under the given conditions. These may include, in particular, natural disasters, fires, military operations, mass riots, epidemics, acts and actions of state bodies, including restriction, blocking or slowing down of communication networks, the internet and particular information resources, as well as general failures of power supply and communication networks beyond the party's control. Breach of obligations by the party's counterparties, the party's lack of funds and an ordinary shortage of resources are not recognised as force majeure. The party affected by such circumstances notifies the other party within five working days from the moment it became aware of them and informs it when they cease; information from official sources or a document of an authorised organisation is sufficient evidence. If the circumstances continue for more than thirty consecutive calendar days, each party may withdraw from the affected Order by notifying the other party. In that case, the Client is refunded the fee for the unused period of the affected feature; no other losses in connection with such withdrawal are compensated. The obligation to pay for access provided before such circumstances arose and the mandatory data protection measures remain in force.

11. Changes and notices

11.1. Version v5.5 dated 11 October 2026 applies to new contracts after it has been posted and the Client has been given the opportunity to review it before acceptance. Each version is published with a number and a date. All versions that apply to existing contracts remain available in the version archive on the Provider's website for the term of such contracts and for three years after their termination. An existing contract remains subject to the previously accepted version until the parties agree on an amendment or the contract is terminated. Publication, logging in to the account, silence, ordinary use of access already provided or automatic renewal under a previously given authorisation do not constitute acceptance of a new version of the contract.

11.2. A new version may be accepted by confirming a new Order, by paying an invoice that expressly refers to that version or by another expressly designated and recorded action after the text has been provided. A separate repeated consent checkbox is not required if that action itself constitutes valid acceptance. Moving an existing contract to a new version requires clearly expressed agreement. A Client that has not accepted a change continues to use access on the previous terms until the contract ends or is lawfully terminated. The price, term and volume already paid are not changed retroactively. The price of the next period changes in the manner set out in the Public Offer (section "Price and payment"); a price change does not by itself constitute acceptance of the entire new set of documents.

11.3. Contact details may be updated, typographical errors corrected and descriptions clarified without new acceptance if this does not change the rights and obligations of the parties. Protective measures and technical implementation may change within the obligations already agreed. New mandatory requirements of law apply in the manner provided for by law. Urgent measures to prevent threats are taken on the basis of the law and the existing contract; they are not used to change the price, shift liability or introduce new optional processing purposes. If a change requires separate consent, it does not apply to the relevant Client or processing until that consent is obtained.

11.4. The Provider gives notice of changes affecting existing access or data processing in the manner set out in clause 11.5. The Client is notified of a change in the price of the next period, a material reduction of paid functionality or the discontinuation of a paid feature at least thirty calendar days in advance, unless a longer period is established by law or an immediate measure is required on the grounds set out in clause 9.2. Receipt or acknowledgement of a notice is not deemed acceptance of the amended terms. Separately required consents to new processing purposes, model training, advertising or recurring charges do not arise from silence.

11.5. Notices and other legally significant communications under the contract are sent to the Client through the account dashboard, to the email address of the account owner, or both, and to the Provider at contact@lynx-ai.uz. The Client keeps its email address up to date. For a Business Client, a communication is deemed received on the day it is posted in the account dashboard or sent to the email address of the account owner, unless the sender has received a notice that delivery was impossible; a communication sent after 18:00 Tashkent time or on a non-working day is deemed received on the next working day. For a Consumer, a communication is deemed received when it becomes available to the Consumer in the account dashboard or arrives at the Consumer's email address.

12. Governing law, language and disputes

12.1. The contract is governed by the law of the Republic of Uzbekistan. Mandatory rules of law apply irrespective of the terms of the contract.

12.2. Before applying to a court in a dispute relating to the contract, a Business Client and the Provider send each other a claim setting out the demand, its grounds, the calculation of the amount and a list of the evidence attached. The claim is sent in the manner set out in clause 11.5 and is signed by an authorised person, including with an electronic digital signature, or is sent as a scanned image of the signed document. A response to the claim is given within fifteen calendar days of its receipt. Recourse to court is permitted after receipt of a refusal to satisfy the claim in whole or in part, or after this period has expired. The pre-trial claim procedure is not required for applications for interim measures. For a Consumer, the pre-trial claim procedure is not mandatory; the Consumer's requests are sent to contact@lynx-ai.uz stating the account or Order details and the substance of the demand, and are considered within fifteen calendar days of receipt, unless a shorter period is established by law.

12.3. The place of conclusion and performance of the contract is the city of Tashkent. Disputes with a Business Client are heard by the economic court at the place of state registration of the Provider in the city of Tashkent. Disputes with a Consumer are heard by the court whose jurisdiction is determined by law; the Consumer may apply to the authorised state body for the protection of consumer rights or to a court, including at the Consumer's place of residence, regardless of whether a claim has been sent. Where Enterprise terms expressly provide otherwise, the dispute is resolved by arbitration as specified in those terms.

12.4. The Client may transfer its rights and obligations under the contract to a third party only with the Provider's prior consent given in written or electronic form, except in the case of universal succession. The Provider may transfer its rights and obligations under the contract to the person to whom the business of providing the Service passes, including as a result of a reorganisation or a transfer of the business; by accepting the contract, a Business Client consents to such transfer. A transfer of the Provider's obligations under a contract with a Consumer, except in the case of universal succession, requires the Consumer's consent. The Provider notifies the Client of the transfer at least thirty calendar days in advance. A Client that does not agree with the transfer may, before it takes place, withdraw from the contract with a refund of the fee for the unused paid period. Personal data is transferred in this case in compliance with personal data legislation. The Provider may assign monetary claims against the Client without the Client's consent.

12.5. The contract is exhaustively determined by the documents listed in clause 2.5 and the Order. Advertising materials, presentations, descriptions on the website not included in the Order, correspondence with staff, responses of the Provider's software assistants and other communications preceding the conclusion of the contract or the Order do not amend or supplement the contract unless the relevant term is included in the Order or in Enterprise terms. This rule does not limit the Consumer's right to reliable information about the service. A party's failure to exercise its right under the contract does not constitute a waiver of that right. If any term of the contract is held invalid, the remaining terms remain in force, and the invalid term is replaced by a term permitted by law that is closest to it in meaning.

12.6. The contractual documents are drawn up in the Uzbek and Russian languages. Both texts have equal legal force. In case of discrepancy between them, the Russian text prevails in relations with a Business Client. In relations with a Consumer, the text in the language in which the Consumer accepted the terms prevails; if the terms were accepted while displayed in another language, the Uzbek text prevails. The English text is a translation provided for convenience and is not used for interpretation. Information that the law requires to be provided in the state language is provided in Uzbek.