Data boundaries
Privacy
Participant names and completed race history stay in your browser by default. Duck Rush ships with no account system, name-upload API, remote name database, or configured analytics destination. The public automatic-only build does not request microphone access.
Local by default: names and race history
Names are processed in browser memory while you configure and run a race. The current code has no built-in account, name-upload endpoint, or remote name database. After a race completes, Duck Rush stores up to 10 recent records in localStorage. A record can include the names, assigned colors, finishing order and times, date, course, course seed, race seed, and draw ID.
Use Draw history → Clear local history to remove completed race records. Clearing site data in browser settings also removes them. Unfinished configuration is not saved as race history.
No microphone or outcome controls
The public build is automatic-only. It does not render microphone controls, request microphone permission, or register keyboard input that can steer a duck. Overview and follow controls only change the camera.
Clipboard, sound, and model assets
Duck Rush writes the finishing order to the clipboard only when you choose Copy results. Sound is generated by the application and starts muted. The shipped 3D model files are requested from the same site after the playable scene starts; no third-party font or model CDN is required.
Diagnostics and observability
The current application writes Debug, Info, Warn, and Error messages to the browser console for loading, race-state, recoverable storage problems, and failures. A small observability adapter records page language, course, game load, aggregate entry count, completion time, Web Vitals, and asset failures. It is designed not to include participant names, copied results, or an unfiltered URL/query.
No remote analytics destination is configured in this repository. A production operator can connect the adapter later; if that changes what is collected or where it is sent, this page must be updated before deployment.
Hosting and future services
The eventual hosting provider may process IP addresses, request headers, security logs, and other standard delivery data. The production domain and hosting provider have not yet been selected, so their retention and contact details cannot be stated here. Search Console is also not connected yet.
This notice must be completed with the operator identity, contact method, hosting details, applicable retention, and any analytics consent requirements before public launch.
URL parameters
track and seed describe course state. Duck Rush does not put participant names into URLs. Avoid manually adding personal data to a URL because URLs can appear in browser history, server logs, and shared links.