Data Security

This page explains exactly how BPMKeyFinder.com handles the audio files you upload — what happens to your file at each step, what the tool does and does not do with your audio, and how your file is cleared after analysis.

For many users, this is the most important page on the site. DJs with exclusive tracks, producers with unreleased material, and musicians with personal recordings all need to know exactly what happens to their audio before uploading. This page answers that question precisely.

The Core Answer

Your audio file never leaves your device.

When you upload a file to BPMKeyFinder.com, it is read from your local storage, decoded, and analysed entirely within your browser. No audio data is transmitted over the internet to any server at any point in the process. BPMKeyFinder.com never receives, stores, or has access to your audio.

Step-by-Step: What Happens to Your File

Step 1 — File selection. You select or drag a file into the tool interface. This triggers the browser’s FileReader API — a standard browser technology that reads files from your device’s local storage into browser memory.

Step 2 — Local reading. The FileReader API reads your file’s raw data into the browser. At no point during this step does the file travel over the internet. The data moves from your device’s storage to your browser’s memory — a process that stays entirely on your device.

Step 3 — Audio decoding. The raw file data is decoded into a raw audio waveform (PCM samples) using the browser’s AudioContext.decodeAudioData() function. This produces an AudioBuffer — an in-memory representation of the audio — at the browser’s native sample rate. This decoding also happens entirely locally. No data leaves your device.

Step 4 — Analysis. The decoded AudioBuffer is passed to the BPM detection algorithm and the key detection algorithm. Both run locally in the browser using JavaScript. No audio data is sent to any external service for processing. The analysis happens on your device, in your browser.

Step 5 — Results. The detected BPM, key, and Camelot Wheel notation are displayed on screen. These are numbers and text derived from the analysis — not any representation of the audio itself.

Step 6 — Session end. When you navigate away from the tool, close the browser tab, or reload the page, the AudioBuffer is cleared from browser memory. No audio data persists in any form. No file is cached, logged, or stored.

What BPMKeyFinder.com Never Does With Your Audio

Does not transmit — no audio data is sent over the internet to any server
Does not store — no audio file, no audio data, and no audio derivative is saved anywhere
Does not retain — audio data is cleared from browser memory when the session ends
Does not identify — your file name, file content, or analysis results are not linked to any personal identifier
Does not share — your audio is inaccessible to any third-party service integrated into this website
Does not log — no record is created of what file you uploaded or what results were returned

Why This Matters for Your Files

Unreleased music. If your file contains an unreleased production, recording, or composition, uploading it here does not expose it to any server, database, or third party. The analysis happens on your device and the file is cleared when you are done.

Exclusive DJ tracks. Promotional tracks, white labels, and exclusive material that you are not permitted to distribute are not distributed when you upload them here. The file stays on your device.

Commercial recordings. Whether you own the rights to a recording or are simply analysing a purchased track, your upload does not create any transmission of the audio that would implicate distribution or copyright concerns.

Browser Memory and Security

The decoded audio data exists in your browser’s JavaScript heap memory during analysis. This memory is:

Not accessible to other browser tabs or other websites
Not written to disk by the browser’s normal operation
Cleared when the browser tab is closed or navigated away from
Subject to the same security protections as all browser memory on your device

The AudioBuffer in browser memory is a processing representation — not a copy of your original file that could be extracted and saved elsewhere.

File Name and Metadata

The file name and any embedded metadata (ID3 tags, EXIF data, etc.) in your audio file are read by the browser as part of the file loading process. BPMKeyFinder.com may use the file name for display purposes in the tool interface. No file name, tag, or metadata is transmitted to any server or stored anywhere.

Contact Form Data

If you contact BPMKeyFinder.com through the Contact page, we receive your email address and the content of your message. Used only to respond to your inquiry. Not shared with any third party. Retained only as long as necessary to resolve the inquiry.

HTTPS

All pages on BPMKeyFinder.com are served over HTTPS. Because file processing occurs entirely within your browser and no audio is transmitted over the network, HTTPS is not relevant to file security specifically — but it protects all other data exchanged during your visit, including contact form submissions.

Reporting a Security Concern

If you discover a security issue or any data handling practice that does not match what is described on this page, please report it immediately via the Contact page. All reports are reviewed personally by Charlotte Hayes and responded to within 48 hours.