Files
coder/docs/admin/setup/telemetry.md
T
Nick Vigilante 1872b183ee docs(docs/admin): reformat setup and integrations docs to one sentence per line (#30704)
Reformats the setup and integrations docs under `docs/admin/setup` and
`docs/admin/integrations` to one sentence per line, as the [docs style
guide](https://github.com/coder/coder/blob/main/docs/.style/style-guide/formatting.md#one-sentence-per-line)
requires. Hard-wrapped paragraphs are unwrapped and lines holding
several sentences are split, so a later edit to one sentence shows up as
a one-line diff.

Apart from the exception below, only whitespace inside paragraphs and
list items changes, and the rendered pages are the same. Comparing the
changed files against `main` word for word, ignoring whitespace and
blockquote `>` markers, finds differences only on the reworded lines.
`git diff --word-diff` is easier to read than the line diff.

1 lines that already contained an em or en dash were reworded by hand,
because `lint/emdash` treats every reflowed line as newly added. Each
uses a parenthetical, a separate sentence, or a colon after a lead-in.
Dashes on lines the reflow did not touch are left alone.

Applied with an in-progress formatter, limited to pages listed in
`docs/manifest.json` and excluding generated reference docs. This is one
of a batch of PRs that split the docs by area (25 files changed, 380
insertions(+), 572 deletions(-)).

---
🤖 Built with AI assistance.
2026-10-14 14:29:20 -04:00

1.8 KiB

title
title
Telemetry

Note

TL;DR: disable telemetry by setting CODER_TELEMETRY_ENABLE=false.

Coder collects telemetry from all installations by default. We believe our users should have the right to know what we collect, why we collect it, and how we use the data.

What we collect

You can find a full list of the data we collect in our source code here. In particular, look at the struct types such as Template or Workspace.

As a rule, we do not collect the following types of information:

  • Any data that could make your installation less secure
  • Any data that could identify individual users, except the administrator.

For example, we do not collect parameters, environment variables, or user email addresses. We do collect the administrator email.

Workspace agent statistics include session counts keyed by normalized application names, which can include custom IDE names that workspace agents report.

Why we collect

Telemetry helps us understand which features are most valuable, what use cases to focus on, and which bugs to fix first.

Most cloud-based software products collect far more data than we do. They often offer little transparency and configurability. It's hard to imagine our favorite SaaS products existing without their creators having a detailed understanding of user interactions. We want to wield some of that product development power to build self-hosted, open-source software.

Security

In the event we discover a critical security issue with Coder, we will use telemetry to identify affected installations and notify their administrators.

Turn telemetry on or off

You can turn telemetry on or off using either the CODER_TELEMETRY_ENABLE=[true|false] environment variable or the --telemetry=[true|false] command-line flag.