kpilot has two parts: a CLI that runs on your machine, and the kpilot service you sign in to — the account, dashboard, and cloud agent runs. This page separates what stays local from what the service receives and stores.
The CLI is a program installed on your machine. It reads your files, edits them, and runs commands locally, and it keeps its own local state.
The kpilot service is what you sign in to: model requests that produce answers, the account dashboard, and cloud agent runs that execute on our servers. The two are separate, and what the service stores is described below.
When you use kpilot locally, your files, terminal output, and repository work stay on your machine. The service does not receive the source you read, the diffs you apply, or the commands you run from the CLI.
The CLI keeps its own state on your machine: your conversations, preferences, and project notes are saved locally in your project and in a configuration folder in your home directory, and your sign-in details for the service are kept in a protected file that only your account can read. The web tools the CLI uses reach the network from your own machine, and they will not reach local or private addresses on your network.
To answer a prompt, the current request — the conversation sent and any tools it may use — is transmitted to the kpilot service and on to the model that serves it. That transmission is what produces the response. Alongside it, the service records usage metadata:
On this model path, the service does not write your prompt text or source code into its database. Usage records are uploaded by the CLI separately; you can turn that off (see Your choices).
This is where content is stored on our servers, and it applies only when you use the cloud part of kpilot. A cloud project is a workspace managed by the service. If you create one and connect a repository, the service copies that repository onto our servers.
A cloud agent run executes on our servers and is saved so the dashboard can stream it live and replay it later. That record includes:
Project chat sessions are stored inside the project's workspace on our servers. Deleting a project or session removes that stored content.
Passwords are never stored in a form anyone can read — only as a one-way protective value that is checked when you sign in. Signing in to the website uses secure, browser-protected cookies, and a signed-in session stays valid until you sign out or revoke the device rather than expiring on a short timer. Refresh credentials and API keys are likewise stored in a protected form, can be revoked at any time, and an API key is shown only once when it is created.
A repository credential you connect to a cloud project is encrypted and is never shown back to a client. The platform's own model and payment credentials are held only by the service — never in your account, your project, or anything you can access.
An account can be set to Zero Data Retention. Such accounts are only served by model providers that do not retain your prompts, and each request instructs the provider not to retain it. If no provider meeting that standard is available, the request is refused rather than served under weaker terms.
Privacy questions? Email hello@konsolepilot.ai, or see our contact page.