Most people treat an iCloud backup as a safety net with no downside. For a casino account on a shared iPad, it is closer to leaving a spare key under the mat. The Casushi app stores session data and login state in its own container, and if that container rides along in an iCloud backup, restoring it to a family iPad can hand someone else a live path into your account without ever touching Face ID. The fix is unglamorous but effective: exclude the app from iCloud backup on any device you do not exclusively control.

How Casushi data actually ends up in an iCloud backup

Apple’s backup system is broad by default. When iCloud Backup is switched on, iOS captures app containers, preferences and keychain-linked credentials unless a developer has deliberately opted out. The Casushi app is a native iOS build distributed through the App Store, so on an iPhone or iPad with backups enabled, its local data is a candidate for inclusion. That is not a flaw in the app; it is how iOS works. The problem is what that data represents once it lands on a second device.

Session tokens are the part people underestimate. A restored backup can carry a logged-in state, and if the Casushi app has Face ID logins enabled, the biometric check is tied to the device’s Secure Enclave, not to the backup itself. Restore that backup onto a different iPad and the app may fall back to whatever non-biometric route it has, or simply present an already-authenticated session. Either way, the person holding the iPad is not you, and they did not pass a Face ID scan to get in.

This is the mistake I see most often in support threads: someone upgrades an iPhone, restores the old backup to a hand-me-down iPad for the kids, and only later notices unfamiliar activity in the cashier deposit history. Nobody hacked anything. The backup did exactly what it was told to do.

Why a shared iPad is the worst place to restore a Casushi backup

A shared iPad breaks every assumption the app makes about identity. Face ID logins assume one enrolled face per device, or at least a passcode the owner controls. Push notifications assume the person reading the lock screen is the account holder. The mobile lobby assumes the welcome bonus and account balance on screen belong to whoever unlocked it. Restore a Casushi backup onto that device and all three assumptions collapse at once.

There is a second, quieter risk: iCloud sync is not a one-way street. If the shared iPad stays signed into the same Apple ID, changes made there, including a fresh login or a cashier deposit, can propagate back to your other devices. You end up with a session that exists in two places, and you cannot tell from your iPhone which one is active. Disabling iCloud backup for the app on shared devices stops the restore problem, but signing the shared iPad out of your Apple ID is the cleaner boundary.

Worth saying plainly: Casushi does not publish a standalone Android APK file, and the same logic applies on the other side of the fence. Android users access the Casushi site through a mobile browser, where the responsive site detects screen dimensions automatically and there is no app container to back up. That removes one class of risk, but it does not remove the shared-device problem. A saved Chrome session on a family tablet is just as exposed as a restored iOS backup.

What to change on the device itself

On iOS, open Settings, tap your Apple ID, then iCloud, then Manage Account Storage, then Backups, and select the device in question. From the list of apps, switch off Casushi. That single toggle keeps the app’s container out of future iCloud backups while leaving the rest of the device backed up normally. Do it before the next scheduled backup runs, which is typically overnight while the device is charging and on Wi-Fi.

If the iPad is genuinely shared, go further. Turn off Face ID enrolment for anyone who is not the account holder, set a passcode only you know, and consider disabling push notifications for the app so the lock screen does not display balance or bonus details to the room. https://casushi-online.uk/app/ offers additional context worth reviewing. The Casushi mobile site offers responsible play tools such as session limits and deposit caps; set them from your own device and they apply to the account, not the hardware, which is exactly what you want when the hardware is not yours.

Myths that push people toward the wrong fix

The first myth is that deleting the app removes the backup. It does not. Deleting an app from a device leaves its data in any existing iCloud backup until that backup is overwritten or the app is excluded. People delete Casushi from the shared iPad, feel safe, then restore an older backup months later and reintroduce the session data. Exclude first, delete second.

The second myth is that Face ID makes a restored session safe. It does not travel with the backup. Face ID logins are a device-level convenience bound to the hardware that enrolled the face. A restore to a different iPad cannot reproduce that binding, and whatever fallback the app uses becomes the actual gate. Treat Face ID as a lock on one door, not a lock on the account.

The third myth is that an App Store listing guarantees a clean restore path. The App Store listing tells you the app is signed and reviewed; it says nothing about what iOS chooses to include in a backup. The fourth is that a home screen shortcut to the mobile site is risk-free. A shortcut is just a bookmark. It inherits the browser session, so if Chrome on the shared iPad is signed in, the shortcut opens straight into the mobile lobby with the welcome offer and balance visible. Clear the browser session or use a private tab on shared hardware.

One more: people search for a Casushi Android APK because they assume the casino app exists as a sideload. It does not. Casushi does not publish a standalone Android APK file, and any site offering one is not Casushi. The Casushi casino app experience on Android is the mobile site in Chrome, full stop. That matters here because sideloaded packages are exactly the kind of thing people restore or copy between devices without thinking, and there is no legitimate package to copy.

For clarity on what this page is: this website operates as an information page only. It does not host downloads, process payments or hold accounts. Anything involving the cashier deposit flow, the welcome bonus or account recovery happens inside the Casushi app or the Casushi mobile site, signed in as you.

A short checklist before you hand over the iPad

Before any restore or handover, confirm three things. First, that Casushi is excluded from iCloud backup on the device you are restoring from. Second, that the shared iPad is signed out of your Apple ID or at least not restoring your backup. Third, that the app’s cashier is locked behind a passcode you control, not a four-digit code the household knows. If you cannot tick all three, do not restore. Set the shared iPad up as a new device instead; it takes twenty minutes and removes the entire category of risk.

If a restore has already happened, act in this order: change your Casushi password from your own iPhone, force a logout of other sessions if the app offers it, review the cashier deposit history for anything you do not recognise, then exclude the app from backup on both devices. Contact support through the official Casushi: Online Casino channels if the history shows activity you cannot account for. Keep the responsive site bookmarked on your personal phone so you always have a clean route in that does not depend on a shared device.

The habit worth building is simple. Treat the Casushi app’s local data as sensitive as the account itself, because on a shared iPad it effectively is. Exclude it from iCloud backup, keep Face ID enrolled only on hardware you physically control, and never restore a personal backup onto a device that lives in a living room. The convenience of a one-tap restore is not worth handing someone a logged-in casino account.