livediagram measures which features get used so the project knows what works, and it does this without creepy tracking. The analytics are anonymous, first-party, and off unless the deployment turns them on. There are no third-party trackers, no ad pixels, and nothing is ever sold or shared beyond a dashboard anyone can read.
What an event looks like
When telemetry is enabled, the editor records small product events made of just three fields: a category, an action, and an optional preset type. For example, "a diagram was created", or "a square element was added". That is the entire shape of an event.
- No identity. Events carry no user id, no account, and no IP address.
- No content. They never include a diagram name, tab name, participant name, element text, share code, or diagram id.
- Only a fixed vocabulary. The type is always a preset value from a closed list, such as a shape kind or a share role, never anything you typed.
The server checks this as well. It throws away any event whose category or action is not on its list, and it will only store a type that is a short token — at most 40 characters of letters, digits, spaces and simple punctuation — so anything the length of a note, or carrying ordinary punctuation, is refused before it is stored.
That second check is a backstop rather than the main protection. The protection is that the editor only ever sends a value from a fixed list in the first place: where a value could come from something you named, it is mapped to a fixed token before it is sent. A theme you built and named yourself is reported as simply "Custom", and your name for it never leaves your browser.
The same rules apply to error tracking. When something breaks, the event records only a generic token: an HTTP status like "Http500" for a failed request, or a fixed kind like "Uncaught" for a browser-side exception. Never an error message, stack trace, URL, or anything about what you were working on. These show up on the dashboard's Exceptions view like everything else.
The public dashboard
Whatever is collected is published openly at the public telemetry dashboard. It shows aggregate counts over Today, the last 7 days, and the last month, grouped by category and action. Old rows are swept automatically, so this is recent trend data, not a permanent archive. The whole point is transparency: anyone can see precisely what is measured.
How to opt out
You are always in control of your own browser.
From that point on, your browser sends nothing, regardless of the deployment's setting.
The opt-out itself is the last signal your browser sends, so even leaving is recorded only as an anonymous "someone opted out", never tied to you.
Telemetry is off by default. On a self-hosted deployment it stays completely off unless the operator explicitly enables it, so a fork or private instance emits and serves nothing.
Was this article helpful?