KAI Terms of Service

1. Application, formation and contractual documents

1.1 Scope and contracting parties

These Terms of Service, referred to as the Terms, govern access to and use of the KAI mobile applications, web workspace, KAI Auth authentication, model inference capacity market, account management, orders and execution records, funds records, fulfilment coordination, capacity metering, application programming interfaces, notifications, billing and customer support. In these Terms, the Company, we, us and our mean VN TECH LTD. You means the individual accepting these Terms or the legal entity or other organisation that the individual lawfully represents with valid authority.

1.2 Acceptance and authority

By confirming acceptance through the relevant interface, or accessing or using the Services after these Terms have been made available to you, you acknowledge that you have read, understood and agreed to be bound by them. A person accepting on behalf of an organisation must have the authority required to enter into and perform the agreement and must ensure that personnel undertaking relevant operations understand the applicable requirements. A person without that authority must not establish a production account, submit instructions or make funding or fulfilment arrangements in the organisation's name.

1.3 Related documents and priority

The User Agreement addresses account establishment, authentication, authorisation and electronic operations. The Privacy Policy explains personal information processing. Agreement confirmations, fee disclosures, feature rules and applicable written agreements set out the details of the relevant Services. Read these documents together within their respective scope. If a signed order, master services agreement or enterprise agreement conflicts with these Terms, the more specific and later signed written agreement prevails only for the conflicting matter. Other provisions continue to apply to their respective subject matter.

1.4 Interpretation and records

Headings, contents lists and highlighted notices assist navigation and do not independently expand or reduce contractual obligations. Product descriptions, examples and estimates must be read against the current formal specification; describing a feature does not establish that it has been enabled for your account. Applicable requirements for separate consent, particular disclosures and rights that cannot be excluded by contract remain effective. Retain the versions, confirmations and separately signed agreements relevant to your use so that the applicable arrangements can be checked if a question arises.

2. Service provider, operational contacts and identity

2.1 Service provider

VN TECH LTD provides KAI, and KAI service operations are located in Hong Kong. KAI is the service name used in these Terms. Unless an applicable written agreement expressly identifies another contracting party, a product name, application name, feature name or service identifier appearing in the interface does not change the contracting party. The names of suppliers, model providers, organisation administrators and other users should not, merely because they appear within the Services, be understood as names of the Company or its authorised representatives.

2.2 Contact information

The Company's correspondence address is 1312 17th Street, Suite 769, Denver, Colorado 80202, United States. The service support email is beidou@kai.com and the contact telephone number is 400 108 2026. Questions about accounts, orders, funds, fulfilment, data rights or these Terms may be submitted with the information described in section 24. Stating a correspondence address identifies a contact location; availability of a particular Service remains subject to account eligibility, agreement specifications and applicable restrictions.

2.3 Specific contractual arrangements

Procurement, technical integration, capacity supply, enterprise permissions and service levels for a particular engagement must be assessed by reference to the documents formally confirmed by the parties. General product descriptions, unconfirmed discussions in an informal exchange and material independently published by a third party should not alone be treated as additional performance, funding, qualification or compensation assurances from the Company. This provision does not exclude a commitment that has lawfully become binding or applicable rules governing representations, disclosures and contractual interpretation.

2.4 Verification of communications

Before submitting a request affecting account security, funds or organisational authority, verify the official service entry point and contact information. A message claiming to represent the Company and requesting changed payment details, complete credentials, transferred account control or an unusual operation should be verified through an established contact channel. Identifying support personnel, discussing a technical matter and accepting a support request are different procedures from confirming a fill, confirming receipt of funds and executing an agreement. Each matter must be established through the formal record appropriate to that matter.

3. Eligibility, organisational authority and production access

3.1 Basic eligibility

An individual using production Services must be at least 18 years old, have legal capacity to enter into and perform these Terms and be an authorised enterprise or professional user. A person acting for a legal entity or other organisation must also possess the necessary representative authority and ensure that the organisation is entitled to conduct the activities associated with its use. Registration information, invitation relationships and organisation names must accurately reflect the actual user and authorisation arrangements. False identities, borrowed eligibility and concealment of material information must not be used to obtain permissions.

3.2 Approval and feature permissions

Production Services are provided through invitation or approval. Establishing an authentication account, verifying an email address, entering a website or viewing a market page does not by itself confer a real account, funds operations, order submission, capacity delivery or API access. Eligibility and individual permissions depend on what the Company has actually enabled for the account. Approval for one feature does not automatically enable another feature or include a subsequently introduced Service within the original authorisation.

3.3 Verification and continuing accuracy

The Company may request identity, organisation, authority, source of funds or other verification information appropriate to checking eligibility, authorisation and compliance, and may refuse or restrict access based on the outcome. Submit accurate, complete and current material through the designated channel. If organisational authority ends, the person controlling an account changes, contact details cease to work or another material eligibility circumstance changes, update the relevant information and take appropriate steps to prevent continued use by people whose authority has ended.

3.4 Location and legal restrictions

