Home/Legal/Terms & Conditions
Legal Agreement

Terms & Conditions

The rules of the road for using AirLLM — written to be read. These Terms cover your account, your content, how billing works, what each of us promises the other, and how disputes are resolved.

Effective: October 23, 2026 Last updated: October 23, 2026 Version 2.2

At a glance — the plain-language version

Your work stays yours

You own your prompts, code, and outputs. AirLLM never uses any prompt to train models, on any plan, and never sells your content. On the Free plan, model providers may train on and retain your prompts.

You supervise the agent

AirCode can change files and run commands on your machine at your direction. Review what it does and keep backups — the results are your responsibility.

Provided as is

AI output can be wrong and isn't professional advice. The Services are provided "as is" and "as available", with no uptime commitment unless you have a signed SLA.

Limits & disputes

AirLLM is for business use only, not for consumers. Our liability is capped at the greater of 3 months of fees or US$100. Disputes go to individual arbitration in Austin, Texas, with a 30-day opt-out.

01The agreement

These Terms & Conditions (the "Terms") are a binding agreement between JettySoft LTD, the company that provides AirLLM ("AirLLM", "we", "us", "our") and the individual or entity using our Services ("you", "Customer"). They govern your access to and use of every AirLLM Service described in Section 02.

By creating an account, clicking "I agree", downloading or installing AirCode CLI or AirCode Studio, or otherwise using the Services, you accept these Terms, our Acceptable Use Policy, and — where you process personal data through the Services — our Data Processing Addendum, all of which are incorporated by reference. Our Privacy Policy explains how we handle personal information. If you use the Services on behalf of an organization, you represent that you have authority to bind that organization, and "you" refers to it. If you have a separate written enterprise agreement signed by AirLLM, that agreement prevails over these Terms to the extent of any conflict.

Record of your acceptance. When you accept these Terms while creating an account — by signing up, accepting an invitation, or first signing in with Google or single sign-on — we keep a record of it on our servers: the versions of these Terms and of our Privacy Policy you accepted, how you signed up, the date and time, and the IP address and browser details you accepted from. We keep that record for 7 years from acceptance, also after your account is deleted, as our Data Retention Policy describes.

This version of these Terms takes effect on October 23, 2026 and replaces the version that took effect on October 22, 2026.

Please read Section 22 carefully. Unless you opt out within 30 days, disputes are resolved by binding individual arbitration rather than in court, and class actions and jury trials are waived.

02Definitions & covered Services

  • "AirLLM Parties" means JettySoft LTD and its parent, subsidiaries, and affiliates, and each of their officers, directors, employees, contractors, agents, licensors, and suppliers. Every disclaimer, limitation of liability, and indemnity in these Terms protects all of the AirLLM Parties, and each of them may rely on and enforce those provisions.
  • "Services" means everything listed in the table below, including the chat, agent, and retrieval (RAG) applications described on our websites, together with any updates, new versions, and related support.
  • "Third-Party Providers" means the independent companies whose models, infrastructure, or services we use to deliver the Services — including model providers such as Anthropic, OpenAI, and Google (reached directly or through aggregation providers), cloud and hosting providers, payment processors, and our other subprocessors.
  • "Input", "Output", and "Customer Content" are defined in Section 06, and "Agent Actions" in Section 09.
ServiceWhat it is
AirLLM platform & websitesThe AirLLM platform, its APIs, and the websites we operate
Air RouterThe intelligent routing layer and its API, which selects a model for each request and returns the response to your tools
AirGPUGPU capacity operated by AirLLM for selected work, with fallback to Third-Party Providers
AirCodeOur coding agent, including AirCode CLI (downloadable terminal software) and AirCode Studio (downloadable desktop software)
Control PlaneThe dashboard, with its account, team, API-key, usage, billing, and policy controls
AlinaOur AI support agent
Docs & integrationsDocumentation, setup scripts, configuration examples, SDKs, and integrations with third-party tools
Beta & preview featuresAny feature labelled alpha, beta, preview, experimental, early access, or similar (see Section 11)

