Offer and License Agreement for Ailoot

Version dated 2026-10-17.

Applies from publication and acceptance in the manner established by this agreement.

The Appendices to the Offer form an integral part of it:

• Appendix 1. Payment and Balance Rules for Ailoot.
• Appendix 2. Payment and Provision of the Digital Service.
• Appendix 3. Refunds and Payment Disputes.
• Appendix 4. Acceptable Use Rules for Ailoot.
• Appendix 5. Model and Supplier Terms.
• Appendix 6. Special Terms for Ailoot Features.
• Appendix 7. Infringement of Intellectual Property Rights — set out in appendix 6 to the Ailoot Privacy Policy.
• Appendix 8. Contact Details and Service Information.

The Offer with its appendices and the Ailoot Privacy Policy with its appendices together constitute the complete set of Ailoot documents accepted when signing in to the account dashboard.

1 Parties and subject matter of the offer

1.1. The ailoot.ai service offers to enter into an agreement for the use of the Ailoot software service on the terms of this public offer. Inquiries are to be sent to support@ailoot.ai. Hereinafter, ‘Ailoot’, the ‘Service Provider’ or ‘we’.

1.2. The agreement is entered into with an individual or organization that has accepted the offer, hereinafter the ‘User’ or ‘Client’. A person accepting the terms on behalf of an organization confirms their authority to enter into the agreement, use the Service on behalf of the organization and incur the associated expenses. A person without such authority must not create the appearance of the organization's consent.

1.3. The subject matter of the agreement is the grant of the right to use Ailoot software and the provision of related digital services: receiving requests through the API, routing requests to models from different suppliers, transmitting files and request parameters, using available tools, returning results (text, images, video, music, speech synthesis and transcription), metering consumption and maintaining the Balance. The specific scope is determined by the selected model, method, mode and request.

1.4. Ailoot is the provider of its own software service. Ailoot's server component provides API-key authorization, routing, processing algorithms, access management and usage accounting. We engage model suppliers and other technology suppliers to execute requests. This does not change the party to the agreement with the User and does not mean that we accept money for a supplier as a payment intermediary.

1.5. Topping up the Balance and using Ailoot do not constitute the purchase of another company's personal account, subscription or API key. Third-party model names identify technology available as part of the service and do not imply a partnership, representation or endorsement unless that relationship is expressly confirmed.

2 Definitions

2.1. ‘Service’ means the software interfaces, the ailoot.ai website, the account dashboard on ailoot.ai and the Ailoot API at https://api.ailoot.ai/v1, compatible with OpenAI, Anthropic and Gemini interfaces, as well as the available features. ‘Account’ means the User's account.

2.2. ‘Input Materials’ means requests, messages, instructions, files, images, audio, video, code, data and other materials provided by the User or on their behalf. ‘Results’ means responses and other materials generated when a request is executed. Input Materials and Results are collectively referred to as ‘Content’. Third-party Content obtained from external sources may have a separate rights holder.

2.3. ‘Model’ means the selected computational model or specialized feature. ‘Model Supplier’ means the person providing the technology or its execution. ‘Route’ means the request execution configuration, including the model, supplier, method, mode, region and processing settings. A single model identifier may have several routes with different prices, availability and data rules.

2.4. ‘Order’ means a confirmed Balance top-up or a request to a model with the displayed price, currency and applicable terms. ‘Pay as you go’ means payment for actual measured usage. ‘Balance’ means internal accounting of prepaid services in US dollars; it does not constitute a bank account, payment wallet or right to make payments to third parties. ‘Reserve’ means the portion of the Balance temporarily reserved for the expected cost of a request until its actual cost is determined.

2.5. ‘Model Terms’ means the mandatory rules, licenses and restrictions of the particular model and route. ‘Consumer’ means an individual purchasing the service for purposes for which applicable law provides consumer protection. ‘Corporate Client’ means a person using the Service in business or professional activities. The selected model or manner of using the Service does not, by itself, remove consumer status established by law.

3 Composition of the agreement and order of precedence

3.1. The agreement includes this offer, the confirmed Order, the applicable version of the model catalogue prices and Appendices 1–4 and 6 to the Offer (‘Payment and Balance Rules for Ailoot’, ‘Payment and Provision of the Digital Service’, ‘Refunds and Payment Disputes’, ‘Acceptable Use Rules for Ailoot’ and ‘Special Terms for Ailoot Features’). Section 11 of this offer establishes the rules for using models; the directory in Appendix 5 to the Offer (‘Model and Supplier Terms’) helps identify the terms applicable to a particular route.

3.2. The ‘Ailoot Privacy Policy’ describes the processing of personal data. It is not blanket consent to all processing and does not replace separate consent where required by law. The Organizational Data Processing Terms (appendix 4 to the Ailoot Privacy Policy) apply, within their scope, to processing under a Corporate Client's documented instructions.

3.3. In the event of a conflict, mandatory law prevails. The following then apply in order: an individually agreed written order or agreement; the special terms of a particular feature with respect to that feature; this offer and the incorporated rules. Model Terms define mandatory boundaries for use of the relevant technology, but do not, by themselves, replace the Ailoot price promised to the User or eliminate claims against Ailoot for its own service.

3.4. An individual amendment is valid if accepted by authorized parties in a written or electronic form that can be retained. Terms unilaterally added by the Client to a payment instruction, purchase requisition or other document do not amend the agreement without our express consent.

3.5. Where documents are available in several languages, the version and language shown at acceptance are retained for the Order. Translation discrepancies are resolved with regard to the meaning of the agreed terms and the User's mandatory rights; an unread version in another language is not used to covertly expand the User's obligations.

4 Formation of the agreement and electronic evidence

4.1. Before placing an Order, the User may review the terms, model and method description, price, usage measurement rules and applicable restrictions. For a paid Order, acceptance is expressed by expressly confirming the relevant terms and completing the specified payment action. Merely visiting a public page does not authorize a charge.

4.2. The User checks the Order and corrects errors before confirming it. The Balance is topped up after the payment provider confirms payment; a confirmation that can be retained is then generated. It must allow the parties, top-up amount, currency and accepted terms to be identified. Electronic confirmations, transaction records, usage records with request identifiers and accounting documents are used to perform the agreement and review requests.

4.3. The parties recognize electronic messages, notices, payment provider confirmations and Service logs as admissible evidence to the extent permitted by law. Such records are not conclusive: the User may provide evidence of an error or other documents. A technical record of a browser redirect does not replace payment confirmation.

4.4. No physical medium is supplied when software is provided electronically. Activation and actual use are confirmed by the electronic system. The absence of a signed paper acceptance certificate does not, by itself, mean that the digital service was not provided if its provision is established by admissible evidence; mandatory accounting and consumer documents are provided where required by law.

4.5. Acceptance is submitted by selecting the mandatory checkboxes and clicking the action button in the Ailoot interface. Before clicking the button, the User may clear the checkboxes or close the window; after that, cancellation and refunds are governed by Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

5 Age, authority and account information

5.1. The minimum age for access is determined by applicable law and the terms of the model or individual feature. Where a legal representative's permission is required to enter into the agreement independently, process data or make payment, it must be obtained before the relevant action. A higher age threshold for an individual route prevails for that route.

5.2. Registration information must be current, accurate and sufficient for the account and Order. Impersonating another person, creating a fictitious organization, concealing mandatory country information or using another person's payment details without lawful permission is prohibited. Changes to contact and billing information must be updated promptly.

5.3. We may request proportionate evidence of authority, account ownership, rights to materials, payment or use of a restricted feature. The request is limited to what is necessary for the particular verification. Passwords, CVV, banking codes and other secrets do not need to be sent by ordinary mail. If the necessary verification cannot be completed, the affected action may be suspended within lawful limits.

6 Security of accounts and API keys

6.1. Personal login credentials must not be shared in a way that allows several people to pose as a single User. The User takes reasonable steps to protect passwords, devices, sessions and their own Ailoot API keys and reports compromises to support@ailoot.ai.

6.2. An API key operates within the permissions, budget and Balance assigned to it. The Client controls its placement in applications, access by developers and contractors, revocation and replacement. A secret key must not be published in public code, disclosed to outsiders or used without permission if it belongs to someone else. Lawful integration of the API into one's own product does not confer a right to resell an Ailoot account or technology suppliers' keys.

6.3. Before receiving notice, we may rely on correctly authenticated account actions, subject to our duty to maintain reasonable security and the requirements for disputing unauthorized transactions. This clause does not make the User responsible for a proven error by Ailoot itself and does not remove mandatory payment protections.

6.4. Where security is threatened, a key may be revoked, sessions terminated, the owner's identity verified or features temporarily restricted. We seek to limit measures to what is necessary. Restoration does not automatically remove lawful restrictions imposed by a model supplier.

7 Corporate accounts

7.1. An authorized purchaser may order features and incur expenses only within the authority granted to them. The organization is responsible for usage ordered by authorized persons.

7.2. Access for an affiliate, customer or contractor is permitted only in a manner provided by the Service. A separate legal entity does not become a party to the agreement or receive an independent license solely because of a shared domain, owner or project.

8 Software license

8.1. Within the rights we hold, a limited, non-exclusive right to use Ailoot functionality through the designated interfaces and API is granted for the term of the agreement and within the scope of paid usage. No exclusive rights, source code or trademark rights are transferred.

8.2. The license is limited by the purpose, scope, territorial availability, number of users and technical limits of the Service. The Service does not grant a right to copy or distribute server software, rent out an account, provide unauthorized sublicensed access or create a false impression of officially representing Ailoot.

8.3. The Ailoot API may be integrated into one's own applications and processes. The Client must comply with requirements concerning end users, the model, key protection and data processing. Such integration is distinct from transferring supplier accounts or covertly reselling access in violation of applicable licenses.

8.4. Updates may change or replace components for security, compatibility and product development. The User is not required to grant rights unnecessary for using an update. When the right of access ends, use of protected components ends to the extent provided by the agreement and law; data export permitted by law remains available.

9 Features, limitations and changes to the service

9.1. The model, method and price description in the model catalogue defines the usage being purchased. The name of another company's feature does not imply that an equivalent Ailoot feature is available. Third-party consumer applications, corporate certifications, dedicated capacity or an SLA are not promised as part of the service without a separately confirmed term of the Order.

