> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openlit.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Anonymous Usage Metrics

> How OpenLIT's anonymous usage metrics work, what is collected, and how to opt out of telemetry with TELEMETRY_ENABLED=false

OpenLIT collects anonymous usage metrics by default so we can see which features are used and where to improve the product. Nothing here is meant to identify you personally - there is no email, name, password, secret, or span/trace content in what we send.

There is **no in-app settings toggle** for this. Opt out with an environment variable on the OpenLIT deployment, then restart so the change takes effect.

## How to opt out of telemetry

Set:

```bash theme={null}
TELEMETRY_ENABLED=false
```

That disables browser analytics, server-side usage events, and the daily install snapshot. Omit the variable (or set it to anything other than `false`) to leave collection on - Compose and `.env` examples ship with it enabled.

## What identifies an install (anonymously)

| Signal                     | What it is                                                               |
| -------------------------- | ------------------------------------------------------------------------ |
| **User**                   | An opaque user id - never your email, name, or password                  |
| **Organisation / project** | Opaque organisation and project group ids - never names or member emails |
| **Install**                | A stable random `install_id` per OpenLIT deployment                      |
| **Environment**            | Ordinary analytics context such as browser, OS, and approximate location |

## What we track

When enabled, OpenLIT sends:

* **Active usage** - opaque user / organisation / project activity, login and registration, and page path visits as people use the UI
* **Feature adoption** - create/update/delete-style signals for prompts, rules, evaluations, dashboards, contexts, OpenGround, and database configurations (ids and counts, not names or contents)
* **Auto features** - whether Auto Pricing and auto evaluation are turned on, and run outcomes
* **SDK-facing API use** - success/failure when applications fetch prompts or Vault secrets through OpenLIT (the OpenLIT server records this; the SDK packages do not phone home on their own)
* **Daily install snapshot** - once per day, aggregate totals for that install: OpenLIT version, counts of users / organisations / projects / database configs, whether auto pricing or auto evaluation is configured, and high-level ingestion volume counts

We never send emails, names, passwords, secrets, API keys, prompt or rule text, or the contents of your spans and traces.

## Where metrics are stored

Usage metrics are sent to PostHog for secure storage and product analytics.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is there a UI switch to disable this?">
    No. Opt out only via `TELEMETRY_ENABLED=false` on the OpenLIT process, then restart.
  </Accordion>

  <Accordion title="Does disabling this stop my own OpenTelemetry traces?">
    No. This only controls OpenLIT's anonymous product usage metrics. Your application's OTLP traces, metrics, and logs are separate.
  </Accordion>
</AccordionGroup>

***

<CardGroup cols={2}>
  <Card title="Configuration" href="/latest/openlit/configuration" icon="gears">
    Full environment variable reference, including TELEMETRY\_ENABLED
  </Card>

  <Card title="Installation" href="/latest/openlit/installation" icon="download">
    Deploy OpenLIT and set environment variables for your setup
  </Card>
</CardGroup>