Effective 2026-10-25

Privacy

What CC Commander collects, why, and how to opt out. Plain language. No dark patterns. No retargeting.

CC Commander is built by Kevin Zicherman (Axiom Marketing Inc., an Ontario corporation). This policy covers commanderplugin.com, docs.commanderplugin.com, and the hosted MCP server at mcp.commanderplugin.com. The plugin itself is MIT-licensed and runs locally on your machine — none of your prompts, responses, or code touches our servers unless you explicitly call the hosted MCP.

What we DO NOT collect

  • Your prompts to Claude Code
  • Claude's responses to you
  • Your code, files, or repository contents
  • Your raw IP address (we hash it for rate-limit dedup only)
  • Any data from local-only plugin skills (the plugin runs in your Claude Code session — that traffic never reaches us)

What we collect when you visit commanderplugin.com

  • Page views via Plausible (EU cloud). URL, referrer, user-agent, browser/device basics. Used to understand traffic and improve the site. Plausible is cookieless. The catalog search sends no events.

What we collect when you use the hosted MCP server

  • GitHub user identifier after OAuth login. We use this to identify your account, and enforce per-user rate limits.
  • Tool name + latency + success/failure on every call you make to the hosted MCP. We log that a tool ran, not what the tool produced. Tool calls (/v1/call) are processed server-side and transiently — the server receives and dispatches your tool arguments to fulfill the request, but we do not store, log, or retain tool inputs after the response is sent. Tool inputs are never sent to any analytics system. The hosted MCP is stateless: no per-user tool history, no input persistence.
  • Monthly call count + rate-limit window. Stored in Supabase + Upstash Redis. Used for the monthly call cap and the burst protection (60 calls/min).
  • Hashed IP (SHA-256) — used for anonymous rate-limit dedup on unauthenticated requests. We never store the raw IP.

Anonymous usage telemetry from the plugin and CLI

Off by default. The CC Commander plugin and CLI send anonymous usage events only if you opt in with CCC_TELEMETRY=1 or "telemetry": true in ~/.commander/config.json. Opted-in events help us see which features are valuable.

What we collect:
  • Event name (e.g., hook_fired, skill_invoked, agent_dispatched)
  • Anonymous device ID (UUID generated once and stored locally in ~/.commander/anon-id)
  • Your OS, Node.js version, plugin version
  • Basic counts and non-sensitive metadata (which hook ran, which skill was invoked)
What we explicitly DO NOT collect:
  • Prompts, file contents, or project paths
  • Environment variable values or secrets
  • Command arguments or personal context
  • Any property with a key matching /prompt|content|path|file|cwd|secret|password|key|token/i
Other outbound calls: an update check at session start (a GET of the public plugin.json on GitHub), a CI status lookup through your own gh login only if you set CCC_CI_TICKER=1, and the bundled Context7 MCP querying context7.com only when you use it. The bundled MCP servers (context7, sequential-thinking) start through npx -y, which fetches each pinned package from the npm registry when Claude Code first launches it (servers start with the session, not on first use); this is on by default, and removing a server from .mcp.json stops it. CCC_TELEMETRY=0 forces telemetry off; CCC_OFFLINE=1 (or "offline": true) blocks every call the plugin makes itself.

Opted-in events go to mcp.commanderplugin.com (fallback commander-mcp.fly.dev) and are treated as anonymous (no personal data, no IP logging). We use this data to build aggregate reports: "X% of users invoke skill Y" and "hook Z fires most often in scenario W." These reports help us ship features people actually want.

Third parties we share data with

Cookies and tracking

We use one cookie:

Auth.js session cookie — set when you sign in via GitHub OAuth to use the hosted MCP. Standard secure httpOnly cookie. Lasts the duration of your session.

No advertising trackers. No retargeting pixels. No third-party identity graphs.

Your rights

  • Access / export. Email hello@commanderplugin.com and we'll send you everything we have on you within 30 days.
  • Deletion. Same address. We'll delete your user record, and any earlier release-notes signup row, on request, no questions asked. (We can't un-hash your IP because we never had it in the first place.)
  • Correction. Tell us what's wrong; we'll fix it.
  • Opt out of analytics. Use a browser DNT signal, an ad blocker, or just decline cookies — we honor all three. The site still works without analytics.

Children

CC Commander is a developer tool. We don't knowingly collect data from anyone under 13. If you believe a minor created an account, email us and we'll delete the record.

Changes

We'll update this page when our data practices change and revise the date at the top. Material changes get a banner on commanderplugin.com.

Contact

Privacy questions or requests: hello@commanderplugin.com.