You must not use a Service where it is prohibited, where a legally required permission has not been obtained or where the use would cause you or the Company to breach applicable law. Website accessibility, a supported interface language, visibility of a market and establishment of a network connection do not confirm that all Services may lawfully be used in every location. Consider your location, actual place of use, organisation's activities and applicable obligations. If eligibility for a particular use is uncertain, obtain the necessary clarification before undertaking production activity that depends on it.

4. Account administration, credentials and security responsibility

4.1 Account information and permitted use

Keep account information accurate, complete and current, and use an account only for yourself or an organisation that has expressly authorised the use. Do not sell, rent, lend or share an account with an unauthorised person, or authenticate under another person's identity. The ability to open an application on a device, a retained browser session or knowledge of a password within an organisation does not replace the business authority required of the person operating it. Organisational account use should correspond to internal roles, purchasing authority and funds approval arrangements.

4.2 Credentials and devices

Protect passwords, passkeys, multifactor authentication material, recovery credentials, devices, authentication sessions and API credentials using measures appropriate to the business risk. Complete credentials must not be included in public code, ordinary support emails, chat records or screenshots. Review access associated with shared devices, credentials previously accessible to departing personnel and automation connections no longer required. Revoke access that is no longer valid through the management capabilities actually available to the account, and keep the underlying organisational authorisation accurate.

4.3 Authenticated instructions

Instructions submitted through valid authentication and within account permissions may be treated as your instructions or those of the organisation you represent, except where applicable law provides otherwise, responsibility rests with the Company or suspicious activity has been reported in a timely manner. Automation, representatives and internal workflows do not remove the need for appropriate authority before submission. Manage their purposes, operating scope and review of results so that the technical ability to call an interface is not confused with business approval to perform the operation.

4.4 Incidents and recovery

If a device is lost, credentials are exposed, a suspicious sign-in occurs or an unauthorised order or other security issue is discovered, stop the affected operations, protect the account from a trusted device and contact the Company with the event time and verifiable records. The service team may assist with restrictions or restoration under identity verification and security procedures. System biometrics authenticate an operator on the current device; they do not replace server authentication, organisational authority or order confirmation, and do not alter either party's responsibilities under law and the agreement.

5. Service scope, production environments and information status

5.1 Service functions

KAI provides tools for discovering, planning, reserving, ordering, recording, coordinating fulfilment of, metering and billing model inference capacity. Use commonly involves reviewing specifications and market information, obtaining account eligibility, submitting orders, checking fills, managing the corresponding capacity entitlements and calling models within the applicable window. The completion conditions and legal effects of each stage must be assessed separately. Accessibility or a success indication at one stage does not establish that all other stages have been completed.

5.2 Nature and suitability of the Services

Unless an applicable written agreement expressly provides otherwise, the Company does not provide professional investment, securities, legal, tax or model-output-use advice, and does not guarantee capacity price appreciation, particular cost savings, increased revenue, business outcomes or the accuracy of an upstream model's output. An hourly agreement concerns capacity of a specified description during a specified period. Its presentation, changing quotations and position records do not promise interest, protection of principal or price appreciation. Evaluate suitability by reference to your actual business requirements.

5.3 Production and demonstration environments

Demonstration mode requires an explicit user choice and uses isolated demonstration data. Its funds, orders, fills, positions and deliveries do not create real service rights or obligations. Within a signed-in real-account flow, failed authentication, insufficient eligibility, an unconfigured account, disconnection or unavailable data must result in an appropriate restriction, error or read-only state. Demonstration records must not be substituted for the real-account state. Verify the environment indicator and account UID before undertaking an operation.

5.4 Information hierarchy and data status

Product introductions, charts, reference exchange rates, capacity heatmaps, estimates and local caches assist understanding and operation. They are not independent proof that a quantity can be executed, a price remains valid or a fulfilment obligation has been completed. Determine specific rights and obligations using the agreement specification, confirmation interface, server receipt, complete account records and applicable written agreement. A missing-data symbol, loading state or stale-data notice does not mean a zero balance, cancelled order or discharged obligation. Investigate an inconsistency using the associated request and records.

6. Hourly agreements, capacity units and metering

6.1 Identification and specifications

Each hourly agreement is identified by its model and version, context limit, fulfilment region, fulfilment date and clock hour. Capacity for different models, context levels, regions or periods is not interchangeable merely because the descriptions are similar. Before ordering, check the agreement code and complete specification, including the selected date, displayed time zone, clock hour and any daylight-saving difference relevant to your intended use. A plan based on a different time zone must be reconciled with the confirmed fulfilment window.

6.2 Lots and Weighted TPM

One lot is a limit of 1,000,000 Weighted TPM continuously available in each 60-second metering window of the specified fulfilment hour. N lots of the same specification provide N times that limit. This is a capacity arrangement for each window, not a cumulative token balance that may be allocated freely over an hour, and it does not allow an individual request to exceed a model's context limit. Input, output and the relevant model weights are calculated under the applicable metering rules, with model weights determined by the corresponding specification.

6.3 Metering and window boundaries

Cache hits, reasoning tokens, output weights, requests crossing a window boundary and failed retries are handled under the rules shown at confirmation and the applicable fulfilment records. Request count, raw character count, a client estimate or the time a network response arrives does not alone determine final metering. Unused capacity in one window cannot be moved to a later window or used to increase the later window's concurrency or metering limit. Combining capacity from separate agreements requires support under the applicable Service rules.

