Chor Sipahi (Raja Mantri Chor Sipahi) — Android App & Website
This Privacy Policy explains how Chor Sipahi ("we", "us", "our", "the App") collects, uses, stores, and protects information when you use our Android application or visit playchorsipahi.com (together, the "Service"). By using the Service, you agree to the practices described in this policy.
We collect only what is needed to run multiplayer rooms, voice chat, and leaderboards. Depending on how you use the Service, this may include:
| Category | Examples | Source |
|---|---|---|
| Account identifiers | Google account name, email address, profile photo URL, Firebase user ID (UID) | Google Sign-In (only if you choose it) |
| Guest identifiers | A randomly generated, temporary guest ID and the display name you type in | Guest Login |
| Gameplay data | Room codes, scores, round results, leaderboard rank, chat messages sent in a room | Generated while you play |
| Voice chat metadata | Room/channel name, temporary voice session token, mute/speaking status | Agora RTC, only when you join a room's voice chat |
| Device & technical data | IP address (transient, for connecting your device to a game server), device type, app version, connection/network status | Automatically, to operate Socket.IO connections |
We do not collect payment information, precise GPS location, contacts, photos/media, or SMS/call data — the App does not request or use any of these permissions.
If you choose to sign in with Google, we use Firebase Authentication to receive your basic Google profile information — your name, email address, and profile photo URL — solely to identify your account, save your progress, and display your name/avatar to other players in a room. We do not receive your Google password. You can review or revoke Chor Sipahi's access at any time from your Google Account permissions page.
You may also play without an account using Guest Login. A temporary, randomly generated guest ID is created for your session so you can join a room and be scored on the leaderboard for that game. Guest data is not linked to any personal identity, is not tied to an email address, and is only retained for as long as needed to support reconnects during an active session (see Data Retention).
Voice chat is an optional feature powered by Agora RTC. When you join a room's voice channel:
Agora acts as our real-time communication sub-processor. See Agora's own privacy practices at agora.io/en/privacy-policy.
The Android app requests the RECORD_AUDIO permission solely to enable Voice Chat. The microphone is only active while you are actively connected to a room's voice channel; it is not accessed in the background or while voice chat is off. You can deny or revoke this permission at any time from Android Settings → Apps → Chor Sipahi → Permissions — the game remains fully playable without it, with voice chat simply disabled.
We use Google Firebase Authentication to manage sign-in sessions securely. Firebase issues a signed identity token that our backend verifies to confirm who you are before letting you create or rejoin a room. Firebase Authentication is governed additionally by Google's Firebase privacy terms. We do not store your Google password — authentication is handled entirely by Google/Firebase.
| Permission | Why we need it |
|---|---|
| Internet | Required to connect to our game server for multiplayer rooms, chat, and voice chat. |
| Network State | Lets the app detect connectivity changes so it can reconnect you smoothly if your network drops mid-game. |
| Microphone | Used only for optional Voice Chat, as described above. |
| Vibration | Used for short haptic feedback on in-game actions (e.g. claiming a role); can be disabled from in-app Settings. |
Pass & Play (offline mode) runs entirely on your device — no gameplay data leaves your phone in this mode, and no network permissions are used while playing offline.
If we introduce analytics or crash reporting in the future to improve app stability and gameplay experience, we will update this Privacy Policy and the app's Play Store Data Safety section beforehand to disclose exactly what is collected.
We do not sell your personal data. We share limited data only with the service providers necessary to run the Service, each acting as a data processor on our behalf:
We may disclose information if required to do so by law, or to protect the rights, safety, and integrity of the Service and its users.
You can request deletion of your account data at any time:
Note: because live gameplay data (scores, room history) is held only in server memory for the duration of a session and not persisted afterward, most gameplay data is already automatically removed shortly after a room ends.
If you are located in the European Economic Area (EEA/GDPR) or California (CCPA), you have the right to:
To exercise any of these rights, contact us using the details in Contact Information below.
Chor Sipahi is intended for a general audience and is not directed at children under 13 (or the minimum age required by your country's law). We do not knowingly collect personal information from children under this age. If you believe a child has provided us with personal information, please contact us and we will promptly delete it.
We take reasonable technical and organizational measures to protect your information, including:
No method of transmission or storage is 100% secure; while we work hard to protect your data, we cannot guarantee absolute security.
Account identity data (Google name/email/UID) persists in Firebase Authentication until you delete your account or request deletion. Live game/room data exists only in server memory for the duration of an active session and is discarded shortly after a room becomes empty or inactive. We do not maintain a persistent gameplay history database at this time.
Chor Sipahi
Website: https://playchorsipahi.com
Privacy inquiries & data deletion requests: privacy@playchorsipahi.com
General support: support@playchorsipahi.com
We may update this Privacy Policy from time to time to reflect changes in our practices, features, or legal requirements. Material changes will be reflected by updating the "Last updated" date below, and — where required — we will provide additional notice (e.g. an in-app notice) before the change takes effect. Continued use of the Service after changes take effect constitutes acceptance of the updated policy.
Last updated: July 15, 2026