03Eligibility, accounts & API keys

  • Eligibility. You must be at least 18 years old (or the age of majority in your jurisdiction) and not barred from using the Services under applicable law, including export-control and sanctions laws.
  • Business use only. AirLLM is offered only to businesses. You may use the Services only for your trade, business, craft, or profession — sole traders and freelancers included — and not as a consumer. By creating an account, you confirm that you are using AirLLM for business. If consumer-protection law applies to you anyway, nothing in these Terms takes away the rights that law gives you.
  • Account accuracy. You agree to provide accurate registration information and keep it current.
  • Credentials and keys. Passwords, API keys, and sign-in codes are confidential, and you are responsible for keeping them secure. You are responsible for all activity and charges under your account and keys — including activity by agents, scripts, and integrations that use them — whether or not you authorized it, until you tell us of a compromise through our Contact page and revoke the affected keys. Do not embed keys in client-side code or public repositories.
  • Workspaces. If your account belongs to an organization's workspace, the workspace administrator controls access, data, and billing for that workspace.

04How the Services work

Air Router receives requests from your tools, selects a model for each request or step based on the alias you call, the work being done, and your plan, and returns the response in the format your tool expects. A request may be served by a Third-Party Provider's model or on AirGPU. AirCode, the chat, agent, and retrieval (RAG) applications, and the Control Plane are built on top of Air Router.

  • Model aliases. Aliases such as airllm-auto, airllm-anthropic, or airllm-openai map to underlying models that we may add, substitute, or retire as providers evolve. We aim for equivalence or improvement in capability when we change a mapping, but we do not guarantee that any particular model will serve a request.
  • Automated decisions. Routing, model-selection, fallback, and caching decisions are made automatically and on a best-effort basis. They may not always pick the fastest, cheapest, or most capable option for a given request.
  • AirGPU. AirGPU capacity is limited and its availability is not guaranteed. When AirGPU cannot serve a request, or the work needs a stronger model, the request may be sent to a Third-Party Provider instead.
  • Short-lived caches. To serve your requests faster and at lower cost, request content may be held briefly in short-lived caches scoped to your account that expire automatically, generally within 24 hours of last use (see Section 07).

05Third-party providers

To fulfill a request, AirLLM transmits the necessary request content to the model provider selected for it, receives the generated completion, and returns it to you. Completions that are not served on AirGPU are generated by third-party models operated by companies such as Anthropic, OpenAI, and Google, reached directly or through aggregation providers. We also rely on other Third-Party Providers, for example for hosting, networking, and payments. Accordingly:

  • Their terms, not ours. Each Third-Party Provider is an independent company that processes data under its own terms of service and privacy policy. To the maximum extent permitted by applicable law, the AirLLM Parties do not control, and are not responsible or liable for, how any Third-Party Provider stores, retains, logs, uses, or discloses data — including any model training it carries out under its own terms — or for its availability, outputs, or security;
  • Your authorization. By submitting a request you instruct and authorize AirLLM to transmit the content necessary to fulfill it to the selected provider;
  • Provider policies. Your use of a given model must also comply with that provider's usage policies, which we pass through to you;
  • Tenant-scoped keys. We may provision a tenant-scoped upstream key for your organization so that your traffic is billed and isolated under your own provider relationship, in which case your own agreement with that provider also applies;
  • Changes and outages. Provider models, capabilities, prices, and availability can change without notice. We are not responsible for provider outages, deprecations, content-filtering decisions, or errors, though we may route around them where we reasonably can;
  • Services you connect. Third-party tools, editors, repositories, MCP servers, packages, and other services you connect to or use with the Services are governed by their own terms, and you use them at your own risk.

The subprocessors we use for the Services are listed in our DPA.

06Your content — inputs & outputs

"Input" means the prompts, code, files, and other content you submit to the Services; "Output" means the completions and other content the Services return in response. Input and Output together are "Customer Content".

  • Ownership. As between you and AirLLM, you own your Input. To the extent we hold any rights in Output, we assign them to you. Because models generate probabilistically, Output may not be unique to you, and other customers may receive similar or identical Output from similar Input; this assignment does not extend to another customer's output.
  • Our license. You grant us a worldwide, non-exclusive, royalty-free license to host, process, transmit, cache, store, and display Customer Content solely to provide, secure, and maintain the Services (including diagnosing failed requests and checking routing quality, as described in Section 07), comply with law, and enforce our policies.
  • Your responsibility. You are responsible for your Customer Content — including having all the rights, permissions, and consents needed to submit it, and ensuring that your use of Output complies with law and does not infringe anyone's rights.
  • Sensitive data. You decide what you send. Do not submit passwords, secrets, or sensitive personal data unless you need to and are legally permitted to.

07Model training & content storage

