A reader-friendly install guide for Android.
The desk publishes this page because most install problems are not download problems, they are publisher-verification problems. The guide below walks through where to find the official package, how to verify the publisher name, and what to read before the first deposit.
Before you install
The desk’s install guide assumes the reader knows the difference between the Google Play official package and a sideloaded APK. Sideloading is permitted on Android but exposes the reader to spoofed packages. The /apk-download/ page is the desk’s separate guide to that path.
Where you see “sideload only”, that is a flag in itself: serious platforms publish a Google Play package.
The five install steps
Open Google Play
Search for the brand name exactly. Confirm the publisher name matches the platform’s published owner page.
Check the publisher
The publisher is shown under the install button. The desk’s safety criteria flag mismatched publishers.
Tap Install
The download is free. Approve the standard storage permission only.
Open the app
Once installed, the app icon appears in your launcher. Open it once to start the KYC flow.
Read the rules
Open Help → Rules before your first deposit. Read the show condition once.
How to verify the publisher
The publisher name on Google Play matches the platform’s registered brand. The desk links the /owner/ page so readers can confirm the operator. Where the two disagree, the platform has not been verified.
This is a small reading step that prevents the most common install mistake: confusing an unrelated publisher for the platform’s official package.
After install
Once installed, read the safety desk before any deposit. The safety desk walks through the deposit-and-withdrawal language and the KYC order; both are required reading.
Reader questions
Where do I install the app?
How do I verify the publisher?
What storage permissions are needed?
Is sideloading allowed?
What if the app fails to install?
Updates and version checks
Google Play notifies of updates automatically. The desk recommends accepting security updates immediately and reading the release notes, most security issues are flagged in the release notes before any newsdesk coverage.
Reading storage and battery use
The app’s storage and battery usage is in Android Settings → Apps. If storage climbs unexpectedly, clear the cache; if battery use climbs unexpectedly, audit the permissions.
After install
After install, the safety desk is the next page. Read it before the first deposit, before the welcome bonus, and before you share KYC documents.
Pre-flight checklist before you tap Install
Most install mistakes are caught in the thirty seconds before the reader taps the button. The desk recommends running this short pre-flight list every time, even on a familiar phone, because publisher names change quietly and the platform the reader intends to install may have been rebranded.
- Confirm the device has at least 200 MB of free storage. The install itself is small, but the runtime cache for live-dealer tables grows quickly.
- Confirm the Google Play account is the same account the reader intends to use for KYC. Mismatched accounts complicate the verification trail later.
- Confirm the Android version is at or above the version listed in the Play Store description. Older Android builds install successfully but may fail to render the cashier.
- Confirm the reader is not on a corporate Wi-Fi network that blocks sideloaded packages. Public networks with strict certificate pinning will block the install silently.
- Confirm the reader has read the state eligibility desk. Six Indian states restrict real-money rummy; the install should pause there.
Reading the permissions screen
Android requests runtime permissions only when the app first needs them, but Google Play lists the install-time permissions on the app’s listing page. The desk flags three permissions as worth reading carefully. Storage is needed for the local cache and the install; this is normal. Camera is needed only for the KYC document scan; the app should not request it before the reader opens the verification flow. Location is optional and should be declined by readers who do not want their play region logged beyond what the eligibility check already requires.
Permissions that the desk considers red flags include access to the contacts list, the SMS log and the call log. None of these are needed for a rummy-and-skill-game install. If any of these are listed, the reader is looking at a repackaged package rather than the platform’s official build.
The /safety/ desk keeps an updated permissions reference; the desk recommends cross-checking the install-time list against that reference before the first launch.
What happens on first launch
On first launch the app requests the reader’s mobile number for an OTP login. The desk’s editorial view is that OTP login is the right primary path because it survives password reset churn, but readers who do not want their mobile number on the platform should stop at this screen and use the web path instead. Web play is supported on the platform’s official website, which the /official-website/ page links.
After OTP verification, the KYC flow opens. The desk’s reading order is PAN first, Aadhaar masked second, bank proof third. The order matters because PAN is the lowest-friction document and the platform should not request a bank statement until PAN has cleared. The /wallet-kyc/ desk walks through the ordering in detail.
First launch is also when the welcome bonus screen appears. The desk’s reading is that the bonus terms are worth opening once before accepting; the wagering rollover and the eligible-game list are stated in plain numbers on the bonus code page. Readers who do not read the terms often find out at withdrawal time that the bonus cap or the eligible-game list does not match their play.
Common install errors and what they mean
The four error messages that most often appear during install are worth recognising. "App not installed" usually means a previous build is still on the device, or the package conflicts with an older version that was sideloaded and not uninstalled. The fix is to remove the older package first, then install from Play. "Storage full" is self-explanatory; clearing the cache of large media apps usually frees enough. "Parse error" indicates a corrupted download, which is rare on Google Play but more common on the APK path; the fix is to re-download from the platform’s official website.
The fourth is the silent install failure. The Play Store shows the install as complete, but the launcher icon never appears. This is most often caused by a profile or work-container policy on corporate-managed Android devices. The fix is to switch to the personal profile before installing, or to use the web platform instead. The desk flags the silent failure as the hardest to diagnose because the error appears in the system log only.
How updates are delivered and when to accept them
Google Play delivers updates in the background once the device is on Wi-Fi and charging. The desk recommends leaving auto-update on for this app, because security patches ship through the same channel and a missed update can leave the reader playing on an older cryptographic library. Security-only updates are usually below 20 MB and do not change the user interface.
Feature updates are larger and ship with release notes. The desk reads every release note on the day it ships, and the newsdesk covers the ones that change deposit-and-withdrawal language, KYC ordering or bonus terms. The platform typically ships four to six feature updates per year; the release note is the canonical record of what changed.
If a reader notices a change in behaviour that is not in the release notes, the customer-care desk is the right next stop. Mismatches between observed behaviour and the release notes are worth flagging because they are usually the first signal of a rollback or a hotfix that has not yet been formally documented.
How to remove the app cleanly
If the reader decides the platform is not for them, removal is straightforward. On Android, long-press the launcher icon and choose Uninstall, or open Settings → Apps → the platform’s name → Uninstall. The reader’s account remains open on the platform’s servers; uninstalling the app does not close the account. To close the account entirely, the /delete-account/ desk walks through the platform’s closure path.
Before uninstalling, the desk recommends withdrawing any balance to a verified bank account and downloading the platform’s monthly account statement. The statement is the reader’s audit trail and is useful for any future KYC re-verification on a different platform. The /wallet-kyc/ desk explains the statement format and the typical contents.
Removing the app does not delete the reader’s data from the platform’s servers. The platform’s privacy policy describes the retention period, and the right to erasure under the Digital Personal Data Protection Act, 2023 is honoured on request through the customer-care desk. The desk flags one operational detail worth knowing: the platform typically retains KYC documents and transaction history for seven years to comply with anti-money-laundering rules, even after an account closure request. The retention is governed by the regulator, not by the platform.
Install is the start of the desk reading, not the end.
Once the app is installed, the safety desk is the next page. The four reading tools there apply to every platform.