kPilotkPilotCleared for takeoff
FeaturesHow it worksPricingFAQ
Get started
Legal

Privacy Policy

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.

Two parts of kpilot

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.

What stays on your machine (the CLI)

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.

When the CLI makes a model request

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:

  • when the request happened, which model served it, how many tokens were used, how long it took, and whether it succeeded;
  • identifiers for your account, device, and session, plus a non-identifying marker for the project folder rather than its name or path;
  • how the request was handled and its estimated cost, calculated from the rates in effect.

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).

Cloud projects and cloud agent runs (the service)

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:

  • the run's prompt and the mode it ran in;
  • the run's activity — the steps it took, the tools it used with their input and output, status updates, the final answer, and usage;
  • status, timing, and any permissions awaiting your decision or already decided;
  • the changes the run made, and any pull request or patch file delivered from it.

Project chat sessions are stored inside the project's workspace on our servers. Deleting a project or session removes that stored content.

Credentials and access

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.

Zero Data Retention

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.

Your choices

  • revoke devices and API keys, and sign out other sessions, from the dashboard;
  • delete cloud projects and chat sessions, which removes their stored content;
  • turn off usage reporting from the CLI — a model request still has to be sent to produce a response;
  • ask us to close your account by emailing hello@konsolepilot.ai.

Contact

Privacy questions? Email hello@konsolepilot.ai, or see our contact page.

kPilotkPilotCleared for takeoff

Build fast, stay in control. A terminal-first AI pilot that lets you ship changes instantly, approve code with a click, and track the cost of every run.

Get started

Create accountnpm package

Legal

TermsPrivacy

Company

AboutContact

© 2026 kpilot. All rights reserved.