BPMFinderYouTube.xyz
Effective date and operator
This BPMFinderYouTube.xyz privacy notice is effective August 29, 2026. BPMFinderYouTube.xyz operates the service in the USA from 30 N Gould St Ste R, Sheridan, WY 82801, USA. Questions may be sent to support@bpmfinderyoutube.xyz. This document describes the current public service and its manual, local-calculation boundary.
The product is designed around data minimization. A visitor can calculate an observation without creating an account, connecting a YouTube profile, providing a URL, uploading media, or submitting a song title. The site needs only manually entered timing and counting values to perform local arithmetic.
Worksheet values remain in the active page
Start and end timestamps, beat counts, count convention, playback speed, optional meter, optional local label, prepared comparison readings, and calculated results remain in ephemeral browser memory. The application does not send those fields to BPMFinderYouTube.xyz, an analytics vendor, a database, a song library, YouTube, or another media service. Reset clears the active worksheet. Closing or reloading the page ends the defined working state.
The launch implementation does not use an account, cloud history, autosave, localStorage, sessionStorage, IndexedDB, or a persistent application cookie for these values. A clipboard action copies the requested observation card to the device clipboard through browser behavior; the operator does not receive that copy. Visitors should still avoid placing sensitive information in the optional label because a copied card may later be shared under their control.
For example, an observation labeled “practice chorus A” with timestamps 04:10–04:30, 41 boundaries, and 0.75× stays in the page while used. The calculation converts 41 boundaries to 40 intervals, derives 120 source BPM, and shows 90 observed BPM. None of those values is needed in a network request. Reset removes them from the page state; the operator cannot retrieve them afterward.
Ordinary web delivery is a separate layer
Loading any website sends ordinary request information to network and hosting systems. Vercel is the declared deployment platform. Depending on its configuration and the visitor’s network, request data can include IP address, requested path, date and time, browser or device information, referring page, response status, and security-related signals. Such data may be processed to deliver content, prevent abuse, investigate faults, and maintain service security.
The manual calculator fields are not placed in URLs, query strings, request bodies, analytics events, or page titles. A route request can show that a page was requested, but it does not include timestamps or BPM values typed after the page loads. Vercel and network intermediaries may process ordinary delivery metadata under their applicable terms.
Support email creates a different record
When a visitor emails support, the sender chooses to transmit an address, message content, routing metadata, and any attachment. Those records may pass through the sender’s and operator’s mail providers and may be kept as necessary to answer, secure the mailbox, maintain continuity, or comply with law. The local-calculation promise does not apply to information voluntarily placed in an email.
Send a neutral reproduction instead of a video, private URL, account name, or media file. A report using invented timestamps and counts is normally sufficient. Requests concerning an email may be submitted through the support address, but identity verification, security, legal obligations, and record-retention limits can affect a response.
No media or platform account access
The site does not call the YouTube API, fetch a video or playlist page, load a thumbnail for analysis, read captions, download or parse audio or video, activate a microphone, or request Google credentials. It cannot see watch history, subscriptions, private videos, channels, comments, or account identifiers. A viewer watches in another tab and transcribes only an observation.
YouTube is a trademark of Google LLC. The site is independent and is not affiliated with, endorsed by, sponsored by, or operated by Google LLC or YouTube. This notice covers BPMFinderYouTube.xyz’s product behavior; it does not replace the privacy terms of YouTube, a browser, an internet provider, or another site the visitor chooses to open.
Retention, security, and age boundary
There is no operator retention period for worksheet values because the launch application does not receive them. Routine hosting and email records may have separate retention determined by operational need, provider settings, security, and law. Reasonable safeguards are planned, but no internet transmission or device environment can be promised perfectly secure.
The service is intended for people aged 16 or older. It is not designed to collect children’s personal information. A parent or guardian who believes a child transmitted personal information through support may contact the operator with enough detail to locate the message.
Privacy rights vary by location. A visitor may ask about access, correction, deletion, restriction, or other applicable rights concerning operator-held information. The operator may need to verify the request and may deny or limit it where law permits. The calculator itself has no account record to export.
Frequently asked questions
Are my timestamps sent to the server?
No. The declared launch logic uses them in active browser memory and does not include them in network requests.
Does the site save my observation label?
No persistent application storage is defined. The label disappears with reset, reload, or tab closure, subject to ordinary browser behavior.
Can hosting still see that I visited a route?
Yes. Ordinary web delivery may produce request and security metadata, which is different from the values entered into the calculator.
How do I request deletion?
Reset local state yourself. For information sent by email, contact support from the relevant address and identify the approximate message date.
Use a non-sensitive label or leave it blank
Review the privacy boundary, keep identifying details out of optional fields, and use reset when the observation is complete. If you need to retain a result, copy it to a location you control and manage according to your own privacy needs.