6.4 Gate close and expiry

An hourly agreement gate-closes 60 minutes before fulfilment begins, and the relevant order operations are restricted at that time. Gate close does not start fulfilment or extinguish obligations already created. Unused capacity expires at the end of its window without automatic extension, accumulation, conversion to cash or refund, except where applicable law, the specific agreement or a written agreement provides otherwise. Arrange connectivity, credentials, request specifications and usage planning in advance; insufficient preparation time does not automatically change a confirmed fulfilment window.

7. Order submission, execution confirmation and cancellation

7.1 Instruction details and authority

Submitting an order authorises the Company to process the selected agreement, side, order type, price, quantity in lots, time in force and confirmation details, and to reserve or debit the relevant funds or lots under the applicable rules. Before submission, verify the UID, environment, current account data, market-data timestamp, price, estimated amount and resulting obligations. Purchases require the necessary available funds. Sales are limited to positions currently authorised and available for sale; lots committed to another order or obligation must not be used again.

7.2 Order types and time in force

A limit order is processed at the specified price or better and may remain unfilled or fill only in part. A market order uses opposing quotations available when processed, and its average price can change when execution crosses price levels. The unfilled portion of a GTC order remains effective under the rules until execution, cancellation, expiry, gate close or another termination condition. IOC immediately processes the executable portion and cancels the remainder. FOK targets immediate execution of the entire quantity or no execution. Availability and final outcomes depend on account capabilities, agreement rules and server receipts.

7.3 Binding fills and cancellation

An order may be delayed, rejected, expire, fill partially or remain unfilled because of liquidity, permissions, balances, timing or system conditions. A quotation or preview does not guarantee execution. A filled portion binds the relevant parties and cannot be withdrawn unilaterally, except where applicable law, a manifest-system-error process or the Company's written determination requires correction. Cancellation concerns only an unfilled portion that remains cancellable. Sending a cancellation request does not confirm completion; check the final receipt and account records for any execution occurring in the meantime.

7.4 Pending, unknown and duplicate requests

A missing page transition, timeout, application closure or absent local notification does not establish that the server failed to receive an instruction or create a fill. Preserve the original request ID when an outcome is pending or unknown, and query its receipt and related orders, fills and reservations instead of creating a new request with the same content. A query retry differs from resubmission. Report duplicate instructions, unusual fills or inconsistent records with their complete associated identifiers; modifying a local display does not establish that the underlying matter has been corrected.

8. Batch instructions, estimates and price protection

8.1 Purpose of the batch tool

The batch tool creates an order basket using criteria such as date range, hour range, weekday selection and lots per hour. Templates and saved selections assist repeated configuration; they do not themselves create orders or guarantee that prices, capacity or permissions existing when saved will remain available. Before every submission, review the included agreements, aggregate lots, estimated amount, quotation timestamp and applicable restrictions. Reusing a configuration requires a new assessment against the current business requirement and the current state of the market and account.

8.2 Independent execution and mixed outcomes

Each agreement within the basket is processed as an independent instruction. Some items may succeed, others may fail, remain unprocessed or await confirmation. The batch facility does not guarantee that every agreement will execute together or be cancelled together. A failure, gate close or absence of offers for one item does not cancel another item already processed successfully. Fills, funds commitments and capacity entitlements already created continue to be governed by their individual records and the applicable Terms.

8.3 Estimates and the protection threshold

The current tool applies a 3% price-deviation safeguard. Before submission, it compares the basket total calculated from current offers with the quote-snapshot estimate. During item processing, it continues to compare amounts calculated from the submitted items’ corresponding quotes and quantities with estimates for those same items. A deviation beyond the threshold stops remaining submissions, so protection may activate before any item is submitted. Successful submission does not establish execution, and these comparison amounts are not final executed charges. Check order and execution receipts separately for fills, positions and changes in funds. The safeguard does not reverse completed fills, guarantee the entire basket or keep final execution costs within a guaranteed range.

8.4 Review after completion or interruption

After completion, interruption or a connection problem, check each item's successful quantity, actual execution amount, failure reason, unprocessed status and original request receipt. Before planning a new submission for an apparently unprocessed item, establish that it has neither executed nor remained pending, and evaluate the new quotation and account state. The first basket's estimate is not automatically a valid budget basis for a later basket. An interruption indication does not establish that all funds reservations or fulfilment arrangements have been released.

9. Quotation units, Service charges and taxes

9.1 Quotation basis

Agreements are quoted in the currency, pricing unit and minimum price increment stated in the interface. The principal market currently quotes Hong Kong dollars per lot, with a minimum price increment of HKD 0.5. Last traded price, best bid, best offer, order-book depth, historical prices and capacity information describe different matters and are not substitutes for one another. The quantity displayed at a price level reflects the record at the relevant time and does not guarantee that the same quantity will remain available when the server processes your instruction.

9.2 Disclosure and payment of charges

You agree to pay execution amounts and applicable charges disclosed in the confirmation interface, execution receipt, fee schedule or applicable written agreement. Review a preview estimate separately from the charges generated by actual execution. Displaying a Service does not itself establish that the Service is free, and a general charging provision does not automatically authorise an undisclosed charge. Obtain clarification before the relevant operation if a fee item, calculation basis or applicable version is unclear.

