Tap Tempo Privacy in the Current Page

Reviewed concrete example

What remains local

Tap tempo privacy begins with the accepted event. A focused pointer, touch, Space, or Enter action creates a performance.now() timestamp in current-page JavaScript memory. Neighboring gaps, recent median, candidates, and count are calculated there.

The current site sends none of those values to a product API, database, account, analytics vendor, or saved project.

Focused, not global

Keyboard events count only while the pulse disc owns focus. The page cannot observe keys in another app, tab, or unfocused region. It does not capture characters, microphone, audio, camera, motion sensors, files, clipboard, URLs, devices, or third-party accounts.

Pointer and touch timing is limited to the visible surface.

Ephemeral state

Reset clears the sequence. A gap over three seconds starts a new one. Reload, closure, or browser conditions can remove current values. No localStorage, sessionStorage, cookie, or account history restores them.

If a BPM matters, copy only the minimal non-sensitive number and pulse label into an approved system.

Ordinary requests

Loading TapTempo.one still contacts Vercel for page resources. Infrastructure may process IP address, time, path, status, user agent, referrer, and security details. “Local taps” does not mean “no web traffic.”

Tap values must never be placed in URLs, metadata, JSON-LD, analytics events, or network payloads.

Browser and device traces

Cache can retain assets and history can record a visited route. Extensions, screenshots, clipboard managers, shared-device tools, developer consoles, or malware may observe local content. Site architecture cannot make an untrusted device private.

Use a trusted environment and clear browser-controlled traces according to local policy.

Support email

Mail to support@taptempo.one leaves the local interaction boundary. Send synthetic timing and omit media, health data, routines, locations, show details, unpublished projects, credentials, and unrelated identifiers.

Reset cannot erase an email or hosting record.

Verification exercise

Open a clean browser profile. Inspect Network, Cookies, Local Storage, and Session Storage. Make four synthetic taps, Reset, and reload. Expected: ordinary resource requests, no tap values in requests, no site-authored storage, and no restored sequence.

Record the browser and observation date. Repeat after dependency or hosting changes. Direct inspection, not policy language alone, establishes actual behavior.

Shared-device workflow

Use generic input, avoid support mail, press Reset, close the tab, and follow organizational clearing rules. These steps reduce visible remnants but cannot override administrator logging or extensions.

Future features

Accounts, analytics, persistent preferences, synchronization, uploads, or remote processing are not part of the current site. Adding any requires revised notice, a documented purpose, suitable security controls, and consent where applicable.

Limits

This guide explains product data flow, not anonymity, device security, or legal advice. Hosting retention and international transfers depend on current provider settings and applicable law.

Follow one synthetic event through the page

Begin with an invented pulse rather than confidential media. The first activation creates one monotonic timestamp in memory. A second adds another timestamp and permits one interval. Later accepted actions add recent intervals until the bounded calculation has enough input for its main state. The screen renders count and candidates from that temporary state. None of these steps requires a name, email address, source title, or user profile.

Press Reset and inspect again. The visible values and in-memory sequence should clear. This is different from deleting browser history, cached assets, hosting logs, or a message previously sent to support. Each layer has its own controller and retention behavior.

Shared classroom scenario

A teacher demonstrates the tool on a shared display using a made-up desk-tap rhythm. Students can see the result without entering accounts or uploading a recording. After the demonstration, the teacher resets and closes the tab according to the institution’s device policy. No student names or performance judgments are recorded.

If the lesson requires saving an observation, use an approved classroom system and store only the necessary, non-sensitive wording. TapTempo.one does not provide a save function and should not be treated as a record system.

What a network inspection should distinguish

Resource requests for HTML, styles, scripts, fonts, or images are ordinary website traffic. A privacy check asks whether tap-derived timestamps, intervals, counts, or BPM values appear in request URLs, bodies, headers, beacons, or third-party events. It also checks whether browser storage restores a sequence after reload.

An empty product-storage panel does not mean the host has no operational records. Conversely, an infrastructure request does not show that tap values were uploaded. Inspect evidence carefully and document the observation date and tested site version before drawing a conclusion.

Safer support reporting

When reporting unexpected persistence, reproduce it with synthetic taps. State the route, browser, steps, observed storage key or request field, and time. Redact IP addresses, tokens, unrelated cookies, file names, and account details from screenshots. Support can investigate a reproducible technical symptom without receiving the original music, movement, project, or identity context.

If a report concerns a general policy question rather than a defect, consult the dedicated privacy and cookie pages. This guide explains the tap interaction at a practical level and does not replace those formal notices.

Frequently asked questions

Use synthetic taps, observe storage and requests, Reset and reload, then report any unexpected persistence with minimal non-sensitive evidence.