Cookie Policy
Cookies and local-storage technologies used by the Desi Battleground website and web game.
1. Summary
The Desi Battleground website does not currently use advertising or third-party analytics cookies. It uses limited storage that is necessary for secure login—including optional Google sign-in—device recognition and game-session continuity. These technologies are not used for targeted advertising.
2. Technologies used
| Name | Type | Purpose | Typical duration |
|---|---|---|---|
desigame_web_sso | Secure, HttpOnly, SameSite=Lax cookie | Maintains the shared authenticated session across approved Desi Battleground web/auth hosts. JavaScript cannot read this cookie. | Until logout or session expiry; configured between 7 and 180 days. |
desigame_device_id | Browser local storage | Creates a random browser-device identifier used to bind magic-link login and reduce session theft. | Until browser/site data is cleared. |
desigame_auth_session | Browser local storage | Stores player ID/name, login method, refresh token and session expiry so the web game can resume login. | Until logout, expiry or browser/site data is cleared. |
desigame_google_login:<random-state> | Temporary browser local storage | Transfers a one-time Google ID credential from the same-origin login popup back to the Web game. The key contains a random state value and is removed immediately after exchange, cancellation or timeout. | Normally seconds; no longer than the two-minute login window unless the browser is closed unexpectedly, in which case stale site data can be cleared manually. |
| Godot game local data | App/browser storage | Stores settings, controls, guest profile state and sanitized local diagnostics. | Until reset, uninstall or storage clearing. |
3. Cookie choices
Because the listed cookie and local-storage entries are used for authentication and core functionality, blocking them may prevent login or session continuity. You can sign out to revoke a server session and clear the cookie, or clear site data in your browser. Clearing app data removes local settings and may remove guest-only progress.
4. Android advertising and Google login
The website uses Google Identity Services only when a player explicitly chooses Google login; that authentication flow is not Google Analytics or an advertising tracker. The website does not use advertising cookies. The Android app includes Google Mobile Ads and Google User Messaging Platform and may show a consent-gated, frequency-capped interstitial only after completed non-training matches while returning to the lobby. Banner, rewarded, rewarded-interstitial, native and app-open placements are disabled.
5. Changes and contact
Effective date: 30 July 2026. Questions: rajniwebdeveloper@gmail.com.