TapTempo.one
Scope
This TapTempo.one privacy policy covers the launch service operated by TapTempo.one, 30 N Gould St Ste R, Sheridan, WY 82801, USA. It is effective August 29, 2026 and applies to visitors aged 16 or older.
It distinguishes temporary tap timing, ordinary hosted-page requests, and information voluntarily sent by email.
Current-page timing
When a visitor activates the focused pulse surface, the page records a performance.now() timestamp in active memory. It derives neighboring gaps, a temporary rate, a recent median from up to eight intervals, and half/double candidates.
The launch product does not send these timestamps, gaps, values, tap count, or candidates to an API, account, database, analytics vendor, or cloud project. It does not store them in cookies, localStorage, or sessionStorage. Reset, a gap over three seconds, reload, closure, or browser conditions can erase them.
TapTempo.one cannot retrieve, export, synchronize, recover, or delete values it never receives.
No audio or external capture
The site requests no microphone, audio, files, camera, motion sensor, clipboard, media URL, or global keyboard access. Space and Enter create events only while the pulse area is focused. Pointer and touch operate only the visible surface.
The product does not identify songs, connect to third-party platforms, or analyze movement.
Hosting
Vercel receives ordinary network requests to deliver HTML, styles, scripts, and images. Infrastructure may process IP address, request time, path, status, user agent, referrer, and security information under actual production settings.
These records are not the tap sequence. Their retention and transfer depend on the provider’s current settings, contractual terms, security needs, and applicable law. Tap-derived values are not deliberately added to ordinary resource requests.
Support email
Emailing support@taptempo.one sends address, headers, message, attachments, and voluntarily included information to the operator and providers. Use synthetic gaps and omit audio, credentials, health data, movement histories, and unrelated personal information.
Correspondence may be retained as reasonably needed to respond, protect the service, maintain records, resolve disputes, and meet lawful obligations.
Cookies and storage
The launch site sets no cookies and uses no advertising identifier, marketing pixel, analytics cookie, account token, saved preference, or retained tempo history. Browser cache and history may store resources or visited routes under browser control; they are not site-authored tap storage.
The cookie policy gives the verification and future-change process.
Purpose and sharing
Local calculation fulfills the requested interaction. Hosting data supports delivery, reliability, abuse prevention, and security. Email supports service, corrections, privacy, accessibility, rights, and incident response.
Ordinary records or mail may be handled by hosting and email providers, professional advisers, transaction parties under safeguards, or authorities responding to valid law. The operator does not sell tap sequences because it does not receive them.
Security and retention
Local processing limits collection but cannot secure an untrusted device. Extensions, malware, screenshots, clipboard tools, shared-device monitoring, and developer tools may observe what appears locally.
Hosting and email retention depends on current provider settings, stated purposes, disputes, security needs, and applicable law. Visitors may ask about records associated with their support correspondence.
Choices and requests
Visitors can refrain from tapping, use Reset, reload, close the page, manage browser cache/history, and minimize email. Applicable requests for access, correction, deletion, restriction, or objection may be sent to support@taptempo.one.
State context and send no excessive identification. Rights and exceptions vary by jurisdiction.
Legal bases and sensitive contexts
Legal bases vary by jurisdiction. Site delivery and basic security may rely on providing the requested service or legitimate operational interests, while correspondence may be processed to answer the sender and meet legal obligations. No single basis or consent rule is asserted for every visitor and every location.
Do not use the pulse surface to encode names, medical events, employment observations, or another person’s behavior. Although the site does not receive the taps, the screen exists on the visitor’s device and could be observed by local software or people nearby. A neutral synthetic rhythm is the most privacy-preserving test.
Age and representative requests
The service is intended for people aged 16 or older. It is not directed to children and does not knowingly provide youth accounts because it provides no accounts at all. A parent, guardian, or authorized representative making a request should identify the capacity in which they act without sending unnecessary identity documents. The operator may need proportionate verification before disclosing or changing correspondence records.
International access and changes
The operator is in the USA and the service may be accessed elsewhere. Transfer and legal-basis language must be confirmed against actual providers and applicable law.
Before any future account, analytics, storage, synchronization, upload, or remote-processing feature becomes active, the operator must update this notice, document the changed data path, add suitable security controls, and obtain consent where applicable.
Frequently asked questions
Are taps uploaded?
No. Launch timing stays in current-page memory.
Does no cookie mean no web request?
No. Hosting still requires ordinary requests.
Can Reset erase support email?
No. Reset affects only product memory.
Can this page determine every privacy right?
No. Rights, exceptions, and request procedures depend on the visitor’s jurisdiction and the records actually held.
Use the minimal data path
Tap a non-sensitive pulse, avoid meaningful labels or mail attachments, use Reset when finished, and contact the operator only with necessary information.