9.3 Conversions and monetary records

A reference currency conversion assists reading and comparison without changing the original pricing currency, execution amount or funds record. Do not treat a reference exchange rate as a commitment by the Company to exchange, withdraw or settle funds at that rate. Reconcile orders, funds and bills using the same currency, business scope and relevant record time. Differences arising from update timing or display precision should be checked against the underlying records rather than resolved solely by comparing screen totals.

9.4 Taxes and billing questions

Except for items the Company is legally required to withhold, collect or bear, you are responsible for determining and fulfilling tax obligations arising from your use in your circumstances. A bill or transaction record does not replace the tax assessment required of you. Report a suspected error with the UID, order or execution identifier, amount and reason for the dispute. Investigation and correction should preserve the relationship between records rather than conceal an event by overwriting its history.

10. Prepayment, funds records and settlement arrangements

10.1 Prepayment and fulfilment settlement

At execution, the buyer prepays KAI the full execution amount and applicable charges. KAI manages prepayments and settles with suppliers after fulfilment. The Services do not provide cash settlement by reference to the difference between purchase and sale prices. Balances, available amounts, reserved amounts and amounts already incurred describe the relevant Service transaction and settlement state. They do not promise interest, protection of principal, immediate withdrawal or any separate arrangement for increasing the value of funds.

10.2 Reservations, debits and releases

Orders and other authorised operations may reserve funds or positions according to their state. Reservation, actual execution, a settlement debit and release of a reservation are different events. Assess available balances together with open orders, completed fills and other applicable obligations. A sent cancellation request, failed page refresh or interrupted batch does not by itself establish that funds have been released. Confirm the change using the server receipt and complete funds records associated with the relevant operation.

10.3 Deposits and withdrawals

Deposits and withdrawals currently require assistance from the service team. Contact beidou@kai.com from the registered email or call 400 108 2026 for assistance. Processing may require identity, organisational authority, account ownership, source of funds, outstanding obligation and compliance checks. Completion depends on verification, banks or other providers, order and fulfilment states and applicable legal restrictions. These Terms do not establish a uniform time by which funds will arrive.

10.4 Refunds and accounting corrections

Capacity already executed, used or expired is not automatically refundable except where these Terms, the specific capacity agreement, an applicable written agreement or law expressly permits it. Order cancellation, withdrawal, fulfilment remedies and reversal of an erroneous accounting entry have different conditions and cannot be substituted for one another. Corrections require verifiable business records and authorised processing; changing a local note, amount display or history list does not create a correction. These provisions do not prevent a lawful claim concerning an incorrect debit or failure to provide an agreed Service.

11. Capacity fulfilment, model requests and use responsibility

11.1 Scope of fulfilment

Use is limited to capacity entitlements you have acquired and the applicable fulfilment window, model specification, region, context limit and account permissions. Holding one agreement does not confer a general allowance for other models, periods or regions. Successful API connectivity, a valid key or an established network connection does not alone prove that a request falls within an enabled fulfilment entitlement. Before calling the model, review the entitlement and the times at which it takes effect and expires.

11.2 Capacity limits and request handling

A request exceeding the context limit may be rejected. Where aggregate Weighted TPM within a metering window exceeds the allowance corresponding to the position, new requests may be rejected or restricted under the applicable rules. Splitting a request, increasing concurrency, changing clients or reconnecting does not invalidate the metering limit. Understand cache hits, reasoning tokens, failed retries and requests crossing windows under the rules applicable at confirmation. Failure to receive the intended output does not necessarily establish that no metering record exists.

11.3 Input rights and output review

You must lawfully obtain the rights, authority and necessary consent required to submit content. Do not submit unlawful, infringing, malicious, highly sensitive or otherwise prohibited content under the applicable model policy. Model output may contain factual errors, omissions, inconsistencies or material unsuitable for a particular purpose. Apply factual verification, permission checks and appropriate human review according to the intended use. Do not directly rely on output for high-risk decisions without suitable human and technical safeguards.

11.4 Service incidents and evidence

Upstream models, capacity suppliers, networks and technical limitations may affect latency, availability, output or request processing. The Company handles incidents under the applicable capacity agreement and written service commitments it has made. Remedies, adjustments and compensation are determined by those arrangements and applicable law. Preserve request identifiers, agreement details, time windows, response status and relevant metering records. Ordinary support communications should not include unrelated personal information, complete credentials or input content beyond what the investigation requires.

12. API credentials, automated instructions and technical controls

12.1 Enablement and authorised purposes

API capabilities are available only to enabled accounts and only for authorised purposes within their permissions. An API entry point in an interface, available documentation or a credential created in demonstration mode does not establish that production API access is enabled. Orders, queries, configuration operations and model requests submitted through an API remain subject to the account, funds, capacity and timing rules of the corresponding interface function. A technical submission method does not change an instruction's business effect.

12.2 Credential management

A complete API key is shown only once, when created. Store it through a controlled credential management method, restrict the people and programs that can access it and keep it out of public repositories, publicly accessible client resources, screenshots and ordinary support emails. Promptly disable or rotate credentials suspected of exposure, no longer needed or affected by the departure of an authorised person. Creating a new credential does not by itself revoke an older credential that remains valid.

