Ownership
Wisp software and website
I retain the copyright to Wisp. No open-source license is granted. Viewing the source does not grant permission to copy, modify, distribute, sublicense, sell, or republish it unless the repository license permits that use or I expressly authorize it.
Official, unmodified Wisp binaries are provided for personal, non-commercial use under the terms distributed with the application repository.
Third parties
Game names and content
Forza Horizon, Xbox, Microsoft, Playground Games, Turn 10 Studios, their names, logos, game content, and related marks belong to their respective owners. Wisp is not affiliated with, sponsored by, or endorsed by those companies.
Wisp does not distribute Forza Horizon 6 or provide access to the game. A separately licensed Windows copy of Forza Horizon 6 is required.
The FH6 Data Out settings image in the setup walkthrough is derived from a capture published by ForzaLabs. The example port is marked as 5500.
Privacy
What Wisp processes
Application telemetry
Wisp receives standard driving data from FH6 Data Out on your PC and uses it to render the overlay and diagnostics. It does not send that telemetry to a Wisp-operated service.
Process-derived HUD state
On Windows PC, Wisp can query the local FH6 process read-only for exact redline, selected driver-assist states, native EV gauge ratios and gameplay visibility. It does not inject code into the game. Wisp uses these readings only when its compatibility checks pass. If those checks cannot validate the game, process-derived readings are unavailable and driving overlays remain hidden.
Saved settings
Appearance, startup, HUD position, setup choices, and learned tire-calibration profiles are stored for your Windows account so they remain available between sessions. Tire profiles are grouped by FH6 car identifier and stay on the local PC.
Saved runs
Runs records driving telemetry when you start a recording or enable automatic completed-lap saving. Saved run files, names, notes, markers, and analysis remain on your PC. Exporting creates a local run file, telemetry CSV, or graph image; Wisp does not upload it. Review names, notes, and recorded details before sharing a file.
Saved tunes and clips
Tune reads the current setup from the supported game process. Saved tuning values, names, descriptions and copies attached to runs stay on your PC.
Clips records only while you enable clipping. It captures the screen containing fullscreen Forza, including visible overlays and notifications. Game audio is recorded by default; optional system audio includes other apps and voice chat. Microphone input is not recorded. Saved clips stay in Wisp's local library, and export creates a copy in the folder you choose. Wisp does not upload the recordings.
Update checks
Optional automatic update checks contact GitHub whenever Wisp opens and every 24 hours while it remains running, including in the tray. You can turn them off in Extras or check manually. GitHub receives standard request metadata. Release details are shown before download confirmation, and installation is not automatic.
Compatibility updates
Wisp also downloads a signed compatibility map of supported game builds from wispoverlay.com shortly after it starts and normally every 24 hours while it runs, with earlier retries when a check fails or a build remains unsupported. This lookup is separate from update checks and runs even when automatic update checks are off; you can also run it on demand in Wisp. The request carries no driving data, and wispoverlay.com receives standard request metadata. Wisp checks the map's signature before using it.
Local error reports
Wisp keeps a short health history in memory and saves local error reports automatically. Reports include version and error information, a limited stack trace and recent app health measurements. After an unexpected exit, Wisp can read a matching Windows application-fault event. These reports are not automatically uploaded.
Automatic app health and usage reporting in 2.6.6
Wisp 2.6.6 automatically sends bounded app health and usage measurements to the private Wisp Tools service. Reporting includes Wisp and game versions, distribution platform, session and feature outcomes, connection health, timing distributions, Wisp process CPU and memory usage, and categorized failures. Failure reports can include sanitized error codes, selected Wisp method names and up to three preceding app health observations. They do not include exception messages or arbitrary stack traces. A randomly generated installation identifier links Wisp sessions on the same installation. It is separate from your saved profiles and is not an account or hardware identifier. Automatic reporting has no in-app opt-out.
Driving packets, individual gauge values, car setups, runs, clips, audio, screenshots, account names, hardware identifiers, personal file paths and raw diagnostic logs are not part of this reporting. Client and deliberately submitted support details expire after 30 days, subject to earlier storage limits. Download totals and their historical snapshots are retained separately. You can preview a support submission before sending it.
The service uses Cloudflare for request delivery, protection and storage. Cloudflare necessarily receives standard network request metadata. Wisp Tools does not store visitor IP addresses or user-agent strings in its app analytics database. Collection is bounded and can be unavailable during outages; it does not replace every local diagnostic or measure the frames physically displayed on your monitor.
Optional local diagnostic logs
Debug logging is opt-in and records bounded local measurements of telemetry reception, UI processing, native HUD data, rendering activity, focus changes, and Wisp's CPU and memory usage. Collection stops after 24 hours per activation. Wisp removes diagnostic log segments older than seven days during local cleanup. These measurements describe Wisp's telemetry processing and rendering. Exported reports stay on your PC until you choose to share them. Review a report before uploading it to a public issue.
Website requests
Hosting and security providers process standard request information to deliver and protect the website.
Cookies and analytics
Wisp uses Cloudflare Web Analytics to understand page visits and loading performance, and Google Search Console for search visibility. Cloudflare Web Analytics uses no tracking cookies. Cloudflare may use an operational cookie for site security.