---
title: "Telemetry"
description: "What the Rayfin CLI collects, what it explicitly does not, and how to opt out with RAYFIN_TELEMETRY_OPTOUT."
url: https://rayfin.ai/docs/reference/cli/telemetry
markdown_url: https://rayfin.ai/docs/reference/cli/telemetry.md
section: reference
product: Rayfin
sdk_version: 1.34.0
cli_version: 1.33.2
last_updated: 2026-08-23T01:28:43-07:00
source: reference/cli/telemetry.mdx
---

# Telemetry

> What the Rayfin CLI collects, what it explicitly does not, and how to opt out with RAYFIN_TELEMETRY_OPTOUT.

The Rayfin CLI collects anonymous usage data to help improve the product. On first run, it
prints a notice explaining what's collected and how to opt out.

## What's collected [#whats-collected]

* Command names.
* Which flags were passed, by name only (for example `--force`, `-v`) — never their values.
* Execution status (success/failure), and on failure, a sanitized error name/type/message
  with file paths and stack traces stripped out.
* Execution duration.
* Environment metadata: OS and Node.js version.

## What's not collected [#whats-not-collected]

No personal data, flag *values*, or file contents are collected — arguments you pass
(project names, workspace names, connection strings, file paths) are never sent, only the
fact that a given flag was used.

## Opt out [#opt-out]

```bash
export RAYFIN_TELEMETRY_OPTOUT=1
```

Set this in your shell profile to opt out permanently, or inline for a single invocation.

## Telemetry endpoint override [#telemetry-endpoint-override]

`RAYFIN_APPINSIGHTS_CONNECTION_STRING` overrides the telemetry endpoint used by the CLI and
the VS Code extension. This is a contributor/internal setting, not something most projects
need to set. See
[Environment variables](/docs/reference/config/environment-variables) for the full
shell-only variable reference.

```prompt title="Disable Rayfin CLI telemetry in CI"
Add RAYFIN_TELEMETRY_OPTOUT=1 to my CI workflow's environment variables so the Rayfin CLI
doesn't send usage telemetry from automated runs.
```