9.2. Model availability and performance depend on the mode, context volume, tools, infrastructure condition and technology suppliers' availability. The stated maximum context window is not necessarily available in its entirety for the User's text: instructions, tools, history and internal processing may use part of it.

9.3. We may develop the interface, fix errors, eliminate vulnerabilities, replace technical components and discontinue obsolete features. A material deterioration of an obligation already paid for is addressed under the law and the refunds section. A routine update does not authorize retroactively recalculating a completed request or reducing a paid Balance.

9.4. Maintenance and temporary unavailability do not, by themselves, promise compensation under a nonexistent SLA. Claims for actual failure to provide, or improper provision of, a paid service nevertheless remain available. Early access, beta and preview features are expressly labelled and governed by special terms; a stable paid product is not retroactively declared beta.

10 Balance, usage and prepayment

10.1. Use of the Service is paid for from a prepaid Balance maintained in US dollars. A one-time top-up is paid for through the payment provider identified on the payment page, using the methods it offers; the payment currency is displayed before payment confirmation. The payment provider displays the exchange rate and fee on the payment page before payment confirmation. The User pays the payment provider's fee in addition to the top-up amount. The minimum top-up is 18 US dollars. A one-time top-up is credited without a bonus. The Balance is credited after the payment provider confirms payment. A one-time top-up does not create a subscription. Ailoot Plus and Pro monthly plans are subscribed to separately on the ‘Pricing’ page (billing.ailoot.ai) under clause 2.2 of Appendix 1.

10.2. Prices are set for each model and method and displayed in the model catalogue in the account dashboard. Charges are based on actual usage: tokens, images, seconds of video, minutes of audio and other disclosed units. Every generated result is returned to the User and charged for. Consumption depends on the model, context, response, files, tools and other disclosed parameters. No particular number of messages or identical cost for different requests is guaranteed.

10.3. Pay as you go API usage is paid for from the Balance based on actual usage. Before a request is sent to the supplier, its expected cost is reserved against the Balance. After the response, the actual cost is debited once and the remainder of the reserve is released. The Balance does not become negative: a new paid request is rejected if the available balance is insufficient. If the outcome of a request cannot be confirmed, its reserve is retained until the outcome is verified; no duplicate charge is made and the unconfirmed request is not automatically sent again. Merely starting a request does not create hidden credit, debt or an automatic budget overrun; debt arising from a disputed payment is governed by clause 22.4.

10.4. Before a top-up is confirmed, the amount payable, applicable taxes if charged, payment currency and total amount including the payment provider's fee are displayed. Models are subject to the published catalogue and the rules of the particular route. Different tools and media may be charged per token, image, character, request, second, minute, hour or other disclosed quantity. An absent rate does not mean that usage is free.

10.5. Additional rules on measurement, reservation and adjustments are set out in Appendix 1 to the Offer (‘Payment and Balance Rules for Ailoot’). The Balance does not confer a right to interest income, currency exchange transactions, transfers to other Users or payments to third-party sellers.

11 Terms of models and technology routes

11.1. This section is part of the agreement, rather than merely an information page. Each model may be used within the mandatory terms of its supplier and the selected route. Provider information and available restrictions are presented in the model catalogue and the directory in Appendix 5 to the Offer (‘Model and Supplier Terms’). The list is not limited to particular brands: Ailoot provides access to models from various suppliers, such as Anthropic Claude, OpenAI GPT, Google Gemini, xAI Grok, Alibaba Qwen, MiniMax and models hosted by NVIDIA. Supplier usage rules apply to requests, including the usage rules of Anthropic, OpenAI and Google.

11.2. Before a request, the User checks the model's purpose and suitability for their task, commercial use terms, country or organization restrictions, available features and material processing rules. If the User does not accept a mandatory model term, they must not send a request through that route and may choose another permitted option.

11.3. A Corporate Client and a developer providing their own product to end users through the Ailoot API undertake to communicate the applicable rules to those users and ensure that the required consent and lawful basis for processing exist before the request. Within the limits of the law, the Client is responsible for use of their integration and authorized users; they cannot extend rights beyond the model's license.

11.4. A model may have several providers and versions. Automatic routing, fallback to an alternative route, and selection of regional execution, training or storage are applied only within disclosed settings and mandatory restrictions. A fallback route must not be used to circumvent the agreed budget, a prohibition on data transfer or territorial unavailability.

11.5. Changes to rules, withdrawal of a model, changes in a supplier's availability or its mandatory requirements may result in restrictions on the relevant route. Material consequences for an existing paid product are communicated in the manner required by law; completed transactions do not become new purchases at revised rates.

11.6. We cannot waive a model developer's licensing, export, age or other mandatory restrictions. Circumventing blocks and safeguards, misrepresenting a country or identity, and using a proxy/VPN to obtain prohibited access are forbidden. A permitted network security tool is not prohibited in itself if it is not used for such circumvention.

11.7. To meet mandatory requirements, we may request reasonably necessary information on rights to materials, consents, authority, country, mode or end use. If information necessary for a particular model is not provided, use of that model may be restricted. This does not create a right to demand unrelated information about all of the Client's activities.

11.8. Technical identification of a region, request class and compatibility may contain errors. The User may request a review. This qualification does not release Ailoot from its own obligations and does not authorize knowingly transmitting a request through an unsuitable route.

11.9. The terms of Ailoot's agreements with suppliers do not make a supplier a party to the User's agreement with Ailoot. Ailoot is responsible for its own interface, charges, price disclosure and contractual obligations to the User to the extent established by law.

12 API integrations and end users

12.1. The API is used in accordance with published documentation, authentication requirements, limits and permitted parameters. The Client is responsible for the correctness of their integration and for checking responses, retries and dependencies. Undocumented methods must not be used to circumvent charging, security or model terms.

12.2. Permitted automation of requests through the API does not constitute prohibited automated data collection (scraping). However, bulk extraction of protected materials and non-public interface information, interference with other clients' operations, circumvention of restrictions or access to infrastructure beyond the provided API is prohibited.

12.3. Idempotency, timeouts, streaming and confirmation of completion must be accounted for in the integration. Sending a new request again does not guarantee an identical response and may create separate chargeable processing; a duplicate error caused by the system itself is addressed under the adjustment rules. Ailoot does not automatically resend a request whose outcome is unconfirmed and does not charge for it twice. Request identifiers allow usage costs and results to be matched.

12.4. A Client serving their own users remains responsible for their product, its representations, permissions, data processing and decisions made on the basis of results. The Client must not promise undisclosed Ailoot guarantees to those users or claim to be Ailoot's authorized representative without a basis.

13 Input Materials and rights to results

13.1. The User retains their rights to Input Materials. They grant limited permission to receive them, store them in the selected mode, reproduce them in the workflow, technically transform them, transmit them to necessary model suppliers, including those outside the User's country, and generate a response solely to perform, protect and support the Service and comply with the law.

13.2. The User confirms that they have the necessary rights, consents and lawful grounds for transmitting materials, including other people's personal data, images and voices, protected works and organizational information. Availability of material on the internet does not always constitute permission to reuse it or send it to a model.

13.3. As between the parties, rights to a Result that belong to Ailoot and are transferable are granted to the User to the maximum extent permitted by applicable law and the model's license. This does not transfer third-party rights, create legal protection where none exists or remove special restrictions applicable to a particular type of result.

13.4. Different users' Results may be identical or similar. The agreement does not grant exclusivity over a general style, idea, facts, publicly available elements or independently created content. Third-party Content from search, a connected source or a tool remains subject to applicable rights and terms of use.

13.5. The User assesses whether publication and commercial use of a result are lawful. Generation does not, by itself, confirm the absence of another party's trademarks, rights concerning a depicted person, the permissibility of advertising or compliance with a software component's license.

14 Files and history

14.1. Files are accepted in supported formats, sizes and quantities specified in the interface or API. We may reject a damaged, dangerous, incompatible or prohibited file and restrict actions that threaten infrastructure. The right to inspect is limited to security, performance and legal compliance purposes.

14.2. Selecting a file for a request constitutes an instruction to use the necessary content through the relevant route. It is not blanket permission to publish all files in the account. Storage arrangements, deletion and backups are governed by the Ailoot Privacy Policy, its appendix 2 (‘Ailoot Data Settings’) and the settings of the particular feature.

14.3. The processing service is not a guaranteed archive or the User's sole backup. Important source materials and results should be saved independently. Data protection obligations and mandatory rights arising from Ailoot's own errors remain in effect.

15 Feedback and Ailoot's rights

15.1. Improvement suggestions voluntarily submitted as feedback may be used to develop the Service without an obligation to pay compensation unless separately agreed otherwise. This clause does not permit all personal content to be designated as feedback and used for an undisclosed purpose.

15.2. The platform, its software components, design, documentation and designations remain with their respective rights holders. Neither topping up the Balance nor using a result transfers rights to Ailoot's code or brand. Use of designations must not create a false impression of authorship, affiliation or endorsement.

15.3. Reports of suspected infringement of intellectual property rights are handled under the procedure set out in appendix 6 to the Ailoot Privacy Policy (‘Infringement of Intellectual Property Rights’). We consider sufficiently specific information, take the affected party's explanations into account and meet applicable legal requirements. Knowingly false complaints or counter-statements are prohibited.

16 AI accuracy and responsible use

16.1. Generative systems produce probabilistic results and may make mistakes, miss context, use outdated information or give unexpected responses. We do not promise that every response will be true, unique or suitable for the User's particular intention.

16.2. Reasonable verification is required before using a result, especially before publishing it or applying it in relation to other people. An AI result must not be presented as a verified professional opinion or human work where doing so is misleading or unlawful. Required labels for synthetic content must be retained.

16.3. A general-purpose Service does not become a licensed medical, legal, financial or other regulated professional service. Significant decisions concerning employment, lending, insurance, housing, education, health and other human rights must not be made solely on the basis of an unverified AI response in violation of applicable requirements.

16.4. Restrictions apply to the relevant use and do not promise complete control over every result. Detailed general and model-specific requirements are set out in Appendix 4 to the Offer (‘Acceptable Use Rules for Ailoot’). They do not remove Ailoot's responsibility for promised functionality, its own charges or remedies provided by law.

