Privacy
Last updated 4 September 2026
There is no server behind Drum Machine. No accounts, no analytics, no advertising, no cookies and no third-party scripts — nothing you do here is sent anywhere, because there is nowhere for it to be sent. What follows is the detail, since “we collect nothing” is an easy sentence to write and a fair thing to want specifics about.
What stays on your device
Your browser remembers a few things so the machine is where you left it. All of it lives in your browser’s own storage for this site, and none of it is transmitted:
- Patterns and banks you save
drum-machine-banks - The theme you picked
drum-machine-theme - Which MIDI input and output you chose
drum-machine-midi-* - Controls you have mapped to a MIDI knob
drum-machine-midi-cc-map - Which speakers you chose
drum-machine-audio-output
None of it identifies you, and clearing this site’s data in your browser settings removes all of it for good. There is no copy anywhere else.
Samples you load
A sound loaded from your own files is decoded in the browser and held in memory while the tab is open. It is not uploaded, not stored, and not carried by a shared link — reloading the page is enough to be rid of it.
Links you share
Copying a link packs the beat — the steps, the mix, the sample settings, the tempo and the effects — into the part of the URL after the #. Browsers never send that part to a server, so a beat travels in the link itself and nowhere else, to wherever you choose to paste it. Nothing is recorded here when you make a link, and nothing is recorded when someone opens one.
Permissions your browser may ask for
MIDI. Choosing a controller asks your browser for access to MIDI devices, which is used to play the machine and to keep or send clock. Nothing about your devices is kept beyond which one you picked.
Microphone. Browsers hide the names of your audio outputs until audio access has been granted once, so the button that reveals them in Sound settings has to ask for the microphone. The stream is stopped the instant it arrives: nothing is recorded, heard or kept, and the recording indicator goes out with it. Declining is fine — the outputs are still listed, just numbered rather than named.
Working offline
The app installs a service worker that copies the page, its code and the preset kits into your browser’s cache, which is what lets it run with no network at all. That cache sits on your device and clears with the rest of this site’s data.
Hosting
The files are served by GitHub Pages. Like any web server, GitHub records the requests it answers, which includes your IP address and the browser you asked with. That is GitHub’s own processing — this site neither controls it nor can see it — and it is described in the GitHub Privacy Statement. No other service is contacted while the app runs.
Changes
If any of the above stops being true — analytics, accounts, anything at all that leaves your device — this page changes before the feature ships, and the date at the top changes with it.
Contact
Questions, or something here that does not match what the app does: open an issue on GitHub.