Privacy,
explained plainly.

The collection and your choices

Waraq-Khana includes Pasoor, Manfee, Teka, Falaash, Panjpar, Chor Voli, Carrom, Thirteen / Tiến Lên and Chaka. You can play the seven card games and Chaka against bots, and practice Carrom offline, without creating an online account. Choosing an online mode creates or reconnects an anonymous online guest.

The launch version uses app-generated names only. Earlier beta versions allowed player-written names; those names are replaced when the updated service reads the account. Older account records and recovery copies remain subject to the retention and deletion rules below.

The intended store audience is adults aged 18 and over. Selecting this store audience does not add an in-app age-verification feature.

The current app has no advertising, third-party behavioral analytics, client crash-reporting service, public chat, social sign-in, payments or in-app purchases. We do not request contacts, precise location, microphone access, photos, or an advertising identifier. You do not need to give us your real name, email address or phone number to play.

Information on your device

• Local guest profile: an app-generated random identifier, friendly guest code, generated display names, the selected generated suggestion, a profile-format version and creation time. The local identifier, guest code and creation time are not sent to the game service. Only the generated suggestion’s catalog index is sent when you enter online play; the service supplies the visible name.
• Preferences: your chosen English, Farsi or Pashto presentation language and card-back selection, plus the versions needed to read those settings. These preferences are kept locally and are not account-synced.
• Online installation credential: when you choose online play, the app creates a random secret for that installation. It is not your visible guest code, a hardware identifier, or an advertising identifier. The app stores it locally and sends it to our game service to create or recover the same anonymous guest.

Offline hands, deck order, actions and scores are held in memory for the running match. Ordinary offline play does not transmit them or save a permanent match history.

Information used for online play

Our game service processes an opaque account identifier, the random installation credential used for authentication, your generated name, temporary login/session credentials, and the records needed to run online games.

• Your generated name is stored on your online guest account and is visible to other participants in your lobby or match. Profile can suggest another name from the app’s fixed catalog. The launch version has no field for entering your own name.
• Matchmaking and private tables use account and request identifiers, compatibility/seat information, readiness, private invite codes and expiry times.
• Gameplay uses actions, turns, scores, cards/deck state where relevant, public Carrom positions and shots, and connection/reconnect information. The service receives the information necessary to validate actions and run the match. Each player receives only the hidden-card information permitted by the selected game's rules; approved result or reveal phases can make dealt cards public.
• Security and reliability use request-limit counters, temporary account/session-expiry records, routing records and service diagnostics. Session access/refresh credentials remain in the running client's memory; the persistent installation credential is a separate value.

Game state is held temporarily in the running game authority. There is no durable full-match recovery or permanent player match history. A server restart can interrupt an active match. Short public Carrom playback buffers are also temporary; they are not saved as player replays.

Network systems necessarily process connection information, such as an IP address and technical request metadata, to deliver the website and online play. This information is not used for advertising or cross-app profiling.

Diagnostics and support

Our production diagnostics feed records sanitized game-service errors and database error/slow-query metadata. It includes timestamps, service/node labels, severity or error codes, source locations, durations, row counts and opaque message/statement fingerprints. That feed excludes raw messages, SQL text and parameters, player identifiers, names, IP addresses, credentials and gameplay payloads.

The database's private slow-query log can contain SQL values before cleanup. Separate local infrastructure error logs are also kept for maintenance and may contain technical connection details. These are owner-restricted operational records, not an advertising or player-tracking service. The retention details below distinguish them from the sanitized cloud feed.

If you email karzai24.mk@gmail.com, Google Gmail processes your sender address, message, replies and anything you voluntarily include, such as your device model or a screenshot. This mailbox is not an app login and receives no ordinary gameplay traffic. Do not email passwords, tokens, installation credentials, private-party codes or cards from a private hand.

Service providers and location

• Oracle Cloud Infrastructure hosts the production game service, website, managed MySQL database, managed backups and sanitized diagnostics in Abu Dhabi, United Arab Emirates.
• Nakama is the software running our operator-managed game service. It uses Oracle's managed MySQL database for production account and coordination records.
• Cloudflare provides authoritative DNS for our public domain. The current DNS-only configuration sends website/game requests directly to Oracle infrastructure rather than through Cloudflare's HTTP proxy.
• Google Gmail processes voluntary support and deletion-request email.
• Apple and Google handle store distribution and testing under their own policies when you use their stores or beta programs.

Restricted historical recovery copies may also be held on owner-controlled storage outside the production region. Support and platform providers may process information in other locations. We do not use the information described here for advertising or sell it for behavioral profiling.

How long information remains

• Local profile and preferences: remain until you remove the relevant data. Forget local guest removes the local profile and its recovery copy; it does not remove the separate language/card-back preferences. Clearing app or website data removes the local files for that installation/origin.
• Online account and authentication mapping: remain until online-account deletion. Confirmed deletion also clears this installation's online credential; entering online play again creates an unrelated guest.
• Login/session records: expire with their access/refresh validity. Expired server token-ID records are removed by bounded hourly cleanup; a backlog can delay removal. Complete session tokens are not stored in that cleanup record.
• Invite and coordination records: private invite codes expire after two hours. Short-lived queue, request and routing records have expiry-based, bounded cleanup, so physical removal can follow logical expiry.
• Match state: disappears when the running authority match ends or stops. Offline state disappears when its local table closes or the app exits.
• Sanitized OCI diagnostics: have a configured 30-day retention.
• Private MySQL slow-query log: is checked every 15 minutes. The table is cleared if an entry is older than 24 hours or it reaches 10,000 records. This is a periodic cleanup rule, not an exact 24-hour maximum.
• Local infrastructure logs: rotate by size. Game/API logs use three 10 MiB files per container; website error logs use two 5 MiB files. These size limits do not set a maximum age.
• Production managed MySQL backups: use Oracle's configured one-day retention. A deletion may remain in an older backup until that backup expires.
• Support correspondence: deletion-request email is removed no later than 30 days after completion. Other support threads and attachments are removed no later than 30 days after the issue is closed. These are owner-operated retention periods; the app does not run an automated mailbox cleanup.

If recovery uses older account data, completed deletion requests must be reapplied before the service reopens to players.

Your choices and deletion

1. To delete the online guest, open Profile → Delete online guest and data, read the warning and confirm. The live account is removed when the server confirms success, together with its authentication mapping, sessions, account-owned records and hosted invite codes.
2. To remove the separate local profile, choose Forget local guest. Clear app/site data if you also want to remove local preferences.
3. If you no longer have the app, follow the account-deletion instructions or email karzai24.mk@gmail.com.

Email requests require enough non-secret information to distinguish anonymous guests, such as the online display name, platform and approximate last-play date. Identified email requests are normally processed within 30 days. Deleting local data or uninstalling alone does not delete the server account.

Security and policy changes

Public online traffic uses HTTPS and secure WebSocket connections. The production database connection uses verified TLS. Account credentials are not intentionally included in ordinary application logs; the sanitized diagnostics feed filters private values before forwarding them. No system can guarantee absolute security.

We will update this policy when the app's data practices or providers change. The effective policy shows its revision date.