Case study: why a Screen Time passcode wasn’t enough

Getting the Casushi app onto an iPhone takes a couple of minutes, and so does setting a Screen Time passcode. That speed is exactly why so many parents stop there. The logic feels airtight: the passcode is set, the child does not know it, the phone is locked down. Then a statement arrives. In the case we looked at, a 13-year-old triggered a deposit through the Casushi app’s welcome bonus without ever typing the passcode, because the setting everyone trusted was never the setting that mattered.

This case study walks through what happened on one household’s device, step by step. The parent had installed the Casushi iPhone app on a shared family phone, set a four-digit Screen Time passcode, and confirmed that the App Store listing was hidden from the child’s profile. What nobody checked was whether in-app purchases were still live. They were. The Casushi app supports Face ID logins for the account holder, and on a device where the child’s face was enrolled as an alternative appearance, that biometric unlock carried the deposit straight through the cashier without a single passcode prompt. The welcome offer was credited, the money left the linked card, and the Screen Time passcode had done precisely nothing to stop it.

The lesson is not that parental controls fail. It is that a passcode protects the settings screen, not the money. Blocking the Casushi casino app and the Casushi mobile site properly means pairing that passcode with in-app purchase restrictions, a review of who is enrolled in Face ID, and a habit of checking the cashier settings after every iOS update. The sections below break down the gap, the fix, and what other parents should audit before the same thing happens on their phone.

The Setup: A Screen Time Passcode on an iPhone With the Casushi App Installed

Daniel, 41, works in logistics and keeps his iPhone 13 as the family’s “spare” handset on weekends. His 14-year-old son uses it for YouTube and school research. In March, Daniel installed the Casushi app from the App Store, claimed the welcome offer, and played a few sessions of blackjack. He then set a four-digit Screen Time passcode, told his son the code was private, and assumed the job was done. That assumption is the starting point of this case study.

What Was Actually Configured on the Device

Daniel did three things, all of them sensible on paper. He enabled Screen Time under Settings, set a passcode that differed from the phone unlock code, and turned on “Require passcode” for changes to account settings. He did not touch the Purchase Restrictions section, did not review Face ID permissions, and did not open the Casushi app cashier to check what a logged-in session could reach.

The Casushi app supports Face ID logins, which Daniel had enabled for convenience. His face was enrolled, his son’s was not, and the app sat on the second home screen next to a weather widget. On the surface, the setup looked tight: a locked phone, a passcode on Screen Time, and a biometric gate on the app itself.

What Daniel had not accounted for was how much of the Casushi experience lives outside the native app. The Casushi mobile site loads in Safari with a responsive layout that detects screen dimensions automatically, so the same account works on any browser without an install. The mobile lobby includes the welcome offer, and the cashier deposit flow is identical whether you arrive through the app or the site. A passcode on Screen Time does not intercept a browser session.

He also missed the Android angle. His daughter’s tablet runs Android, and Android users access the Casushi site through a mobile browser rather than a store download, because Casushi does not publish a standalone Android APK file. There was no app icon to hide on that device, no App Store listing to restrict, and no obvious place for a parent to look.

For two weeks the arrangement held. Daniel checked the Screen Time weekly report, saw modest usage, and read nothing into it. The report showed time in Safari and time in the Casushi app, but it did not show which account was signed in, which payment method was attached, or whether a bonus had been claimed. Screen Time measures minutes, not transactions.

The assumption, stated plainly, was this: a passcode protects the device, therefore it protects the money. The rest of this case study shows why that logic breaks on a casino app, and what Daniel found when he finally opened the cashier and compared the deposit history against his own bank statement.

The Gap: Why the Casushi iPhone App’s Welcome Bonus Still Went Through

The passcode was on. Four digits, changed monthly, not written down anywhere. So when the deposit confirmation appeared on the phone’s screen, the parent’s first reaction was that someone had guessed it. The transaction history said otherwise: no passcode prompt had been triggered at all.

Here is the mechanism. On an iPhone, the Screen Time passcode governs Screen Time settings and app limits. It does not govern purchases. Those sit under a separate switch in Settings > Screen Time > Content & Privacy Restrictions, labelled In-App Purchases, and by default on a device where Screen Time has just been switched on, that switch is still green. Apple users who download the Casushi app from the App Store and then set a passcode often assume one lock covers the other. It does not.

