Data Security

This page explains exactly how BPM-Calculator.com handles data when you use its tools — what the calculation tools capture (nothing), what the tap tempo tool captures (keyboard timing only, no audio), and what happens to audio in the beat detection tools.

Why This Page Exists

Some tools on BPM-Calculator.com process audio from your microphone or from files you upload. Users reasonably want a clear technical explanation of what happens to that audio — not reassuring language, but a specific account of the process.

Part 1 — Calculation Tools: No Data Captured

The BPM Calculator, BPM to Milliseconds Converter, and Tempo Markings reference are pure mathematical tools. They require no microphone access, capture no audio, and do not interact with any sensor or input device on your computer beyond receiving the numbers you type into the input fields.

When you enter a BPM value, the browser performs arithmetic on that number using standard JavaScript. No data leaves your device, no data is stored, and no network request is made. The computation happens entirely within the browser’s JavaScript runtime and the result is displayed on screen.

There is no data security consideration for these tools beyond the security of your browser itself.

Part 2 — Tap Tempo: Keyboard Timing Only

The Tap Tempo tool records the timestamp of each keyboard or mouse input using JavaScript’s performance timing API. These timestamps are used to calculate the average interval between taps and convert it to BPM.

No audio is involved. No microphone access is requested. The tool does not listen to your environment — it only records the moment you press a key or click a button. The tap timing data exists only within your active browser session and is cleared when you stop tapping or leave the page.

Part 3 — Audio Beat Detection: What Happens to Your Audio

The audio beat detection tool analyses audio either from your device microphone or from an uploaded audio file. Here is what happens at each step:

Microphone Input

Step 1 — Your explicit permission. When you activate the microphone beat detection mode, your browser displays its standard microphone permission prompt. BPM-Calculator.com cannot access your microphone without your explicit approval. Clicking Block prevents the tool from functioning in microphone mode.

Step 2 — Local audio capture. If you grant permission, the browser opens a real-time audio stream into the Web Audio API — a standard technology built into modern browsers that processes audio locally on your device.

Step 3 — In-browser onset detection. The audio signal is analysed within your browser tab to identify beat onset events and calculate the interval between them. All of this processing happens on your device, not on any server.

Step 4 — Result display. The calculated BPM is displayed on screen. This is the only output of the audio processing.

Step 5 — Session end. When you stop the tool or navigate away, the audio stream is terminated and all audio data is cleared from browser memory. Nothing is retained.

File Upload

Step 1 — Local file reading. When you select or drag an audio file, the browser’s FileReader API reads the file from your device’s storage into browser memory. The file does not travel over the internet at any point.

Step 2 — In-browser decoding and analysis. The audio file is decoded into an AudioBuffer within the Web Audio API and analysed locally using the same onset detection pipeline as the microphone mode.

Step 3 — Result display. The calculated BPM is displayed on screen.

Step 4 — Session end. When you close the tab or navigate away, all decoded audio data is cleared. The original file on your device is unaffected.

What BPM-Calculator.com Never Does With Your Audio

Does not upload — no audio or file data is sent over the internet
Does not record — no audio file is created from your microphone input
Does not store — no audio data is retained after your session ends
Does not share — your audio is not accessible to any third-party service integrated into this site
Does not profile — your audio activity is never connected to any personal identifier

Part 4 — Contact Form Data

If you contact BPM-Calculator.com through the Contact page, we receive your email address and message content. Used only to respond to your inquiry. Not shared with any third party, not retained longer than necessary.

Part 5 — HTTPS Security

All pages on BPM-Calculator.com are served over HTTPS, encrypting all data transmitted between your browser and this website. Because audio and tap session data is processed entirely within your browser and never transmitted, HTTPS is not relevant to that data specifically — but it protects all other information exchanged during your visit including contact form submissions.

Part 6 — Reporting a Security Concern

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