Terms of Service
The scope of this website, the responsibilities involved in model-assisted work, and the limits of illustrative content.
Updated
01. Service scope
These Terms of Service describe use of the Switchka public website and the access-request interfaces presented here. The website introduces a smart model router intended to work with Cursor, Claude Code, and Codex. It includes product explanations, conceptual documentation, illustrative interfaces, and browser-based inquiry and account-request forms.
The website is not itself an operational model-routing account, an authenticated service, or a model provider. Descriptions of intended workflows do not establish that every integration method, model tier, or control is available in a particular environment. A connected product may require confirmed access, a supported configuration, and additional applicable terms before use.
02. Account requests and access
Submitting an early-access request is not immediate account activation. Access, compatibility, and onboarding need confirmation. No activation timeline, subscription price, or guaranteed place in an access program is published on this website. Provide accurate contact details and a concise description of the intended use when making a request.
The current website forms validate fields and display requested messages in the browser. They do not deliver submissions to a backend, create accounts, authenticate users, or send activation email. The login page does not collect a password and directs users toward support. A review or thank-you message is an interface state, not evidence that an account has been created or a request received by a service team.
03. Acceptable use
Use the website and any connected service lawfully and with respect for others. Do not attempt unauthorized access, interfere with availability, distribute malicious material, impersonate another person, or submit information you are not entitled to share. Do not use a connected routing workflow to bypass restrictions imposed by a tool, model provider, project owner, or applicable rule.
Avoid submitting credentials, private source code, confidential business material, or unnecessary personal information through website forms. If an inquiry needs a technical example, sanitize it first. The existence of a text field does not make the website an appropriate destination for sensitive material or large project archives.
04. Your responsibilities
You are responsible for choosing suitable tasks, supplying appropriate context, and evaluating the resulting work. Review code changes, check assumptions, and run relevant project checks before accepting an output. A route to a more capable model does not guarantee correctness, fitness for a purpose, or safe execution of a proposed command.
You are also responsible for confirming that you may use the tools, repositories, models, and information involved in a workflow. Establish any restrictions on external processing before connecting a cloud path. Model routing is separate from permission to read files, modify a repository, execute commands, or communicate with remote systems. Keep those permissions under the controls appropriate to your project.
05. Third-party tools and models
Cursor, Claude Code, and Codex are third-party tools named to explain the intended development workflows. Their names do not imply ownership by Switchka, endorsement, or an agreement beyond the integration intent described. Third-party software and model services may have their own terms, privacy practices, fees, technical limits, and availability.
This website does not publish a verified provider list, SDK, model compatibility matrix, or executable installation procedure. Confirm the supported connection and available models during onboarding. You remain responsible for complying with third-party obligations that apply to your use. A change in a tool or model service can affect compatibility or the behavior of a connected workflow.
06. Routing and savings limitations
Switchka’s approach is local-first, followed by efficient cloud capability and frontier models when the task requires them. A route depends on the task and available capability. The examples on this website do not establish a deterministic rule that a named task always uses one tier, a published confidence threshold, or a retry guarantee.
The supplied savings claim is 70%+ less token spend. Savings vary by workload. Task mix, available local models, prompt and response sizes, repeated attempts, and the need for frontier reasoning can materially affect results. Evaluate total spend for accepted work against a representative baseline. Local processing can reduce cloud token charges while still using machine resources. No universal savings level or complete elimination of computing costs is promised.
07. Illustrative content and documentation
The dashboard uses example request names, costs, durations, and tier percentages to communicate the product concept. These are illustrative values, not account data, benchmarks, measured performance, or a service-level commitment. The preview is not a working routing console and does not establish that every depicted control is available.
Documentation is conceptual unless explicitly confirmed otherwise through a supported onboarding process. Do not turn descriptive labels into guessed configuration keys or connect a tool to an invented endpoint. Before making changes to an environment, confirm the supported method and the permissions needed. Product explanations should support informed evaluation rather than replace environment-specific guidance.
08. Availability and changes
Website content and any connected service may change as supported workflows develop. Availability can depend on hosting, network access, third-party tools, model availability, and your environment. This website publishes no uptime commitment, response-time guarantee, contractual service level, or guarantee of uninterrupted access.
Information may need correction or revision, particularly when the implementation or a third-party integration changes. Evaluate the current documentation and any confirmed onboarding guidance before relying on a workflow. Keep your own project records and do not use this website as the sole storage location for work or as the only route for time-sensitive communications.
09. Intellectual property and supplied material
The Switchka website’s brand presentation, supplied artwork, text, and code may be protected by applicable intellectual-property rules. Third-party names and marks remain associated with their respective owners. Viewing the website does not transfer ownership of any brand, tool, model, or other protected material.
You retain responsibility for material you choose to provide and for having the rights needed to share it. This website does not claim ownership of your project merely because an inquiry describes it. The current forms do not upload repositories or submit project content to a model. Any rights needed for a later connected service should be addressed by the terms applicable to that service.
10. Restrictions and suspension
Access to a connected service may need to be restricted where use is unauthorized, harmful, unlawful, technically incompatible, or inconsistent with applicable requirements. This statement does not establish an automatic enforcement system on the static website or a guaranteed notice process. The current website does not maintain authenticated account sessions.
If you believe an access issue is a mistake, seek help through a confirmed support channel for your service relationship. The contact page describes the intended inquiry route, but its current browser-only form state does not establish delivery. Do not submit repeated requests containing secrets or attempt to bypass an access restriction.
11. Disclaimers and liability
The website and its explanatory material are provided subject to their stated scope and limitations. Model-generated content can be incomplete or wrong, routing may not produce the expected savings, and a supported workflow may not suit every project. No claim on this website should be interpreted as a security certification, error-free output guarantee, or assurance that all processing stays local.
To the extent permitted by applicable rules, reliance on the website or a connected model output does not create a promise to compensate for every loss, interruption, cost, or unsuccessful result. Nothing here is intended to exclude responsibilities or rights that cannot lawfully be excluded. These terms do not set an invented monetary liability cap, governing jurisdiction, subscription fee, or refund policy.
12. Updates and contact
These terms were updated on 21 October 2026. Revisions may be needed when product access, integration support, hosting, or delivery workflows change. The version displayed on this page describes the current public website. Terms for an operational service should be reviewed before relying on that service.
Visit the contact page for product, onboarding, account, or other questions. The Privacy Policy explains the current browser-only form handling and information limits. Where a request is time-sensitive, use an established, confirmed service contact rather than treating an on-page status message as proof of delivery.