Data Use and Telemetry

This page applies to the Fivetran CLI tools identified below. Both the Fivetran CLI and the Connector SDK CLI share the same telemetry behavior. The tools collect anonymous usage telemetry to help us understand how the tools are used, prioritize improvements, and track reliability. They do not capture your connector code, configuration values, credentials, or any data your connector processes.

When you haven't set DO_NOT_TRACK or saved is_telemetry_enabled, the CLI prints a one-time notice and sends no event on that run. You can read the notice and opt out before we send any usage data. If you don't opt out, we send events from your next run onward. An explicit enabled preference, including DO_NOT_TRACK=0, skips the notice and permits telemetry on the first run.

Events collected

Both the Fivetran CLI and the Connector SDK CLI tools send one event every time you run a CLI command.

Field	Description	Why it is collected
Command	The command you ran, including any subcommand, for example `debug`, `deploy`, or `package create`.	Understand which commands are used most.
Option names	The names of the options you passed, not their values.	Understand which options are adopted.
Status and exit code	Whether the command succeeded or failed. If a command fails because of a Fivetran API call, the HTTP status code of that call.	Monitor reliability.
Duration	How long the command took to run.	Monitor performance.
Tool version	The installed tool version.	Plan support for versions.
Python version	The Python version running the CLI.	Plan support for Python versions.
Operating system and architecture	For example `darwin` and `arm64`.	Plan platform support.
Anonymous ID	A random UUID generated on your machine and stored in the tool's configuration file. It isn't derived from you, your account, or your machine.	Count unique installations, not people.

Example event

The following is an example of an event sent for a deploy command:

{
  "cli_tool": "fivetran-connector-sdk",
  "actor_id": "3f2b8c1e-9d4a-4e6b-8a57-1c2d3e4f5a6b",
  "cli_version": "2.0.0",
  "python_version": "3.12.4",
  "os": "darwin",
  "command": "deploy",
  "options": ["--api-key", "--destination"],
  "status": "success",
  "exit_code": 0,
  "duration": 4.217,
  "architecture": "arm64"
}

What the tools do not collect

We do not collect the following usage data:

Your connector code or any file contents.
Values of command-line options, configuration values, or configuration.json contents.
Credentials, API keys, or tokens.
Data processed by your connector.
File paths, usernames, or hostnames.
Error messages or stack traces.

Data handling

Fivetran collects and handles usage data as follows:

Telemetry is sent over HTTPS to Fivetran.
Events are sent in a background process, so they don't slow down or block your commands. If delivery fails, the failure is ignored and your command isn't affected.
If you opt out, no telemetry events are sent.

How to opt out of telemetry

You can use the following opt-out mechanism to opt out of telemetry, checked in order:

Set the DO_NOT_TRACK environment variable to 1 or true. The environment variable takes precedence over the configuration file, and is useful for CI/CD pipelines. Once DO_NOT_TRACK is set, any value other than 1 or true leaves telemetry enabled and the configuration file is not read.
Set is_telemetry_enabled to false in the tool's configuration file:
Tool Configuration file
Connector SDK CLI (fivetran-connector-sdk) ~/.fivetran/connector_sdk/_config.json
Fivetran CLI ~/.fivetran/fivetran_cli/_config.json

Tool	Configuration file
Connector SDK CLI (`fivetran-connector-sdk`)	`~/.fivetran/connector_sdk/_config.json`
Fivetran CLI	`~/.fivetran/fivetran_cli/_config.json`

To turn telemetry back on, set DO_NOT_TRACK to 0. Alternatively, unset DO_NOT_TRACK and set is_telemetry_enabled to true.

When telemetry is disabled, the tools send no telemetry events.

Privacy

For information on how Fivetran handles personal data, see the Fivetran Privacy Policy.