Privacy controls

EditVolt collects no telemetry — the telemetry pipeline is structurally removed from the binary, not just disabled — and requires no account to use. Signing in is optional; if you do, we hold only your email address and basic profile, and never your code. This page covers the controls you can tune. For the formal policy, see the Privacy Policy.

Everything here is also reachable under EditVolt Settings → Privacy & Data.

Strict privacy mode

{ "product.privacy.strict": true }

One setting forces every AI request — chat, agent, and embeddings — to on-device providers, disabling all cloud providers. It also overrides routing: the fast lane and heavy-model settings are ignored, escalation from a local to a cloud model is refused, and the in-editor browser is restricted to localhost and loopback URLs.

Combined with the bundled on-device chat models, the local completion engine and local indexing, nothing leaves your machine at all.

The ignore file

.editvoltignore (gitignore syntax) keeps sensitive paths out of the semantic index and out of chat/agent context. Enabled by default (product.privacy.ignoreFile) with defaults covering:

.env*
*.pem  *.key
id_rsa*  .ssh/
.aws/
secrets*

Add your own patterns per project or globally. Under strict privacy, secret-shaped files are hard-blocked with no override path.

Where secrets live

Provider API keys are stored in the OS keychain (macOS Keychain, Windows Credential Manager, libsecret on Linux), read per-request, and never written to config files.

Command sandboxing

Commands the agent runs can be network-confined with product.commands.sandboxNetworkMode, and file-deletion protection (product.commands.protectFileDeletion) is on by default. See Agent mode for the full consent model.

Accounts and sign-in

An EditVolt account is optional — nothing on this page depends on having one, and the editor and all AI features work signed out.

If you do sign in (GitHub or Google, via our authentication provider Supabase), we receive and store:

• your email address
• your basic public profile — display name, username, avatar URL
• the provider account ID linking the sign-in to your EditVolt account
• authentication records — sign-in timestamps, IP, and user-agent, kept in security logs

Sign-in requests identity scopes only. EditVolt never requests or receives access to your repositories, code, mail, or files held by GitHub or Google.

The resulting session token is handed to the IDE over loopback (127.0.0.1) and stored in your OS keychain; signing out removes it. To delete the account record itself, email hello@editvolt.com — see the Privacy Policy for the full data-rights process.

The audit surface

The Activity Log (EditVolt Settings → Activity Log, or the Audit Dock view) shows the session's outbound-connection count in real time — the 0 outbound · telemetry-zero indicator. Set product.audit.persistAcrossSessions if you want the log to survive restarts. Every release is additionally verified with network-interception audits before it ships.

Optional network features, all off or explicit

Feature	Setting	Default
In-editor browser	product.browser.enabled	off
Cloud inline completions	product.completions.source	local
Auto fast-lane to cloud	product.routing.autoFastLane	off
Langfuse trace export (dev/QA)	product.observability.langfuse.enabled	off
Product announcements	product.announcements.enabled	on
Account sign-in (GitHub / Google)	user action only	signed out

Third-party notes

• Extensions come from Open VSX and have their own privacy behavior — review before installing
• The optional Claude Code CLI bridge uses Anthropic's own CLI, which performs its own diagnostics under Anthropic's policies; use API-key mode or on-device models if you prefer to avoid that
• On-device model downloads fetch from product.models.baseUrl (Hugging Face by default) and are SHA-256 verified; you can repoint them at an internal mirror
• Auto-update checks fetch version metadata only, over a certificate-pinned connection, and can be disabled in settings