Privacy Policy

This privacy policy explains what happens to information when you use BPM Key Finder, which tools you can find on the site, and what rights you have. The short version: your audio is analyzed on your own device, we do not operate user accounts, and we do not sell data — because we never collect it in the first place.

Who is responsible

BPM Key Finder is an independent web project offering free browser-based tools for music analysis: a combined BPM and key finder, dedicated BPM, key and tempo detectors, a tap tempo tool, an online metronome and a BPM calculator. The site does not require registration, and no user profiles exist.

Audio files and analysis results

All audio analysis — tempo detection, key detection and tempo classification — runs locally in your browser using standard web APIs. When you select a file, the browser reads it into memory, decodes it and hands the raw signal to a background worker on the same device. The file contents are never transmitted to us or to any third party.

Analysis results are displayed on your screen only. They are not saved to a server, not linked to an identity (there is no identity to link to), and not used for any other purpose. When you close or reload the page, both the audio and the results are gone.

To be precise about the limits: any website you load necessarily travels over your internet connection, but the audio you analyze after loading does not. If you want to verify this yourself, load a tool page, disconnect from the network, and analyze a file — it will keep working, because there is no server involved in the analysis.

Local storage on your device

The tools use your browser's local storage in a strictly limited way:

• Interface preferences. The selected language and the light or dark theme are stored so the site looks the same on your next visit.
• No audio, no results. Nothing you analyze is ever written to local storage or to cookies.

This data stays on your device. You can clear it at any time through your browser settings, and deleting it has no functional downside beyond resetting the appearance.

Analytics

If analytics is enabled on a page, it collects anonymized, aggregated statistics: how often pages are viewed, roughly from which region, and what kind of device and browser is used. The purpose is understanding which tools are helpful and whether pages load quickly enough.

Analytics never includes your audio files, your analysis results, tapping patterns, or anything you type into the calculators. If analytics is not enabled, nothing is measured at all.

Cookies

The tools themselves do not set advertising or tracking cookies. Where technically necessary, a cookie may remember session-level preferences such as the language choice. Any such cookie is functional, not promotional, and expires with your session or shortly after.

Third parties

We do not sell, rent or trade personal data — as a data source it does not exist on our side. Standard internet infrastructure (for example the network provider that transports the page content to you) processes technical connection data under its own terms, but receives no information about the songs you analyze.

Data retention

Because no audio, no results and no account data are stored, there is nothing to retain, back up or delete on our side. The only data that persists is the interface preference stored locally in your own browser, and you control it.

Children

The tools are suitable for general audiences, including music students. We do not knowingly collect personal information from anyone, regardless of age, and no accounts or profiles can be created.

Your choices

You can use every tool without providing any personal information. You can clear the local preferences at any time in your browser settings, and you can block analytics with common browser content blockers without losing any functionality — the analysis runs either way.

Security

The sensible risk in music analysis would be uploading songs to a server; that risk is designed out. Pages are delivered over encrypted connections, and because the site stores nothing, there is no database of user content that could be breached.

Changes to this policy

If this policy changes, the updated date at the top of the page changes with it. Material changes — for example any future feature that would involve storing data — would be described explicitly here before they take effect.

Summary

Read the files you want, get your BPM, key and tempo answers, close the tab. That is the entire data lifecycle: local processing, nothing retained, nothing shared.

What data exists at all

For clarity, here is the complete inventory of data that can arise when you use the site:

• Audio you select — stays in your browser memory, never transmitted, never stored.
• Analysis results on screen — exist only in the page you are looking at.
• Interface preferences (language, theme) — in your browser's local storage, under your control.
• Aggregate usage statistics — only if analytics is enabled, and never tied to you or your files.

That is the whole list. There are no accounts, no uploads, no databases of songs or results behind it.

Rights you can exercise

Because we do not process personal data of yours, classic requests — access, correction, deletion, portability — are already satisfied: there is nothing of yours in our hands to access, correct or export. Where local privacy law grants rights that go beyond our processing, the practical path is the same for everyone: clear your browser storage to erase every trace on your device, and use standard browser tools to block any analytics you do not want.

Where these guarantees come from

These are not promises bolted onto a product — they follow directly from the architecture described on the About page. Local processing is verifiable: load the page, go offline, and analyze a file. A guarantee you can test yourself is worth more than a paragraph of assurances.