The short version: MIDI First Note processes keyboard events in your browser. It does not send us device names, played notes, MIDI messages, timing taps, or downloaded support cards.
What the app accesses
If you choose “Connect MIDI keyboard,” your browser asks for MIDI permission. We request ordinary MIDI input only; we do not request system-exclusive (SysEx) access. The app counts available input ports but deliberately does not display, store, or export their names.
What stays on your device
Incoming note and controller messages are used momentarily to update the screen, synthesize a tone, and calculate your tap result. They live only in memory and disappear when the page reloads or closes. The service worker may cache the application shell so the tool can reopen offline, but it does not cache MIDI activity.
Downloads and clipboard
Support-card exports are created locally. They contain only pass/fail states, a count of visible ports, and optional timing measurements. They exclude device names, note history, account identifiers, and network identifiers. You decide whether to save or share them.
Analytics and third parties
There are no analytics, advertising trackers, third-party scripts, cookies, accounts, or cloud storage. Fonts and imagery are served from this site. Your browser and hosting provider may process routine network logs when loading the static files.
Your choices
You can deny MIDI access and still run the sound test. Revoke previously granted access using your browser’s site controls. Clear this site’s storage to remove the offline application cache.
Questions
Open an issue in the public source repository without including device identifiers or lesson details.