12.3 Automation controls

Ensure that automation follows interface documentation, rate and concurrency limits, capacity metering, price protection, gate close and access controls. Handle repeated execution, timeouts and uncertain outcomes appropriately. If a modifying request has an unknown outcome, investigate using its original identifier rather than retrying without limit or generating new identical orders. Querying programs should control refresh frequency and avoid unnecessary concurrent requests for the same data source from several pages or jobs.

12.4 Restrictions and monitoring

Do not circumvent restrictions by rotating accounts, distributing request origins, forging requests or changing parameters, and do not automate manipulation, abuse, overload or unfair access. Monitor the calls, orders, charges and abnormal states actually produced by your programs, and maintain the ability to stop malfunctioning automation. The Company may reject or restrict requests that do not comply with Service security and capacity requirements. An error, rate-limit response or failed connection must not be interpreted by automation as evidence that authority has been granted.

13. Lawful use, market integrity and prohibited conduct

13.1 Lawful use

Comply with the laws applicable to your activities and these Terms. Do not use the Services for fraud, infringement, money laundering, sanctions evasion, unauthorised funds activities or other unlawful conduct. Do not obtain access by submitting false identity, organisation, authority, funding or business information. Do not impersonate the Company, a capacity supplier, a model provider, another user or any of their representatives when communicating instructions or information to another person.

13.2 Market and order conduct

Do not engage in market manipulation, fictitious execution, self-trading arrangements, misleading quotations, interference with price formation or activity manufactured without genuine demand. Do not knowingly exploit a discovered system error, delay or display anomaly to increase an improper benefit, or use duplicate orders, abnormal requests or coordinated operations to interfere with other users' ordinary access. Legitimate price comparisons, capacity planning and authorised transactions remain subject to genuine intent, valid authority and applicable rules.

13.3 Systems and data

Do not access another person's account or information you are not entitled to receive. Do not probe, bypass or damage authentication, eligibility, metering, limits or other security controls, distribute malicious software, disrupt networks or attack the Services. Protected market data must not be resold, scraped, mirrored or extracted at scale without written permission. Communications intended to report a suspected vulnerability should use the formal support channel and avoid expanding access, obtaining unrelated data or affecting normal Service operation.

13.4 Investigation and action

Where a breach is reasonably suspected, the Company may reject instructions, restrict functions or investigate, and may preserve and disclose necessary records when law permits or requires it. Action should relate to the identified risk and applicable obligations and is not automatically a final determination that a user has acted unlawfully or breached the agreement. You may explain a suspected mistaken assessment or record issue through the complaint channel. Preserve relevant material during review and avoid continued conduct that could expand the effect of an incident.

14. Capacity suppliers, model providers and third-party services

14.1 Third-party participation

The Services may involve capacity suppliers, model providers, cloud infrastructure, networks, authentication, communications, banks and professional service providers. Their respective involvement and responsibilities depend on the specific arrangement. A model, supplier name or technical identifier appearing in the interface generally identifies a specification or source. Its appearance does not independently establish that the third party has made the same commitments to you as these Terms or automatically change your contractual relationship with the Company.

14.2 Applicable third-party rules

Third-party services may have separate terms of use, content policies, location restrictions and technical requirements. Before selecting a model or access method, review the provisions that have been made available and apply to that use. Restrictions imposed on content, functionality or territory may affect whether a particular request can be processed. Unauthorised circumvention of those restrictions is outside the access rights granted by these Terms.

14.3 External links and independent arrangements

External links, model information and support resources assist identification of relevant information. If you independently visit a third-party website, enter into its agreement or establish an external payment or technical arrangement, verify the actual provider and applicable terms. Unless the Company expressly accepts a written obligation, a price, deadline, compatibility representation or support arrangement independently agreed between you and a third party does not automatically become an obligation of the Company. The existence of an external link does not replace that review.

14.4 Incidents and coordination

The Company coordinates capacity and fulfilment under the applicable agreement but does not control every third-party system. A third-party failure does not expand the Company's responsibility beyond its applicable written service commitments or exclude responsibility that the Company has under law and the agreement. Preserve related orders, agreements, request identifiers and times when an incident spans different stages. Those records assist in distinguishing account permissions, connectivity, model responses and capacity fulfilment and in determining what needs to be investigated.

15. Personal information, confidentiality and business records

15.1 Personal information processing

The Company processes personal information under the KAI Privacy Policy and applicable data processing arrangements. The Policy explains information categories, sources, purposes, sharing, cross-border processing, retention and individual rights. Ensure that you are entitled to provide the relevant information and fulfil legally required notices, permissions and other obligations when representing an organisation or submitting information about other people. Acceptance of the Services is not treated by these Terms as consent to every optional processing activity.

15.2 Confidential information

The parties protect each other's non-public information under any confidentiality terms they have signed. Without a separate agreement, a recipient must still take reasonable measures and process information clearly designated, or confidential by its nature, only for providing or using the Services. Handle account security information, non-public business arrangements and unpublished technical material according to their actual nature. Technical access to information does not authorise its use for unrelated purposes or disclosure to unrelated recipients.

