Telemetry

What OpenUI Lang collects, why it is collected, and how to control installation and runtime telemetry.

OpenUI Lang collects limited telemetry about how @openuidev/lang-core is installed and used. Installation telemetry is on by default and can be disabled. Runtime telemetry is off by default and must be enabled explicitly.

Why is telemetry collected?

We want OpenUI to work well beyond the environments and examples we test ourselves. Telemetry helps us understand common runtimes and the broad shape of component and tool setups, so we can improve OpenUI Lang generation, compatibility, performance, and developer experience.

Runtime telemetry is optional, but enabling it helps us improve OpenUI based on real-world usage rather than assumptions.

What is being collected?

During installation

When @openuidev/lang-core is installed, we collect:

  • A random installation ID
  • A project identifier created locally so the original repository URL or path is not sent
  • OpenUI Lang Core, Node.js, operating system, and package manager versions
  • Whether the installation is running in CI or Docker

This runs during package installation. It does not run during your application build unless the build also installs dependencies.

At runtime

Runtime telemetry is off by default. When enabled, OpenUI Lang samples successful prompt generations on your server and sends telemetry for about 1 in 10 of them. Browser calls never send runtime telemetry.

We collect:

  • OpenUI Lang Core and server runtime versions
  • Environment and CI information
  • The number of components and tools in the prompt setup
  • Project and prompt-setup identifiers created locally so the original values are not sent

What about sensitive data?

We do not collect:

  • Prompts, messages, preambles, examples, additional rules, or generated output
  • Source code or full component, tool, or schema definitions
  • Repository URLs, project names, file paths, branches, or commits
  • Names, email addresses, usernames, user IDs, or chat data
  • Credentials, API keys, environment values, errors, logs, or stack traces
  • Routes, DOM data, or UI interactions

How do I opt out of installation telemetry?

Set either variable when installing dependencies:

OPENUI_TELEMETRY_DISABLED=1 pnpm install

or:

DO_NOT_TRACK=1 pnpm install

These variables also work with npm, Yarn, and Bun. In CI, set one before the dependency-install step.

How do I opt in to runtime telemetry?

  1. Set this variable in your server environment:
OPENUI_RUNTIME_TELEMETRY_ENABLED=1
  1. Restart your server or redeploy your application.

To turn it off, remove OPENUI_RUNTIME_TELEMETRY_ENABLED. The global OPENUI_TELEMETRY_DISABLED and DO_NOT_TRACK settings always take priority.

Please consider enabling runtime telemetry—it helps us improve OpenUI Lang for everyone.

On this page