Data and Privacy

Summary of what the app and website send, and what they do not send.

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

Website analytics: This website uses Cloudflare Web Analytics to understand page views, referrers, approximate visitor location, device/browser information, and page performance. Cloudflare Web Analytics does not use cookies or local storage for analytics, and Cloudflare states that it does not collect or use visitors' personal data for Web Analytics. Analytics data is used only to improve the website and understand which pages are useful.

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.