Our commitment: AirLLM never uses any prompt to train models, on any plan. AirLLM never uses your prompts, code, files, outputs, or support chats to train, fine-tune, or improve any AI model, and never sells them.

  • Every Service, every plan. This commitment applies to every Service, including Alina and beta and preview features, and to every plan. It covers what AirLLM does; what model providers may do is described in the next item. See also our Privacy Policy.
  • Model providers and your plan. Model providers may retain prompts under their own policies, for example to monitor for abuse. On paid plans, AirLLM avoids model providers that use prompts to train models. On the Free plan, model providers may use your prompts to train models and may retain them. If that matters for your use, choose a paid plan.
  • Content we keep. AirLLM doesn't store prompts to train models. To run the service, request content — the prompts and responses of requests sent through Air Router or the AirLLM API, including the model calls AirCode makes — passes through short-lived, account-scoped caches that expire automatically, generally within 24 hours of last use. When a request fails, we may keep its content, with secrets removed, to diagnose the failure, and we may keep samples of responses to check routing quality; these records are deleted with your account's data. The content of a failing request, with secrets removed, may also be attached to a ticket in our engineering issue tracker, where it is kept only as long as needed to diagnose and fix the problem, with access limited to our engineering staff. None of these records is used for training or sold.
  • AirCode sessions. AirCode session transcripts shown in the Control Plane are relayed live from your machine; AirLLM holds them for at most about a minute to deliver them and does not store them. Instructions an administrator types into a session from the Control Plane, and session control records (pause, resume, end), are stored with the session's records.
  • Alina support chats. When you use Alina, your question and Alina's answer — with the page you were on and, when you're signed in, your account ID — are stored so we can answer you, investigate problems, and improve our support answers and documentation. Reviewing support chats to improve our written support answers and documentation is not model training. We delete support chats when they are no longer needed for support, and on request. In your browser, the open conversation is kept only for the browser session.
  • Safety records. If a safety guardrail or an Acceptable Use review is triggered, we may keep a record that includes the text that triggered it, for up to 2 years, for enforcement and legal defense.
  • Usage metadata. We keep usage metadata that contains no content — such as timestamps, token counts, the model that served a request, latency, and errors — for billing, security, support, and service-quality metrics, under the schedule in our Data Retention Policy.
  • Third parties are separate. This commitment covers AirLLM. Third-Party Providers process content under their own terms and may keep data under those terms, as described in Section 05.
  • On your own devices. AirCode CLI and AirCode Studio keep their own data — such as history, settings, and project files — on your device, under your control, and you are responsible for securing and backing it up.
  • What you send us directly. Information you choose to send us outside of model requests — such as support tickets, messages through our Contact page or to our Legal Cell, or feedback — is handled under our Privacy Policy.

08Use requirements & restrictions

You agree to use the Services in compliance with applicable law and our Acceptable Use Policy. In addition, you must not:

  • Reverse engineer, decompile, disassemble, or attempt to discover the source code, routing logic, or non-public model configurations of the Services, except where such restriction is prohibited by law;
  • Circumvent rate limits, usage budgets, safety systems, billing checks, or access controls, or probe or scan the Services other than through an authorized security program;
  • Interfere with or disrupt the Services, other customers' use of them, or the networks and systems behind them;
  • Resell, sublicense, or provide the Services to third parties as a stand-alone offering without a reseller agreement (building your own product on our API is welcome);
  • Use Output to develop or train AI models that compete with the Services, or in any way the serving provider's terms prohibit;
  • Represent Output as human-generated where doing so would deceive anyone, or remove required AI-disclosure notices;
  • Scrape the Services, or benchmark them for publication without identifying the configuration used and giving us reasonable notice.

09AirCode agents & automated actions

AirCode CLI and AirCode Studio act on your machine at your direction. Depending on the permissions and modes you choose, AirCode can read, create, change, and delete files; run commands and scripts; install dependencies; make commits; launch simulators, emulators, and browsers; and reach network resources. These are "Agent Actions".