15.3 Content and different record categories

Model input and output, account information, orders and fills, funds entries, capacity entitlements, metering, authentication events and audit records have different purposes and processing requirements. A deletion request for one category, clearing a device cache, signing out or ceasing application use does not automatically eliminate the basis for retaining another category. Retention, deletion and rights requests are handled under the Privacy Policy, applicable written arrangements and law.

15.4 Reconciliation and copies

Orders, executions, funds, fulfilment, metering, authentication and audit records may evidence Service activity, subject to applicable law and the circumstances. Retain available copies required for your business and legal purposes, and provide related identifiers and times when raising a question. Request verification of the underlying records if a display error or discrepancy appears. Local notes, caches and screenshots may assist an explanation but do not independently replace verified server-side business records.

16. Intellectual property, content rights and access licence

16.1 Rights in the Services

The Company and its licensors retain their lawful rights in the Services, software, interface designs, trade marks, identifiers, documentation and arrangements of market data. Access to the Services, payment of charges and acquisition of capacity do not automatically transfer those rights or make you the owner of a brand, software component or model. Rights not expressly granted in these Terms or an applicable written agreement remain with the relevant rights holder.

16.2 Limited access licence

While you comply with these Terms and maintain the necessary eligibility and permissions, the Company grants a limited, revocable, non-exclusive and non-transferable right to access the Services for authorised internal business purposes. Read that right together with the features actually enabled, interface rules and applicable third-party conditions. It does not authorise bypassing controls, reselling accounts, representing yourself under the Company's brand or extracting information outside your permissions. Rights that applicable law does not permit to be restricted remain unaffected.

16.3 Content you submit

You retain your existing rights in content lawfully submitted and grant the Company the limited processing rights necessary to provide, secure and improve the Services. Those rights do not transfer ownership of your content to the Company or displace applicable confidentiality, privacy and purpose restrictions. Determine permitted information use by reading the Privacy Policy, relevant data processing arrangements and applicable model-service rules. A general Service licence must not be understood as authorisation for any undisclosed purpose.

16.4 Output and rights review

Conditions for using model output may depend on applicable law, the selected model's rules, rights in input material and the intended purpose. Conduct the appropriate review before external publication, commercial delivery or another use that may affect third-party interests. Report suspected infringement in content or Service materials through section 24, identifying the relevant rights and the specific material or location concerned.

17. Availability, maintenance and account data integrity

17.1 Availability arrangements

The Services are provided on an as-is and as-available basis. Except for an express commitment in a signed service level agreement or capacity agreement, continuous, uninterrupted and entirely error-free operation is not guaranteed. An application opening, a website being reachable or a successful health check establishes only the state of the component observed. It does not independently prove that account data is complete, an order can be accepted or model capacity can immediately be fulfilled.

17.2 Maintenance and feature changes

The Company may maintain, adjust or discontinue a feature, capacity agreement or service territory for security, legal, capacity, supplier or operational reasons, giving notice of material changes where reasonably practicable. Changes must be considered together with confirmed agreements and written obligations; a general maintenance provision does not retrospectively alter the core economics of completed fills. Monitor notices relevant to the features and fulfilment windows you use and make appropriate arrangements for integration and operational monitoring.

17.3 Complete snapshots and read-only states

Account summaries, orders, positions, fills, funds and deliveries should be understood through the complete account snapshot. Updating market data does not prove that the account snapshot is also valid. Missing permissions, expired authentication, an unready connection or a failed snapshot update may disable modifying operations while retaining the last available information for reference. Retained information should show its time and stale status and does not confirm that the same available balance or capacity remains present.

17.4 Recovery and continuity

After sign-in, reconnection or a successful refresh, verify the environment, UID, account state and unresolved instructions before continuing. Maintain monitoring, backups, request limits and human response arrangements appropriate to your reliance on the Services. Remedies for an availability issue depend on the applicable capacity agreement, written service commitments and law. General information does not replace those express arrangements or guarantee a restoration time, output result or the cost of obtaining a substitute service.

18. Instruction rejection, permission restrictions and suspension

18.1 Operational rejection

The Company may reject an instruction or restrict the relevant feature where funds or saleable positions are insufficient, information is invalid, the agreement has gate-closed, permissions are absent, a request is duplicated or a Service is unavailable. An operational rejection does not automatically terminate the account or establish that all previous instructions remained unfilled. Determine each request's outcome from its actual receipt rather than inferring the account's historical state solely from an error currently shown.

18.2 Security and compliance restrictions

If the Company reasonably suspects a security incident, fraud, unlawful activity, breach of these Terms or a risk to market integrity, it may reject instructions, restrict features, reserve relevant funds or lots, suspend or terminate an account. The measure should relate to the relevant risk and applicable obligations. Where law, an authority's requirement or necessary security handling prevents immediate explanation, the Company may withhold confidential risk-control details within the permitted scope.

18.3 Explanation and restoration checks

Where law and security permit, the Company will provide a reason for the restriction or steps necessary for restoration. Submit accurate explanations and relevant verification material through the official channel. Do not evade an unresolved restriction by creating accounts, borrowing an identity, replacing credentials or using another access method. Submitting information does not guarantee immediate removal of a restriction; restoration and its scope depend on verification, account eligibility and the Service conditions then applicable.

