BPMCounter.click
Scope and effective date
This BPMCounter.click privacy policy explains the current service operated by BPMCounter.click, 30 N Gould St Ste R, Sheridan, WY 82801, USA. It is effective August 29, 2026. It distinguishes temporary product values from ordinary web delivery and voluntary support correspondence.
The service is intended for people aged 16 or older. Do not use it if you are below the minimum age applicable under this policy.
Tap data stays in active page memory
When you activate a supported counter control, the page records a high-resolution monotonic timestamp in browser memory. It derives adjacent intervals, BPM summaries, elapsed time, recent-window values, range, and variation on your device.
The current product does not send timestamps, interval lists, target values, settings, or calculated results to a product API, account, database, analytics vendor, or cloud project. It does not put them in localStorage or sessionStorage. Reset, reload, timeout, browser memory pressure, or tab closure can remove them.
That design also means BPMCounter.click cannot retrieve, export, synchronize, restore, or delete an active sequence it never receives.
No listening or media collection
The site does not request microphone access, capture system audio, read media files, accept uploads, fetch pasted URLs, monitor devices outside focused page controls, or identify songs. Space and Enter are handled only when the counter region is focused. Keyboard auto-repeat is ignored.
If a future version proposes any materially different data path, it requires separate review, updated public notice, and appropriate consent before the new processing begins.
Ordinary hosting records
Viewing a hosted page still creates network requests. The host, Vercel, may process IP address, request date and time, requested path, response status, user agent, referrer, and security or delivery information under its infrastructure practices.
These records are distinct from the tap sequence. They may be used to deliver assets, maintain reliability, prevent abuse, investigate incidents, and comply with legal obligations. Exact infrastructure settings and provider retention can vary, so this policy does not state a fixed log-retention period that the operator has not verified.
Support correspondence
If you email support@bpmcounter.click, BPMCounter.click receives the address, message, headers, attachments, and any information you voluntarily include. Use a synthetic interval list and avoid media, passwords, identifiers, health data, and unrelated personal details.
Support correspondence may be retained as reasonably needed to answer, maintain records, protect the service, resolve disputes, and meet lawful obligations. A sender can request review through the same address, subject to applicable exceptions and identity verification proportionate to the request.
Cookies and browser storage
The current site sets no cookies. It uses no advertising identifiers, marketing pixels, analytics cookies, saved preferences, account tokens, or persistent tap storage. Necessary browser cache and history are controlled by browser and delivery layers and are not equivalent to site-authored cookies.
Read the cookie policy for the exact launch statement and change process.
Purposes and legal context
Local computation serves the visitor’s request to summarize deliberate taps. Ordinary hosting data supports delivery, security, and reliability. Support information is used to respond, correct content, handle rights and privacy matters, investigate security reports, and maintain appropriate records.
Privacy rights and legal bases vary by location and processing context. BPMCounter.click responds to applicable requests through support@bpmcounter.click and may ask only for information reasonably needed to understand or verify a request. This policy does not promise a right or remedy that does not apply to the requester.
Sharing
BPMCounter.click does not sell tap sequences because the product does not receive them. Ordinary records or correspondence may be handled by service providers supporting hosting and email, professional advisers, or authorities when required by valid law. Information may also be involved in a lawful business transaction with appropriate safeguards.
No sharing description expands the product into an audio, media, or session-storage service.
Security and retention
Browser-local computation limits collection but does not eliminate risk. Device malware, extensions, screenshots, shared computers, developer tools, and clipboard actions remain outside the site’s control. Use a trusted device and do not treat an active page as secure archival storage.
Retention for hosting and email follows provider and operational settings. The operator keeps information no longer than reasonably needed for the stated purpose, security, disputes, and legal duties. No fixed period is claimed where the relevant setting or obligation varies.
Your choices and requests
You can avoid entering taps, reset the active session, reload or close the tab, clear browser-controlled cache or history, and omit optional support information. Privacy, access, correction, deletion, restriction, or objection requests may be emailed to support@bpmcounter.click where applicable.
State the context and avoid sending excess identification. Some rights depend on jurisdiction and lawful exceptions.
International access and changes
The operator is in the USA, and the site may be accessed elsewhere. Providers may process ordinary hosting or email information in other locations under their terms and applicable law. Contact support@bpmcounter.click with a location-specific privacy question.
Material policy changes should receive a new effective date and clear public notice. A new storage, analytics, account, upload, or remote-processing feature cannot be covered by silent wording alone.
Frequently asked questions
Are my tap intervals uploaded?
No. Launch calculations stay in active browser memory.
Does no cookie mean no network request?
No. The host still receives ordinary requests needed to serve the page.
Can I request deletion of reset taps?
The operator cannot delete values it never received. A request may still concern email or hosting records.
Do privacy rights work the same everywhere?
No. Available rights, exceptions, and verification requirements depend on the law that applies to the request.
Make a privacy-conscious choice
Read the cookie boundary, use a non-sensitive pulse, avoid placing personal material in support mail, and reset or close the page when finished.