17 Prohibited conduct and checks

17.1. Unlawful activities, infringement of intellectual property and personal rights, exploitation of children, fraud, unauthorized access, malware, interference with infrastructure, dangerous use and circumvention of mandatory restrictions are prohibited. The full categories and conditional model rules are defined in Appendix 4 to the Offer (‘Acceptable Use Rules for Ailoot’).

17.2. Attempts to obtain non-public source code, secrets, model weights or other users' data by reverse engineering, extraction or circumvention of technical measures are prohibited, except to the extent expressly permitted by mandatory law or an applicable open license. Permitted security research is conducted under an agreed programme where such a programme is offered; general API access does not, by itself, constitute consent to attacks.

17.3. The User must not disable designated safeguards, distort metrics, abuse funds credited to the Balance without payment if such credits are provided, create fictitious accounts to circumvent limits or help third parties violate these rules. Use of results to train another model is subject to data rights and the mandatory restrictions of the selected technology; a supplier's prohibition is not deemed waived merely because an intermediate call is made through Ailoot.

17.4. To the extent necessary, automated and human checks, blocking of an individual request or file, restriction of a feature, retention of incident-related evidence and lawful reporting to a competent authority may take place. Checks do not mean that all content is continuously read by people. Their purposes and grounds are described in the Ailoot Privacy Policy.

18 Confidentiality

18.1. Confidential information means non-public information disclosed in connection with the agreement and marked as confidential or reasonably of that nature: private content, commercial information, technical materials, individual order terms, and security and access information.

18.2. The receiving party uses it to perform the agreement and protect the relevant rights, maintains reasonable confidentiality and permits access only to persons who need it and are bound by an applicable duty of protection. When a contractor is engaged, only the necessary portion of the information is transferred, subject to the agreement, model rules and data legislation.

18.3. The restrictions do not apply to information that becomes public without a breach by the recipient, was lawfully known to them beforehand, was lawfully obtained from an independent third party or was independently developed without using the disclosed confidential information. An exception must be substantiated rather than presumed solely from similarity of information.

18.4. Where disclosure is mandatory under a lawful demand, it is limited to the required scope. Where permitted, the disclosing party is informed of the demand and given a reasonable opportunity to protect the information. This clause does not require breaching a prohibition on notification or obstructing a lawful investigation.

18.5. When the lawful basis ends, information is returned, deleted or retained to a limited extent for mandatory recordkeeping, protection of claims, security and backup cycles. Confidentiality obligations remain in force for lawfully retained information. Personal data rules prevail within their scope.

19 Third-party services

19.1. Ailoot does not control all terms and content of an external website and does not promise its uninterrupted operation. However, engaging a supplier to perform Ailoot's own paid obligation does not automatically remove Ailoot's liability to the User. Data from a third-party source and its intellectual property rights are governed by the relevant terms.

20 Personal data and business processing

20.1. Processing relating to accounts, payment, security, requests and support is described in the Ailoot Privacy Policy and its appendices 1 (‘Ailoot Cookie Policy’) and 2 (‘Ailoot Data Settings’). The public offer does not replace any specifically required consent for optional processing.

20.2. A User submitting other people's data must have an applicable basis. A Corporate Client is responsible for the lawfulness of their instructions, notifying data subjects and obtaining necessary permissions for transfer. This does not automatically mean that Ailoot is never a data operator/controller: its role is determined by the particular operation and applicable law.

20.3. Processing on an organization's instructions is governed by appendix 4 to the Ailoot Privacy Policy (‘Organizational Data Processing Terms’). General privacy text does not prove that special agreements concerning health data, international transfers or other regulated processing have been entered into. Information must not be submitted where the mandatory conditions of the selected route have not been met.

20.4. Request contents (prompts and files) are transmitted to the model supplier servicing the request; it may be located outside the User's country. Arrangements for retaining requests, files and technical logs vary by feature and supplier. The terms ‘confidential’, ‘no training’ or ‘ZDR’ are not a universal promise for every route. The User may choose only modes actually available with disclosed boundaries.

21 Payment, top-ups and price changes

21.1. Payments are made only through a top-up method actually offered by the payment provider identified on the payment page. Check the recipient, amount and currency. Service provision inquiries are directed to Ailoot; unauthorized card transaction inquiries may also be directed to the issuing bank.

21.2. Automatic top-ups and other recurring charges require separate express authorization specifying a threshold, amount or calculation and a way to disable them. Saving a payment instrument does not, by itself, authorize every subsequent charge. The User may revoke authorization for future payments in the prescribed manner.

21.3. Use of the Service is paid for from the prepaid Balance. A one-time top-up does not require cancellation of renewal. To cancel future automatic renewal of a monthly plan, open ‘Pricing’ from the account dashboard, select ‘More’ → ‘Cancel subscription’ and confirm cancellation. The Service forwards the cancellation to the payment provider; if a payment that has been made is confirmed after cancellation, the corresponding credit is added to the Balance. The plan credit remains available until the end of the paid period, after which its unused portion expires; the balance from one-time top-ups remains available indefinitely. Cancellation does not trigger an automatic refund. The unused Balance is not refunded or paid out in money at the User's request, except in the cases specified in section 22 and Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

21.4. A payment that fails or is not confirmed by the payment provider does not top up the Balance; paid requests are not accepted if the Balance is insufficient. Payments already confirmed and lawful claims that have arisen are accounted for separately. A repeated payment notification is not grounds to credit or debit the same transaction again.

21.5. A new price applies to new requests and top-ups after it is disclosed in the model catalogue or during a top-up. Completed requests are not recalculated at the new price. An erroneous price does not authorize secretly charging a different amount: proper disclosure and consent are required before the corrected Order is performed, or the erroneous transaction must be cancelled in accordance with the law.

21.6. The Balance is maintained in US dollars, and a one-time top-up is paid for through the payment provider in accordance with clause 10.1; applicable currency and tax rules apply to payments. The payment provider displays the exchange rate and fee on the payment page before payment confirmation. All mandatory information about the final amount payable is communicated before the top-up is confirmed; the User's bank's own conversion is governed by its terms.

22 Refunds and mandatory remedies

22.1. A Balance top-up is not refunded at the User's request, and the unused Balance is not paid out in money, including when use ends or the account is deleted, except where a refund is mandatory under applicable law or on the grounds specified in clauses 22.2 and 23.4 and Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

22.2. Refunds and corrections remain available for confirmed erroneous and duplicate charges, unauthorized payments, payments debited from the payer but not credited to the Balance due to a payment failure, services not provided or materially improperly provided, and termination of a paid service by Ailoot without a breach by the User (clause 23.4), as do statutory withdrawal rights, mandatory consumer guarantees and payment provider procedures. The corresponding grounds and application procedure are set out in Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

22.3. Stopping use of the Service differs from withdrawing from an agreement already entered into. The Consumer retains applicable withdrawal rights, digital service guarantees and statutory time limits. A checkbox requesting early commencement of the service is not a universal waiver of all rights.

22.4. A refund of the original transaction takes account of the law and the actual payment route. Receiving reimbursement through a bank does not entitle the User to receive the same amount again from Ailoot. If a payment is disputed through a bank and the amount cannot be recovered from the Balance, the difference remains the User's debt; until it is repaid, new requests from the User are not accepted and the message ‘payment disputed, access suspended’ is displayed, and the debt is automatically repaid from subsequent top-ups or released reserves. Contacting support does not remove the right to contact a bank, supervisory authority or court.

23 Term and termination of the agreement

23.1. The agreement takes effect upon acceptance within the scope of the access granted and the necessary settlements. The User may stop using the Service and request deletion of the account under the procedure described in appendix 3 to the Ailoot Privacy Policy (‘Deletion of the Ailoot Account and Data’). These actions have different consequences; neither results in a refund of the unused Balance (clause 22.1).

23.2. We may suspend an individual feature, model, key or account in the event of a material breach, a substantiated security threat, fraud, infringement of rights, a mandatory legal or supplier requirement, unpaid charges or an inability to lawfully continue providing service.

23.3. Where possible and proportionate to the circumstances, we notify the User of the grounds and provide an opportunity to remedy the breach. Urgent protective measures, a lawful prohibition on notification or a risk of continuing harm may require action without advance notice. The opportunity to challenge the action by writing to support@ailoot.ai remains available to the extent permitted by law.

23.4. Permanent termination of a paid service without a breach by the User is accompanied by settlement of the prepaid portion not provided, including where continuing the service becomes impossible because a supplier ceases operating or a legal restriction applies. Replacing an individual route while preserving the agreed material capabilities does not, by itself, constitute termination of the entire service. The consequences of a material deterioration are determined by the Order, Appendix 3 to the Offer (‘Refunds and Payment Disputes’) and mandatory law. In the event of a proven breach, the unused balance does not automatically become refundable, but it also cannot be taken away contrary to mandatory law.

23.5. Upon termination, rights to further use end and the relevant keys and sessions are revoked. Accrued payment claims, confidentiality duties, obligations to protect rights and data, applicable limitations of liability and dispute procedures survive. Lawfully retained documents and data are not destroyed merely because the account is closed.

23.6. Where a storage feature or access to data ends, export, deletion and other rights are exercised under applicable law, the agreement and the feature's actual capabilities. This clause does not confer a right to demand indefinite free storage after the service ends.

24 Warranties and limits of promises

24.1. We provide the described software service within the agreed Order and applicable mandatory requirements. Beyond mandatory warranties and expressly agreed written commitments, the Service is provided in its actually available condition and scope. Freedom from all errors, absolute security, continuity of every model or achievement of a particular commercial outcome are not promised.

24.2. Neither a demonstration of a result nor a marketing example replaces the Order terms or guarantees an identical response to a different request. Matters of regulated activities, licenses for materials and final verification of a decision remain the responsibility of the person using the result, within the limits of the law.

24.3. A route temporarily disabled by a supplier or a network failure does not automatically constitute a breach of a particular contractual obligation by Ailoot. However, this qualification does not exclude liability for Ailoot's own fault, concealed non-conformity with the promised product or mandatory consumer remedies.

25 Limitation of liability

25.1. To the maximum extent permitted by law, we are not liable for indirect or consequential losses, lost profits, unrealized savings or commercial opportunities arising from use of the Service. This limitation does not exclude losses or remedies that mandatory law prohibits excluding or limiting.

