Privacy Policy
What this website handles, what stays in the browser, and what to consider before connecting a product workflow.
Updated
01. Scope of this policy
This Privacy Policy describes information handling for the Switchka public website and its current browser-based forms. Switchka introduces a local-first model-routing product for coding workflows. This website provides product information, conceptual documentation, and access and support interfaces. It is not a running model-routing service or an authenticated account console.
The policy distinguishes what happens in this website from what may happen in a separately connected product environment. It does not establish the privacy practices of Cursor, Claude Code, Codex, a model provider, or a hosting provider. Before using a connected product with project material, review the applicable processing arrangements and the information supplied during onboarding.
02. Information you provide in forms
The contact form asks for an email address, an inquiry category, and a message; a name is optional. The early-access form asks for an email address and a preferred coding tool, with an optional workflow description. The access page asks for an email address and directs you to support. None of these forms asks for a password.
The current forms validate input and display status messages in your browser. Their current handler does not transmit submissions to Switchka, save them in browser storage, or create an account. A displayed review or thank-you message does not establish that a message has been delivered. The form values remain part of the open page until you change them, reset the page, or leave it; browser behavior such as autofill is controlled by your browser.
03. Information to leave out
Provide only the information necessary to explain your question. Do not include API keys, passwords, access tokens, private source code, confidential business material, unredacted logs, or unnecessary personal information. Use a short sanitized description when explaining a technical problem. You are responsible for ensuring that you are permitted to share any material you choose to provide.
If a connected contact or account workflow is introduced, its purpose should remain clear at the point of collection. This policy does not authorize collecting additional sensitive information merely because a text field allows it. Support and onboarding can begin with the tool name, relevant environment, and a concise statement of the issue.
04. Browser, device, and operational information
The website’s own JavaScript does not install analytics, advertising trackers, or cookies. It does not use localStorage or sessionStorage to retain form submissions or account state. Documentation search filters content in the page; it does not send search terms to a search provider. Navigation and FAQ controls operate within the browser.
When the site is served, your browser necessarily requests pages and assets from the server. The hosting environment may receive network and request information, such as an IP address, requested path, and browser headers. The files in this project do not configure a logging service, a log-retention period, or a hosting provider’s independent practices. Browser caching, history, extensions, and autofill may also operate according to your own browser settings.
05. Purposes and limits of use
In the current implementation, form input is used locally to check required fields and present the requested interface state. Documentation search is used to show matching sections. There is no website account database, mailing list subscription, or authentication session created by these scripts.
If delivery and account services are connected later, information supplied for an inquiry would be relevant to answering that inquiry, assessing compatibility, or arranging access. Such a connection requires a real processing workflow and an updated explanation of applicable handling. This policy does not claim that the current website already carries out those activities, nor does it permit unrelated marketing use of a support request.
06. Service providers and third-party tools
No third-party form endpoint, analytics script, remotely hosted font, or advertising service is embedded in the current site. The supplied brand and hero assets are served with the website. The website does not send prompts to a model provider or operate the integration workflows described in its conceptual content.
A hosting provider may be involved when the files are deployed, and a connected product may involve external tools or models. Those relationships and their information flows depend on the actual deployment and service configuration. Do not infer a provider identity, processing agreement, or security certification from a product page. Review the terms and privacy information for any third-party service you choose to use.
07. Retention principles
The current form handler creates no server-side submission record and no persistent browser copy under the website’s control. It therefore has no form-record retention schedule to apply. Any hosting logs, browser history, caches, or autofill records are separate from form storage and depend on the relevant environment and settings.
If a delivery workflow is connected, retention should be tied to the purpose of the request, the need to resolve it, and applicable obligations. This page does not promise a fixed deletion date or describe an implemented deletion system. Avoid entering material that should not be retained anywhere, particularly secrets and confidential project content.
08. Questions, rights, and requests
Depending on your circumstances and applicable rules, you may have rights relating to personal information, including access, correction, deletion, or restrictions on use. This policy does not assign a jurisdiction or claim that every right applies in every situation. Questions about information handling can be directed through the contact page using the privacy request category.
Describe the request clearly and include only the information needed to identify the issue. Do not send identity documents or credentials through the form. Because the current form does not deliver messages, its on-page confirmation does not establish receipt of a rights request. If you already have an established service relationship, use its confirmed support channel for time-sensitive matters. A production delivery channel must be connected before this page can receive requests.
09. International processing
This website does not itself select a model-processing region or transfer form submissions to a destination. A deployed host may serve visitors across countries, and third-party tools or later connected services may process information internationally. The relevant locations and arrangements depend on those actual services.
No particular data-residency commitment, transfer mechanism, or geographic restriction is represented here. If location matters to your project, establish that requirement before using a connected routing service. Local-first is a routing preference and should not be interpreted as a guarantee that every associated system operates in one country or on one machine.
10. Children and appropriate use
The website concerns developer tooling and is not directed at children. It does not knowingly request information specifically about children or provide a children’s account flow. Do not submit a child’s information in an access or support request.
If you have a concern about information relating to a child in a connected service, use that service’s confirmed support process. The website contact page explains the intended inquiry route, subject to the current delivery limitation described above.
11. Changes and contact
This policy was updated on 21 October 2026. Changes to hosting, analytics, form delivery, account services, or product processing may require revisions so that the description continues to match the implementation. The current version is available on this page; a displayed update date identifies the version of this text.
For product, account, or privacy guidance, visit the contact page. Read the Terms of Service for the scope and limitations of this website. Do not rely on a browser-only status message as evidence that a communication has reached Switchka.