Test data & local saves
Last updated: October 3, 2026.
Your character save
The Early Public Test stores the Wanderer locally in your browser on your device. Fornward does not currently provide a cloud account or cloud save for this test. You can export a local backup from the in-game SAVE panel. Planned test-character wipes may happen while progression, skills and gear foundations change. Exported test saves are useful recovery copies, not a promise of perpetual future compatibility.
What the test sends
The public test sends a deliberately small set of technical journey events: startup, local save state, ready, expedition start, first room clear, first run end and fatal startup/runtime. Each event includes the build identity, page path and elapsed time. Save state is only fresh, loaded, repaired, blocked or unavailable; it never contains the save itself. A run-end event includes only the outcome; a fatal event includes only a coarse error type.
These events do not include your character save, inventory, detailed combat/debug journal, account identity, cookie, browser fingerprint, persistent player ID or URL query string.
Hosting and normal request data
The site is hosted using Vercel. Like ordinary web hosting, the hosting provider processes network request information needed to serve and operate the site, which can include IP address and technical request data. Fornward's own Early Public Test event payload does not add IP address, user-agent, cookies or request headers to its event log line. These events are reviewed in the hosting provider's operational function logs; this test does not add a separate analytics database. Log retention follows the hosting account's current configuration.
Why
The purpose is to tell whether a candidate starts, can read or safely refuse the local save, becomes playable, reaches the intended first loop and suffers fatal startup/runtime failures. The detailed local gameplay telemetry used during development is not transmitted as the public-test measurement stream.