You are in charge of the agent. Treat AirCode like any powerful developer tool: watch what it does, review its changes, and keep backups. You are solely responsible for Agent Actions and their results.

  • Supervision. You are responsible for supervising AirCode, reviewing its changes and commands before you approve or rely on them, and choosing which permissions and approval modes to enable. If you let AirCode act without approving each step, you accept that added risk.
  • Backups and environments. Keep your work under version control and backed up, and run AirCode only in environments suited to the task — not against production systems, live data, or credentials you cannot afford to have changed or exposed.
  • What it reaches. You are responsible for the commands it runs, the packages and dependencies it installs, the services and networks it contacts, and for complying with the licenses and terms of anything it uses on your behalf.
  • No liability for Agent Actions. To the maximum extent permitted by applicable law, the AirLLM Parties are not liable for data loss, damage to code, systems, or devices, costs or charges (including third-party cloud, API, or service charges), or security incidents arising from Agent Actions.
  • Routing and AirGPU. To the same extent, the AirLLM Parties are not liable for the results of Air Router's routing, model-selection, and fallback decisions, which are automated and best-effort, or for AirGPU being unavailable.
  • Safeguards are best-effort. Loop protection, budget and spend controls, and similar safeguards are provided on a best-effort basis. They are not guaranteed to stop a run or to prevent charges, and you remain responsible for monitoring your usage and for all charges incurred under your account.

10AirCode software license

Subject to these Terms, AirLLM grants you a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to install and use AirCode CLI and AirCode Studio (the "Software") on devices you own or control, for your internal purposes, while your account is in good standing.

  • Restrictions. You may not copy the Software (except as needed to install and use it), modify, distribute, sell, rent, or sublicense it; reverse engineer, decompile, or disassemble it, except to the extent applicable law expressly permits despite this restriction; or remove or bypass any notice, license check, or security feature.
  • Open-source components. The Software may include open-source components licensed under their own terms. Where those terms grant you broader rights in a component, they apply to that component.
  • Updates. The Software may check for and install updates automatically, and some updates may be required to keep using the Services.
  • As is; may change. The Software is provided "as is" under Section 18. We may change, suspend, or discontinue the Software or any version of it, or stop supporting particular operating systems or versions.
  • Your devices. You are responsible for the devices, operating systems, and environments you install the Software on.
  • End of license. This license ends automatically when your account closes, when these Terms end, or if you breach this section; you must then stop using and uninstall the Software.
  • Ownership. The Software is licensed, not sold. AirLLM and its licensors keep all rights not expressly granted.

11Beta, preview & free features

Features labelled alpha, beta, preview, experimental, early access, or similar ("Beta Features"), and the Free plan and any other features offered at no charge ("Free Features"):

  • are provided "as is" and "as available" without any warranty of any kind, and are not covered by any SLA or support commitment;
  • may be unstable, incomplete, or inaccurate, and may change, be limited, or be withdrawn at any time without notice;
  • may be subject to additional terms we show you when you use them; and
  • remain covered by AirLLM's no-training commitment in Section 07 — though on the Free plan, model providers may use your prompts to train models and may retain them, as Section 07 explains.

Do not rely on Beta Features for production or critical work.

12Plans, fees & payment

Plan types

  • Subscription plans are billed monthly in advance. Each plan's usage allowance is released in weekly portions, and weekly usage limits apply. When a key reaches its weekly limit, we refuse further requests (with an HTTP 402 error) until the limit resets. If the key still has credit on its balance, or has auto-recharge turned on and the recharge payment succeeds, requests continue instead, and usage past the weekly limit is charged to that balance at usage-based rates. Reaching the weekly limit doesn't move a key to other or lower-cost models. Only if a fault on our side briefly stops us checking a key's usage or balance may we serve it with lower-cost models, at no charge, until the check works again.
  • Prepaid token plans draw down a prepaid balance per request. Prepaid plans are fail-closed: when your balance reaches zero — or cannot be verified — requests are rejected with an HTTP 402 error until you top up.
  • The Free plan is available at no charge, limited to one per account, and includes a limited usage budget on free and lower-cost models. It does not convert to a paid plan automatically. Once a key moves from the Free plan to a paid plan, it cannot return to the Free plan. We may change the Free plan's limits at any time. On the Free plan, model providers may use your prompts to train models and may retain them (Section 07).

