Casushi iCloud Backups: What’s Stored and What’s Kept Out

Anyone who has restored a Casushi iPhone from an iCloud backup knows the odd mix of feelings that follows: the loyalty tier is exactly where you left it, the game history is intact, yet the cashier asks you to authenticate all over again. That is not a glitch. It is the result of a deliberate split in how the Casushi app stores data, and once you understand which files carry the no-backup flag, the restore process stops being a surprise. This deep-dive treats the Casushi app as what it is: a container of several data classes with different rules attached to each.

The short version: iCloud backups preserve game history, in-app preferences and loyalty progress; they do not preserve cashier tokens, payment credentials or anything tied to a live session. Apple users who download the Casushi app from the App Store get an iOS container that separates these categories at the file-system level, and Android users who access the Casushi site through a mobile browser sit outside the app backup model entirely. Apple’s backup rules, Google’s rules and the browser’s rules are three different rulebooks, and mixing them up is where most confusion starts.

Use this as a checklist rather than a story. Confirm what your backup actually captures, confirm what it deliberately leaves out, then decide what you need to redo by hand after a device migration. The payoff is concrete: no lost loyalty tiers, no stale payment tokens resurrected on a new handset, and no false expectation that a browser session on the Casushi mobile site will reappear after a restore. Keep the distinctions in mind and the rest of the restore process behaves predictably.

How the Casushi App Stores Data on iPhone and Android

Everything the Casushi app remembers about you lives in one of three places: an on-device container, the platform keychain, or a cloud sync layer. Knowing which is which saves a lot of guesswork when you swap handsets.

On iPhone, the Casushi app from the App Store is sandboxed. Its container holds the mobile lobby cache, your game preferences, session history and loyalty counters. Two sub-folders matter. Documents and Library/Application Support are included in iCloud backups by default. Anything the developer flags as excluded is skipped, and that flag is set file by file, not app by app. Apple users who restore from an iCloud backup therefore get the container back in the state it was last backed up, minus the flagged files.

Credentials follow a different path. Login tokens and biometric enrolment references sit in the iOS Keychain, which is encrypted and governed by its own accessibility classes. A Keychain item marked ThisDeviceOnly never leaves the handset, not through iCloud Backup and not through iCloud Keychain sync. The Casushi app supports Face ID logins, and that binding is exactly the kind of item kept device-local. Restore to a new iPhone and the container returns, but the biometric handshake has to be set up again.

Android works on the same principle with different plumbing. Android users access the Casushi site through a mobile browser or, where offered, a home screen shortcut that opens the same responsive layout. Casushi does not publish a standalone Android APK file, so there is no sideloaded package writing to internal storage. The browser profile does the storing: cookies, localStorage and the cached mobile lobby. Android’s Keystore protects any cryptographic keys, and Google’s backup service captures app data only for apps that opt in and only within the user’s Google account quota. Browser data is a separate matter entirely and is not part of any app backup.

That last point is the one people miss. The Casushi mobile site is a website, not an installed build. Its state lives in the browser sandbox, tied to that browser on that device. Clear site data, switch from Chrome to Safari, or move to a new phone without signing into the same browser account, and the local session goes with it. Your account on the server is untouched, but the convenience layer is gone.

Here is the checklist to keep straight:

• On-device container: lobby cache, preferences, history, loyalty counters. Backed up on iOS unless flagged; backed up on Android only if the app opts in.
• Keychain / Keystore: login tokens and biometric references. Device-bound when marked as such, never part of a standard cloud backup.
• Cloud sync: iCloud Backup for iOS containers, Google backup for opted-in Android apps. Neither touches browser storage.
• Browser session: the Casushi mobile site’s cookies and local data. Yours to manage, invisible to app backups.

One clarification worth pinning down: this website operates as an information page only. It does not hold your account, your balance or your backup. Everything described here happens between your device, the platform’s backup service and the operator’s servers.

What iCloud Backups Preserve: Game History, Preferences and Loyalty Progress

