Ownership
Wisp software and website
Copyright remains with the Wisp project owner. 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 or the copyright holder expressly permits that use.
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. Wisp independently marks the example port 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 supported Steam and Xbox app / Microsoft Store builds for 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. Steam uses an executable fingerprint; Store uses package identity and bounded checks of the loaded executable. It does not inject code into the game. Unrecognized builds disable process-derived state and keep driving overlays hidden rather than reuse another build's data.
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.
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.
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, and files are retained for no more than seven days. Reports do not measure game FPS or GPU presentation latency. Exported reports stay on your PC until you choose to share them. Review a report before uploading it to a public issue.
Website requests
The website serves static files. Its hosting and security providers may process standard request metadata, including an IP address, request path, user agent, and timestamp, to deliver and protect the site. Wisp does not add application analytics or advertising trackers.
Cookies and analytics
The website does not set cookies or include analytics or advertising. Cloudflare may set an operational cookie when required by its security controls. This notice will be updated if the website's collection or tracking changes.