Last updated: July 29, 2026.
When camera access begins
The browser requests camera permission only after you press Start with camera. Gesture Synth does not request the camera during initial page load. You can decline permission and use Mouse Mode, touch pads, or number keys instead.
What happens to camera frames
Camera frames are read by the MediaPipe Hand Landmarker model running in the browser. The model returns hand landmark coordinates used to estimate finger count and hand height. Those frames and coordinates are not sent to a Gesture Synth application server. Closing the page or pressing Stop camera ends the active media tracks.
The hand-tracking runtime and model files are downloaded from their public package/model hosts when camera mode starts. Fetching these software files is not a video upload; camera frame data is not attached to those requests.
Local recording and downloads
During a chord challenge, supported browsers can combine the visible stage canvas and generated Web Audio into a WebM recording. The recording is assembled in browser memory. It becomes a file only when you download it. Gesture Synth does not automatically upload or retain that WebM.
MIDI export contains note numbers, start times, durations, and velocity values derived from the played chords. It does not contain video, audio, images, biometric templates, or raw hand landmarks.
Data the core tool does not collect
- Camera frames or camera recordings
- Microphone audio
- Raw or historical hand landmark coordinates
- Face data or identity information
- Account credentials
- Downloaded WebM or MIDI files
Operational analytics
This build creates internal events for starts, completions, errors, and downloads. No third-party analytics endpoint is configured, so those events do not leave the page. If analytics is added later, this page must first name the provider, retention period, consent behavior, and exact event fields.
Your controls
Deny camera permission, switch to Mouse Mode, stop the camera, close the tab, or revoke site permission in browser settings at any time. Downloads remain under your device and browser controls. Clearing site data removes any future preferences stored locally by the site.
External services required by the page
The production page may request font files, the MediaPipe WebAssembly runtime, and the hand landmark model from their public hosts. Standard network metadata such as IP address and user agent can be visible to those hosts under their own policies. Self-hosting the assets would remove those runtime requests.
Questions or problem reports
Use the contact page to report unexpected camera behavior, a privacy concern, or a browser-specific recording problem. Include the browser and operating system, but do not attach a camera recording unless you intentionally choose to share one.