Back to Field of Banners

Privacy and analytics

This game can collect a small, pseudonymous set of product-analytics events to understand whether visitors can discover, start, finish and play another battle. Collection is output-only and is never used to change the simulation.

What is collected

Provider

PostHog Cloud, hosted in the United States, when the site has been configured with its public project key.

Identity and storage

PostHog supplies a pseudonymous browser identifier and session identifier. The SDK uses local storage to keep that identity across ordinary visits. Clearing storage, private windows and different devices create separate identities.

Events

We send game arrival, actual battle start, accepted battle finish and actual play-again milestones, plus a bounded set of diagnostic actions. We do not send room or join tokens, replay blobs, order paths, URL fragments or full URLs.

Session replay

When explicitly enabled in deployment configuration, eligible production sessions may be recorded at a starting rate of 2 frames per second and reduced canvas quality. DOM inputs and text are masked. Canvas frames containing PvP room information are omitted, and network headers, bodies and console logs are disabled. Recordings are for private product diagnosis and are not public media.

Purpose and access

The owner and explicitly authorized operators use this information to diagnose discovery and play-flow problems. We do not sell it or use it for advertising. PostHog's own processing and retention are governed by the configured project and current provider terms.

Your choices

Collection is disabled when the site has no public PostHog key. If you want to opt out, use this control before returning to the game. It stores only the opt-out preference in this browser; it does not contact PostHog.

Opt out of analytics on this browser

To request access or deletion of data associated with this pseudonymous browser, contact the Field of Banners owner through the channel where you received this site link and include the approximate visit time and browser storage identifier if available. Do not send passwords, room tokens or replay links in that request.

Deployment configuration

The public key and US host are supplied at build time through VITE_POSTHOG_KEY and VITE_POSTHOG_HOST. Recording is an independent opt-in build setting, VITE_POSTHOG_RECORDING. No personal API key is shipped to browsers.