Privacy
Last updated 30 August 2026 · applies to chordloop.org and the ChordLoop app
ChordLoop has no server, no accounts and no analytics. It does not collect, transmit or share any personal data, and there is nowhere for it to send any. Everything the app knows is stored by your own browser, on your own device. The rest of this page is the detail behind that sentence.
What is stored, and where
The app keeps its state in your browser's local storage and in its cache. That data never leaves the device it is on. It is:
- the loop you currently have open, so it is still there when you come back;
- loops you have saved and named, and the loop library's own settings;
- your practice log — how long the loop was running, and when;
- your settings: instrument, tuning, theme, note-colour palette, diagram size;
- a copy of the app itself and of the instrument samples you have played, so it opens without a network.
None of this is transmitted anywhere. There are no cookies, no tracking pixels, no advertising identifiers, no crash reporting service and no third-party scripts of any kind.
The microphone
The tuner and the play-along features read pitch from your microphone. When you start one of them your browser asks your permission, and the audio is analysed frame by frame in the page, on your device. It is never recorded, never stored and never uploaded — the app has no server to upload it to. The microphone is released as soon as you stop, and closing the tab ends it either way.
MIDI
If you connect a MIDI instrument, the app asks your browser for access to it and reads the notes you play so it can score them against the loop, and can send notes out to a MIDI device you choose. That traffic stays between your browser and your own hardware.
Crash reports
When something goes wrong the app writes the error to a log in your browser so you can read it back in the Diagnostics panel and copy it out if you want to report it. Nothing is sent automatically. If you send a report, you are the one sending it, and you can see exactly what it says first.
Sharing a loop
A loop can be shared as a link. The whole loop is encoded into the URL itself, in the part
after the #, which browsers do not send to any server — so a shared loop is
carried by whoever you send it to, not stored by anybody. Nothing about you travels with
it.
Backups you make yourself
The app can export everything it holds to a file. That file is written by your browser to wherever you tell it, and what happens to it afterwards is up to you. Restoring one merges it with what is already there rather than replacing it.
Hosting
Loading chordloop.org means requesting files from a web host, exactly as loading any other site does. A host may keep ordinary server logs — the request, the time, an IP address — for its own operations and security. That is the whole of the data collection involved in using ChordLoop, it is not linked to any account because there are none, and it is not used to build a profile of you.
Children
ChordLoop is suitable for any age and collects no personal data from anyone, of any age.
Deleting your data
Clearing site data for chordloop.org in your browser, or uninstalling the app from your home screen and clearing its storage, removes everything: loops, practice log and settings. There is no copy anywhere else, and nothing to request from anybody. For the same reason, exporting a backup first is worth doing if you want to keep it.
Changes
If this policy ever changes, the date at the top changes with it. If ChordLoop ever gained a feature that genuinely needed to send something off the device, it would be asked for plainly at the point of use rather than covered by a sentence here.