An iCloud backup of a Casushi iPhone captures the app’s Documents and Library directories along with its preferences plist. That is a narrower slice than most players assume, but it covers the things you would actually miss after a device swap. Here is what travels, what it looks like on restore, and where the edges of the backup are.

Session and game history. The Casushi app writes each session record to a local database inside its container: game title, stake, spin or hand count, timestamp, and outcome. iCloud picks this up on the next automatic backup, which runs when the phone is locked, charging, and on Wi-Fi. Restore that backup to a new iPhone and the history tab repopulates within a minute or two of first launch. Two caveats worth knowing. First, the backup is a snapshot, so anything played after the last backup is absent. Second, the history is a local mirror, not the source of truth. The operator’s server holds the authoritative record, and the app reconciles against it on login, which is why a restore usually ends with the same numbers you saw before.

In-app preferences. These are small but irritating to rebuild by hand. The backup preserves notification settings, sound and haptics toggles, currency display, language, and lobby layout choices. They live in the app’s preferences file and ride along with the container. On restore, you should not need to touch a single toggle. If a preference does not survive, the usual cause is a backup taken before you changed it, not a fault in the app.

Loyalty and rewards progress. The mobile lobby includes the welcome offer and the loyalty programme, and the app caches your tier, points balance, and progress toward the next reward band locally. That cached state is inside the backup. Restore to a new handset and the loyalty screen shows your tier straight away, before you have re-entered anything. Treat this as a convenience, not a guarantee. The server is the ledger. If the cached figure and the server figure disagree after a restore, the server wins and the app refreshes.

What the restore actually looks like. Apple users who download the Casushi app from the App Store and restore from an iCloud backup will see the lobby open with history, preferences, and loyalty intact. Nothing about the restore process is Casushi-specific: it is standard iOS container restoration. The app does not need to be reinstalled separately if the backup includes it, and if you install it fresh, the container is rehydrated on first launch.

The edges. Three things sit outside this picture. Cashier tokens are excluded by design and are covered in the next section. Browser-based play through the Casushi mobile site leaves no app container to back up at all, so safari data is not captured here. And an Android handset on the same account has its own backup path, which does not read from iCloud. Keep iCloud Backup switched on, check the last successful backup date before you wipe or trade in a phone, and remember that this website operates as an information page only, so account recovery always goes through the operator, never through a third party.

The No-Backup Flag: Why Cashier Tokens Stay Off iCloud

How the no-backup attribute works inside the app container

Every Casushi iPhone install keeps its data in a sandboxed container. Inside that container sit two very different classes of files. Preferences, session logs and loyalty counters are written to paths that iOS treats as ordinary app data, so they are swept into the next iCloud backup without any extra work. Cashier tokens, payment session identifiers and cached card references are written to a path flagged with the no-backup attribute (the standard NSURLIsExcludedFromBackupKey marker). iOS reads that flag and skips the file entirely.

The trade-off is deliberate. A backup is only as safe as the weakest Apple ID protecting it. Storing a live payment token there would mean anyone who restores that backup to their own hardware inherits a session the cashier would otherwise have asked to re-authenticate. Marking the token no-backup closes that gap at the cost of one extra login step after a device swap.

Worth knowing: this is app-side engineering, not a user setting. There is no toggle in the Casushi app to include or exclude cashier data from backup, and no profile screen that reveals which files carry the flag.

What the flag covers, and what it leaves alone

Not every sensitive field is treated the same way. The split looks roughly like this:

Data type	Stored in	Included in iCloud backup
Session history and game logs	App container, standard path	Yes
In-app preferences (sound, limits, layout)	App container, standard path	Yes
Loyalty and rewards progress	App container, standard path	Yes
Cashier session tokens	App container, no-backup path	No
Payment method references	App container, no-backup path	No
Face ID enrolment for the app	Secure Enclave, device-bound	No, never leaves the device