Billing terms

  • Responsibility for charges. You are responsible for all fees and usage charges incurred under your account and keys, including usage generated by agents, scripts, and integrations. Budget and spend controls are best-effort (see Section 09).
  • Automatic renewal. Paid monthly plans renew automatically on the 1st of each month, at the plan's monthly price, until you cancel. When you buy a plan partway through a month, the first charge may be prorated for the rest of that month. We ask for your consent to automatic renewal when you buy a plan and keep a record of it, and we email you a receipt for every charge. Once a year we also email you a reminder that lists every plan on your account that renews automatically, with its price, its next renewal date, and how to cancel it.
  • Cancelling a plan. You can cancel anytime in the dashboard: API Keys → the key → Cancel. Cancelling stops automatic renewal: the key keeps working until the end of the period you've paid for and isn't charged again. Fees aren't refunded except where the law requires.
  • Turning a key back on. When you turn a paid key back on, we ask you to agree to automatic renewal again. If the period you've paid for hasn't ended, nothing is charged that day and the key renews on the 1st as usual. If it has ended, you're charged for the rest of the current month, prorated like a new plan's first month. You're never charged for the months while the key was off; usage from before you turned it off is still billed.
  • Auto-recharge. Auto-recharge starts only after you agree to it, and we keep a record of your agreement. While it's on, we charge your payment method automatically, for the recharge amount you chose, whenever the key's balance falls below the amount you chose — and, on a subscription key, when the key reaches its weekly limit without enough balance left. You can turn auto-recharge off at any time in API Keys, and nothing is recharged after that.
  • Refunds. Except where required by law, fees are non-refundable, including unused prepaid balances and partial subscription periods.
  • Price changes. We will give at least 30 days' notice before a price increase, effective on your next renewal.
  • Payment processing. Card payments are processed by our payment processor, Stripe, which handles your card data under its own terms.
  • Taxes. Prices and fees exclude taxes. You are responsible for the VAT, GST, sales, use, and similar taxes that apply to your purchases, other than taxes on our income. Where the reverse-charge rules apply (for example, for business customers in the EU or the UK), you account for that tax yourself.
  • Failed payments and late payment. If a charge fails, we email the billing contact on your account with the amount due, a link to pay, and the date the affected service would pause, and we send reminders before that date. We may suspend the Services for overdue undisputed amounts only after 14 days' written notice by email to the billing contact. Once the amount is paid, the reminders stop.

13Availability & changes to the Services

We work to keep the Services fast and available, but they are provided "as is" and "as available". We make no uptime, latency, or availability commitment unless a separate written enterprise SLA signed by AirLLM says otherwise.

  • Outages and errors. To the maximum extent permitted by applicable law, the AirLLM Parties are not liable for outages or interruptions (including those of Third-Party Providers), failed, delayed, or incomplete requests, routing or caching errors, or lost or corrupted data. Keep your own copies of anything important.
  • Changes. We may modify the Services — including routing behavior, models, and features — provided we do not materially degrade the core functionality of your paid plan during a paid term. We may discontinue a Service as described in Section 21.
  • Maintenance. We may perform scheduled maintenance with reasonable notice and emergency maintenance without notice.
  • Performance figures. Savings, speed, uptime, benchmark, and similar figures on our websites or in our materials are estimates or past results under specific conditions. They are not commitments, and your results may differ.

14AI output disclaimer

Artificial intelligence is probabilistic. Output may be inaccurate, incomplete, outdated, biased, insecure, offensive, or otherwise harmful, and may not reflect our views. It is provided "as is" and is not professional advice.

Output is not legal, medical, financial, security, engineering, or other professional advice. You must review, test, and evaluate Output for accuracy and fitness before relying on it or shipping it, and you are solely responsible for your use of Output and for any decisions, code, or products based on it. To the maximum extent permitted by applicable law, the AirLLM Parties are not responsible or liable for Output. In particular:

  • Review and test all generated code before deploying it, especially code touching security, payments, or production data;
  • Do not rely on Output as a substitute for advice from a qualified lawyer, doctor, accountant, financial advisor, security professional, or engineer;
  • Keep a qualified human in the loop for any consequential decision about a person, such as employment, credit, housing, insurance, or medical care.

Alina. Our AI support agent can make mistakes too. Its answers are general information only, are not legal advice, and do not change these Terms or our policies or create any commitment on AirLLM's behalf. If an answer conflicts with these Terms or our policies, the Terms and policies control.

15Security

We use reasonable administrative, technical, and physical safeguards designed to protect the Services and the data we process. No system is completely secure, however, and we do not guarantee that the Services, or data sent to or through them, will be secure or free from unauthorized access, loss, or attack.

  • Limits on our liability. To the maximum extent permitted by applicable law, the AirLLM Parties are not liable for unauthorized access to, breaches of, or attacks on the Services or your data, except to the extent caused by AirLLM's own gross negligence or willful misconduct.
  • Your part. You are responsible for securing your credentials, API keys, devices, and networks, the machines and environments where you run AirCode, and your own applications and integrations.
  • Breach notification. If we become aware of a security breach affecting your personal data or Customer Content in our systems, we will notify you without undue delay, as required by applicable law and as described in our DPA.
  • Reporting. Report suspected vulnerabilities or compromised keys through our Contact page. Security testing of the Services is allowed only with our prior written authorization.