25.2. Where a limitation is permitted, Ailoot's aggregate contractual liability for related claims does not exceed the amount actually debited from the Balance for the usage to which the claim relates. A different limit may be separately agreed in an individual B2B agreement.

25.3. The limit does not apply to liability that cannot be limited, including liability for intentional misconduct, fraud, harm to life or health in the cases provided by law, mandatory personal data requirements and non-excludable consumer rights. It does not turn a refund due by law into an arbitrary payment at the service's discretion.

25.4. The User takes reasonable measures to mitigate loss, retain necessary evidence and notify us of an error. This does not shorten the statutory period for making a claim or impose an obligation to waive rights to seek recourse through a bank or court.

26 Third-party claims in business use

26.1. This section applies to a Corporate Client to the extent permitted by law; it does not impose a hidden obligation on an ordinary consumer to reimburse all Ailoot expenses. The Client is responsible for the lawfulness of their content, instructions, product and authorized users' actions.

26.2. If a third party brings a claim caused by the Client's content that violates the law or agreement, a lack of necessary permissions or unlawful operation of the Client's integration, the Client arranges Ailoot's defense at their own expense in a manner permitted by law and reimburses documented reasonable defense expenses, including legal assistance, as well as awarded amounts and agreed settlements to the extent attributable to the Client's breach. Reimbursement does not cover Ailoot's own culpable acts or circumstances unrelated to the Client.

26.3. Ailoot notifies the Client of such a claim without undue delay and provides reasonably necessary assistance at the Client's expense; delayed notification releases the Client only to the extent that it demonstrably prejudiced the defense. The Client entrusts the defense to a qualified representative reasonably acceptable to Ailoot and reports material actions. Ailoot may participate through its own representative at its own expense; if the Client fails to provide a timely defense or a material conflict of interest arises, Ailoot may arrange the necessary defense with reimbursement of proportionate expenses under clause 26.2. A settlement that includes an admission of a breach by Ailoot, a payment or other obligation on its part, or that does not fully release it from the relevant claim requires its prior written consent. Neither party assumes obligations on behalf of the other without authority; consent is not unreasonably delayed or withheld.

26.4. Special protection against IP claims concerning the results of a particular model or technology supplier is not automatically provided. It applies only if expressly included in an individual order and the corresponding rights are available throughout the contractual chain. This does not remove Ailoot's liability for its own infringement of exclusive rights.

27 Circumstances beyond reasonable control

27.1. A party is not liable for non-performance to the extent it is caused by proven circumstances beyond its reasonable control and applicable law permits such relief: an extraordinary event, a mandatory prohibition by a competent authority, a widespread disruption of communications infrastructure or another comparable circumstance.

27.2. An ordinary lack of funds, a party's own security breach or any contractor error is not automatically declared force majeure. The affected party reports a material impediment where possible and takes reasonable steps to mitigate its consequences. The paid portion not provided and lawful termination rights are addressed separately.

28 Applicable law and dispute resolution

28.1. The agreement is governed by applicable legislation, preserving the mandatory rules and consumer remedies applicable to the particular User. Determining the applicable law does not deprive a consumer of access to a court or authority protected by mandatory legislation in their country.

28.2. To have a dispute considered, a claim may be sent to support@ailoot.ai, setting out the circumstances, Order or request identifiers, evidence and remedy sought. We consider it within the applicable statutory period. A pre-litigation procedure is mandatory only to the extent established by applicable law or a lawful individual agreement.

28.3. Unless a separate agreement provides otherwise, a business dispute is heard by the competent court in the manner established by applicable legislation. The agreement does not automatically introduce mandatory foreign arbitration, a waiver of collective claims or an obligation on a consumer not to go to court.

28.4. Submitting a claim does not prevent urgent protective measures, compliance with a mandatory regulatory request or protection of rights through a bank. Statutory periods for seeking recourse are not shortened by a general qualification about support convenience.

29 Notices, amendments and transfer of the agreement

29.1. Legal and service notices are sent through the account email, account dashboard, Order confirmation or another agreed channel. The parties keep contact information current. Advertising messages have a separate legal basis and an opt-out option; accepting the agreement does not mean a mandatory subscription to advertising.

29.2. Amendments are introduced for security, legislation, technology terms or product development. A new version is published with a date; material changes are notified in advance to the applicable extent, with an opportunity to decline the new terms and discontinue the corresponding future usage. Completed transactions are not recalculated retroactively.

29.3. Continued use following proper notice constitutes acceptance only to the extent permitted by law; where separate consent is required, it is requested separately. Removing a link to the previous text does not change the provable terms of an earlier Order.

29.4. The User must not transfer the account or contractual rights and obligations to a third party in circumvention of the agreement's restrictions or without the necessary consent. Transfer of the Service to another person is permitted in the manner established by applicable legislation, subject to notification and personal data requirements and preservation of acquired rights; it does not allow arbitrary deterioration of a consumer's position.

30 Final provisions and contact details

30.1. The parties are independent persons. The agreement does not create a partnership, employment relationship, agency authority to accept payments for a model supplier or authority to represent the other party without a separate basis.

30.2. Failure or delay in exercising a right does not constitute a waiver of that right. Invalidity of an individual provision does not invalidate the remaining provisions if the agreement can operate without it; an invalid term is applied or replaced only to a lawful extent, without diminishing the User's mandatory rights.

30.3. This Offer with its appendices, the Ailoot Privacy Policy and the confirmed Order constitute the parties' agreement for the relevant usage. Advertising representations are taken into account to the extent provided by law; mandatory liability for an inaccurate description is not excluded by an entire-agreement clause.

30.4. Any additional rights of a technology supplier as a third party apply only where required by the applicable license and disclosed for the route. The agreement does not give an unspecified group of persons an independent right to debit the User's funds or manage their account.

30.5. Support, payments, refunds, content complaints and personal data: support@ailoot.ai. Service Provider: the ailoot.ai service.

Appendix 1. Payment and Balance Rules for Ailoot

1 What is purchased

1.1. The User prepays for use of the Ailoot service — an API router through which requests made with an API key using interfaces compatible with OpenAI, Anthropic and Gemini are routed to models from several suppliers. Prepayment is made by topping up the account balance, which is maintained in US dollars. Usage is paid for from the balance based on actual transactions. The balance, including funds credited without payment if the Service provides them, is not money, electronic money, currency, an investment asset or a means of payment and is not held in a bank.

1.2. The account separately displays the available balance and amounts temporarily reserved for requests being executed (section 4). If the Service credits funds without payment, for example for testing, their application and spending conditions are disclosed when credited; such funds are not considered interchangeable with the paid balance unless expressly provided by the credit terms. Spending rules and the available balance are displayed in the account dashboard.

1.3. The balance must not be transferred to another User, sold as money, gifted outside a designated feature or used to pay a third-party seller. The balance cannot be withdrawn or paid out in money; a refund is possible only on the grounds in Appendix 3 to the Offer (‘Refunds and Payment Disputes’) and where mandatory under applicable legislation.

2 Price and contents of an order

2.1. The model catalogue in the account dashboard discloses current prices for each model and each method. Before paying for a top-up, the User sees the top-up amount in US dollars, the payment amount and currency, the payment provider's fee, applicable taxes if charged and the final amount. The purchaser may check the order before confirmation and retain its terms.

2.2. The Service sells one-time Balance top-ups and Ailoot Plus and Pro monthly plans on the ‘Pricing’ page (billing.ailoot.ai). Monthly prices and Balance credits in US dollars are: Ailoot Plus — 20 and 20; Ailoot Plus 50 — 45 and 50; Ailoot Pro 100 — 85 and 100; Ailoot Pro 200 — 160 and 200; Ailoot Pro 500 — 350 and 500, respectively. Usage is paid for from the prepaid balance at catalogue prices for the actual quantity. A plan is subscribed to with a monthly automatic payment through the payment provider after the User separately confirms it on the payment or banking page; acceptance of the Offer does not, by itself, authorize automatic charges. The amount in the payment currency is determined at signup using the payment service's exchange rate, fixed for that subscription and not automatically recalculated each month; the User pays the payment service's fee, and the total is displayed before confirmation. A credit for each period is made after confirmed payment, rather than merely linking an automatic payment. The paid monthly period begins with confirmed payment and ends on the date of the payment provider's next charge accepted by the Service. Until that date is confirmed, the plan credit does not expire. Unused plan credit expires at the end of its period; a one-time top-up has no expiry date. Renewal is paid for by the next monthly automatic payment; cancellation and refunds are described in clause 21.3 of the Offer.

2.3. The Balance is maintained in US dollars, while a one-time top-up is paid for through the payment provider identified on the payment page, using the methods it offers. The payment provider displays the exchange rate and fee on the payment page before payment confirmation. The User pays the payment provider's fee in addition to the top-up amount. The minimum top-up is 18 US dollars. Independent conversion by the issuing bank is governed by the User's relationship with that bank.

2.4. The model catalogue publishes the exact applicable prices, units and special terms for the selected model and method. A price per million text tokens is not used as a universal unit for audio, images, video or other methods. Different modes, quality, duration, context size, cache, tools or suppliers may change the calculation; the applicable price, unit and condition are available before a request.

3 API usage measurement

3.1. Actual usage is recorded using the applicable measures: input and output tokens, cache tokens, internal reasoning where chargeable, images, seconds of video, minutes of audio, speech synthesis characters, requests or other units disclosed in the catalogue. Parameters and units follow the particular model and method, rather than only the general feature name. Every generated result is returned to the User and charged for.

3.2. For a price per million tokens, the chargeable quantity is divided by 1 000 000 and multiplied by the corresponding price. For another unit, its published scale is used. The same consumption must not be counted again as separate components unless the price provides for different, separate operations.

3.3. Some catalogue values describe a base, minimum or route-dependent price. A price dependent on the route or calculated using additional parameters does not become zero because an internal field is zero, negative or absent. The total is determined by the disclosed formula for the particular mode.

3.4. The price and calculation method are available before execution; the expected cost is reserved against the balance before the request is sent (section 4). After processing, the history shows actual units, amount, model, method, time and request identifier. This information helps match usage to the order and request a review of an error.

