Privacy Policy

⚡ The short version: EditVolt runs on your computer. We collect no telemetry, require no account, and operate no servers that receive your code. The only time anything leaves your machine is when you use an AI feature with a cloud provider you configured — and that request goes directly from your machine to that provider, never through us. Prefer nothing leaving at all? Strict privacy mode runs everything on local models.

1. What we collect: nothing

EditVolt collects no personal data, usage analytics, or telemetry of any kind:

• No telemetry. Telemetry is disabled at build time, and the telemetry machinery is structurally replaced with a no-op inside the application — there is no data-collection pathway alive in the shipped binary.
• No crash reporting. The crash reporter has no upload destination configured; crash data never leaves your machine.
• No experiments, A/B tests, surveys, or ads.
• No account. EditVolt requires no sign-up, sign-in, or registration, and we operate no account or authentication servers.

Because we collect nothing, there is nothing for us to sell, share, profile, or be asked to delete.

2. AI features and your code

When you use an AI feature (chat, agent mode, cloud completions), the relevant prompt and code context is sent directly from your machine to the AI provider you configured — Anthropic (Claude), Google (Gemini), an OpenAI-compatible endpoint of your choice, Hugging Face, or a local model. EditVolt operates no proxy, gateway, or backend in between: we never receive, store, or log your prompts, code, or the model's responses.

Your relationship with each AI provider is governed by that provider's own terms and privacy policy, under your own API key or account. Please review the policies of any provider you connect.

• Local by default where possible. Inline completions run on a bundled local engine, and codebase indexing uses a bundled on-device embedding model — neither touches the network.
• Strict privacy mode. One setting routes every AI request to local models only, disabling all cloud providers. No silent substitution: EditVolt never quietly reroutes a request to a different provider than the one you chose.
• Sensitive-file protection. The .editvoltignore file (enabled by default) keeps matching paths — including .env files, private keys, SSH and cloud credentials — out of the AI's context and the local index.

3. Third-party CLI integration

EditVolt can optionally bridge to an AI vendor's own command-line tool installed on your system (for example, Anthropic's Claude Code CLI) so you can reuse an existing sign-in. In that mode, the vendor's tool handles the requests itself and may perform its own diagnostics and event logging to the vendor and its logging services, under the vendor's policies — this is that tool's behavior, not EditVolt's. If you prefer to avoid it, connect with a direct API key or use local models instead.

4. Data stored on your device

Everything EditVolt saves lives on your computer, in the application's data folder:

• Settings, keybindings, and themes
• Chat and session history (stored per workspace, with automatic size caps)
• The local semantic index of your codebase and its embeddings
• Optional project memory (off by default)
• Your customization files: rules, skills, subagents, hooks, commands, automations

None of this is synced to us. Deleting the data folder removes it permanently.

5. API keys

Provider API keys are stored in your operating system's secure keychain — never in plaintext files — and are read only for the duration of the individual request that needs them.

6. Network connections EditVolt makes

For transparency, here is the complete list of network connections the app can make, and why:

Destination	When	What is sent
Your chosen AI provider	Only when you invoke an AI feature	Prompt and selected code context
Open VSX (extension marketplace)	When you search for or install extensions	Search queries; extension downloads
EditVolt update server	Periodic update check (can be disabled)	Version metadata only; connection is certificate-pinned
npm registry	Only when you install MCP servers or packages	Package requests
localhost (your machine)	Local models (Ollama, bundled engine), local tooling	Never leaves your machine

This behavior is verified with network-interception audits against a blocklist of known telemetry endpoints before each release.

7. Extensions

Extensions you install from Open VSX are third-party software with their own privacy practices and may make their own network connections. Review an extension's documentation before installing it.

8. This website

This website is a static site. It sets no cookies, runs no analytics, and hosts no tracking scripts. If you email us to be notified about product launches, we use your email address only for that notification and delete it on request.

9. Children's privacy

EditVolt does not collect data from anyone, including children.

10. Changes to this policy

If EditVolt's data practices ever change — for example, if an optional, opt-in metrics service is introduced — we will update this policy and call out the change prominently in the release notes before it ships.

11. Contact

Questions about privacy? Email hello@editvolt.com.