Legal · Terms of Service

Terms of Service

Effective 9 September 2026 · Version 1.0-beta · English original

1. Who we are

The service is operated by Samuel Ján Mucha, acting as a sole individual under the name Klunq Labs (“we”, “us”), based in Brno, Czech Republic. Contact: admin@klunqlabs.com. There is currently no registered company; a Czech company is planned and, once formed, this section is updated and continued use of the service constitutes acceptance of the change. See also the Imprint .

2. Definitions

  • Service — the Klunq Proxy gateway, the account dashboard, the management API and these docs, all operated by us.
  • Widget — the Klunq Widget, a separate open-source project (MIT licence) on GitHub. It is not part of the Service and is governed solely by its MIT licence.
  • Client — a registered account holder: the owner of a team who issues virtual keys, sets budgets and manages End Users.
  • End User — a human interacting with the Widget through a virtual key. End Users have no direct contractual relationship with us; their relationship is with the Client.
  • Virtual key (v-key) — a revocable, budget-capped credential a Client issues for use with the Service.

3. The Service (beta)

We provide a hosted LiteLLM-based gateway with team budgets, virtual keys and page-locked access, plus a dashboard to manage them. The Service is currently in free public beta: no payments are accepted and no payment obligation exists. We may change, suspend or discontinue parts of the Service at any time; material adverse changes are announced in advance.

4. Accounts

  • You must have legal capacity to enter a contract and provide a working email address.
  • One account per person unless we agree otherwise. Keep your credentials and, above all, your team management key secret — it can create and delete keys for your whole team.
  • Your login email must stay reachable: it is the channel for abuse notices, security alerts and contract changes.
  • Spend or actions performed with your keys count as yours until you revoke the key. A leaked key is your incident to contain by revocation; then tell us.

5. Acceptable use and enforcement

There is currently no numeric cap on virtual keys per team, and dormant keys (e.g. a key per real user, even inactive ones) are explicitly not abuse. We reserve the right to introduce caps, rate limits and quotas at any time. The following is abuse:

  • pattern-generated key farms (e.g. sequential generic aliases in the thousands) with no attributable End User;
  • traffic shaped to degrade the Service, evade budgets or page-locking, or inflate stored data;
  • using keys outside their page-locked purpose, probing other teams' data, or circumventing technical restrictions;
  • unlawful content or unlawful use of model outputs.

Enforcement ladder: written notice to your login email → 14-day cure period → throttling or suspension → deletion of offending keys or the account. For active attacks (ongoing flooding, credential abuse, data destruction) we may act immediately without prior notice and inform you after.

6. Availability and liability

The Service is provided “as is”, on a best-effort basis, without any SLA or uptime warranty. We aim for maximum availability including maintenance windows, but outages, data loss and breaking changes may occur and do not entitle you to compensation. To the maximum extent permitted by law we exclude liability for indirect, incidental and consequential loss (including lost profit, lost data and business interruption). Our aggregate liability is capped at the fees you paid in the 12 months before the claim (currently €0 in beta). Nothing limits liability that cannot be limited by law. Force majeure events suspend our obligations.

7. Intellectual property

The proxy, dashboard, API and docs are © Samuel Ján Mucha / Klunq Labs — all rights reserved. The Widget is MIT-licensed (see its repository); underlying LiteLLM is MIT. Feedback you send may be used without compensation or attribution.

8. Future paid plans

We plan a prepaid model: Clients fund a shared team budget (macro-budget) that End-User requests draw from at model pricing, processed by a merchant of record (planned: Lemon Squeezy, acting under its own terms for payment handling). No charge happens without your explicit opt-in; paid plans launch together with updated terms. Third-party models (e.g. via OpenRouter) are subject to their providers' terms; model availability and pricing may change downstream of us.

9. Termination

Either party may terminate anytime: you by deleting keys and stopping use (account deletion on request to admin@klunqlabs.com), we with notice except for abuse (see §5). On termination your keys are revoked; data handling follows the Privacy Policy .

10. Changes and governing law

We may update these terms with notice on the site and, for material changes, by email; continued use after the effective date is acceptance. The contract is governed by the laws of the Czech Republic, with mandatory EU consumer protections and applicable US state consumer laws applying where you qualify. Disputes go to the competent Czech courts unless mandatory law says otherwise.

Templates, not legal advice — attorney review recommended before reliance. See Privacy Policy , Cookie Policy , Imprint .