Privacy

This page describes data handling for the VeloxCLI client as described on this marketing site. For authoritative behavior, read the version you install and its documentation.

What runs locally

The installed binary, configuration file, session history, plugin code loaded from disk, and file contents you attach all reside on your machine unless you copy them elsewhere. VeloxCLI does not ship a background analytics channel in the client described here.

What goes to Groq

When you use Groq-backed inference, prompts and the context you include (for example attached files, tool output, and session text) are transmitted to Groq's API under your API key. Groq's privacy policy and terms govern that transfer.

Telemetry and analytics

The open-source client documented on this site does not include product telemetry or usage analytics. Network use is limited to what you configure: inference, user-approved tools, and MCP servers you enable.

API key handling

Store keys in environment variables or restricted configuration files with appropriate file permissions. Do not commit keys to version control. Rotate keys if they leak. VeloxCLI maintainers never receive your key through the software itself.