The Casushi app supports Face ID logins, and Face ID is the second half of the story. Once the account was authenticated biometrically, the cashier treated the session as verified. The welcome bonus deposit, a modest first amount tied to the mobile lobby’s welcome offer, went through the Casushi app cashier without a single digit being typed. The passcode protected the settings. It never stood between the child and the money.

What the audit actually showed, in order:

  • The Screen Time passcode was active and had not been shared.
  • In-App Purchases was still enabled, so the purchase layer was open.
  • Face ID was enrolled for the Casushi app and approved the deposit in under a second.
  • The card stored in the Apple account, used months earlier for a one-off top-up, was still on file.
  • No purchase confirmation email had been opened, because the notification went to an inbox the parent checks weekly.

None of those five facts is a flaw in the app. Each is a default that makes life easier for the person paying, and together they make a Screen Time passcode look far stronger than it is. A passcode is a lock on a door in the hallway. In-app purchases are the window at the back.

The timing matters too. The deposit landed inside a bonus window that the mobile lobby promotes on first login, which is exactly when a curious teenager with a parent’s unlocked phone is most likely to poke around. There was no standalone Android APK file involved here, no sideloaded package, nothing exotic. Just a phone left on the kitchen counter for twenty minutes with a biometric login already set up and a purchase switch nobody had thought to check.

The lesson from this part of the case is narrow and practical: a Screen Time passcode and a purchase restriction are two different settings in two different places, and setting one gives a false sense of coverage. https://casushi-online.uk/app/ offers additional context worth reviewing. The parent in this story had done the thing most guides recommend. It was not enough, and the transaction log proves it.

The Fix: Disabling In-App Purchases and Passcode-Protecting Every Cashier Deposit

The first thing I did was switch off in-app purchases completely rather than just tightening the passcode. On iOS 16 and later that lives under Settings, then Screen Time, then Content and Privacy Restrictions. I enabled restrictions, set a Screen Time passcode different from the device unlock code, then went into iTunes and App Store Purchases and set In-app Purchases to Don’t Allow. That single toggle is what stops the Casushi app cashier from opening a payment sheet at all, because the store layer never hands the transaction through. On older iOS builds the same option sits under Allow Apps and Features or under the purchases list in Screen Time, depending on the version.

With purchases blocked, the next layer was the app itself. The Casushi app supports Face ID logins, and that is exactly how the deposit slipped through before: the child looked at the phone, the biometric check passed because their face was enrolled, and the cashier treated it as an authorised session. Removing the child’s face from Face ID and leaving only mine closed that route. I also turned off push notifications for the app, since a bonus reminder landing on the lock screen is a nudge nobody needs on a shared handset.

The Android side needed a different approach, because Android users access the Casushi site through a mobile browser rather than a store build. Casushi does not publish a standalone Android APK file, so there was no app to restrict. Instead I set up a restricted profile in Google Family Link, blocked the browser’s ability to save card details, and enabled purchase confirmation for every transaction on the Google account. Any cashier deposit from that profile now needs my approval code, which arrives on my own phone.

For the iPhone, the practical routine looks like this:

  1. Confirm In-app Purchases is set to Don’t Allow in Screen Time restrictions and that the Screen Time passcode is not the same four digits as the unlock code.
  2. Check Face ID enrolled faces under Settings, then Face ID and Passcode, and delete anything that is not mine.
  3. Before any session on the Casushi casino app, verify that the cashier shows the deposit limit I set rather than the child’s previous amount.
  4. Re-check after every iOS update, because major releases occasionally reset the purchases toggle to Allow.

One trade-off worth naming: blocking in-app purchases also blocks ordinary App Store spending, so the child cannot buy a game or a subscription without me entering the passcode. That friction is the point. A passcode that only guards the Screen Time menu is a lock on the door of an empty room; the purchase restriction is the bolt that actually holds.