18.4 Existing records and outstanding obligations

Suspending access, disabling ordering or terminating an account does not automatically reverse completed fills, remove charges already incurred or resolve outstanding fulfilment and funds matters. Those records and obligations remain subject to these Terms, applicable written agreements and law. If a restriction prevents you from accessing necessary records, explain the required scope through support and request assistance. This does not promise disclosure of protected information before identity is verified or where disclosure is legally prohibited.

19. Account closure, post-termination handling and surviving obligations

19.1 Closure request

Submit a closure request from the registered email to beidou@kai.com. To prevent unauthorised closure, identify the account UID, requested action and information necessary to establish identity. Do not send passwords, verification codes, recovery codes or complete API keys. A person requesting closure for an organisation must have authority to close the account and address the associated records, funds and fulfilment matters.

19.2 First contact and completion conditions

The service team will contact the registered email within 72 hours after receiving the request. This period is a first-contact target, not an assurance that all account closure, settlement or data deletion will be completed within 72 hours. Identity and authority checks, open orders, account balances, fees due, fulfilment obligations, disputes, security investigations and mandatory retention matters may need to be addressed before closure can be completed.

19.3 Effects of closure

Before requesting closure, review active orders, future fulfilment windows, automation and copies of records you need, and handle matters capable of cancellation or termination under their applicable rules. Deleting an application, clearing browser data, signing out, disabling notifications or ceasing active access is not formal account closure. None of those actions automatically cancels a valid instruction, ends an existing fulfilment obligation or completes the handling of a balance that may be available for withdrawal.

19.4 Continuing provisions

Closure does not discharge payment, settlement or other obligations already accrued and does not remove records that applicable law requires to be retained. Provisions concerning payment, records, confidentiality, intellectual property, liability limitations and dispute resolution continue where their nature requires survival. Deletion, anonymisation and retention of personal information are addressed separately under the Privacy Policy and applicable law. Formal closure and immediate permanent deletion of every item of information are different processes, and their completion must not be assumed to occur at the same time.

20. Business risks, technical risks and suitability assessment

20.1 Prices, liquidity and capacity

Capacity supply, demand, prices and executable depth can change. An order may remain unfilled, execute only partially or be impossible to cancel or sell at the expected time. Displayed reference prices, historical fills, supply information and heatmaps do not guarantee future capacity or liquidity. Purchased capacity has a defined time window; changes in your demand plan or failure to use it on time may cause capacity to expire without being fully used.

20.2 Operations and connectivity

Selecting an incorrect model, context limit, region, date, time zone, quantity, side or time in force may create obligations inconsistent with your requirements. Networks, devices, authentication, upstream models, suppliers or systems may fail and cause delay, interrupted connectivity, inconsistent states or unknown outcomes. Simultaneous use by several devices or programs can increase the possibility of duplicate submission, decisions based on stale information or delayed recognition of abnormal activity.

20.3 Models and security

Requests may exceed capacity or context limits, be rejected under a content policy or produce inaccurate, incomplete or unsuitable output. Exposed credentials, phishing, malicious software, unauthorised automation and inadequate internal permission management may cause losses involving accounts, information or funds. Security settings and biometrics assist access protection but do not replace proper organisational authority, review of business instructions and verification of model output for the intended use.

20.4 Legal changes and suitability

Changes in law, regulation, taxation and third-party service conditions may restrict particular territories, models, purposes or access methods. Assess the Services against your architecture, procurement objectives, legal obligations and continuity requirements, and maintain suitable backups, monitoring, limits and human review. The stated risks assist understanding of concrete usage conditions; they are not an exhaustive list of every possible event and do not relieve the Company of its legal or contractual responsibilities. Evaluate the relevant circumstances rather than treating a generally available feature as a recommendation for your particular activity.

21. Service representations, liability limitations and statutory rights

21.1 Express commitments and general information

The Company performs obligations expressly undertaken in applicable capacity agreements, signed service level agreements and other written documents according to those arrangements and applicable law. Beyond those express commitments, general descriptions, estimates, examples, reference information and third-party model output do not independently guarantee continuous availability, a particular result, error-free operation or suitability for a special purpose. Interpret each limitation in these Terms in the context of the actual Service and relevant legal requirements.

21.2 Categories of loss

To the fullest extent permitted by applicable law, the Company is not liable for indirect, incidental, special, punitive or consequential loss, or loss of profit, revenue, goodwill, data, opportunity or substitute-service cost. Whether a particular loss falls within one of these categories depends on applicable law, the relevant facts and effective written agreements. The description applied to a loss by either party does not alone determine its legal classification or the extent to which a limitation is enforceable.

21.3 Aggregate cap and exceptions

Except for fraud, wilful misconduct, gross negligence, intellectual-property infringement, confidentiality obligations, amounts due or liability that law does not permit to be limited, VN TECH LTD's aggregate liability is capped at the fees you actually paid for the affected Services during the 12 months preceding the event giving rise to the claim. Responsibility falling within an express exception is not automatically restricted by this general cap. An effective, separately signed provision that lawfully takes priority applies according to its terms.