3.5. Quantities are measured by Ailoot's technical systems and those of the model supplier that serviced the request, within the applicable mode. Differences between a user's text count and the tokenizer may arise from history, internal instructions, tools, attachments and encoding method. In a dispute, records relevant to the transaction are considered; a technical log is not conclusive evidence.

3.6. Rounding, minimum chargeable quantities and special price intervals are disclosed in the model catalogue before use. New rules are not applied retroactively to completed transactions. The User must not assume that catalogue prices for future requests will remain unchanged indefinitely.

4 Reservation, errors and repeated requests

4.1. Before a request is sent to the model supplier, its expected cost is reserved against the balance. The Reserve limits the available balance but is not the final charge. After the response, the actual cost is debited once and the unused portion of the reserve is released; the status and adjustments are recorded in the history. The Balance does not become negative.

4.2. If a request is rejected before chargeable processing begins, its cost is not treated as unconditionally consumed. An erroneous charge is reviewed and adjusted. Rejection by safeguards, platform failure, absence of a result and cancellation by the client involve different technical circumstances; they must be assessed on the basis of the processing actually performed and provided and mandatory law.

4.3. Disconnecting the client connection or closing the window does not always stop execution that has already begun. For streamed or partial results, completed processing may be charged for if that rule is disclosed and permitted by law. The Service must not classify an undelivered operation as successful merely because the model supplier has billed it.

4.4. If the outcome of a request cannot be confirmed, its reserve is retained until the outcome is verified. There is no duplicate charge for a single request, and a request with an unconfirmed outcome is not automatically sent again. A new submission by the User after a timeout may be a separate request. Automatic fallback to another route must remain within the agreed settings, budget and data rules. Switching to a materially more expensive mode does not create unlimited authorization for additional spending.

4.5. For a disputed transaction, write to support@ailoot.ai and provide the account email, request or payment ID, model, method, time and type of error. Do not send the full request content if an identifier is sufficient for diagnosis. A confirmed error is corrected; any monetary refund due is made under Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

5 Subscriptions and usage restrictions

5.1. The validity period of a monthly plan credit is specified in clause 2.2 of this Appendix. Features, applicable models, methods and restrictions are shown in the model catalogue and account dashboard. Requests of different complexity consume different quantities and result in different charges against the balance.

5.2. Rate, concurrent request and individual feature limits may apply independently of the balance amount. Having funds on the balance does not guarantee unlimited throughput.

5.3. A change to calculation terms applies only in a disclosed and confirmed scenario. The mere availability of a more expensive mode or model does not authorize automatically charging its cost or recalculating past transactions.

5.4. The procedure for confirming payments and crediting top-ups is described in Appendix 2 to the Offer (‘Payment and Provision of the Digital Service’).

6 Top-ups

6.1. The Balance is topped up by paying at least 18 US dollars through the payment provider identified on the payment page. Before a top-up, the amount to be credited in US dollars, payment amount and currency, payment provider's fee and rules relating to the purchase are displayed. The top-up is credited to the balance after the payment provider confirms payment. A repeated notification or a repeated visit to the payment result page must not create multiple credits for one payment.

6.2. If the available balance is insufficient for the reserve, a new paid request is not accepted. The authorized amount must not be independently increased or the payment instrument changed without the necessary consent. An insufficient-funds message is not a new order.

6.3. If a payment is disputed through a bank (chargeback) and the amount cannot be recovered from the balance, the difference becomes the User's debt. Until it is repaid, new requests from the User are not accepted and the message ‘payment disputed, access suspended’ is displayed. The debt is automatically repaid from subsequent top-ups or released reserves. For details, see Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

7 Validity of the balance

7.1. A balance top-up is not refunded at the User's request, and the unused paid balance is not paid out in money, except where a refund is mandatory under applicable legislation. The grounds in Appendix 3 to the Offer (‘Refunds and Payment Disputes’) remain in effect: erroneous or duplicate charges, payment not credited to the balance due to a payment failure, failure to provide the service, termination of the service by Ailoot without a breach by the User, mandatory consumer guarantees and the right to dispute a payment through a bank. The period for using the paid balance is determined by the Offer and applicable legislation. Changes to future rules do not cancel a previously paid balance contrary to the agreed terms and mandatory law.

7.2. Funds credited without payment, for example for testing if the Service provides them, are provided on the terms disclosed when credited: applicability, restrictions, duration and spending procedure. They do not create a claim for their nominal value to be paid out in money and do not replace a monetary refund due without the User's consent.

7.3. Where funds credited without payment are linked to a purchase, the consequences of cancelling that purchase are determined by the terms disclosed when credited and by law. A paid portion not actually provided must not be debited as consumed merely because credited and paid funds are accounted for together. The history must allow transactions relating to the purchase to be identified.

7.4. Attempts to sell, exchange or transfer the balance without authorization may result in access restrictions and checks. Termination or deletion of an account does not result in a refund or payout of the balance; refunds mandatory by law and lawful document retention are governed by the Offer and Appendix 3 to it (‘Refunds and Payment Disputes’). Restricting access under this clause does not, by itself, mean confiscation of the paid balance.

8 Taxes, confirmations and corporate payments

8.1. Applicable taxes and information needed to determine them are taken into account in the order. The Client provides accurate information on country, organization and tax status where necessary. A client's tax identification number does not, by itself, imply a tax exemption or application of reverse charge.

8.2. After payment, an electronic confirmation that can be saved is provided, and the credit is recorded in the balance history. Mandatory fiscal and accounting documents are generated under the applicable rules. A payment notification is not always the same as a fiscal receipt; these documents must not be substituted for one another.

8.3. Postpaid billing, a credit limit, an individual payment document, a special payment deadline or a corporate minimum-volume commitment apply only if separately agreed. They do not arise under this appendix for an ordinary prepaid account. An error in a payment document is considered upon an application accompanied by documents, preserving statutory rights.

8.4. Ailoot's agreement with a model supplier, a supplier discount or its non-refundable expenses do not automatically change the Ailoot terms accepted by the User. Payment and accounting inquiries are accepted at support@ailoot.ai.

Appendix 2. Payment and Provision of the Digital Service

Balance and API usage

The Service operates on a prepaid basis: the User tops up an account balance maintained in US dollars and sends requests using an API key through interfaces compatible with OpenAI, Anthropic and Gemini. The cost of each request is debited from the balance based on actual usage of the selected models and methods (tokens, images, seconds of video, minutes of audio and so on). Every generated result is returned to the User and charged for. Ailoot Plus and Pro monthly plans with Balance credits are described in clause 2.2 of Appendix 1. Current prices for each model and method are available in the model catalogue in the account dashboard.

Order confirmation

For a one-time top-up, the top-up amount in US dollars, payment amount and currency, payment provider's fee, applicable taxes if charged, material terms and total payable are displayed before confirmation. The payment provider displays the exchange rate and fee on the payment page before payment confirmation. The final amount and currency are displayed on the provider's payment page before payment confirmation. If the card issuer performs conversion, its exchange rate applies. The User pays the payment provider's fee in addition to the top-up amount. The minimum top-up is 18 US dollars.

Payment is accepted through the payment provider identified on the payment page, using the methods it offers. The methods available for a particular payment may depend on the country and device. Selection and confirmation take place in the secure payment interface of the provider, bank or wallet. Card details and bank confirmations are entered only in the designated form.

Card details are entered only in the payment provider's or bank's payment form over an encrypted connection (HTTPS/TLS). Ailoot does not request, receive or store the full card number, its expiry date or the CVV/CVC code; payment information is received from the payment provider without full card details. The card issuer or bank may ask the cardholder to confirm payment using a one-time code or another method. Payment data is transmitted to the payment provider and bank to process the payment.

A payment method may be saved only on the payment provider's secure payment page, with the User's separate consent and if the provider offers that capability. Ailoot does not receive full card details. A saved method is used only for payments that the User initiates or confirms, and for automatic transactions only if the User has separately enabled them. The User is notified in advance of changes to these terms.

Provision of access

The service is provided electronically in the Ailoot account: a top-up is credited to the balance after the payment provider confirms payment, after which the balance can be spent on requests. Each top-up is credited in full, electronically and in a single instance; there are no partial or multiple deliveries. No physical goods, delivery, customs clearance or transfer of a tangible medium are required. The payment and credit record allows the amount, status and date to be checked.

A browser redirect to the payment result page does not, by itself, replace the payment provider's confirmation. While a transaction is being checked, its status may remain pending. If a top-up is not credited to the balance after confirmed payment, send the transaction ID, date, amount and account email to support@ailoot.ai; the correction and applicable refund procedure is set out in Appendix 3 to the Offer (‘Refunds and Payment Disputes’).

Managing purchases

To stop paying for one-time top-ups, simply stop making them. To stop future automatic renewal of a monthly plan, cancel the subscription on the ‘Pricing’ page under clause 21.3 of the Offer. Stopping use, deleting an account and applying for a refund are different actions. Stopping use and deleting an account do not result in a top-up refund or payout of the unused balance.

The payment confirmation and credit record appear in the balance history in the account dashboard. The payment provider may issue its own notifications and receipts under its rules. Mandatory fiscal documents are generated under the applicable rules.

A refund on an established ground is processed against the original transaction in accordance with the law and the payment provider's rules. Support does not request banking secrets to consider an application. The payment provider does not become the provider of Ailoot's service: claims relating to its provision are considered by the ailoot.ai service.

Appendix 3. Refunds and Payment Disputes

1 Basic rule

1.1. A top-up of the prepaid balance is not refunded at the User's request, and the unused balance is not paid out in money, including when use ends, the account is deleted, the User changes their mind or subjectively disagrees with a correctly functioning model. Exceptions are the grounds listed in these rules and cases where a refund is mandatory under applicable legislation.

1.2. The exceptions are listed below. They include mandatory consumer rights and guarantees, erroneous and duplicate charges, payment not credited to the balance due to a payment failure, failure to provide the service and termination of the service by Ailoot without a breach by the User. An unlimited refusal stating ‘no refunds under any circumstances’ does not apply. The terms on which Ailoot obtains access to models from their suppliers do not remove Ailoot's obligations to its own Client.