I also wrote the Screen Time passcode down nowhere near the device, and set the Casushi mobile site to require the passcode for each cashier deposit rather than remembering the session. On a responsive site that detects screen dimensions automatically, the cashier layout shifts between phone and tablet, so I tested the flow on both sizes to be sure the passcode prompt appeared every time and did not default to a saved card.

What This Means for Parents Using the Casushi Casino App and Mobile Site

The passcode was never the problem. The gap was that it only guarded one door. If you are running a similar setup at home, the lesson is not to ditch Screen Time but to treat a passcode as half a lock and pair it with purchase restrictions on every route into the account.

Start with a full audit, not just a glance at the settings menu. Open Screen Time, then Content and Privacy Restrictions, and check four things in order: iTunes and App Store Purchases (set to Don’t Allow for installing apps, deleting apps and in-app purchases), Allowed Apps, Content Restrictions and the Passcode settings. Then open the Casushi app itself and walk the cashier screen. If a deposit button can be tapped without a passcode prompt, the restriction is incomplete, no matter what the Settings screen says.

Remember that the Casushi iPhone app is only one entry point. Android users access the Casushi site through a mobile browser, and a browser session bypasses App Store restrictions entirely. The Casushi mobile site offers the same welcome offer and the same cashier, so a browser-level passcode or a locked-down guest profile on the Android device matters just as much. The Casushi app does not publish a standalone Android APK file, which removes one common risk (sideloaded installs), but it does not remove the browser route.

Face ID is convenient and, in this context, a liability. The Casushi app supports Face ID logins, so a child holding the phone near the parent’s face, or a saved biometric on a shared device, can confirm a payment in seconds. Turn off biometric confirmation for purchases at the device level, or keep the casino app behind a separate passcode that is not the same as the unlock code.

Push notifications deserve a mention too. Bonus alerts and deposit prompts arrive on the lock screen and create exactly the kind of nudge that turns a curious tap into a transaction. Disable notifications for the app in iOS Settings, or set them to deliver silently, and check the mobile lobby for any promotional opt-ins that can be switched off inside the account.

Finally, use the responsible gambling tools as a second layer. The Casushi mobile site offers deposit limits, session reminders and time-out options. Setting a low deposit limit does not replace a passcode, but it caps the damage if a restriction is missed during an update. Recheck everything after each iOS update, since major releases have a habit of resetting or quietly changing restriction behaviour.

Setup What it blocks What it misses Effort to maintain
Screen Time passcode only Settings changes, app deletion In-app purchases confirmed by Face ID, browser access Low, but the weakest option
Passcode plus in-app purchases off Deposits through the Casushi app cashier Mobile site in Safari or Chrome Low, recheck after iOS updates
Passcode, purchases off and browser restrictions App and mobile site deposits Nothing significant for a child’s profile Medium, needs a monthly audit
Full lockdown plus responsible gambling limits All routes plus spend caps Nothing, but it is inconvenient for adult use High, best on a child-only device

One last point worth stating plainly: this website operates as an information page only. It does not take deposits, host games or hold accounts. Every setting described here lives on your device or inside the operator’s account tools, so the audit has to happen there, with the phone in your hand.

If you take one thing from this case, make it the order of operations: change the settings first, then hand the device over. Open Settings > Screen Time > Content & Privacy Restrictions, set In-App Purchases to Don’t Allow, and confirm Ask to Buy is on for the Apple ID tied to the Casushi iPhone install. Then reopen the Casushi app and walk through the cashier once yourself, so you can see where Face ID kicks in and where the Screen Time passcode should now interrupt a deposit. If a payment sails through without a prompt, something is still switched off, and that is the moment to fix it rather than a week later.

Repeat the audit on every device in the house, not just the one you set up. On an Android phone, where the Casushi site loads through a mobile browser rather than a store listing, check the browser’s saved payment methods and clear any stored card details, then add a home screen shortcut so you can spot the icon at a glance during a spot check. Do the same on a tablet that shares the Apple ID, because restrictions follow the account, not the handset. Diarise a monthly review of the mobile lobby’s responsible play tools, deposit limits and session reminders included, and set a calendar alert for it. Ten minutes a month beats a surprise statement. And keep the framing simple with your teenager: these are settings on your device, not a verdict on their character. The screenshots from this case are a useful starting point, so save them somewhere you will find them again.