Legal template

Terms of Service

These terms govern access to a CustomRouter deployment, including the admin console, OpenAI-compatible API endpoints, routing features, and any managed BYOK hosting or assisted self-hosting services the operator may provide. Replace the bracketed placeholders before external launch.

Privacy PolicyBack to Admin
Operator details to fill in

Replace [LEGAL ENTITY NAME] and any billing or governing-law references with your real business details.

1. Use of the service

These Terms form an agreement between you and [LEGAL ENTITY NAME] ("we", "us", or "our") for your use of this CustomRouter instance. The service may be offered as a self-hosted deployment, a managed BYOK-hosted deployment, or an assisted self-hosting engagement.

You may use the service only in compliance with applicable law and these Terms. Access may be suspended or revoked if use creates operational, legal, or security risk for us, our infrastructure providers, or our upstream model providers.

If your organization self-hosts this software, your organization is the service operator and is responsible for its own terms, privacy disclosures, security controls, and customer commitments.

  • Do not use the service for unlawful, abusive, or fraudulent activity.
  • Do not attempt to bypass rate limits, authentication, or service restrictions.
  • Do not submit content you do not have the right to process.
  • You remain responsible for prompts, uploaded content, and downstream use of model output.

2. What the service does

CustomRouter is an OpenAI-compatible routing proxy. It accepts requests through API endpoints such as chat completions, responses, and model-listing routes, then may classify, route, retry, pin threads, and attach routing metadata before forwarding requests to one or more upstream model providers.

Features may include admin-issued API keys, invite-only registration, configurable routing profiles, thread stickiness, guardrails, BYOK gateways, and stored routing explanations. Not every deployment enables every feature.

3. Accounts and API keys

You are responsible for activity under your account, session, and API keys. Keep credentials confidential and revoke them promptly if you suspect compromise.

API keys issued here authenticate access to this routing proxy only. The service forwards eligible traffic to upstream model providers you configure or that we make available. You are responsible for all token consumption, quotas, and charges imposed by those providers; we do not operate as an intermediary for upstream billing and are not liable for provider-side usage or fees. You should configure spending limits, budgets, and rate or token controls directly with each upstream provider.

We may impose rate limits, usage caps, model restrictions, or other controls to protect the service and upstream providers.

We may restrict account creation through closed or invite-only registration and may require admin approval for certain features, gateway changes, or elevated usage.

4. Your content and BYOK credentials

You retain rights to content you submit, to the extent you already own those rights. You grant the service a limited right to process that content for routing, safety, logging, abuse prevention, and request fulfillment.

If you configure your own upstream gateway or API credentials, you represent that you have authority to use them and authorize us to store and use them to fulfill your requests. Stored BYOK credentials may be encrypted at rest, but you remain responsible for choosing appropriate upstream providers and plans.

Do not send sensitive, regulated, or high-risk data unless you have independently confirmed that the deployment, security controls, retention settings, and upstream provider terms are appropriate for that data.

5. Upstream providers and AI-specific disclaimers

The service depends on third-party infrastructure and model providers. Requests may be routed to providers you configure or that the operator makes available.

  • Model output can be inaccurate, incomplete, or inappropriate for your use case.
  • The service may rely on third-party upstream model providers and can degrade or fail when those providers do.
  • Availability, model selection, routing behavior, and limits may change without notice.
  • Upstream provider fees, token usage, and spending or rate limits are solely between you and each upstream provider; you should configure budgets, alerts, and caps with them directly.

6. Fees and billing

For self-hosted use of the public codebase, no software license fee is charged by this repository itself unless you enter into a separate services or hosting agreement. Managed hosting, support, migration work, or assisted self-hosting may be billed under a separate order form, statement of work, or subscription agreement.

Hosted Starter subscriptions are billed in advance on the interval selected at checkout and renew automatically until canceled. Customers can manage or cancel paid subscriptions through the billing portal.

We may also offer fixed-duration promotional Starter access through promo codes. Promotional access does not collect a payment method, does not auto-renew, and downgrades to the Free plan automatically when the stated promotional period ends unless the account upgrades separately.

7. Termination

We may suspend or terminate access at any time to protect the service, comply with law, or respond to abuse, unpaid usage, or upstream provider restrictions.

8. Warranty and liability

The service is provided on an "as is" and "as available" basis. To the maximum extent allowed by law, we disclaim warranties and are not liable for indirect, incidental, special, consequential, exemplary, or lost-profit damages.

9. Contact and governing terms

Questions about these Terms should be sent to me@therealpablo.com. Add your governing law, venue, and effective date here before launch.

Before you publish this

This version is now product-specific, but it still needs your entity name, contact method, fees, refund policy if any, governing law, and support commitments.