21.4 Non-waivable rights

Some jurisdictions do not permit exclusion of particular warranties, limitation of certain losses or restrictions on specific statutory remedies. The exclusions and limitations apply only where legally permitted, do not affect rights you cannot waive and do not transfer to you responsibility the Company cannot lawfully exclude. You may raise billing, fulfilment, security or other disputes according to the circumstances and section 22. These Terms do not require acceptance of an internal determination as a condition for exercising a statutory right.

22. Complaints, governing law and jurisdiction

22.1 Raising a complaint or dispute

If you dispute an account matter, order, fill, funds record, fulfilment outcome or application of these Terms, first contact beidou@kai.com from the registered email. Include the UID, relevant order or request identifiers, times, verifiable records, reasons for the dispute, requested outcome and contact details. To protect account and third-party information, the Company may verify the requester's identity and authority to represent the account holder before providing protected records.

22.2 Good-faith discussion

The parties will attempt to resolve the dispute in good faith within 30 days after it is received. Provide complete related records where available and distinguish confirmed facts from matters that remain to be verified. This discussion arrangement does not predetermine the outcome, a compensation amount or a technical restoration time. It does not restrict a non-waivable right or a remedy available under applicable law, and correspondence with support should be assessed according to what has actually been confirmed.

22.3 Applicable law and courts

These Terms and non-contractual disputes arising from them or the Services are governed by Hong Kong law, excluding its conflict-of-law rules. The parties submit relevant disputes to the exclusive jurisdiction of the courts of competent jurisdiction in Hong Kong, except where applicable law grants a non-waivable right to another forum or a consumer right that must be preserved. Accessing the Services from another location does not automatically change this agreement on law and jurisdiction.

22.4 Scope of the dispute mechanism

These Terms contain no mandatory arbitration provision and no class-action waiver. Internal customer support, technical investigation and accounting explanations do not replace a decision by a court or another body lawfully entitled to determine the matter. Preserve relevant records during the dispute and continue handling unrelated matters where applicable law and effective agreements permit. Necessary immediate security measures may be taken under the corresponding provisions of these Terms while the dispute remains under review.

23. Revisions, assignment and general provisions

23.1 Revisions and notification

The Company may revise these Terms in response to changes in Services, applicable law, security requirements or operational arrangements and will identify the corresponding version and dates. Material changes will be notified through the application, website, registered email or another reasonable channel. Where law requires consent or a particular procedure, the Company will follow that requirement. Monitor notices relevant to the Services you actually use and retain the document versions applicable to matters already confirmed.

23.2 Effect of a revision

Continued use after a revision becomes effective signifies acceptance of the Terms applicable to subsequent use, subject to legal requirements concerning consent and the effectiveness of changes. A revision does not retrospectively alter the core economics of completed fills. Separately signed agreements remain subject to their provisions and the document-priority rules in these Terms. A page's revision date does not itself establish that the parties have entered into a new agreement for every existing transaction.

23.3 Severability and preservation of rights

If a provision is held invalid or unenforceable, other provisions that can apply independently remain effective, with the treatment of the affected provision determined by applicable law. A party's failure to exercise a right immediately does not automatically waive that right or the ability to address a similar matter later. Read contents lists, language versions and explanatory material with the relevant text; an isolated heading or translation difference does not expand the original allocation of responsibility.

23.4 Assignment and complete documents

You may not assign this agreement without the Company's written consent. The Company may transfer it together with the related obligations in a merger, reorganisation or transfer of the Services, giving notice required by law. These Terms, applicable written agreements, confirmations and incorporated documents together determine the relevant arrangement. Additional Services or special requirements not expressly covered should be confirmed through the appropriate formal documents before use, rather than inferred as additional commitments from a general feature description.

24. Contacts, request handling and document retention

24.1 Service contact details

VN TECH LTD
1312 17th Street, Suite 769
Denver, Colorado 80202
United States

KAI service operations: Hong Kong
Service email: beidou@kai.com
Telephone: 400 108 2026

24.2 Information for a request

To assist correct identification and handling, use the registered email and state the request category, UID, relevant agreement, order or request identifier, event time and desired outcome in the subject and message. For funds matters, identify the amount and currency. For fulfilment questions, identify the model specification, region and time window. For privacy requests, identify the right you wish to exercise and the information concerned. Provide only the material necessary to handle the particular request, keeping unrelated account or third-party information out of the message.

24.3 Sensitive material and secure communications

Do not send passwords, one-time verification codes, recovery codes, complete API keys or unrelated personal information in ordinary support emails. If further identity checks or protected documents are required, follow the formal procedure supplied by the service team. Verify through an established official channel any request claiming that complete credentials, bypassed verification or changed local records can directly correct funds, reverse an order or restore capacity. The information required should correspond to the actual support purpose.

24.4 Related documents and retained records

Refer also to the User Agreement, Privacy Policy, Product Introduction and Help Centre. Retain relevant records together with applicable agreement confirmations, fee disclosures and separately signed documents. Acceptance of a support matter does not automatically amend the contract. Formal written arrangements that have become effective, and applicable legal requirements, are applied according to their actual effect. A retained copy assists identifying the applicable provision and should be read with the corresponding transaction or request records.