Milkman Games
Feedback privacy
This notice explains what the game feedback feature collects and how submitted reports are handled.
What stays in your browser
While a game is running, recent game diagnostics are held in browser memory for up to 60 seconds. The buffer is bounded to 100 entries and 64 KiB. It can include game state such as position, speed, commands, sensor status, and recent events. It does not record keystrokes or content from other apps. This buffer is not sent continuously; it is attached to a report when one is sent.
Reports sent by the game
The game may send an automatic report after a runtime error, graphics context loss, or a serious performance interruption. These reports do not ask first and may include an error message, stack trace, game and build identifiers, and recent game diagnostics. The client limits automatic reports to three per feedback session, applies a cooldown, and suppresses duplicates.
You can also open the feedback form to send a report yourself. You choose the text. A game screenshot is optional and is captured only if you select the screenshot option; it shows the game view, not your desktop. Recent game diagnostics and the game and build identifiers are included with submitted reports.
Verification and service storage
Before a public report can be submitted, the browser requests an invisible verification token from Cloudflare Turnstile. Cloudflare may process network and browser information, including your IP address, to provide that check. After verification, Vibecade sets a signed, secure, HttpOnly, same-site cookie for up to four hours to limit abuse. The service uses an HMAC-derived IP identifier for quotas; raw IP addresses are not kept in report records.
Reports are stored in a private, access-controlled inbox for project administration. Pending reports remain there until the maintainer marks them tracked; the inbox rejects new reports if its storage limit is reached. Tracked reports are deleted 30 days after tracking. Maintainers may export reports needed for follow-up; exported copies are managed separately from the inbox.
Reports submitted after GitHub delivery is enabled may also be summarized in issues in the private GitHub repository for Milkman Games, where repository contributors can read them. A private GitHub Actions artifact linked from the issue contains the report JSON, logs, and, if you attached one, the screenshot. These artifacts are kept for seven days, after which their download links expire. This artifact retention is separate from the inbox: the inbox keeps the original report and screenshot under the service retention described above.
Report content is untrusted data. It is handled as feedback and diagnostics, not as instructions to run code or create automated tasks.
Reports are reviewed by the project maintainers. Submitting feedback does not create a public post, a local game ticket, or an automated agent task.
Local development builds
Some local Jet builds route manually submitted feedback and diagnostics to ticket and log files on the machine running the game. Those local files are managed by that developer and are outside the public inbox retention described above.