ToolsXpo
Workspace & BillingToolsXpo CodeReference

What we collect

ToolsXpo Code sends no analytics, no crash reports and no usage data. What that means, and why there is no setting for it.

Updated September 2, 2026

ToolsXpo Code sends no analytics, no crash reports and no usage data.

There is no setting for this, because there is nothing to turn off. A switch would imply the other position exists.

Never transmitted

  • Your code, prompts, file contents and file names
  • Your API keys and provider credentials
  • Which files you open, or how long you use the editor
  • Crash reports, stack traces and error telemetry

How this is enforced

Two ways, so it does not depend on one:

The telemetry client cannot initialise without a build-time key, and released builds ship without one. And the telemetry setting defaults to disabled rather than to an ask-me-later state — so it is a decision rather than an accident of configuration.

What we do have

Operating the service requires knowing some things, and they are all visible to you in your dashboard:

  • Request logs — which model, how many tokens, how long, which key. Under Dashboard → AI → Logs. This is what your bill is computed from.
  • Account details — your name, email, plan and workspace membership.
  • Connected apps — which editors and CLIs hold a key, and when each was last used.

None of this includes your code or your prompts.

Reporting a problem

Because we collect no crash reports, a bug you hit is invisible to us until you say so. Logs are in ~/.toolsxpo/vscode/logs/ and ~/.toolsxpo/cli/logs/ — attach the relevant part when you get in touch. Read it first; it is your machine's log, and only you decide what to share.

See also

privacytelemetrysecurity

Related