Before you reinstall, back up your account state. For the desktop installer, your account state lives on the publisher's servers, not on your hard drive — your login credentials, balance, transaction history, KYC documents, and responsible-play settings are all server-side. The only thing that lives on your machine is the local cache of tiles and reels, which is rebuilt automatically on first launch of the new install. For the Android APK, the same server-side model applies: account state is bound to your phone number or email, not to the device. Backing up the APK is not a backup of your account; reinstalling the APK and logging in returns you to the same account.
That distinction matters because it changes when reinstall is the right move. Reinstall is appropriate when the local install is corrupted — for example, when the app launches but the tile spinner does not render, or when the login dialog accepts your credentials but then returns to a blank screen. Reinstall is also appropriate when the platform has published a security advisory that requires a clean install, or when you are switching devices and want to start fresh rather than migrate a local cache. Reinstall is not appropriate as a first response to a connectivity issue, a transaction delay or a login failure — those are server-side events diagnosed through the customer-care channel, not local issues fixed by reinstalling.
01
Back up what the server does not store
Before uninstall, export any locally-stored notes you keep inside the app — favourite table stakes, hand-history files you saved locally, and screenshot folders. The publisher does not back these up for you; they live on your device and are removed by uninstall. The settings, balance and KYC status are server-side and persist.
02
Verify account continuity after reinstall
After the new install completes, log in with the same credentials. The first screen after login should show your real balance, your real display name, and your verified KYC status badge. If any of these is missing or shows a previous user's data, log out immediately and contact customer care — this is a sign the publisher's account-merge logic has misfired, and customer care resolves it from the server side.
03
Reinstall after a suspected account compromise
If you are reinstalling because you suspect your account has been accessed by someone else — for example, an unfamiliar login notification, a withdrawal you did not make, or a changed password you did not change — the reinstall itself is not enough. Change your password from the login screen, revoke any active sessions from the security settings, and contact customer care to flag the incident. Reinstall without those steps leaves the attacker with the same session and the same access on the new install.
Account continuity is verified by three checks after the reinstall. First, the balance matches the balance you saw before the uninstall. Second, the responsible-play settings you previously configured — deposit limits, session timeouts, self-exclusion — are still active. Third, your withdrawal method is still linked and the last four digits of the bank account or UPI ID match. If all three match, the reinstall was clean and your account is intact. If any of the three is wrong, log out and contact customer care before placing a deposit or a withdrawal request.
One more point worth recording. The publisher's customer-care channel is the authoritative source for account-state questions after reinstall. The app's UI on the new install is a server-side view of the same account, so what the UI shows is what the server records; if the UI shows a number you do not recognise, the server has a number you do not recognise, and the only resolution path is the support ticket that the customer-care team can action on the server side. Documenting the timestamp of your reinstall, the build number you moved from, and the build number you moved to will shorten the resolution time when that ticket is filed.