Two rows deserve a closer look. Face ID credentials are not files at all; the private key lives in the Secure Enclave and cannot be extracted, copied or restored to different hardware. https://casushi-online.uk/app/ offers additional context worth reviewing. And the cashier tokens the app itself manages are session artefacts held server-side as well, so even a hypothetical container copy would be voided on the next authentication check.

The practical upshot: a restored iPhone carries your history and your loyalty tier, but arrives with an empty cashier. That is the design working as intended, not a bug in the restore.

What this means when you restore a Casushi iPhone

Run the checklist after any restore from iCloud:

• Confirm loyalty progress and preferences appear. If they do not, the backup predates your last session or the restore pulled an older snapshot.
• Re-enrol Face ID for the Casushi app. The old enrolment is gone because it was tied to the previous device’s Secure Enclave.
• Open the cashier and re-authenticate. Expect a fresh login and, depending on your payment method, a verification step before the first deposit.
• Check for stale push notifications. Old alerts tied to the previous install can linger in Notification Centre; clearing them avoids confusion about pending cashier actions.
• Keep the old device switched on and connected until the restore is verified, in case you need to re-trigger a backup.

One more point on scope: this website operates as an information page only and does not process accounts or payments. Anything involving cashier credentials has to be handled inside the Casushi app cashier itself, where the no-backup rules apply.

Restoring to a New iPhone: Loyalty Carry-Over and Face ID Re-enrolment

You have just unboxed a new iPhone and you are restoring from an iCloud backup taken the night before. Here is exactly what to expect when the Casushi app comes back to life, step by step.

Step 1: Restore the backup, then let the app settle. Choose the iCloud backup during iOS setup, sign in with your Apple ID, and wait for the app grid to repopulate. When you first open the Casushi app after a restore, give it a minute on a stable Wi-Fi connection. It reads its restored container, re-checks the session state, and rebuilds the mobile lobby. Your account credentials are not in the backup, so expect a login prompt rather than a straight drop into the lobby.

Step 2: Confirm loyalty progress and preferences. This is the part that works cleanly. Open the rewards or loyalty area and check three things:

• Your points balance and tier status match what you saw on the old handset.
• Any progress bars (weekly streaks, tier milestones) are intact, not reset to zero.
• Notification preferences, display settings and saved game favourites are as you left them.

If a figure looks off, force-quit the app and reopen it before contacting support. Most discrepancies are a stale local cache, not lost data. Keep the old device switched on and connected until you have verified all three, because a second restore is easier while the source handset still holds a current install.

Step 3: Re-enrol Face ID for the app. The Casushi app supports Face ID logins, but the enrolment is device-bound. The biometric template never left your old iPhone and the app’s authentication token was flagged as no-backup, so the new handset starts clean. In practice: sign in with your username and password, then approve the Face ID prompt when the app asks. If the prompt does not appear, check iOS Settings for Face ID and passcode, confirm the app is allowed to use it, then toggle the in-app biometric option off and on again.

Step 4: Re-authenticate the cashier. Payment access is deliberately the slowest thing to come back. The Casushi app cashier manages payments through short-lived tokens that are excluded from iCloud backups, so on a restored iPhone you will be asked to:

1. Re-enter your password to unlock the cashier.
2. Re-confirm Face ID at the point of a deposit or withdrawal.
3. Re-verify any saved payment method, even one you have used for months.

Have your payment details and any verification documents to hand before you start. A fresh withdrawal request may trigger a routine identity check that your old device had already passed, and that check cannot be skipped because the trust token did not travel with the backup.

Step 5: Test before you travel. Complete one small deposit and one withdrawal on the new iPhone while the old handset is still nearby. That confirms the cashier, Face ID and loyalty state all line up. Then wipe the old device: sign out of the app first, then erase it, so no residual session survives the handover.

Cross-Platform Gaps and Practical Backup Advice for Casushi Users

