Privacy Policy

2. Data we process

Account and profile data

When you choose account login, we process your email address or mobile/WhatsApp number, or—when you use Google sign-in—Google's stable account identifier, verified sign-in result, display name and masked email address. We also process verification status, player ID, login method and account timestamps. We do not receive or store your Google password or Google access token. Guest play can be used where offered, but guest progress may remain only on the device.

Device, session and network data

We process an app-generated device identifier, device label, platform, session identifiers, token hashes, IP-address hashes, user agent, connection status and security/audit events. Raw passwords are not used for magic-link login. Never send us your OTP, password, refresh token or banking information.

Gameplay and safety data

Online play may process matchmaking selections, room and match identifiers, team, gameplay inputs, movement and combat state, match results, reconnect events, anti-cheat signals, abuse reports and server diagnostics. This is needed to operate authoritative multiplayer gameplay and protect fair play.

Settings and locally stored data

The game may store graphics, control, audio, language and HUD-layout settings. A sanitized local analytics log can be written on your device for diagnostics; it blocks common personal-data fields and is not automatically uploaded by the current client. The website stores a device ID and login session data in browser local storage.

Support and legal requests

If you contact support or submit a copyright, privacy, impersonation or account-deletion request, we process the information you provide. Identity evidence is requested only when reasonably required for verification. Do not submit an unmasked Aadhaar number, OTP, password, financial credential or biometric information.

3. Android permissions, Google login and advertising consent

The Android export requires Internet access for login, downloads and online multiplayer. Google login is optional and is used only when selected by the player. Signed Android releases may also use Google Play Games Services v2 for automatic authentication status, manual sign-in retry, the player's Play Games account identifier, display name, profile image reference, and Google-hosted Achievements and Leaderboards screens. AdMob-enabled Android builds include Google Mobile Ads and Google User Messaging Platform; UMP checks consent requirements before the ads SDK is initialized. When permitted, the app may preload and show a frequency-capped interstitial only after completed non-training matches while returning to the lobby. The merged SDK manifest may include network-state and advertising-ID permissions. The app does not request precise or approximate location, contacts, SMS, call logs or broad file access. Camera permission is used only when the player opens the optional floating Face Cam, microphone permission only when team/global voice chat is enabled, and notification permission only when the player chooses match, maintenance or update alerts. These permissions are requested from their relevant feature and are not required by Play Games Services. Play Console Data safety and advertising-ID declarations must match the published build.

4. Why we use data

• Provide login, account recovery, profile and cloud HUD settings.
• Operate matchmaking, multiplayer sessions, reconnect, voice-room signaling and content downloads.
• Detect cheating, abuse, fraud, attacks and service instability.
• Diagnose crashes, performance and network faults.
• Respond to support, privacy, deletion, copyright and lawful requests.
• Maintain security records and defend legal claims.

5. Sharing and service providers

We do not sell personal data. Infrastructure providers may process data for hosting, login delivery, networking, storage, security and legal compliance. Google Identity Services processes sign-in data only when Google login is selected. Google Play Games Services may process Play Games authentication state and profile information according to Google's terms; Desi Battleground does not currently submit achievement unlocks or leaderboard scores through this integration. Google Mobile Ads and UMP may process consent and advertising-related device data according to the player’s consent choices and Google’s service terms; the approved configuration enables only a consent-gated, frequency-capped post-match interstitial and keeps rewarded, app-open, native and banner placements disabled. Providers may process data only for the service they perform. We may disclose information when required by law, to protect users and systems, or during a legitimate business transfer with appropriate safeguards.

6. Security

Production account, website and gameplay traffic uses HTTPS or WSS. The assignment service does not issue join tokens for the current plaintext UDP transport; clients are routed to the authoritative WSS fallback until a verified encrypted DTLS or QUIC transport is available. Authentication tokens and identifiers are hashed where practical, access is restricted, sensitive complaint files are stored outside the public website, and server records use controlled permissions. No system is perfectly secure, so promptly report suspected account or privacy incidents.

7. Retention

Pending magic links expire quickly, normally within 10 minutes. Login sessions are configured for a limited period and can be revoked. Account and profile data remain while the account is active. Match, anti-cheat, audit, support and security records are retained only as reasonably needed for operations, abuse prevention, dispute resolution, backups or legal obligations. After a verified deletion request, linked account data is deleted or irreversibly de-identified, except limited records that must be retained for security, fraud prevention or law; retained records are isolated and not used for gameplay or marketing.

9. Children

Desi Battleground is intended for users aged 13 and above and is not directed to children under 13. A parent or guardian may contact us to review or request deletion of a minor’s information. Target-audience and content-rating declarations in Google Play must match the released build.

10. Your choices and rights

You may use guest mode where available, sign out, revoke Desi Battleground's Google account access from your Google Account settings, disable optional voice mode, clear local app/browser data, request access or correction, object to certain processing, or request deletion. Rights vary by location. We will respond after reasonable identity verification.

11. International processing

Online services may route or store data in locations where our infrastructure providers operate. We apply contractual and technical safeguards appropriate to the data and service.

12. Changes and contact

We will update this page when data handling or app features materially change. Effective date: 30 July 2026. Contact: rajniwebdeveloper@gmail.com.