1.3. Funds credited without payment, for example for testing if the Service provides them, are not refunded in money. A refund of a paid service is assessed on the basis of the original payment, its actual amount, the portion provided and applicable law. We do not use higher current prices to artificially reduce a refund due for a past payment.

2 Stopping use

2.1. Usage is paid for from the prepaid balance. To stop spending on requests and one-time top-ups, stop sending requests and making top-ups. To stop future automatic renewal of a monthly plan, cancel the subscription on the ‘Pricing’ page under clause 21.3 of the Offer. Inquiries about stopping use are accepted at support@ailoot.ai and should include the account email.

2.2. Stopping use does not cancel the portion already provided and is not grounds for refunding a payment made or paying out the unused balance. If a payment has already been made, it may be disputed on an applicable ground, but merely stopping use afterward does not make it erroneous.

2.3. Balance top-ups are paid for through the payment provider identified on the payment page. Deleting an Ailoot account does not cancel transactions already initiated with the payment provider. Support explains the applicable channel without falsely implying authority to independently refund any payment controlled by another party.

3 Erroneous and unauthorized payments

3.1. A confirmed duplicate charge, incorrect amount or charge without an agreed order is corrected to the relevant extent. The order, authorization, payment identifiers, amount, currency and payment provider information are compared during verification. Correcting one transaction does not mean refunding all other lawful purchases on the account. If payment fails or is not confirmed by the payment provider, the balance is not topped up; if money has nevertheless been debited from the payer, the amount is credited to the balance after payment confirmation or refunded through the payment provider and bank.

3.2. If you suspect an unauthorized transaction, immediately secure your account and API keys and contact your bank, as well as Ailoot at support@ailoot.ai. The matter is considered under applicable law and the bank's procedure. Any correct use of a password or API key must not be treated as sufficient grounds to deny statutory protection.

3.3. Do not send a full card number, CVV/CVC, PIN, password, full API key or one-time banking codes. For an initial inquiry, the account email, payment identifier, date, amount and description of the circumstances are sufficient. Additional verification of identity and ownership of the payment must be proportionate.

4 Failure to provide the service and defects

4.1. If a confirmed payment is not credited to the balance, the Service's own error causes an incorrect charge or paid functionality materially differs from its description, provide the transaction details. We investigate and offer the correction, repeat provision, price reduction or refund required by law.

4.2. For a partially completed request, the processing actually provided and the disclosed charging procedure are taken into account. A client connection failure and a failure where the result is not provided through the platform's fault are not automatically treated as identical. A model supplier's invoice alone does not prove that the User received the promised service. If the outcome of a request cannot be confirmed, its reserve is retained until the outcome is verified; no duplicate charge is made and such a request is not automatically sent again.

4.3. An unverified or subjectively unsuccessful model response is not necessarily a legal defect in the service. Nevertheless, a general qualification concerning AI errors cannot exclude established non-conformity with promised features, a false description or a mandatory digital service guarantee.

5 Termination of access and changes to a paid service

5.1. If access to the Service is permanently terminated without a breach by the User, the prepaid portion not provided is settled. This rule also covers termination because the service cannot continue following the departure of a model supplier or a legal restriction. An available replacement for an individual route that preserves the agreed material capabilities does not, by itself, constitute termination of the entire service. Quantities already properly used do not automatically become refundable.

5.2. If a material deterioration of the service or a change to an existing agreement gives the User a statutory right to terminate the agreement and obtain a refund for the portion not provided, that right remains in effect. A price increase for future requests generally allows the User to stop using the service; it does not automatically recalculate past transactions.

5.3. A block for a proven breach does not create an independent right to a refund of any remaining balance. However, the balance cannot be confiscated contrary to mandatory law. An erroneous block may be challenged; refund consequences are considered after the grounds and relevant transaction have been verified.

5.4. Closing or deleting an account by the User is not grounds for refunding a top-up or paying out the unused balance. A lawful claim submitted before deletion is not lost merely because access to the interface ends. Records necessary for the application are retained to the extent permitted.

6 Mandatory consumer right of withdrawal

6.1. Where applicable legislation gives a consumer a right to withdraw from a distance contract, the withdrawal rights and time limits it establishes apply. The period is calculated and extended in the cases provided by applicable legislation; missing mandatory information is not remedied merely by referring to this appendix.

6.2. A separate express request from the consumer is used to begin providing the service before that period ends. In the event of subsequent withdrawal, only a lawful proportionate charge for what was actually provided may be retained if the necessary conditions for retaining it are met. The first request or top-up is not a universal waiver of all remedies.

6.3. For separate digital content not supplied on a tangible medium, exclusion of the right of withdrawal applies only where permitted by law and all conditions are met, including the necessary express consent to commencement, acknowledgment of the loss of the relevant right and confirmation of the agreement. These rules must not automatically be extended to every ongoing service merely because it is described as ‘digital’.

6.4. Mandatory time limits, guarantees and remedies granted to consumers by applicable legislation remain in effect. Ailoot's voluntary policy does not replace them with a less favorable regime.

7 Payment provider and third-party programmes

7.1. The grounds, party responsible for processing a refund and payment application procedure depend on the payment method, payment provider's rules and mandatory law. An application is directed to the party authorized to process the relevant payment. If the payment provider requires a particular transaction identifier, support explains where to find it without requesting card secrets.

7.2. Top-ups or unused balances are not refunded beyond the grounds specified in these rules and cases where a refund is mandatory under applicable legislation. Contacting support, including about another matter, does not create a promise of such a refund.

7.3. Corporate migration programmes, credit programmes or special procurement commitments of other companies, including model suppliers, do not become part of Ailoot's terms unless expressly offered by the Service. An application is considered under the User's agreement with the ailoot.ai service, rather than under Ailoot's rights as a customer of another service.

8 Application, documents and time limits

8.1. Send the following to support@ailoot.ai: the applicant's name, account email, payment ID, date, amount and currency, requested action and information relevant to the grounds. For an API error, the request ID, model, method and time are useful. Do not send excessive personal files if identifiers are sufficient.

8.2. Where there is a right to withdraw without giving a reason, no reason needs to be stated. You may write: ‘I hereby give notice of withdrawal from the agreement relating to payment [number], made on [date]. Name [name], account email [email], application date [date]’. Another unambiguous statement, an applicable standard form and a statutory withdrawal feature on the website are also permitted.

8.3. The ability to simply stop using the service does not replace a mandatory online withdrawal feature where required by law. Support must not deliberately send the User through repetitive actions to obstruct an application.

8.4. A refund to which the User is entitled is made without undue delay within the period established by applicable legislation.

8.5. The period for verification and initiation is not the same as the date on which funds appear with the issuing bank or payment provider. We communicate the status and available refund identifier. If necessary confirmation is missing, we explain what information is required; this does not permit artificially restarting a mandatory time limit.

9 Method, amount and payment dispute

9.1. A refund is processed against the original transaction, in the original transaction currency and using the original payment method where required by applicable law and the payment provider's and bank's rules. For a closed card or a particular payment route, the lawful procedure established by the servicing party is used. Arbitrary transfers to third parties or cash payouts are not offered.

9.2. The amount is determined on the basis of the documented paid portion not provided, applicable law and the terms of the particular payment. Funds credited without payment are not paid out in money. Unjustified penalties and deductions are not introduced, and Ailoot's expenses with a model supplier do not automatically become the User's expenses.

9.3. If a dispute has already been opened with the issuer or the amount has already been refunded through the dispute, actions are coordinated with the payment provider to avoid duplicate reimbursement. If a payment is disputed through a bank (chargeback) and the amount cannot be recovered from the balance, the difference becomes the User's debt. Until it is repaid, new requests from the User are not accepted and the message ‘payment disputed, access suspended’ is displayed. The debt is automatically repaid from subsequent top-ups or released reserves. We do not require waiver of statutory rights as a mandatory condition for initial consideration. If a refund is refused, the grounds and available way to apply again are communicated.

9.4. The service provider is the ailoot.ai service. Inquiries are accepted at support@ailoot.ai. The right to contact a bank, competent authority or court in the manner established by applicable legislation remains available.

Appendix 4. Acceptable Use Rules for Ailoot

1. Purpose and scope of the rules

1.1. These rules define the basic boundaries for using the ailoot.ai Service: the ailoot.ai website, account dashboard, API at https://api.ailoot.ai/v1, Input Materials, Results and permitted integrations. They apply to the User, their authorized persons and, for API integrations, end users of the Client's product to the extent the Client provides them with access to Ailoot.

1.2. Ailoot provides access to different Models and Routes. They may have additional mandatory restrictions concerning age, country, organization, Content type, distribution of Results, security, licenses, data or technical limits. These are shown before use in Appendix 5 to the Offer (‘Model and Supplier Terms’) and the model catalogue in the account dashboard. Such a rule applies to the relevant Route but is not declared, without grounds, to be a universal prohibition for every other Model.

1.3. The User must not use the Service if the selected Route is incompatible with their country, role, age, data or task. Changing a model, automatically falling back to another route or changing the execution region must not be used to circumvent the agreed budget, data requirements, availability or a supplier's mandatory restriction.

1.4. These rules do not promise that Ailoot will recognize every violation in advance, continuously moderate all requests or prevent every harmful result. The Service may nevertheless check the necessary portion of data using automated means and human review where required for security, legal compliance, consideration of a complaint, protection of rights or operation of a particular feature. The scope of a check is limited by its purpose and applicable law.

2. General obligations of the User

2.1. The User complies with applicable law, the Order terms, these rules, the rules of the selected Model and third-party rights. They are responsible for the lawfulness of Input Materials, instructions, choice of Route, use of Results and actions they instruct to be carried out through an available feature.

2.2. The User must have the necessary rights, licenses, authority and consents to upload, process, transmit, publish and use each material. A person must not impersonate another person, organization, Ailoot representative or Model supplier without a lawful basis and express permission.

2.3. A Corporate Client and a developer providing their own product through the Ailoot API communicate applicable restrictions and necessary AI notices to end users, obtain required consents and do not extend users' rights beyond their own Order and the Model Terms. In a user chat or other interface, the Client clearly discloses the use of AI where required by law, the selected Route or the nature of the interaction. Lawful integration of a permitted API into one's own application is allowed; it does not grant a right to transfer a third-party account or supplier key or broker undisclosed access to another party's technology.