Android handles backups differently, and the gap matters when you switch handsets. Google’s Auto Backup for Apps covers most app data by default, but only up to 25 MB per app, and developers can exclude folders with backup rules. The Casushi Android app sits in that framework: preferences and session history can ride along to a new device if the user had Google Drive backup enabled and the developer left those files in scope. There is no equivalent of Apple’s no-backup attribute, so the exclusion of sensitive cashier data depends on how the app’s own backup rules are written, not on a platform-level guarantee. Treat Android restore as convenient but less predictable than iOS.

Browser play is a separate story. If you use the Casushi mobile site through Chrome or Safari rather than an installed app, almost nothing about your session is captured in an app backup. The mobile lobby, the welcome offer display, and your responsible play tools settings live in cookies and local storage tied to that browser profile. Android browser play can sync some of this through a signed-in Google account; Safari on iPhone stores it in the device backup only if the browser data is included, which many people switch off to save space. A fresh install of the browser, or clearing site data, resets the lobby to its default state.

Account recovery is the one path that works the same everywhere. Your balance, loyalty tier, and transaction history sit on the operator’s servers, not on your phone. Signing in on any device with your username and password, plus whatever second factor the account uses, brings all of it back. Backups only save you re-entering preferences and re-reading old session lists. That distinction is worth internalising: the backup is a convenience layer, the account is the source of truth.

Device migration checklist:

• Confirm your login credentials and second factor work before wiping the old phone. Test on a tablet or a second browser first.
• On iPhone, run a manual iCloud backup right before switching so the latest preferences and loyalty progress are captured, then restore from that backup rather than from a computer.
• On Android, check that Google Drive backup is enabled for the device and that the Casushi Android app is listed under backed-up apps.
• After restore, re-enrol Face ID or biometric login and re-authenticate at the cashier. Payment tokens were never in the backup, by design.
• If you play through the browser, note your responsible play settings manually; they will not transfer with an app backup.

Keeping payment credentials secure is mostly about not undoing the platform’s work. Do not jailbreak or root a device you use for deposits, because that strips the protections around the Keychain and Keystore. Do not sideload an APK file claiming to be the Casushi Android app; the operator does not publish one, and any such file is not a secure download. Apple users should stick to the App Store listing, and Android users should reach the site through a mobile browser and add a home screen shortcut if they want an app-like icon. Turn off push notifications for anything you do not recognise.

One last point for readers researching the app: this website operates as an information page only. It does not host the software, process deposits, or hold account data, so nothing here appears in your iCloud or Google backups either. For account recovery, device migration help, or a dispute about a missing balance, go to the operator’s own support channel with your username and the approximate date of the last transaction.

Keep a short migration checklist before you touch a new phone: confirm your Casushi login email and password work, note your loyalty tier, and check the last deposit method you used so the cashier re-authentication step is quick. On iPhone, go to Settings > [your name] > iCloud > Manage Account Storage > Backups, open your current device backup and confirm it completed after your last Casushi session. If the timestamp is older than your latest play, run a manual backup over Wi-Fi before wiping the old handset. On Android, the Casushi app data rides along with Google account backup only if backup is switched on in Settings > System > Backup; the Casushi site in a mobile browser stores nothing you can restore, so bookmark the mobile lobby and sign in fresh. Install the Casushi app from the App Store on iOS, or open the Casushi site through a mobile browser on Android, since Casushi does not publish a standalone Android APK file. Add a home screen shortcut for one-tap access and skip any third-party APK from search results.

Once you are signed in on the new device, do three things in order: re-enrol Face ID for the Casushi app, set a fresh cashier deposit method and check the withdrawal limits, then open the responsible gambling tools and reset deposit, loss or session limits to the levels you actually want. Turn push notifications on or off to taste. If loyalty progress looks short after a restore, wait for the account to sync, then contact support with your username and the date of your last session before assuming the data is gone. Treat the welcome bonus as a one-account offer tied to your profile, not to the handset, so a restore will not trigger a second claim. This website operates as an information page only and does not process registrations, deposits or account recovery, so route anything payment-related through the Casushi cashier and official support channels.