We do not publish an app. This page covers how these apps are distributed, which permissions are ordinary and which are worth refusing.
How distribution actually works
Real-money skill-game apps in India are frequently unavailable in mainstream app stores because of store policies on real-money gaming. Operators respond by distributing an installable package from their own website. That is why a legitimate product and a malicious imitation can arrive through the same mechanism, and why the checks below matter more here than for an ordinary app.
Before you install
Type the operator's domain yourself rather than following a link from a message.
Confirm the site names the operating entity and a registered address.
Check that withdrawal and KYC terms are published before you install, not after.
Prefer an official store listing when one genuinely exists for that product.
Treat a download link arriving by SMS or a forwarded message as untrusted by default.
Permissions worth a second look
A card game needs very little from your phone. Requests well beyond that deserve a reason.
Permission
Reasonable?
Why
Network access
Yes
Required for any online table.
Storage, scoped
Usually
Caching assets and saving KYC uploads.
Camera
Situational
Only when you are photographing a document for KYC.
SMS read
Rarely
Sometimes used to auto-fill an OTP, but it also exposes every other code on the device.
Contacts
No
Referral features do not require your address book to function.
Accessibility services
No
Grants broad control over the device. A card game has no legitimate need.
Our download guide covers the install step itself, and APK installs covers the sideloading case specifically.
Editorial note
jackpotcityin.com is an independent editorial desk. We do not operate a skill-game product, hold player balances or process payments. Anything on this page that concerns a specific platform should be confirmed against that platform's own published terms before you rely on it.
How to get the platform’s app on an Android or iOS device
The two routes below are the only ones this desk recommends. Any other route — a forwarded link, a search result, a third-party APK host — is a route on which a lookalike app can replace the platform’s real one.
For iPhone and iPad
Open the Apple App Store, search for the platform by name, and confirm the publisher is the platform itself (not a publisher with a slightly different name or a generic publisher). Tap "Get" and authenticate with Face ID, Touch ID or your Apple ID password. The app installs and appears on the home screen.
For Android phones and tablets
Open the Google Play Store, search for the platform by name, and confirm the publisher is the platform itself. Tap "Install". The app installs and appears in the app drawer. The Google Play Store is the only source this desk recommends for the Android app.
What not to do
Do not install an APK forwarded by a chat, SMS, email or social media post. The forwarded file is, in a non-trivial share of cases, a lookalike app.
Do not install a "mod" or "premium" version of the platform’s app. The platform does not publish a "mod" version; the file is a lookalike.
Do not install a second copy of the platform’s app from a different source. A phone with two apps that look like the platform is a phone on which the reader does not know which app holds the real credentials.
On both platforms, the publisher’s name and the app’s install count are visible in the listing. A platform’s real app has a publisher name that matches the platform and an install count in the high six figures or more. A lookalike app usually has neither.
The permissions a platform’s app asks for, and what each is for
A skill-game app asks for a small set of permissions. The list below is what each permission is for, the reason the platform wants it, and the practical effect of denying it.
Storage / photos and media
The app uses this permission to read KYC documents from the phone’s storage (when the reader chooses a document from the gallery rather than capturing it) and to save the platform’s own files. Denying this permission blocks the gallery-based KYC path; the camera-based path still works.
Camera
The app uses this permission to capture KYC documents and, on some platforms, a selfie for liveness checks. Denying this permission blocks the camera-based KYC path; the gallery-based path still works on Android but not always on iOS.
Phone
The app uses this permission to read the device’s phone number for registration, and on some platforms to detect SIM swap. Denying this permission usually forces the reader to enter the phone number by hand at every login, which is workable but slower.
Location
Some platforms ask for location to confirm the reader is in a state from which the platform accepts players. Denying this permission usually requires the reader to confirm the state in account settings instead. The permission is reasonable; the platform’s published state list is the document that actually governs who the platform accepts.
Notifications
The app uses this permission to deliver deposit confirmations, withdrawal updates, KYC status and responsible-play reminders. Denying this permission still allows play; the reader simply does not get the in-app alerts.
Permissions the app should not ask for
Contacts, microphone (unless the platform offers a voice-based support flow), calendar, and background location are not required by a skill-game app. If the app asks for any of these, deny and contact the platform’s support; an honest app does not need them.
When to use the app, and when to use the web version
Most regulated platforms offer both an app and a web version. The two are not interchangeable, and using the wrong one for a given task is a common cause of friction. The list below is what this desk suggests by default.
Use the app when
You are playing. The app’s rendering of the table, the timer and the discard pile is, on most platforms, faster and more stable than the web version’s.
You are depositing. The app’s payment flow uses the phone’s native UPI app or the phone’s native payment method, which is faster and more reliable than a web-based payment form.
You are doing KYC. The app uses the phone’s camera for document capture, which is faster and lower-friction than uploading from a desktop scanner.
Use the web version when
You are reading the platform’s published rules. The web version’s larger screen is easier to read for a long rules document.
You are filling out a long KYC form. The web version’s form layout is, on most platforms, easier to navigate than the app’s.
You are on a borrowed or family-shared device. The web version does not require an install; the credentials and KYC documents are not stored on a device the reader does not control.
Why the same account works on both
The same login credentials work on the app and the web version. The account, the balance, the KYC documents and the responsible-play tools are the same on both; only the surface the reader is interacting with is different. A reader who logs out of the web version on a shared device, and does not save the password on that device, is a reader whose account is not exposed to the next user of the device.
Storage, cache and a clean install
The app’s cache is the data the app stores locally to render faster. The cache is not the app; clearing the cache removes the locally stored data and forces the app to re-download it. The list below is the working order to follow when the app misbehaves.
1. Close and reopen the app
The first step for any app misbehaviour is to close and reopen the app. On iOS, swipe up from the bottom of the home screen (or double-tap the home button on older devices) and swipe the app card away. On Android, open the recent apps view and swipe the app card away.
2. Clear the app cache
Clearing the cache is the second step. The setting is usually in Settings > Apps > [platform name] > Storage > Clear cache. Clearing the cache does not log the reader out; clearing the data does. A reader who clears the data has to log in again, which is the more invasive step.
3. Update the app
The third step is to update the app to the latest published version. The app store’s "Update" button is the right path. A reader who has not updated the app in several months is a reader who is, in our experience, also missing the most recent security patches.
4. Reinstall as a last resort
Reinstalling the app is the last step, not the first. Reinstalling clears the cache and the data; reinstalling also forces the reader to log in again. A reader who reinstalls the app as a first step is a reader who has spent an unnecessary five minutes re-entering the credentials.
