Privacy Policy

Last updated: October 19, 2026

MidiGlow is a free, browser-based MIDI player and visualizer. This page explains — in plain language — exactly what happens to your files and your data when you use it. The short version: your files never leave your device. Site-usage analytics follows the regional consent choices explained below.

Your files never leave your device

When you open a .mid or .midi file, your browser's File API reads it straight into the page, where it is parsed, synthesized, and drawn locally. MidiGlow never uses form uploads, fetch/XMLHttpRequest, or any third-party upload SDK to transmit your files — there is no server anywhere in the product able to receive them. The only network requests the core MIDI tool makes are for its own static assets (the page itself and the optional demo file hosted on the same domain). Once the page has loaded, the core tool even works offline.

Analytics and consent

We use Google Analytics to measure page visits and site usage, including browser, device, and approximate location information. Your files, images, prompts, and tool inputs are never sent to analytics. For visitors in the EEA, UK, and Switzerland, analytics cookies and scripts load only after Allow. Elsewhere analytics is enabled by default. Use Privacy settings to decline or withdraw consent and clear analytics cookies. We store your consent choice in this browser. Advertising features are disabled.

Local tool data

Loaded MIDI files, playback position and track settings remain in this tab. They are not uploaded or included in analytics.

Error handling

If something goes wrong while parsing a file, the error message you see is generated locally in your browser. MidiGlow's error handling never includes file contents, MIDI event details, or local file paths beyond the name of the file you chose to open.

Changes & contact

If this policy ever changes, the update will be published on this page. Questions? Reach us via the contact page.