Telemetry

partyline collects a small amount of anonymous usage data so we can see how many installs are actually being used — not just downloaded. It carries no identity, no code, no paths, and no content, and you can turn it off with one environment variable.

What's sent

Once a day, the CLI sends a single "active" ping containing only:

  • a random install id — a UUID generated on your machine, stored in ~/.partyline/telemetry.json. It is not derived from your account, hostname, email, or anything identifying. It exists only so two pings from the same install aren't counted as two installs.
  • the CLI version (e.g. 0.6.24)
  • the operating system (e.g. darwin, linux)

That's the entire payload. No file paths, no project names, no repository contents, no keystrokes, no account — by construction.

What's not sent

  • ❌ Your identity, email, or GitHub username
  • ❌ Any absolute path, directory name, or project label
  • ❌ Terminal contents, prompts, or agent output
  • ❌ Secrets or environment variables

The CLI only ever talks to partyline.sh. It never sends events to a third party directly; the control plane forwards anonymized counts to our analytics server-side.

Turn it off

Set either of these in your environment and the CLI never sends a ping:

export PARTYLINE_TELEMETRY=0
# or the cross-tool standard:
export DO_NOT_TRACK=1

Telemetry is also off automatically in CI (CI is set) and for local dev builds.

You'll see a one-time notice the first time telemetry is about to run on an interactive terminal — and no ping is ever sent before that notice has been shown, so a headless or scripted invocation never phones home undisclosed.

The update check

Separately, the CLI checks for a newer version (ptln version / a quiet ≤once-a-day background check). That request includes your version + OS so we can measure adoption of releases. It honors its own opt-out:

export PARTYLINE_NO_UPDATE_CHECK=1

Logged-in usage

If you enroll a machine as a daemon, it already reports its version + OS + liveness to power the fleet map. That's part of the product, not anonymous telemetry, and is scoped to your own account.