BabelizeBabelize
CLI

Telemetry

What anonymous usage data the Babelize CLI sends, what it never sends, and how to turn it off.

The Babelize CLI sends anonymous usage data so we can see which commands, frameworks and translators people use, and where runs fail. It is on by default, prints a notice the first time it sends anything, and is easy to turn off.

What is sent

One event when a command runs (cli_command), and one when a translation finishes or fails (cli_translate, from babelize translate and the npx babelize wizard).

FieldExample
Commandtranslate, run start
CLI, Node.js version, OS, CPU architecture1.4.0, 22.11.0, darwin, arm64
Whether it runs in CI or a terminal, and whether you're signed intrue / false
Framework detected and its support statusnextjs, supported
Translator type and BYOK provider namebyok, anthropic
Target localesfr, de
Result and error codeok, partial, error / hosted_credits
Counts and durationfiles scanned, strings and keys extracted, keys translated, failed keys, milliseconds

Events carry a random install ID created on first use and stored in the CLI's config file. It is not linked to your Babelize account.

What is never sent

Your code, strings, translations, keys, file names or paths, repository names, environment variables, API keys, email address or Babelize account ID.

babelize check and babelize translate --provider pseudo send nothing at all: both are documented as never using the network.

Turn it off

Any one of these:

npx babelize telemetry disable   # this machine, until you run `telemetry enable`
export BABELIZE_TELEMETRY=0      # this shell or CI job
export DO_NOT_TRACK=1            # the cross-tool convention, also respected

babelize telemetry status shows whether it's on and why.

Last updated: 2026-10-27

How is this guide?

On this page