2.4. Requirements concerning age, territory, organization, payment, limits, models, data modes or security must not be circumvented by misrepresenting identity, country, request source, account or other information. Use of a VPN, proxy or another network security tool is not prohibited in itself, but it must not serve as a means of obtaining prohibited access.

3. Prohibited unlawful and dangerous use

3.1. The Service must not be used for an action that is itself unlawful or to knowingly facilitate such an action. In particular, trafficking in persons, exploitation, extortion, fraud, theft of identity or credentials, forgery of documents, money or payment data, sale of counterfeit goods, conducting or facilitating real-money gambling, unlawful trade in prohibited goods and services, and concealment of the criminal origin of funds or data are prohibited.

3.2. Creating, organizing, directing or substantially facilitating threats, intimidation, harassment, violence, terrorism, extremist violence, discriminatory practices or abuse of people or animals is prohibited. Practical instructions that increase the ability to cause serious physical harm, create, acquire, deliver or use weapons or highly dangerous explosive, chemical, biological, radiological or nuclear agents, or circumvent mandatory controls over them, must not be requested.

3.3. Destroying, disrupting or obtaining unauthorized access to critical infrastructure, communications facilities, transport, energy, healthcare, financial systems, water supply systems and other critical systems is prohibited. Lawful risk analysis, safety education and historical or academic discussion do not constitute a violation in themselves, provided a request does not become instructions for unlawfully affecting a real target.

3.4. Causing psychological harm or exploiting a person's vulnerability is prohibited: encouraging suicide, self-harm, eating disorders, dangerous challenges, appearance-based humiliation, sexual violence, graphic violence for harassment or manipulative emotional pressure. Supportive, preventive, educational and artistic discussion of these subjects is not prohibited in itself; however, a Result does not replace emergency assistance, a doctor, psychologist or another qualified source of help.

4. Systems security and good-faith technical research

4.1. Creating, delivering or using malicious code, ransomware, botnet, phishing, credential harvesting, unauthorized scanning, vulnerability exploitation, denial of service, interception of communications, persistence, covert installation of components, circumvention of safeguards, interference with hardware or firmware, and obtaining or publishing other parties' secrets are prohibited.

4.2. Using the Service for unauthorized red teaming, social engineering against real people, circumventing other services' restrictions, jailbreak for a harmful result or preparation for mass compromise is prohibited. Automation, multiple accounts, proxies, keys or technical errors must not be used to evade a rate limit, quota, block, check or fee.

4.3. Lawful defensive research, auditing one's own resource, educational work, vulnerability analysis with the owner's permission and development of safeguards are permitted. The User must have authority, limit testing to their own system or agreed scope, refrain from extracting other parties' data and not apply a Result against a real target without permission. If the selected Route requires prior approval for such a task, that requirement applies.

5. Privacy, identity and biometric information

5.1. Collecting, buying, selling, disclosing, combining, tracking or profiling other people's private, confidential, contact, medical, financial, account, biometric, neural or other sensitive data without the right and necessary consent is prohibited. Doxxing, covert surveillance, unauthorized location tracking, interception of communications and attempts to obtain a password, banking code or other secret are prohibited.

5.2. Creating a facial recognition database, conducting remote biometric identification in a public space, performing social scoring or inferring a person's sensitive traits, emotions, health, sexuality, religion, political views or risk of committing a crime without a lawful basis and required safeguards is prohibited. In particular, using such inferences to monitor workers, students or other persons in vulnerable positions is impermissible where prohibited by law or the route terms.

5.3. A person's image, voice, video, name, signature, personal style or other characteristics must not be used to plausibly represent their participation, statement or consent without the necessary rights and consent. Presenting AI as a human or concealing the artificial origin of a Result is prohibited where it misleads the recipient or violates the law, personal rights or a rule of the selected Model.

6. Minors and sexual content

6.1. Child sexual abuse material, including material created or altered by AI, grooming, sexualization or imitation of a minor, involving a child in a dangerous or age-restricted action, concealment of exploitation and any attempts to circumvent age safeguards are strictly prohibited. Where there is a clear risk to a child, the Service may impose an urgent restriction and act in the manner required by law.

6.2. Creating or distributing unauthorized intimate material, sexual violence, images or recordings of a person without consent, or using the Service for sexual coercion, harassment or blackmail is prohibited.

6.3. These general rules do not automatically prohibit every lawful adult conversation about relationships, sexual health, culture, literature, art or a fictional plot. However, an individual Model may completely prohibit explicit sexual content, erotic roleplay or another type of adult material. Such a stricter rule applies only to the expressly identified Route and must be visible before the request is sent.

7. Accuracy, manipulation and decisions of public significance

7.1. A Result must not be used to fraudulently mislead others about identity, source, events, organizations, law, science, health or another material fact. Fake reviews, fabricated endorsements, false documents, false attribution of authorship/source, presenting synthetic media as authentic, covert imitation of a voice or face for deception, and presenting AI work as the user's independent work in an assessment where this violates the relevant institution's or assignment's rules are prohibited.

7.2. Using the Service for targeted political persuasion of specific people based on their profiles, misleading election campaigns, false voting information, suppression of electoral participation or disruption of the electoral process is prohibited. Lawful information sharing, neutral analysis, journalism, research and historical or public discussion are not prohibited in themselves if they do not become deception or unlawful interference.

7.3. AI must not be used as the sole or automatically final mechanism for a decision with legally significant or comparably serious consequences for a particular person, including decisions concerning credit, insurance, hiring, dismissal, housing, education, medicine, legal status, access to an essential public service, migration, law enforcement measures or product safety. Permitted supporting work requires a lawful basis, qualified human oversight before the final decision, verification of the Result and required notification of AI use.

7.4. Results concerning law, medicine, mental health, finance, investments, insurance, taxes, safety or another regulated field do not, by themselves, constitute a professional service, diagnosis, personal recommendation or guarantee of compliance. The User must ensure qualified review and compliance with the special requirements of applicable law and the Route.

8. Intellectual property rights, brands and third-party materials

8.1. Infringing third-party copyright, related rights, patent rights, trademark rights, trade secret rights, image rights, contractual or other rights is prohibited. The User must not upload restricted materials, pass off another party's work as their own, remove mandatory attribution or use a Result contrary to an applicable license.

8.2. Copying, selling, renting, distributing, reverse engineering or extracting non-public parts of the ailoot.ai Service, its interface, data, models, algorithms and systems is prohibited, except for actions expressly permitted by law or published documentation. Authorized API access is not automated data collection (scraping) of the interface and does not grant a right to bulk-extract protected data, other parties' Results or internal information.

8.3. Ailoot's, a Model supplier's or a third party's designations must not be used to suggest an official partnership, certification, endorsement or sale of another party's account where none exists. The procedure for reporting suspected infringement of rights is described in appendix 6 to the Ailoot Privacy Policy (‘Infringement of Intellectual Property Rights’).

9. Platform, accounts and commercial use

9.1. Selling, gifting, transferring or publishing another party's API key, password, account or access to it; creating accounts in bulk to circumvent terms; reselling Ailoot as covert access to a third-party Model; and interfering with charging, logs, limits, availability or payment are prohibited. This does not prohibit development of one's own product using the Ailoot API as permitted by the offer, provided the Client follows the documentation, discloses AI assistance to the end user, complies with flow-down requirements and does not conceal mandatory Route restrictions.

9.2. Input Materials or Results must not be used for training, distillation, extraction or creation of a competing model where prohibited for the selected Model, supplier or product. Ailoot does not impose this restriction on other Routes without its own rule or a mandatory requirement; the specific boundary is set out in Appendix 5 to the Offer (‘Model and Supplier Terms’).

9.3. Confidential data must not knowingly be sent through a Route that prohibits it, nor may attempts be made to misclassify data or circumvent a route-specific data setting. If the data terms are unsuitable for the task, the request must be rejected, deferred or sent only through an option lawfully chosen by the User that expressly permits such data.

9.4. The Service, including through API integrations or automated workflows, must not be used for covert access to other parties' systems and accounts, automated spam distribution, circumvention of an external service's terms or an action that the User is not authorized to approve.

10. Response to violations and appeals

10.1. Where there are reasonable indications of a violation, the Service may request explanations or documents, issue a warning, restrict a particular request, Result, key, integration, model, route, budget or account, or temporarily suspend access. The measure is selected in proportion to the risk, recurrence, law, technical capability and supplier's mandatory rules.

10.2. Action may be taken before notification where security, children, third-party rights, infrastructure or payment are threatened, or where required by mandatory law. In other cases, the Service communicates the grounds and available way to remedy the situation where possible. Restriction of one Route does not mean automatic confiscation of the entire lawfully funded balance or denial of a refund mandatory under Appendix 3 to the Offer (‘Refunds and Payment Disputes’) and applicable law.

10.3. The User may challenge an action by writing to support@ailoot.ai and identifying the account, request/notice identifier, circumstances and available supporting evidence. The Service considers the inquiry within a reasonable period, taking account of the nature of the risk. The Service is not required to disclose other parties' data, security methods, keys, investigation information or information whose disclosure is prohibited by law. A knowingly false complaint, fabrication of evidence or abuse of the appeal process may themselves constitute a violation.

10.4. Suspected infringement of intellectual property rights is considered under the separate procedure described in appendix 6 to the Ailoot Privacy Policy (‘Infringement of Intellectual Property Rights’). Removal or restriction of public material following a complaint does not constitute a final judicial determination of rights.

11. Changes and contact details

11.1. The rules may be updated following changes in the law, threats, features actually available, mandatory model terms or safeguards. A material change applies prospectively in the manner specified in the Offer; it does not create a hidden retroactive obligation for a request already completed.

11.2. Questions, reports of violations and appeals are to be sent to support@ailoot.ai. Service Provider: the ailoot.ai service.

Appendix 5. Model and Supplier Terms

The model usage rules form part of section 11 of the Offer. This directory helps locate technology suppliers' published terms for the selected model and route. The model catalogue and prices for each model and method are shown in the model catalogue in the account dashboard on ailoot.ai.

