Privacy

The short version

• No KnightCode account is required.
• You configure your own provider key for model access.
• Agent prompts, file context, and tool results may be sent to the provider/model route you choose.
• Local settings, credentials, tasks, and logs may be stored on your machine for the CLI to work.

What KnightCode stores locally

• Credentials and onboarding choices, including your OpenRouter key and optional search-provider configuration.
• Project task state in .knightcode files when durable tasks are used.
• Rules, skills, memories, and settings that you add for project or global context.
• Session output and logs needed for debugging or resuming work, depending on the command and feature in use.

What KnightCode sends over the network

KnightCode sends network requests only when a feature needs them:

• Model requests go through the provider route you configure. In the current alpha, that path is OpenRouter-first.
• Search requests may go to the search provider you configure, such as Brave or Tavily.
• Web fetch requests are made when you ask the agent to fetch a URL.

Whatever context you send to a provider is governed by that provider's privacy policy and retention settings.

What the website collects

The website is hosted separately from the CLI. It may receive standard HTTP request logs from the host and uses Vercel Analytics to understand basic page traffic. Do not put secrets into website forms or URLs.

Third-party providers

KnightCode is BYOK. That means provider accounts, billing, retention, rate limits, and abuse monitoring are handled by the services you configure, not by a KnightCode-hosted account system.

Changes

If this policy changes, the “Last updated” date at the top of the page changes with it. Material changes may also be mentioned in the changelog.

Contact

For questions or bug reports, please open an issue on our GitHub repository. For security concerns, please see our Security Policy.