If you have ever restored an iPhone from an iCloud backup and watched the storage bar fill up, you know the anxiety of not knowing what is inside each app’s slice. For anyone running the Casushi app on an iPhone or iPad, the question is sharper than usual: does that backup contain card details, bank references or session tokens, or is it just a shell of preferences and cached lobby assets? The answer is verifiable in about ninety seconds, and the check is worth doing once and then again after any major update. This article gives you a reporter’s checklist for confirming, in Settings, exactly how much space Casushi is claiming and what that figure tells you about payment data.
Start with the iCloud Manage Storage figure
Open Settings, tap your name at the top, then iCloud, then Manage Account Storage (on older iOS builds it reads Manage Storage). Scroll the backup list until you find your device name, tap it, and look for Casushi in the per-app breakdown. The number beside it is the honest answer to the question in the headline. A well-behaved casino client on iOS should sit comfortably under 50 MB in a backup, because what gets backed up is preference plists, session flags and a thin cache, not the payment rails themselves.
Why 50 MB as the threshold? A typical iOS casino client’s real payload is a few megabytes of settings. Anything approaching or exceeding 50 MB suggests the app is stashing something heavier: downloaded lobby imagery, cached game bundles, or, in a badly built app, transaction history written to local storage. Casushi’s own architecture keeps account and cashier activity server-side, so a bloated backup entry is more likely to be cache than card data. Still, the size is your first signal, and it costs nothing to read it.
Write the figure down. Note the date. If you repeat the check in a month and the number has jumped by tens of megabytes without you using the app more heavily, that is a change worth investigating before your next cashier deposit.
Interpret the number before you panic
Under 50 MB is the green light. It means the backup is carrying configuration, not financial records. Payment data in a properly built iOS casino app lives behind the cashier, which talks to the operator’s servers over encrypted connections; nothing about a card or a bank transfer needs to sit in a local backup file. The Casushi app cashier manages payments server-side, so the backup entry should stay lean.
Between 50 MB and roughly 200 MB, treat it as amber. The usual culprit is cached media: promotional banners, game thumbnails, short audio loops. Delete the app’s cache if the app offers that option, or offload and reinstall the app, then re-check the backup size after the next overnight backup cycle. If the figure drops back under 50 MB, you have confirmed it was cache.
Above 200 MB, or any figure that grows steadily week on week, is red. That is not normal for a lobby client. Review the app’s in-app data and privacy settings, look for any „save history locally“ style toggles, and consider excluding Casushi from the iCloud backup entirely (toggle it off in the same per-app list) until you are satisfied. Excluding it does not affect your account; your balance and history live on Casushi’s servers, not on your phone.
What a small backup actually proves
A sub-50 MB entry proves the app is not writing large local records. It does not prove the app never touches payment data in memory during a deposit, and no storage check can prove that. What it does prove is that nothing payment-shaped is being persisted into Apple’s cloud on your behalf. Combined with Face ID logins, which keep credentials out of the app’s stored files, that is a reasonable posture for a mobile casino app.
One caveat for iPad users: if you run Casushi on both an iPhone and an iPad, check each device’s backup separately. https://casushi-online.uk/app/ offers additional context worth reviewing. The per-app sizes will differ, and the iPad entry is often the larger of the two because of cached lobby artwork at higher resolutions.
Adjust app data settings and trim the backup
If the figure is larger than you would like, the fix is a short sequence rather than a deep dive. First, inside Casushi, hunt through the settings area for anything labelled cache, downloads or storage, and clear it. Second, in iOS Settings, scroll to Casushi in the main app list and review the permissions it holds; location and background app refresh are the two that quietly inflate local data. Third, return to the iCloud per-app backup list and toggle Casushi off if you want a guaranteed zero footprint, or leave it on once the size is back under 50 MB.
Push notifications are worth a mention here. They do not add meaningful backup weight, but they are the one channel through which a casino app can nudge you toward a deposit. If you are auditing the app’s footprint, decide deliberately whether you want them on. Turning them off in iOS Settings has no effect on your account or the welcome offer sitting in the mobile lobby.
Repeat the check after any app update. Updates occasionally reset cache behaviour, and a version that was lean in March can be heavier in June. The Manage Storage screen is the single source of truth for this, so bookmark the path mentally: Settings, Apple ID, iCloud, Manage Storage, device, Casushi.
Separate the iPhone app from the Android route
Apple users download the Casushi app from the App Store, and that listing is the only official install route on iOS. There is no sideloading story to worry about, which is one reason the backup check above is reliable: the binary comes from Apple, signed and sandboxed, and its data container is inspectable through the storage screen.
Android is a different picture. Casushi does not publish a standalone Android APK file, so there is no APK to scan for payment-skimming code, and no Android equivalent of the iCloud per-app size check. Android users access the Casushi site through a mobile browser, typically Chrome, and the responsive site detects screen dimensions automatically to serve the right layout. Browser play keeps data in the browser’s own storage, which you can clear from Chrome settings whenever you like. Add a home screen shortcut and you get an app-like launch without an installed package.
On either platform, the Casushi mobile site offers responsible play tools, and the mobile lobby includes the welcome offer, so nothing about the experience is lost by skipping a native install. For Android, the shortcut-plus-browser route is arguably the cleaner privacy choice, because there is no app container to audit at all.
The practical wrap-up: run the iCloud check today, confirm Casushi sits under 50 MB, and if it does not, clear the app cache, review in-app data settings, and toggle the app out of your iCloud backup until the figure settles. Note the date and the number, re-check after updates, and treat any sudden growth as a prompt to look again. This website operates as an information page only and does not process deposits, so the verification belongs in your own Settings app, on your own device, where the evidence actually lives.