Skip to main content
Relic collects anonymous usage telemetry to help us understand how the product is used and where to improve it. Telemetry is entirely optional and can be disabled at any time.
No secrets, project names, environment names, or personal data are ever collected.

​
What Is Collected

​
CLI & TUI (Server-Side)

The CLI and TUI send anonymous events through a first-party telemetry proxy (telemetry.withrelic.com) to PostHog. Events collected: Metadata attached to each event:
  • platform (e.g. darwin, linux)
  • arch (e.g. arm64, x64)
  • node_version
Not collected: secret values, secret keys, project names, environment names, email addresses, passwords, or any encrypted data.

​
Web (Client-Side)

The website (withrelic.com) uses PostHog client-side analytics for page views, navigation patterns, and feature usage (login, onboarding, dashboard interactions, upgrade flow). Web telemetry uses person_profiles: "anonymous", meaning no personally identifiable information is tied to events.

​
Privacy & Compliance

​
GDPR (EU/EEA)

For visitors from EU/EEA countries, web analytics are not loaded until the user gives explicit consent through a cookie banner. This is enforced at the edge:
  1. The Cloudflare Worker detects the visitor’s country via CF-IPCountry
  2. A relic-geo cookie is set (eu or other)
  3. If eu, PostHog is only initialized after the user clicks “Accept”
  4. If the user clicks “Reject”, no analytics are loaded
EU/EEA countries include all EU member states plus Iceland, Liechtenstein, Norway, Switzerland, and the UK.

​
CCPA (California)

Web analytics use anonymous profiles only. No personal information is sold or shared with third parties. See the Privacy Policy for details.

​
CLI & TUI

CLI and TUI telemetry does not use cookies or track personal information. The distinctId is a random value generated per process and is not tied to any user account. Telemetry is automatically disabled in CI environments and dev mode.

​
Telemetry Proxy

CLI and TUI events are routed through a first-party proxy at telemetry.withrelic.com (a Cloudflare Worker) before reaching PostHog. This prevents ad blockers from interfering and keeps the data flow under our control. The proxy:
  • Forwards events to PostHog (us.i.posthog.com)
  • Strips cookies from forwarded requests
  • Passes X-Forwarded-For for geo-IP (PostHog does not store raw IPs)
  • Caches static PostHog assets at the edge

​
How to Disable

​
CLI & TUI

To re-enable:
Check the current status:
The preference is stored in ~/.config/relic/telemetry.json.
You can also set the RELIC_TELEMETRY=false environment variable to disable telemetry without modifying the config file. This is useful for CI or automation scripts.

​
Web

For EU/EEA visitors, click “Reject” on the cookie consent banner. For all other visitors, telemetry can be blocked with any standard ad blocker or by disabling JavaScript.

​
When Telemetry Is Automatically Off

Telemetry is disabled automatically when any of these conditions are true:
Last modified on October 8, 2026