Privacy
What happens to your songs and your visit.
MIDI.PLAY has no accounts. Your songs live in your browser, but turning audio into notes means uploading it. This page says what leaves your device, what stays, and what we count. Last updated 29 October 2026.
The short version
- Audio is uploaded. A song you add as audio is sent to a transcription service to be turned into notes. Splitting it into parts sends it to our model server. MIDI files are not uploaded.
- Your library stays in your browser. Songs, notes and settings are saved on your device. There is no account and nothing syncs.
- Analytics are off until you turn them on. Google Analytics only loads if you choose it, and never if your browser sends Do Not Track or Global Privacy Control.
- Only add songs you own or have permission to use. Do not add anything you would not want sent to a server.
What leaves your browser
- Audio for transcription
- When you add an MP3 or other audio file, the file, including its name, is uploaded to a transcription service that sends the notes back. For this site that is a service the makers run on Modal’s cloud GPUs. Some builds of the app, and the
/api/transcriberoute on this site, use Kyutai’s public MuScriptor service instead. The request passes through Cloudflare, which hosts this site. The request also carries a random ID that lives only as long as the browser tab, so a service can tell one visit from another. - Splitting into parts
- If you split a song into parts, the audio is uploaded to the MIDI.PLAY model server, which the makers run on Cloudflare’s infrastructure. It may keep the files it has worked on so it does not have to repeat the work. Deleting a song from your library in the app also asks the server to delete its copy. This is optional and is not always available.
- YouTube links
- If a link import is available and you paste one, the link is sent to the model server, which downloads the audio itself. This feature is often blocked by YouTube and may be switched off.
- MIDI files
- Never uploaded. They already list the notes, so nothing needs transcribing.
- Piano sounds
- When the app first needs its piano sounds, it downloads a sound library file from
huggingface.co(or fromraw.githubusercontent.comif you choose the other bank). Those hosts see your IP address and the request, as any website would. The file is then kept in your browser. - Fonts and the rest
- Fonts, scripts and the demo songs are served from this site. Apart from the piano sounds above, and Google Analytics if you switch it on, the pages load nothing from other companies.
- Server logs
- This site is served by Cloudflare Pages, which, like any host, sees your IP address and the pages you request. The site’s own code does not log visits or uploads.
What stays in your browser
The app stores these on your device only. Clearing site data for midi.falsaclub.com removes all of it.
- Your library in IndexedDB: the audio you added, the notes found in it, your edits and each song’s settings.
- Settings and choices in local storage: things like the sound bank, note colours, the demo songs already added, whether you confirmed you may use the songs you add, and your analytics choice.
- The sound library in the browser’s cache.
- A tab ID in session storage, gone when the tab closes.
MIDI.PLAY sets no cookies of its own. The only cookies involved are Google Analytics’, and only if you turn analytics on.
Analytics
We would like to know which parts of MIDI.PLAY get used, so we can fix and improve them. We use Google Analytics 4 for that, and it is off by default. Nothing is sent to Google until you switch it on here or in the footer of any page. Your choice is saved in this browser and applies to the whole site, including the app. It never turns on if your browser sends Do Not Track or Global Privacy Control.
Analytics need JavaScript to switch on, so they are off.
What is counted when it is on
- Page views, and the usual details Google collects with them: your IP address, browser, device, approximate location and the page you came from. Google sets the
_gacookies. - Events when you use the app: a song added, opened or finished, a split or transcription started or completed, a part or practice mode chosen, a tool or the note editor opened, a MIDI keyboard connected, and import errors.
- Song names. Events include the song’s name (for an upload, the file name without its extension, cut to 100 characters), so avoid a file name you would not want shared. Error events include the error message.
The audio, the notes and anything you type are not sent to analytics. Switching analytics off removes the choice, stops events at once and deletes the Google cookies from this browser. Data already sent stays in Google Analytics under its own retention settings.
Your songs and your choices
Only add songs you own or have permission to use. The app asks you to confirm this before your first song.
To remove a song, delete it from your library in the app. That removes it from your browser and asks the model server to delete its copy. To remove everything MIDI.PLAY stores on your device, clear the site data for midi.falsaclub.com in your browser settings.
There are no ads and no accounts. Questions or a request about a copy held on a server? See the contact page.
Free · In your browser · No account