Data used for core site operation
The pages are static and do not ask for an account, payment information, newsletter address, or form submission. The site does not store an analytics preference because it has no analytics choice interface.
The hosting provider must still process ordinary web requests and may maintain operational or security logs such as IP address, requested URL, timestamp, user agent, and error information under its own policies.
- Account dataNot collected by this site
- Payment dataNot collected by this site
- Analytics preferenceNot stored by the current build
- Hosting requestsProcessed by the hosting provider
Analytics runtime states
The site supports only two GA4 runtime states: direct or disabled. Disabled emits no Google loader, configuration, request, or analytics choice UI. Direct is used only when a valid measurement ID is deliberately supplied to the build and may send page, device, and outbound-link measurements to Google.
Microsoft Clarity is also omitted when no project ID is configured. If either provider is enabled for a future release, the operator must review the target-market decision, the provider behavior, and this privacy notice before publishing that build.
- Exact build stateReported in the direct briefing above
- Disabled stateNo provider loader, request, or choice UI
- Direct stateLoads only from an explicitly supplied valid ID
- Provider policiesGoogle or Microsoft controls its own processing
Browser storage and controls
This guide does not create an analytics-consent value in local storage and does not present a cookie or privacy-settings toggle. Ordinary browser cache, hosting behavior, and third-party destinations can still operate under their own controls.
Visitors can use browser privacy settings, tracker protection, or provider controls. A future direct-analytics release would not add an on-site opt-in toggle; if direct loading is unsuitable for the target market, analytics must remain disabled.
- On-site analytics toggleNot present
- Analytics choice storageNot created
- Browser controlsAvailable through the visitor's browser
- Third-party controlsUse Google, Microsoft, or browser privacy tools
Outbound links and policy updates
Links to Steam, the Steam Community, GitHub, or other external services leave this site. Those services receive requests directly and apply their own privacy, cookie, and account policies.
This notice reflects the local site behavior checked on August 27, 2026. If provider configuration or data flow changes, this notice must be updated before the new build is released.
- External servicesApply their own privacy policies
- Policy effective checkAugust 27, 2026
- Site owner contactUse the corrections route on the contact page
- Game publisher dataNot controlled by this unofficial site
Frequently asked questions
Does this site use analytics?
The exact state for this build is reported in the direct briefing above. Disabled means no provider loader or request; direct means a valid configured provider loads without an on-site choice UI.
Does the site store an analytics choice?
No. The current runtime has no analytics choice banner, toggle, or analytics-specific local-storage value.
What changes if analytics is enabled later?
A valid explicitly supplied provider ID would load analytics directly. The privacy decision and this notice must be reviewed before that build is released.
Does this site collect payment or Steam account data?
No. It has no checkout or Steam login. Following an external Steam link takes you to Steam, where Valve's own policies apply.