Data Security

This page explains exactly how Tempo-Finder.com handles data when you use its tools — specifically what the tap tempo tools capture (no audio — none), what happens to audio in the beat detection tools, how uploaded audio files are handled, and how advertising and analytics systems relate to your audio activity.

Why This Page Exists

Some tools on Tempo-Finder.com use your microphone or process audio files you upload. Users reasonably want a clear, honest explanation of what happens to that audio at each step — not marketing language, but a specific technical account of the process.

Part 1 — Tap Tempo Tools: No Audio Involved

The tap tempo tools — including the Tempo Finder and Tap Tempo — require no microphone access and capture no audio from your device whatsoever.

These tools work exclusively from the timing of your taps. When you press the spacebar, click the button, or tap the screen, the browser records the timestamp of that action using JavaScript’s performance timing API. The interval between consecutive timestamps is calculated mathematically to produce a BPM reading.

No sound enters the browser. No audio stream is opened. No microphone permission is requested. Your device’s microphone is completely uninvolved.

The BPM to Milliseconds Converter and any other pure calculation tools on this site are similarly audio-free — they compute results from numbers you type.

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

The audio beat detection tool analyses audio either from your device microphone or from an audio file you upload. Here is exactly 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. Tempo-Finder.com cannot access your microphone without your explicit approval. If you click Block or dismiss the prompt, the tool cannot function 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 detect onset events — moments where audio energy spikes sharply, indicating a beat. The interval between onsets is calculated to determine BPM. 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. No audio persists in any form.

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 browser tab or navigate away, the decoded audio data is cleared from browser memory. The original file on your device is unaffected.

What Tempo-Finder.com Never Does With Your Audio

Does not upload — no audio or audio file data is sent over the internet to any server
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 Google AdSense, Google Analytics, or any other service integrated into this site
Does not profile — your audio activity is never connected to any personal identifier or advertising profile

Part 3 — Advertising and Analytics Are Separate From Audio

Tempo-Finder.com uses Google Analytics for traffic measurement and Google AdSense for advertising. Both services may set cookies on your device.

Neither Google Analytics nor Google AdSense has access to your microphone, your uploaded audio files, or your beat detection results. The audio processing pipeline and the advertising/analytics systems are entirely isolated — they do not share data, identifiers, or results in any direction.

Full details on cookies and advertising data are in the Cookie Policy and Privacy Policy.

Part 4 — Contact Form Data

If you contact Tempo-Finder.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 to resolve the inquiry.

Part 5 — HTTPS Security

All pages on Tempo-Finder.com are served over HTTPS, encrypting data transmitted between your browser and this website. Because audio processing occurs entirely within your browser and no audio is transmitted over the network, HTTPS encryption is not relevant to audio data specifically — but it protects all other data exchanged during your visit.

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, please report it via the Contact page. All reports are reviewed personally by Olivia and responded to within 48 hours.