Wild Hand WorksAPPLIES TO EVERY WILD HAND WORKS PRODUCT
General policy
We collect only what a product needs. A product-specific card below explains exactly what that means for each app and takes priority if its details differ from this shared policy.
Who is responsible
Wild Hand Works is responsible for the data practices described here. Privacy questions and requests can be sent using the contact link below.
What we collect and why
Each app card states the categories of data it processes, where the data comes from, why it is needed, the legal basis where applicable, and whether anyone else receives it. If a card says “none,” the app does not collect personal data.
Sharing, sale and tracking
We do not sell personal data or use it for cross-context behavioral advertising. Any service provider, disclosure, or off-device transfer required by an app will be named in that app’s card.
Retention and security
Data is kept only for the period stated in the relevant app card or as required by law, then deleted or anonymized. We use reasonable safeguards appropriate to the data, but no system can promise absolute security.
Your choices and rights
Depending on where you live, you may ask to access, correct, delete, or receive your personal data; object to or restrict certain processing; withdraw consent; appeal a decision; or complain to your local data-protection authority. We may need to verify a request and may retain information where the law permits or requires it. We will not discriminate against you for exercising a privacy right.
Children and international transfers
Our products are not directed to children under 13, and we do not knowingly collect their personal data. If data is processed outside your country, the relevant app card will identify the transfer and safeguards used.
Changes
We update this page before materially changing a released product’s data practices and revise the effective date. Earlier versions can be requested from us.
APPENDIX 01 / THIS WEBSITE
This website
What the site does
This website does not set cookies, run advertising or analytics scripts, create accounts, or collect information through forms. You can contact us directly by email.
Hosting records
Like any website host, our infrastructure provider may process technical request data—such as IP address, time, requested URL, and browser information—to deliver and secure the site. We do not use those records to profile visitors. The provider controls its operational retention period.
Support requests
If you email us, we receive your email address, message, and anything you attach directly from you. Our email provider may process that information for us. We use it to answer your request on the basis of your request and our legitimate interest in providing support. We retain support correspondence for up to 12 months after the request is closed, unless a longer period is required for security, disputes, or legal obligations.
APPENDIX 02 / CURSOR TOOLS
Cursor Tools
No personal data collection
Cursor Tools does not collect, transmit, sell, rent, or share personal data. It has no accounts, analytics, advertising, tracking, cloud storage, or network requests.
Screen Recording permission
Color Lens and Magnifier use the macOS Screen Recording permission to read pixels under the pointer while either tool is active. Processing happens locally in memory. The app does not create recordings, screenshots, or files from the screen stream.
Settings and clipboard
Enabled tools, shortcuts, interaction mode, magnifier scale, language, and color-copy preferences are stored locally in macOS user defaults. If you enable copy on release, the chosen color value is written to the system clipboard; Cursor Tools does not retain a separate copy.
Logs and deletion
Technical lifecycle and ScreenCaptureKit errors may be written to Apple’s unified system log, whose retention is controlled by macOS. Preferences remain until changed or the app’s local data is cleared; the current app has no full-reset button.
APPENDIX 03 / WORLD CAPTIONS
World Captions
Microphone and system audio
World Captions uses microphone access to classify nearby sounds. If you enable system-audio analysis, it also analyzes the Mac’s overall outgoing audio. It does not capture screen images or video.
What is processed
Live PCM audio, acoustic features, classification confidence, detected sound type, time, repeat count, and technical identifiers for available input devices are processed in memory. Speech is treated only as a sound category; words, names, and conversation content are not transcribed.
Local-only operation
Audio is analyzed on the Mac using Apple system frameworks. The app creates no audio files and has no network requests, accounts, cloud backend, analytics, advertising, tracking, third-party SDKs, or app-operated crash reporting.
Retention and deletion
Audio buffers and acoustic features remain temporarily in memory. Visible events disappear after the chosen display time—five seconds by default—and all event data disappears when the app exits. Preferences remain in macOS user defaults until the app’s local data is cleared; there is currently no full-reset button.
APPENDIX 04 / FORCE TOUCH LAB
Force Touch Lab
Permissions
Accessibility access is required to observe the global mouse lifecycle, suppress the original Force Click, and send the chosen shortcut to the active app. Input Monitoring availability is checked, and optional Launch at Login is managed by macOS.
Transient input
Pressure, finger count and position, contact size, cursor position, mouse state, modifier flags, event types, and the active app’s bundle identifier are processed in memory. The app does not read documents, screen contents, clipboard contents, typed text, or browser history.
Saved settings
Language, haptics, enabled profiles, custom action labels and icons, shortcuts, selected-app bundle identifiers, names, and local paths are stored in the app’s local preferences. Custom profiles can be deleted and built-in actions can be reset.
No off-device transfer
The app has no network requests, backend, cloud sync, accounts, analytics, advertising, tracking, third-party SDKs, or app-operated crash reporting. Diagnostics are held briefly in memory and may also enter Apple’s unified system log, whose retention is controlled by macOS.
APPENDIX 05 / FUN CURSOR
FunCursor
Pointer activity
Mouse coordinates, button state, movement and click events, short-lived trails, idle timing, active-app process identifier, fullscreen state, cursor visibility, and display geometry are used locally to animate the companion. Keyboard content and key codes are not read.
Saved preferences
Character choice, size, opacity, position, behavior, click effects, custom emoji, onboarding state, and optional launch-at-login choice are stored locally. No history of pointer coordinates is written to disk.
Retention
Behavioral state and trails remain in memory for fractions of a second and disappear when the process ends. Preferences remain until changed or the app container is cleared. The current reset control does not erase every preference.
No off-device transfer
No network requests, server, cloud sync, account, analytics SDK, app-operated crash reporting, advertising, tracking, or third-party runtime dependency was found. Technical messages may be retained in Apple’s system log under macOS rules.
APPENDIX 06 / DREAMLINE
DREAMLINE
Body and head controls
Camera access is used to estimate shoulder, head, and hand positions. Motion access is used for head gestures with compatible AirPods. Video frames, preview frames, pose points, confidence values, and headphone orientation are processed for controls.
No recordings
The current code does not save camera video or motion streams to files. Current calibration and preview data stay in memory while the related control mode is active.
Progress and diagnostics
Scores, statistics, crystal balance, character and upgrade purchases, and settings are stored locally without an automatic expiry. Debug builds may print pose coordinates to process output; release diagnostics will be reviewed before distribution.
No off-device transfer
The current build has no network service, cloud account, analytics, advertising, tracking, third-party SDK, or app-operated crash reporting. System diagnostics are controlled separately by macOS.
APPENDIX 07 / STARSTACKING
StarStacking
User-selected files
The app reads RAW images chosen through the macOS open panel and writes TIFF exports only to a destination chosen through the save panel. Source files are opened read-only and are not modified.
Local image processing
Pixels, file paths and names, camera and lens metadata, capture settings, processing choices, alignment values, frame weights, and noise estimates are processed locally. There are no accounts, analytics, advertising, tracking, cloud transfers, network requests, or third-party network services.
Temporary and exported data
Processing creates temporary folders containing intermediate TIFFs, JPEG previews, and a report. The prototype does not yet delete these folders automatically; they remain until macOS or the user removes them. Exported TIFFs remain wherever the user saved them.
Local libraries
Python, rawpy/LibRaw, NumPy, Pillow, and tifffile run locally as processing components. They do not receive files as online services. This statement will be rechecked after final application packaging.
APPENDIX 08 / GAZE STUDIO
Gaze Studio
Camera analysis
Camera frames, face and eye geometry, pupil position, Vision confidence, approximate orientation, calculated gaze coordinates, trails, and heatmaps are processed in memory to create the visualization. Camera frames are intentionally not saved.
Local OBS connection
If OBS output is enabled, Gaze Studio runs an HTTP/SSE server bound to 127.0.0.1:47777. It sends normalized coordinates, tracking visibility, visual settings, and clear commands to a browser source on the same Mac. It does not send camera frames, audio, screen contents, user name, or app list.
Saved settings
Calibration coefficients and date, validation error, overlay choices, color, size, opacity, trail, and heatmap settings are stored locally. Reset removes calibration and its validation error; a single control to erase every preference is not yet available.
No external service
The app has no cloud backend, external network request, account, analytics, advertising, tracking, third-party runtime SDK, or app-operated crash reporting. OBS is a local recipient chosen by the user.
APPENDIX 09 / МЕХ
МЕХ
TECHNICAL PREVIEW — PRIVACY REVIEW IN PROGRESSThis card reports only behavior verified in the reviewed prototype. A complete source audit is required before public release.
Verified input handling
Lid angle and measurement time are read through IOKit/IOHID to calculate bellows speed, direction, and pressure. Game-key events are monitored locally inside the app, and trackpad scroll amount can simulate the bellows. Microphone recording was not found in the reviewed files.
Saved settings
Selected language and the bellows-noise preference are stored in macOS user defaults. Active notes, held keys, current lesson, and lesson position were found only in the live model. No full data-reset control was identified.
Local sound resources
The app plays bundled accordion samples, including the CC0 FreePats Button Accordion HN sound bank, and may use a procedural fallback synthesizer. The sound bank is a local resource, not a connected service.
What remains to verify
The currently reviewed interactions appear local, but a complete audit has not yet confirmed the presence or absence of every network call, diagnostic path, or system permission. This policy will be finalized before distribution.
APPENDIX 10 / ECHOSPACE
EchoSpace
Acoustic measurements
EchoSpace records a short microphone response when the user starts a measurement or tracker. Raw samples may contain surrounding speech and other sounds. The app does not recognize speech or identify people.
Processed information
Audio samples, correlation, delays, peaks, approximate distances, signal levels, clipping, change history, calibration, Mac model, OS version, and audio-device names, identifiers, channels, and sample rates are processed locally. Device names may include an owner-provided name.
Exports
Measurements remain in memory unless the user exports them. A single-measurement JSON export includes raw audio as numeric arrays; tracker exports contain derived measurements without raw audio. Exported files remain at the chosen location, including any cloud-synced folder, until the user deletes them.
Retention and transfer
Tracker history is capped at 1,200 frames and is cleared when a new tracker session begins. Data in memory disappears when the process ends. The current app has no network requests, cloud backend, accounts, analytics, advertising, tracking, third-party SDKs, or app-operated crash reporting.
APPENDIX 11 / TF2 LAUNCHER — WORKING NAME
TF2 Launcher
Local environment
The launcher checks macOS version, architecture, Rosetta availability, and free space. It reads local Steam manifests, remembers the selected game and display mode, and stores Wine, Steam, games, downloads, and session logs under Application Support/TF2Launcher.
Downloads and third parties
The launcher connects to Sikarugir GitHub Releases for Wine components and to Akamai’s Steam CDN for the official Windows Steam installer. Windows Steam then connects to Valve, Steam APIs, VAC, and selected game servers. Those services receive ordinary network data such as IP address and govern their own retention.
Steam account and logs
Steam authentication happens inside the official Windows Steam client; the launcher does not read or transmit the Steam password. Local logs may contain technical Steam or game output, identifiers, and file paths. Logs are not analyzed or uploaded by Wild Hand Works and currently have no automatic rotation.
No studio tracking
The launcher has no Wild Hand Works account, backend, cloud sync, analytics, telemetry, advertising, tracking, donation service, or automatic log upload. Steam and game services are independent third parties selected by the user’s installation and play choices.
Deletion
Deleting the app alone does not remove Wine, Steam, games, logs, or preferences. To remove them, delete ~/Library/Application Support/TF2Launcher and the preferences for dev.tf2launcher.prototype, then remove the app. A one-click deletion control is not yet available.