HOOD WARFAREHood Warfare privacy policy
This policy describes the data used by this browser game. Last updated October 15, 2026.
Anonymous play and essential session storage
You can play without creating an account or supplying an email address. Online play uses an HttpOnly session cookie called hw_session, lasting up to 30 days, to recognize the browser joining a room and protect host actions. The cookie is an essential game session credential. Its value is not displayed publicly. A separate HttpOnly hw_visit cookie groups activity into a visit and expires after 30 minutes of inactivity. The site automatically associates limited usage events with a one-way identifier derived from the game cookie. Clearing site data creates a new identity and can remove your ability to manage earlier rooms or scores.
Local settings and practice history
Your chosen display name, character appearance, and recent local practice results may be saved in local storage in this browser. Closing an update announcement also saves its ID and the local calendar date in this browser and against your anonymous player identity in Cloudflare D1, so that update stays closed for the rest of the day. Announcement display and dismissal records are retained for up to 90 days. Browser data does not automatically synchronize across devices. You can remove local data using your browser’s site-data settings.
Online rooms and public results
Your display name, character, team, and match performance are visible to other players in your room. Avoid using a real name or other personal information as your alias. The server processes movement and action inputs to run online matches. Cloudflare D1 stores rooms, queue attempts, match status and timestamps, and each participant’s alias, one-way browser identifier, team, character, kills, deaths, captures, objective time, score, weapon totals, and connection history. Leaving or interrupted matches are also recorded. Online combat statistics are calculated by the server. Local practice records only start, completion, or exit events on the server; it does not submit practice scores. Public and solo result totals can be shown on leaderboards. Custom matches are excluded from those leaderboards. Match summaries are stored privately in Cloudflare R2.
Weapon and skin progression
D1 stores reputation rewards, weapon kill challenge results, daily UTC check-in claims, and equipped guns and skins under your anonymous browser identity. Eligible match rewards are calculated by the server and recorded once per match. The reward ledger, check-in claims and saved loadout are retained to preserve progression, separately from the normal analytics retention periods. Detailed armory action events are retained for up to 90 days. There is no Google or Steam account connection. Clearing cookies prevents automatic access to the earlier identity; it does not itself erase its server records. Rewards may be corrected or removed for invalid matches, abuse, service operation, or a valid privacy deletion request.
Site and game analytics
The site automatically records limited page and game events, including the route name, device category, mode, lobby visits, queue starts, match starts and endings, and connection errors. An event ID prevents duplicate records. Events are linked to pseudonymous browser and visit records so we can understand repeat visits, sources, loading failures, queue waits, and match completion. Visit records include a coarse country code, device and browser family, language, landing route, referring hostname, and allowlisted campaign labels. We measure visible page time with periodic heartbeats. During matches we also collect sampled foreground frame times, slow-frame counts, network round-trip latency, snapshot gaps, and foreground/background transitions to diagnose performance. Missing measurements stay unknown; background pauses are recorded separately. These diagnostic records are retained for up to 90 days. Event records do not include aliases, raw session cookies, keystrokes, message content, IP addresses, full URLs, invite codes, or browsing activity on other sites. There is no advertising or session-replay tracker in this release. Analytics failures do not block play.
Google Analytics
We use a dedicated Google Analytics 4 property to automatically measure page visits and game events. Google Analytics can use first-party _ga cookies to distinguish browsers and sessions; these cookies are configured to expire after up to 90 days without extending their expiry on each visit. We send the route without query strings, the page title, mode, and event name; we do not send aliases, game session cookies, or invite codes. Google signals and advertising personalization are disabled. Google processes network and device information under its own policies. You can clear site cookies, block the Google Analytics tag in your browser, or use Google’s Analytics opt-out tools. These measurements support game operation and improvement.
Hosting and security
Cloudflare processes network information such as IP addresses, request headers, and diagnostic logs to deliver and secure the service under its own policies. This operational processing is separate from the minimal event records described above. We use collected game information to operate matches, troubleshoot failures, and improve the service. We do not sell player information.
Retention and your choices
Detailed site events, visits, and practice lifecycle records in Cloudflare D1 are retained for up to 90 days. Match participation, queues, combat events, and weapon totals are normally retained for up to one year. Inactive browser profiles are removed after one year when no retained records depend on them. Google Analytics data is processed and retained separately under the property’s data settings and Google’s policies. Completed match summaries and score records are normally retained for up to one year, unless removed earlier to operate or improve the service. Clearing browser storage removes local data, but does not by itself delete server-side results. For access, correction, or deletion requests, contact lijing123lll@gmail.com and describe the alias and relevant matches without sending session cookies. We may need enough information to establish that a request concerns your data.
Contact and updates
For privacy questions, email lijing123lll@gmail.com. We update this policy when the data or services used by the game change. The date above identifies this version.