Data and Privacy

MIDI Command Studio sends data only for licensing and when you choose to send feedback or crash reports. It does not include analytics or background telemetry.

Licensing & activation: The app makes network requests for license actions (activate/status/deactivate). These requests include your license key and non-identifying device/install identifiers (a non-reversible machine hash and an install ID) used to manage activations. In full-license mode, a status check may run on startup. No usage tracking or MIDI input data is transmitted. If a licensing response includes an email address, it is displayed locally only.

Feedback & crash reports (optional): If you choose to send feedback or a crash report, the app sends the report content to help diagnose issues. This can include app version, device/preset labels, stack traces, and a log tail (from error_log.txt, up to 200 KB). The log redacts your Windows user path (e.g., C:\Users\<redacted>\...). The feedback form can prefill a non-reversible machine hash and (optionally) the log text. No license keys are included unless you manually add them.