Skip to main content
Version: 2.3-dev

Telemetry

MaestroHub includes an optional telemetry system that collects anonymous usage statistics to help us improve the platform. This page explains what data we collect, why we collect it, and how you can control it.

Privacy First

No Sensitive Data

We never collect passwords, API keys, or workflow content.

Anonymous Location

Geographic info is approximate (city-level), derived from your public IP.

Transparent

All collected data categories are documented on this page.

Full Control

You can disable telemetry at any time with a single config change.

What We Collect

Every report contains only aggregate counts and system metadata — never workflow content, credentials, or personally identifiable information beyond the first admin email.

CategoryExamples
SystemMaestroHub version, OS, CPU architecture, hostname, public IP
LicenseLicense ID and type (trial, active, expired)
UsersTotal user count, first registered email
LocationCountry, city, region, ISP (derived from public IP)
ConnectionsTotal count and breakdown by type
PipelinesTotal and enabled pipeline counts, node counts by type
UNSTopic count, MQTT mode and client count, storage mode
ExecutionTotal / success / failure counts, success rate, uptime
OtherOrganization count, data model count
info

Geographic information is derived from your server's public IP address. It is approximate and used solely for understanding the global distribution of MaestroHub installations.

When Reports Are Sent

Reports are sent automatically at three points during the lifecycle of a MaestroHub instance:

  • On startup — an initial report is sent when MaestroHub starts
  • On first user creation — a one-time report when the first admin is created
  • Hourly — usage statistics are sent every 60 minutes

Disabling Telemetry

Telemetry is enabled by default. The way you disable it depends on how MaestroHub is deployed.

Edit config.yaml in the MaestroHub directory:

modules:
phonehome:
enabled: false

Then restart MaestroHub.

To re-enable telemetry, set the value back to true and restart.