Data Collection

Xarmo uses limited analytics, delivery, security and advertising services to operate and improve the website.

Current services

Google Analytics: production-only measurement of page and game usage.
Google AdSense: production-only account verification, consent messaging and advertising code. Ad serving depends on Google approval, provider configuration and applicable consent choices.
Cloudflare Web Analytics: operational website measurement.
Cloudflare delivery and security: request and network information needed to serve and protect the website.

Typical data categories

These services may process page paths, approximate location, browser and device information, referring pages, visit timing, technical network information, advertising identifiers, cookies or local storage, consent selections and advertisement interactions. Exact fields depend on provider configuration, browser settings and applicable consent controls.

Advertising data

Google AdSense may process information needed to select, deliver, measure and protect advertisements. Advertising may be personalised, non-personalised or limited depending on region, consent and account configuration. Xarmo does not receive a complete copy of all information processed within Google's advertising systems.

Consent controls

Where applicable, advertising and analytics storage will be governed by consent or privacy choices supplied through the configured provider message. Refusing optional advertising purposes may change the type of advertising shown or prevent some advertising features from operating.

Game data

The games run primarily in the browser. Xarmo does not currently maintain public accounts, cloud saves or user profiles. The site does not intentionally send command text, player names entered into games, detailed keystrokes or complete game-board state to analytics or advertising providers.

Purpose-limited product events

Product analytics may include bounded events such as game page views, engagement-session starts and ends, coarse engagement duration and control type, plus game-specific completions, restarts or failures where those events are explicitly implemented. The shared engagement measurement records only the broad control category such as keyboard or touch; it does not send the actual key pressed, pointer coordinates, command text or board state. Event names and parameters are restricted by the shared analytics helper.

What will not be collected by default

authentication tokens or passwords;
payment-card data;
every mouse movement or keystroke;
private messages;
unbounded or intentionally sensitive metadata.