A single model may have different execution suppliers. The terms of the route actually selected apply, including its license, acceptable use and territorial and age restrictions. Requests are subject to model suppliers' usage rules (for example, the usage rules of Anthropic, OpenAI and Google). Before sending a request, consider the information in the model listing and route settings. Supplier rules do not change the Ailoot price stated in the model catalogue or replace the ailoot.ai service's responsibility for its own service.

The directory below lists technology suppliers whose models are available through Ailoot. Inclusion of a supplier does not mean that every request is sent to it. The directory itself does not establish a uniform retention period, training on data, processing location or Zero Data Retention mode for all models. Such terms depend on the selected model, route and available settings; for details, see the Ailoot Privacy Policy and its appendix 2 (‘Ailoot Data Settings’).

This directory is not a list of Ailoot's active routes or actual recipients of personal data. The terms applicable to a particular request are determined by the selected model, actual route and corresponding order.

The current restrictions of the selected model take precedence over a supplier's general description. If the applicable terms are unavailable or unclear, contact support@ailoot.ai before using the relevant model.

Appendix 6. Special Terms for Ailoot Features

1. When special terms apply

1.1. A section of this appendix applies only to a feature actually enabled for the User in the account dashboard, API documentation or confirmed Order. Mentioning beta, voice, video, a medical scenario or another capability does not mean that it is already available, certified, included in the model catalogue or promised by Ailoot.

1.2. Before a particular feature is first used, the model listing in the catalogue or the Route description must show its purpose, necessary Input Materials, material data terms, available settings, known limitations, usage measurement method and applicable model rules. In the event of a conflict, the special terms govern that feature but do not override mandatory law, the confirmed Order or the ailoot.ai service's obligation to provide its own service.

1.3. A third-party Model, tool or feature name does not convey to the User an account, key, cloud product, certification, SLA, data residency, zero-data-retention or commercial right of the supplier unless expressly offered and confirmed for the selected Route.

2. Early access, beta, preview and evaluation features

2.1. A feature is an early access feature only if expressly labelled in the interface or documentation as alpha, beta, preview, early access or evaluation. A stable paid feature does not retroactively become beta because of an incident, model change or inconvenience for support.

2.2. Before enabling such a feature, Ailoot discloses its experimental status, known material limitations, available level of support, applicable data and retention terms and a way to opt out, if provided. Beta may be changed, restricted or discontinued more quickly than a stable feature; this does not remove the User's mandatory rights or create a blanket disclaimer of liability not permitted by law.

2.3. Beta is not intended for production, safety-critical, regulated or other high-risk tasks unless the feature listing and the law expressly confirm otherwise. Beta does not equate to a guaranteed SLA, independent audit, industry certification, special retention regime or technical fitness for a particular purpose.

3. Files, attachments and Content

3.1. The User uploads only files and materials necessary for the task and to which they have rights. To execute a request, Ailoot transmits the file itself, its extracted text, technical properties, context fragments and other necessary data within the disclosed Route to the selected Model's supplier servicing the request. Such a supplier may be located outside the User's country.

3.2. Permitted formats, size, number of files, availability of analysis and retention period are determined by the actual feature and shown before upload or in documentation. Refusal to accept a file, incomplete text extraction, a format error or a context limit do not, by themselves, promise another processing method.

3.3. Checks for malicious code, technical compatibility, violations of Appendix 4 to the Offer (‘Acceptable Use Rules for Ailoot’) and legal compliance may be used to protect the Service. A check does not guarantee that a file is safe, free of rights infringements or produces a correct Result. The User must not upload secrets, sensitive third-party data or material that the selected Route does not permit to be processed.

3.4. Where a feature provides a library, project, history or persistent file storage, the interface must show how to find, manage and delete the object. Media files created on request are stored for the User to download; their retention period is determined by section 7 of the Ailoot Privacy Policy. Where no such feature exists, uploading a file for a single request does not become a promise of permanent storage, immediate deletion or backup in a particular country.

4. Search, browsing and external sources

4.1. Where search, browsing, retrieval or other access to an external source is enabled, the request, part of it and necessary technical parameters may be transmitted to that source to the extent specified by the feature. An external website, database, search provider and their materials have their own rules, availability, licenses and privacy policy.

4.2. External information and Results may be incomplete, outdated, erroneous, unavailable in a particular country or protected by third-party rights. The User verifies important facts, the original source, date, license and right to subsequent use. A link, quotation or summary does not mean that Ailoot or the supplier guarantees accuracy, endorses the source or transfers its intellectual property rights.

4.3. Search must not be used for bulk extraction of restricted content, circumvention of paywalls, robots/contractual restrictions, collection of personal data, spam or access to another person's account. Lawful open-source research, analysis of one's own database or search of materials to which the User has rights are not prohibited in themselves.

5. Voice, images and video

5.1. When a voice, audio, image or video feature is enabled (including image, video and music generation, speech synthesis and transcription), the User must have rights and, where necessary, consent for all uploaded or created materials. Particular attention is required for voices, faces, appearance, names, identity, images of children, and third parties' medical or other sensitive data.

5.2. A feature must not be used to identify a person, create a biometric profile, infer sensitive characteristics, or clone or plausibly imitate a voice/face without the necessary lawful basis and consent. Stricter restrictions of a particular Model apply only to that Model and are specified in Appendix 5 to the Offer (‘Model and Supplier Terms’).

5.3. Rights to a Result, permission for commercial use, mandatory labelling, restrictions on an individual audio file, likeness and public distribution may differ between Routes. The User checks them before publication. Ailoot does not promise uniqueness, absence of similarity, absence of third-party rights or permission for every form of distribution. Every result generated by a Model, including additional images or files returned by the supplier, is provided to the User and charged for based on actual usage.

6. Code, software Results and development

6.1. Code, a configuration, command, library or other technical Result may contain an error, an insecure dependency, third-party license restrictions or a fragment resembling another solution, or may require adaptation. The User conducts review, testing, security analysis and license and compliance checks before execution, publication or delivery to a user.

6.2. A Result does not replace a security audit, legal review of a license, code review, penetration test or manufacturer support. Code must not be used for prohibited interference with a system, circumvention of controls, license infringement or training/extraction of a Model where prohibited by the selected Route.

6.3. A developer integrating Ailoot into a product remains responsible for their UI, representations, data processing, user terms, disclosure of AI assistance, error handling and decisions made by their end users. They must not claim that their product is an official service of the Model supplier unless it has that status.

7. Context, Models and automatic routing

7.1. Context capacity, speed, queue, concurrency, tool use, availability and price depend on the particular Route. The price is stated in the model catalogue in the account dashboard separately for each model and method; charges are based on actual usage (tokens, images, seconds of video, minutes of audio, etc.). The stated maximum context window does not mean that the entire capacity is available solely for the User's Input Materials: system instructions, history, files, tools, protective processing and the Result may occupy part of it.

7.2. Automatic Model selection, fallback to another route, execution region, storage, training, security checks and logging are permitted only within the disclosed configuration, Model Terms and the User's/organization's choice. If an alternative path materially changes the data arrangements, country requirement, price or permitted task, the ailoot.ai Service must not covertly use it instead of the agreed Route. A request whose outcome could not be confirmed is not automatically sent again: its reserve against the balance is retained until the outcome is verified, and no duplicate charge is made.

7.3. The User may obtain available information about the actual Route, usage measurement and material data terms. Ailoot is not required to disclose secrets, keys, vulnerabilities, other clients' data or information whose disclosure would violate security, the agreement or the law.

8. Regulated, sensitive and high-risk scenarios

8.1. The Service is not a medical device, diagnostic system, legal representative, payment organization, investment adviser, insurance intermediary, personnel/credit scoring tool, critical infrastructure system or guarantor of compliance with an industry standard. Its use in such scenarios is possible only with a lawful basis, mandatory qualifications, human oversight, technical measures and permissive terms of the particular Route.

8.2. Protected health information, medical images for diagnosis, identity documents, biometric templates, banking secrets, state secrets or other sensitive material must not be submitted to an ordinary Route unless the feature listing and applicable agreement expressly permit such processing. An interface warning does not replace a separate agreement, risk assessment, consent, security measures or an appendix required by law.

8.3. If a separate feature for a regulated scenario is launched, its role, permitted purpose, necessary checks, Result limitations, specialist requirements, data arrangements, incident contact and applicable special terms must be published before use. Until then, this appendix does not promise HIPAA suitability or suitability for medical, financial, educational, government or other industry-specific purposes.

9. Changes, termination and relationship with other terms

9.1. Ailoot may develop, replace, restrict or discontinue a feature because of security, the law, technical compatibility, supplier rules or product development. A material change to an existing paid obligation is governed by the Offer, Order and Appendix 3 to the Offer (‘Refunds and Payment Disputes’); it does not provide grounds to retroactively alter a request already completed.

9.2. Where a feature involves an organization's personal data and the ailoot.ai service processes it under the Corporate Client's documented instructions, the Organizational Data Processing Terms (appendix 4 to the Ailoot Privacy Policy) also apply within their scope. Mentioning a feature on a public page does not replace a separate B2B DPA where one is required.

9.3. Questions about a feature, its restriction, the selected Route or data are to be sent to support@ailoot.ai. Service Provider: the ailoot.ai service.

Appendix 8. Contact Details and Service Information

Ailoot is the ailoot.ai software service. The Service provides its own software, routing of requests to models from different suppliers, processing and usage accounting for available features. A Client with an API key sends requests through interfaces compatible with OpenAI, Anthropic and Gemini and receives model responses: text, images, video, music, speech synthesis and transcription. Access to the Service is currently by invitation.

Support and inquiries

For inquiries concerning access, payment and the balance, refunds, data, security and content complaints, send a message to support@ailoot.ai. Include the account email, subject and payment or request ID relevant to the inquiry. Do not send a password, secret API key, full card number, CVV/CVC, PIN or banking confirmation code.

The consideration procedure is determined by the relevant document: the Offer and its Appendices 1 (‘Payment and Balance Rules for Ailoot’), 2 (‘Payment and Provision of the Digital Service’) and 3 (‘Refunds and Payment Disputes’), the Ailoot Privacy Policy and its appendix 3 (‘Deletion of the Ailoot Account and Data’), and appendix 6 to the Ailoot Privacy Policy (‘Infringement of Intellectual Property Rights’). Time limits for mandatory claims are observed in accordance with applicable law.