Privacy
The analytics consent switch, the events Mixar sends while it is on, and what happens to the identifier.
Settings → Privacy (“Anonymous app usage data.”) holds the telemetry consent switch.
Analytics
The card is Analytics, subtitle “Share anonymous app data.”
| Control | Type | Values | Default | Effect |
|---|---|---|---|---|
| Send anonymous usage data | header switch | on / off | off | Sends the events listed below while it is on. |
There is no prompt at any point. The switch saves without restarting the engine, like the Theme select and the Visible fields checkboxes.
What it sends
With the switch on, the app sends two kinds of event to the same EU-hosted PostHog project the website uses:
| Event | When | Payload |
|---|---|---|
app launched |
once per launch, after the engine starts | app version, OS, OS version, CPU architecture, build mode |
$exception |
each framework or uncaught asynchronous error the app reports at runtime | error type, message, stack trace when available, plus the same build fields |
Reports begin once the engine has started and analytics is armed. An error raised earlier in start-up is not sent. Identical reports (same type and message) are collapsed for a minute, so a widget that throws every frame sends one event, not thousands.
What is removed from a report
Before an event is queued, an absolute file path is replaced with <path>, and everything after it on that line goes with it. Text before the path survives. A message can still name a single file. A relative path written by the failing code stays as written, and your library’s paths are absolute, so they never survive.
Identifier
Both events carry the random identifier created when you first turn the switch on. That identifier is deleted when you turn the switch off, and turning it off also drops anything already queued.