16Intellectual property & feedback

We and our licensors own the Services, including our software, routing technology, documentation, trademarks, and all improvements. Except for the rights expressly granted in these Terms, no rights are transferred to you. The AirLLM, Air Router, AirGPU, AirCode, and Alina names and logos are trademarks of AirLLM or its affiliates and may not be used without our permission, except to refer to the Services accurately. If you send us feedback, ideas, or suggestions, you grant us a perpetual, irrevocable, royalty-free license to use them without restriction or obligation to you.

17Confidentiality & privacy

Each party will protect the other's non-public information with at least reasonable care, use it only to perform under these Terms, and disclose it only to personnel and advisors bound by confidentiality obligations, or where required by law with notice to the other party where lawful. Our handling of personal information is described in the Privacy Policy, and processing of personal data in Customer Content is governed by the DPA.

18Warranty disclaimer

EXCEPT AS EXPRESSLY STATED IN THESE TERMS, THE SERVICES — INCLUDING AIR ROUTER, AIRGPU, AIRCODE CLI, AIRCODE STUDIO, THE CONTROL PLANE, AND ALINA — AND ALL OUTPUT ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITH ALL FAULTS. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE AIRLLM PARTIES DISCLAIM ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE.

WITHOUT LIMITING THE ABOVE, THE AIRLLM PARTIES DO NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE; THAT OUTPUT, OR ANY ROUTING, MODEL-SELECTION, OR FALLBACK DECISION, WILL BE ACCURATE, COMPLETE, RELIABLE, OR SUITABLE FOR YOUR PURPOSE; THAT AGENT ACTIONS WILL PRODUCE THE RESULTS YOU INTEND; THAT DATA WILL NOT BE LOST OR CORRUPTED; OR THAT DEFECTS WILL BE CORRECTED. BETA FEATURES AND FREE FEATURES ARE PROVIDED WITHOUT ANY WARRANTY OF ANY KIND. NO ADVICE OR INFORMATION, WHETHER FROM AIRLLM OR FROM ALINA, CREATES ANY WARRANTY NOT EXPRESSLY STATED IN THESE TERMS. SOME JURISDICTIONS DO NOT ALLOW CERTAIN DISCLAIMERS, SO PARTS OF THIS SECTION MAY NOT APPLY TO YOU.

19Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW: (a) IN NO EVENT WILL ANY OF THE AIRLLM PARTIES BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, DATA, OR GOODWILL, OR THE COST OF SUBSTITUTE SERVICES, ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY (INCLUDING CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, OR STATUTE), EVEN IF ADVISED OF THE POSSIBILITY OF THOSE DAMAGES; AND (b) THE TOTAL AGGREGATE LIABILITY OF ALL AIRLLM PARTIES COMBINED FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THESE TERMS OR THE SERVICES WILL NOT EXCEED THE GREATER OF (i) THE FEES YOU PAID TO AIRLLM FOR THE SERVICES GIVING RISE TO THE CLAIM IN THE 3 MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY, OR (ii) US$100. THESE LIMITATIONS APPLY EVEN IF A REMEDY FAILS OF ITS ESSENTIAL PURPOSE, AND THEY ARE AN ESSENTIAL BASIS OF THE BARGAIN BETWEEN YOU AND AIRLLM.

Without limiting the above, and to the maximum extent permitted by applicable law, the AirLLM Parties are not liable for losses arising from Output (Section 14); Agent Actions, or routing, model-selection, and fallback decisions (Section 09); the acts, omissions, outages, data handling, or security of Third-Party Providers (Section 05); outages, interruptions, or lost data (Section 13); or unauthorized access, breaches, or attacks, except to the extent caused by AirLLM's own gross negligence or willful misconduct (Section 15).

Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under applicable law — for example, where the law does not allow it, liability for fraud, gross negligence, willful misconduct, or death or personal injury caused by negligence. These limits do not reduce your payment obligations or your obligations under Section 20. If a separate written enterprise agreement signed by AirLLM sets different limits, that agreement controls to the extent of the conflict. Some jurisdictions do not allow certain limitations, so parts of this section may not apply to you.

