Restoring an iCloud backup onto a shared iPad is one of the quietest ways to hand someone else access to your Casushi account. The Casushi app supports Face ID logins, and that biometric gate feels reassuring until you realise what a restore actually carries across: stored session data, app preferences, and the logged-in state that the operating system treats as part of the device snapshot. The mistake is not using iCloud. The mistake is leaving the Casushi app inside the backup set on a device more than one person touches. This article breaks down what really happens to app data in iCloud, which beliefs about mobile casino security are wrong, and how to configure things so a shared iPad never becomes a back door.
Apple’s backup system is designed to make a new or wiped device feel like the old one. That is excellent for a personal iPhone and risky for a family iPad. When you restore from an iCloud backup, iOS reinstalls the apps that were in the snapshot and reinstates their container data, including keychain items tied to the app where the developer has enabled that behaviour. The Casushi app is not exempt from this. Session tokens, remembered account state, and interface preferences can all travel with the restore.
Here is the part most people miss. Face ID is a local authentication layer, not a server-side lock. If the restored app state already presents a logged-in session, the biometric prompt may never appear, because there is nothing to unlock. The next person who picks up the iPad opens the app and lands straight in the account. No password, no face scan, no warning.
The fix is procedural, not technical wizardry. On any shared device, open Settings, tap your Apple ID, then iCloud, then Manage Account Storage, then Backups, select the device, and switch off the Casushi app under “Choose Data to Back Up”. Do this before the first backup runs after installation. Disabling iCloud backup for the app on shared devices is the single most effective step, and it costs you nothing on your personal iPhone where the backup is genuinely useful.
Face ID is genuinely good at what it does: it stops someone picking up your unlocked iPhone and tapping into the Casushi app. Apple’s implementation stores the biometric template in the Secure Enclave and never sends it anywhere. None of that is in question. The gap is that Face ID protects the entry point, not the underlying session. Restore the session elsewhere and the entry point is bypassed entirely.
Reporters who cover mobile security see this pattern repeatedly across banking and betting apps. The biometric prompt is a convenience lock, and convenience locks assume the device itself is trusted. A shared iPad fails that assumption. Treat Face ID as a lock on the front door of one house, not as a padlock that follows your account around.
Search forums for “Casushi casino app” and you will find a tangle of half-truths. Some are harmless. Others lead directly to the shared-device mistake above. Sorting the myths from the mechanics is worth ten minutes of anyone’s time.
The pattern across all five is the same: people assume the app behaves like a website, where logging out on one device has no bearing on another. Native iOS casino software behaves more like a desktop client. State persists, and state can be copied.
The practical setup for a household device takes about five minutes and should be repeated whenever someone new starts using it. https://casushi-online.uk/app/ offers additional context worth reviewing. The order matters, because a backup can run overnight before you get round to it.
First, decide whether the Casushi app belongs on the shared device at all. If the answer is yes, disable iCloud backup for it immediately after installation. Second, if the device is restored from a backup at any point, open the Casushi app cashier and check the session state before handing the iPad to anyone. Log out manually if the app presents an active session. Third, review which Apple ID owns the device. A shared iPad signed into your personal Apple ID will sync your keychain, your messages, and your app data. Create a separate Apple ID for shared hardware, or use the browser route instead.
The table below compares the realistic options for someone who wants Casushi on a device that other people also use.
| Setup | What it protects | What it exposes | Best for |
|---|---|---|---|
| Casushi app on a personal iPhone with iCloud backup on | Full restore after loss or upgrade, Face ID login intact | Session data sits in iCloud, so account security depends on Apple ID hygiene | One-person devices with a strong Apple ID password and two-factor authentication |
| Casushi app on a shared iPad with iCloud backup off for the app | Stops session data syncing to a restore target | App still installed, so manual logout discipline is required | Households where one person plays and others use the iPad for streaming and browsing |
| Casushi mobile site via Chrome with a home screen shortcut | No app container data, nothing for a backup to carry | Browser history and saved passwords need separate management | Shared devices, guest use, and anyone who wants a clean exit |
| Casushi app on a shared iPad with iCloud backup on | Nothing meaningful | Session data can restore onto the same device or a replacement, skipping Face ID | Nobody. This is the configuration to avoid |
| Guest mode or a separate shared Apple ID with the app installed | Isolates your personal keychain and app data | Requires setup effort and a second Apple ID | Families with teenagers or lodgers using the same hardware |
Apple occasionally reshuffles the Settings menus, and a major iOS update can re-enable defaults you previously changed. After any update, verify two things: that the Casushi app is still excluded from the iCloud backup set, and that the device is not signed into an Apple ID you do not want syncing. The same applies if you use the Casushi mobile site. Chrome’s sync settings can carry saved passwords across devices if you sign in, so check that too.
One more procedural note. If you sell or hand down an iPad, sign out of iCloud and erase all content and settings rather than just deleting apps. A deleted app can be reinstalled from the App Store by the next owner, but a restored session cannot survive a full erase with iCloud sign-out. That is the difference between a tidy handover and a security incident.
None of this advice is about avoiding the product. The mobile lobby includes the welcome offer, the Casushi app cashier manages payments, and the Casushi mobile site offers responsible play tools such as deposit limits and session reminders. Those features are the reason people want the app on a convenient device in the first place. The point is to use them without leaving a session trail that outlives your intent to log in.
Responsible gambling tools deserve a specific mention here because they interact with the shared-device problem. Deposit limits and time-outs are account-level settings, so they follow you regardless of device. That is good news. If someone does get into your account via a restored session, your limits still apply. They are not a substitute for proper device hygiene, but they are a meaningful backstop.
Payments are the other area where a shared device raises eyebrows. The cashier in the Casushi app may offer to remember payment methods, and on a shared iPad that remembered card is visible to the next user. If you must use the app on shared hardware, decline any “save this method” prompt. The mobile site route avoids this too, because browser autofill is easier to clear and easier to keep switched off.
The short version: iCloud backup is a feature, not a flaw, but it treats your Casushi session as data worth copying. On a personal iPhone that is convenient. On a shared iPad it is a hole. Disable iCloud backup for the Casushi app on any device more than one person uses, check the session state after every restore, and consider the mobile site with a home screen shortcut if you want a setup that leaves nothing behind. If you only take one action from this piece, make it the backup toggle. It takes under a minute and closes the exact gap that Face ID cannot.
