BPMFinder.xyz Cookie Policy

Policy in one sentence

This BPMFinder.xyz cookie policy states that the application intentionally sets no cookies. It also writes no beat count, duration, count convention, comparison window, candidate BPM, or preference to localStorage, sessionStorage, IndexedDB, or another persistent browser database. The policy is effective August 29, 2026.

Because there is no site cookie or tracking technology to choose, the interface does not need a cosmetic consent banner. You can confirm current behavior with the inspection steps below.

Cookies and their purposes

A cookie is a small domain-associated value a browser can return with later requests. Sites may use cookies for sessions, authentication, preferences, security, measurement, advertising, or other purposes. Some expire with a browsing session, while others remain until a date or deletion.

BPMFinder.xyz has no sign-in, saved project, cart, advertising profile, analytics vendor, or remembered settings. Its manual calculator therefore has no application need for a cookie.

Active memory is different

When you type 24 intervals and 12 seconds, the page must hold those numbers long enough to calculate 120 BPM. That is active in-memory interface state. It is not written as a cookie and is not intended to survive reset, refresh, closure, or navigation.

Reset removes visible values. Leaving the page may erase them. A browser can sometimes restore a prior screen from its own back-forward cache, but the application must not treat that as a saved record. Copy any observation you need before moving on.

The same rule covers comparator windows and planning values. No tool creates a hidden tempo history.

Cache and browsing history

Browsers often cache public files—such as the favicon, hero image, stylesheet, script, and HTML—to improve loading. They may store a history entry containing a visited route. Those features are distinct from a site cookie and should not include private tempo inputs under the behavior described here.

Device extensions, password managers, accessibility software, enterprise controls, screen recording, and network tools can have their own access. Review their settings where local confidentiality matters. Private browsing changes some local retention, but it is not a universal anonymity system.

No analytics or ad identifiers

The site includes no analytics tag, advertising pixel, heatmap, session replay, cross-site identifier, or marketing tracker. User-entered values are not placed in event payloads. The product does not create a profile of musical interests or measurement behavior.

Vercel still processes ordinary network requests to serve static pages and protect infrastructure, as described in the privacy policy. That technical delivery does not authorize a cookie-based visitor profile or calculator logging.

Worked state example

You enter 33 audible events over 16 seconds. The tool normalizes to 32 intervals and displays 120 BPM. Under this policy:

• no cookie contains 33, 16, 32, or 120;
• no persistent browser key stores the result;
• no account attaches it to an identity;
• no analytics event transmits the inputs;
• reset clears the interface state.

Your browser may retain that you visited /tools/manual-bpm-finder and may cache public page assets. Clearing cookies alone would not necessarily remove history or cache because they are separate stores.

Why preferences are not retained

Remembering a default count convention might be convenient, but persistent preferences require documentation, lifecycle decisions, testing, and potentially consent analysis. Beginning with no storage makes the promise easy to audit and prevents a harmless preference mechanism from becoming an undeclared observation history.

Before any future storage is introduced, the operator will document the exact key, value, purpose, provider, duration, removal method, user control, and legal basis. The privacy and cookie pages will receive a new effective date, and the live behavior must match the written explanation.

How to verify the live site

To inspect current behavior, check:

• response headers for Set-Cookie;
• Cookies, Local Storage, Session Storage, and IndexedDB in browser developer tools;
• service-worker caches for private field values;
• network calls to unapproved third parties;
• script bundles for analytics or replay code;
• state after reset, reload, closing, and back navigation;
• consent UI, which should be absent when no consent-requiring technology exists.

A written policy cannot establish live browser behavior by itself. Direct network and storage inspection provides the practical check.

Limits of the promise

The policy covers technologies intentionally used by the product, not every record created by an internet provider, DNS resolver, browser, operating system, hosting platform, email service, workplace, or extension. Disabling cookies does not stop ordinary page requests. Clearing browser storage does not erase emails already sent.

Privacy rights vary by location and implementation. Contact support with a question about this site’s practices, and seek qualified advice for your own legal situation.

Frequently asked questions

Why is there no cookie banner?

The site sets no cookies and adds no analytics or advertising technology requiring a preference.

Is sessionStorage allowed?

No. Tool values remain in active memory only.

Does the site remember my last BPM?

No. There is no result history or saved preference.

What if a host cookie appears?

The behavior should be removed or disclosed accurately with any controls required by applicable law before it remains in use.

Report unexpected storage

Email support@bpmfinder.xyz with the route, cookie or storage key, provider, and what action created it. Do not include private measurement notes.