20Indemnification

To the maximum extent permitted by applicable law, you will defend, indemnify, and hold harmless the AirLLM Parties from and against any claim, demand, or proceeding brought by a third party (including a government authority), and all related losses, damages, liabilities, fines, penalties, settlements, costs, and expenses (including reasonable attorneys' fees), arising out of or relating to:

  • your Customer Content;
  • your use of the Services or Output, including any decisions, code, or products based on Output;
  • Agent Actions you direct, approve, or allow;
  • your integrations, applications, products, or services that use or connect to the Services, and their users;
  • your breach of these Terms or the Acceptable Use Policy; or
  • your violation of applicable law or of any third party's rights, including intellectual-property, privacy, and publicity rights and a provider's usage policies.

We will notify you of a claim we ask you to defend; a delay in notice relieves you of your obligations only to the extent it prejudices you. You may control the defense with counsel reasonably acceptable to us, and we may participate with our own counsel at our own expense. You may not settle any claim in a way that admits fault by, or imposes any obligation on, any AirLLM Party without our prior written consent.

21Term, termination & account deletion

  • Term. These Terms apply from your first use of the Services until your account is closed.
  • Closing your account. An Enterprise Admin can close the account at any time in the dashboard under Settings → Close Account. Any outstanding balance must be paid first. Closing the account cancels every plan and API key immediately: nothing is charged again, everyone on the account is signed out, and remaining prepaid credit isn't refunded. To stop a single plan instead, cancel it in API Keys (Section 12).
  • Suspension by us. We may suspend or limit access immediately, at our discretion, where reasonably necessary to address a security risk, a suspected violation of these Terms or the Acceptable Use Policy, or a legal requirement, or to protect the Services, other customers, or third parties — giving notice and an opportunity to cure where practicable. We suspend for overdue amounts only as described under "Failed payments and late payment" in Section 12, after 14 days' written notice.
  • Termination by us. We may terminate for material breach uncured within 14 days of notice; immediately for serious or repeated Acceptable Use Policy violations, fraud, or where the law requires it; or with 30 days' notice if we discontinue the Services (in which case we will refund prepaid, unused fees).
  • Export first. Export or copy anything you need before you close your account. After closure you may no longer be able to access it.
  • Deletion 1 year after closure. One year after an account is closed, we delete the account and its data, except billing records, which are kept for 7 years from the invoice date (or longer if the law requires), records of your acceptance of these Terms, which are kept for 7 years from acceptance, and auto-renewal and auto-recharge consent records, which are kept for 3 years from when consent was given. Engineering tickets are kept only as long as needed to diagnose and fix the problem (Section 07). Deleted data may remain in backups for a limited time until they're overwritten in the normal cycle. We keep other information longer only where needed to meet a legal obligation, resolve a dispute, or under a hold described in our Data Retention Policy. Where the law gives you the right to earlier deletion, ask our Legal Cell at legal@airllm.ai.
  • Effect. On termination your access and your license to the Software end, and any amounts owed remain due. Sections that by their nature should survive — including Sections 02, 05–07, 09, 10 (restrictions), 12 (amounts owed), 13–20, and 22–26 — survive termination.

22Governing law & dispute resolution

Please read this section carefully — it affects your legal rights. Unless you opt out, disputes are resolved by binding individual arbitration instead of in court, and you and AirLLM each waive the right to a jury trial and to take part in a class action.

Governing law

These Terms, and any dispute arising out of or relating to them or the Services, are governed by the laws of the State of Texas, USA, excluding its conflict-of-laws rules and the UN Convention on Contracts for the International Sale of Goods. The Federal Arbitration Act governs the interpretation and enforcement of this section.

Informal resolution first

Before starting arbitration or any court proceeding, the party bringing the claim must send the other a written notice describing the dispute and the relief sought. Notices to AirLLM must be sent to our Legal Cell at legal@airllm.ai or through our Contact page; notices to you go to the email address on your account. Both parties will then try in good faith to resolve the dispute informally for 60 days, and any time limit for bringing the claim is paused during that period.

Binding individual arbitration

If the dispute is not resolved within those 60 days, it will be resolved exclusively by binding arbitration administered by the American Arbitration Association ("AAA") before a single arbitrator — under the AAA's Commercial Arbitration Rules for business customers, or its Consumer Arbitration Rules where those apply. The seat of arbitration is Austin, Texas; where the applicable rules allow, hearings may be held by video conference or decided on written submissions. Fees are allocated as the applicable AAA rules provide. The arbitrator may award the same individual relief a court could, but only in favor of the individual party seeking relief and only to the extent needed to resolve that party's claim. Judgment on the award may be entered in any court with jurisdiction.

Class-action and jury-trial waiver

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOU AND AIRLLM EACH AGREE THAT CLAIMS MAY BE BROUGHT ONLY IN AN INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS, COLLECTIVE, CONSOLIDATED, OR REPRESENTATIVE PROCEEDING, AND YOU AND AIRLLM EACH WAIVE ANY RIGHT TO A TRIAL BY JURY. The arbitrator may not consolidate more than one person's claims. If this waiver is found unenforceable for a particular claim, that claim (and only that claim) will be decided by a court as described below, not in class arbitration.

Exceptions

  • Small claims. Either party may bring an individual claim in small-claims court if it qualifies and stays there.
  • Intellectual property and security. Either party may seek injunctive or other equitable relief in court to stop infringement or misappropriation of its intellectual property, and AirLLM may seek such relief in court to stop unauthorized access to, misuse of, or attacks on the Services.

30-day opt-out

You may opt out of arbitration by sending a written opt-out notice to our Legal Cell at legal@airllm.ai (or through our Contact page) within 30 days after you first accept these Terms (or, if you were already a customer, within 30 days after this version takes effect). Include your name, the email address on your account, and a clear statement that you are opting out of arbitration. Opting out does not affect any other part of these Terms.

Courts

Any dispute that is not arbitrated — including because you opted out — will be brought exclusively in the state or federal courts located in Travis County (Austin), Texas, and each party consents to their personal jurisdiction and venue.

Two-year time limit

To the maximum extent permitted by applicable law, any claim arising out of or relating to these Terms or the Services must be brought within two years after it arises, or it is permanently barred.

If we change this section, the change will not apply to a dispute that either party had already notified to the other before the change took effect. Nothing in this section limits any non-waivable rights you have as a consumer under the laws of the place where you live.

23Force majeure

To the maximum extent permitted by applicable law, neither the AirLLM Parties nor you will be liable for any delay or failure to perform (other than an obligation to pay fees) caused by events beyond reasonable control, including natural disasters, epidemics, fire, flood, war, terrorism, civil unrest, labor disputes, government action, outages or failures of Third-Party Providers (including model, cloud, hosting, and payment providers), internet, network, or telecommunications failures, power failures, and cyberattacks, including denial-of-service attacks.

24General terms

  • Changes to these Terms. We may update these Terms; for material changes we will give at least 30 days' notice by email or in-product notice. Continued use after the effective date constitutes acceptance; if you do not agree, stop using the Services and close your account before the changes take effect.
  • Export & sanctions. You may not use the Services in violation of export-control or sanctions laws, or from embargoed jurisdictions, and you represent that you are not a sanctioned or restricted party.
  • Copyright complaints. Section 26 explains how to send a copyright (DMCA) notice or counter-notice to our Copyright Agent.
  • Notices. Legal notices to AirLLM — including dispute notices and arbitration opt-outs — must be sent to our Legal Cell at legal@airllm.ai (or through our Contact page) and identified as a legal notice. We may send notices to you by email to the address on your account or by in-product notice, and you agree to receive communications from us electronically.
  • Assignment. You may not assign these Terms without our consent, except to a successor in a merger or sale of substantially all assets; we may assign to an affiliate or successor.
  • Third-party beneficiaries. The AirLLM Parties are intended third-party beneficiaries of the disclaimers, limitations, and indemnities in these Terms. Otherwise, these Terms create no rights for anyone other than you and AirLLM, and nothing in them creates a partnership, joint venture, or agency relationship.
  • Entire agreement. These Terms, together with the policies they incorporate and any order form, are the entire agreement and supersede prior discussions. If any provision is unenforceable, it will be enforced to the maximum extent permitted and the remainder stays in effect; failure to enforce a provision is not a waiver. Headings are for convenience only.

25Trademarks

  • Our marks. The AirLLM, Air Router, AirGPU, AirCode, and Alina names and logos are trademarks of AirLLM or its affiliates, as Section 16 describes.
  • Third-party marks. Third-party company and product names are trademarks of their respective owners and are used only to identify compatible products and services. AirLLM is not affiliated with or endorsed by them.