You set a £50 weekly deposit limit, you stick to it, and you assume the number holds wherever you log in. That assumption is exactly what one player tested without meaning to, and the result is a useful lesson for anyone using the Casushi app, the Casushi mobile site or any other mobile casino app. Over three weeks he tracked every deposit in a spreadsheet, played mostly through the Casushi app on his iPhone, and stayed comfortably inside his cap. Then a Saturday session on his Android phone, opened through the browser rather than the app, took him £40 past the limit he thought was locked in. Nothing was broken in the way he first suspected. The cap had simply not followed him from one access route to the other, and it took a support ticket and a round of cookie clearing to work out why.
This case study walks through what happened, step by step, in the practical tone of a troubleshooting guide. You will see how a deposit limit set in the Casushi casino app behaved in app sessions, how it behaved on the Casushi mobile site, and what the difference between the two turned out to be. The short version: stored cookies and session identifiers on the Android browser created a separate state, so the cap that governed the app did not govern the browser until those cookies were cleared. That single detail explains a surprising amount of confusion around responsible play tools on phones, and it points to a wider principle worth internalising. Limits need to sit on your account, not on a device or a browser session.
Along the way you will get a checklist you can actually use. It covers verifying your limits in account settings, signing out of stray browser sessions, clearing cookies on Android, and confirming that the same numbers show up in the Casushi app and on the Casushi mobile site before you deposit another penny. If you play across an iPhone, an Android handset and the occasional browser tab, this one is worth ten minutes of your time. The fix is simple once you know where to look, and the lesson generalises well beyond a single brand.
Why responsible play tools must work across app and browser
A deposit limit is a promise you make to yourself, and it only means something if the software enforces it every time you tap a button. On a desktop that was easy to reason about: one browser, one login, one set of controls. Mobile changed the picture, because the same account can now be reached through several doors at once.
Take the Casushi setup as a working example. Apple users download the Casushi app from the App Store and play inside a native shell. Android users access the Casushi site through a mobile browser, which may or may not be saved to the home screen as a shortcut. Some players do both, switching between an iPhone and an Android tablet on the same account. Each route is a separate piece of software with its own storage, its own login flow and its own way of remembering who you are.
Three doors into one account
When a casino offers a mobile casino app alongside a responsive site, the player experience is stitched together from parts that do not always talk to each other in the way you would expect:
- Native app: installed from the App Store, updated by the developer, and able to use Face ID logins and push notifications. The Casushi app supports Face ID logins, which means the device holds a credential rather than asking for a password each session.
- Mobile browser: no install, no update prompt, and state kept in cookies and local storage. The responsive site detects screen dimensions automatically, so it looks right on a phone without a separate build.
- Home screen shortcut: a browser tab dressed up as an app. It feels native but behaves like the browser it is, cookies and all.
Notice that Casushi does not publish a standalone Android APK file, so Android play runs through the browser by design. That single fact matters for this case study, because browser storage is where the trouble starts.
The controls themselves are usually account-level on paper. 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, session reminders and time-outs. The intention is that a limit set once applies to the account, not the device. The gap between intention and behaviour is exactly what the next section documents.
Limits work when they follow the account. They fail when a device or a browser session keeps its own version of the truth. This website operates as an information page only and does not take deposits or hold accounts, so treat what follows as a walkthrough of a real pattern rather than a set of instructions tied to one operator. Keep one question in mind throughout: if you set a limit tonight, would it still be there tomorrow on a device you have not touched in a month?
The £50 weekly deposit limit that worked in the app but not the browser
Dan, a 34-year-old shift supervisor from Leeds, set a £50 weekly deposit limit on a Tuesday evening. He did it the way most people do: opened the Casushi app on his iPhone, tapped through to the account area, chose the deposit limit option, picked £50 per week and confirmed. The app showed the new limit immediately, with a countdown to when it could be raised again. That is exactly how a deposit limit should behave, and for the next three weeks it did.
His routine was simple. Payday Friday, open the Casushi app, use Face ID to log in, head to the cashier, deposit £25, play for an hour or two. The following Friday, another £25. By Sunday the £50 allowance was spent, and any further deposit attempt in the app was blocked with a clear message. The welcome bonus he had claimed in week one was wagered through without drama. From the app’s point of view, the limit was watertight.
The problem surfaced in week four. Dan was on a train with patchy signal and the Casushi iPhone app kept stalling on the loading screen. Rather than wait, he opened Chrome on his work phone, a mid-range Android handset, and loaded the Casushi mobile site. He logged in with the same username and password, went to the cashier and deposited £20. No block, no warning. He assumed the limit had reset because it was a new week, deposited another £20 the next day, and only later realised he had put £90 through his account in seven days.
What confused him was that the mobile lobby showed his limit as active. The account page on the browser displayed the same £50 weekly figure he had set on the iPhone. Yet the cashier accepted the deposits anyway. He tried clearing his browsing data on the Android phone out of frustration, logged back in, and this time a £20 deposit attempt was refused with a message saying the weekly limit had been reached. Same account, same site, same login. The only thing that had changed was the browser’s stored data.
That detail matters. It points to a session or cookie state on the Android browser that had been created before the limit was set, and which the cashier was reading instead of the live account record. Dan’s case is not proof of a systemic flaw in any one operator’s platform, and this website operates as an information page only, so we cannot test every build. But the sequence is repeatable enough to be worth understanding, and it is the kind of thing that turns a sensible £50 cap into a figure that only exists on one device.
The practical takeaway for anyone using a mix of Casushi app and Casushi mobile site access is to verify limits from both entry points after setting them, and to treat any discrepancy between the lobby display and the cashier response as a signal to sign out, clear cookies and check again before depositing another penny.
How cookies and session data let browser play bypass a deposit limit
When the £50 cap failed in the browser, the first instinct was to blame the operator. The more likely explanation sits in the phone itself. A deposit limit is a value stored against your account, but the browser only knows about that value if it can match your session to the right account record. Cookies are how it does the matching. Break the match and the limit stops appearing, even though the account still carries it.
What the Android browser was actually storing
A mobile browser keeps a small set of files for every site you visit: a session cookie that identifies your logged-in state, preference cookies that remember currency, language and layout choices, and often a cached copy of the last pages you loaded. When the limit was set inside the Casushi app, the change landed on the account. The Android browser, however, was still holding an older session cookie from a login made before the limit existed. That cookie pointed to a session state where no cap had been recorded.
Session identifiers make this worse because they are designed to be independent. Each new login can generate a fresh identifier, and each identifier can carry its own view of the account. If the browser resumed a cached session rather than requesting a fresh one, it never asked the server for the updated limit. The result looked like a bypass. In practice it was a stale view: the account had the cap, the browser session did not.
There is a second layer. Cached pages are served from the device, not the server. A cached cashier screen can show deposit options and accept input without re-checking the limit until the final submission. Some flows re-validate at that point and some do not, depending on how the operator has built the responsive layout. Where validation happens late, a stale session can push a deposit through before the account state is consulted.
Clearing cookies fixed it because it forced the browser to forget the old identifier. The next visit triggered a fresh login, a new session, and a clean request to the server. The server returned the account with the £50 weekly cap attached, and the browser displayed it correctly. Nothing about the limit changed. Only the session that was reading it changed.
The practical lesson is that cookies and session data are not a security feature, they are a convenience feature, and they can hold an out-of-date picture of your account. Three habits close the gap:
- After setting or changing a limit, sign out of every browser session on the phone, then sign back in and check the limit is visible in the cashier.
- Clear cookies and site data for the casino domain if a limit looks wrong, then reload the mobile lobby rather than resuming a cached page.
- Treat the Casushi app cashier as the reference point: if the app shows the cap and the browser does not, the browser is the one holding stale data.
One caveat worth stating plainly. This website operates as an information page only and does not process deposits, so the behaviour described here comes from user reports rather than from logs we can inspect. If a limit genuinely fails to apply after a clean sign-in and cleared cookies, that is an operator-side fault and worth raising with support the same day.
Account-level versus device-level limits: what the case reveals
The £50 cap held in the app and vanished in the browser, and that single fact tells you almost everything about how the limit was being enforced. A deposit limit that lives at device level is really just a local setting. It belongs to a browser profile, a cookie jar, an app install, a session token. Clear the cookies and the setting is gone. Switch to a different access point and the setting never existed. The player’s account, meanwhile, sits untouched in the middle of all of it.
Account-level enforcement works the other way round. The limit is stored against the player record on the operator’s server, and every deposit request, whatever channel it arrives from, is checked against that record before the transaction is authorised. It does not matter whether the request comes from the Casushi app cashier, the Casushi mobile site on an Android phone, or a Safari tab on a Casushi iPhone. One account, one limit, one place where the check happens.
The case reveals the practical risk of the alternative. Device-level and session-level controls create what amounts to several parallel versions of the same player, and the strictest version is not necessarily the one in force. Consider how that plays out across the access points a typical player uses:
- Casushi Android via browser: a fresh session with cleared cookies can behave as though no limit was ever set, which is exactly what happened in the case.
- Casushi iPhone via app: the limit shows correctly in account settings, giving a false sense of security about the other channels.
- Casushi mobile site on a second device: a tablet or an old phone signed into the same account may carry its own stored state and its own view of the cap.
- Private or incognito browsing: no persistent cookies means no persistent local limit, so every session starts from scratch.
None of these gaps require anyone to behave badly. A player who genuinely wants to stick to £50 a week can drift past it simply by opening the browser instead of the app on a Thursday evening. That is the core danger of device-level controls: they depend on the player remembering which door they came in through, at the exact moment their judgement is weakest.
There is a second, quieter risk. Session-level limits can make a player believe they are protected when they are not, which is worse than having no limit at all, because it removes the caution they would otherwise apply. The Casushi mobile site offers responsible play tools, and the Casushi app supports the same account settings, but the value of those tools depends entirely on the limit being written to the account rather than to the device. When you set a limit, the question to ask is not “did it save?” but “where did it save, and will the browser respect it?”
The lesson from the case is blunt. Treat any limit you cannot see reflected in your account settings, from a different device, as unconfirmed. Account-level enforcement is the only model that follows the player across app, browser and handset, and it is the standard worth checking every time you set a cap.
Setting deposit limits correctly across the Casushi app and mobile site
Here is the routine that fixed the £50 cap in the case study, and it takes about ten minutes from start to finish. Work through it once, then repeat the last step any time you switch between the Casushi app and a mobile browser.
Step 1: Set the limit from the account menu, not a game screen. Sign in to the Casushi app and open your account settings before you open any lobby or game. Navigate to the responsible play section and set your weekly deposit limit there. Setting it from a game screen or a cashier prompt can attach the limit to that session rather than the account, which is exactly how the £50 cap went missing for the Android browser user in the case study.
Step 2: Note the confirmation details. When the limit saves, the app shows a confirmation with the amount, the period and the date it takes effect. Screenshot it. You will need that timestamp in step 5 to confirm the same rule shows up in the mobile site, and it settles any dispute about when the limit started.
Step 3: Sign out of every browser session. Open Chrome, Samsung Internet or whichever browser you use for the Casushi mobile site, and sign out of the account rather than just closing the tab. A signed-in browser session holds a session identifier that can keep the old state alive. Signing out forces a fresh handshake with the server on your next login.
Step 4: Clear cookies for the casino domain. In the browser settings, find site data or cookies for the casino domain and delete them. On Android, Chrome’s Settings > Site settings > All sites lets you search the domain and clear storage in two taps. On iPhone Safari, Settings > Safari > Advanced > Website Data does the same job. This is the step that restored the limit in the case study, so do not skip it because the app looks fine.
Step 5: Log back in through the browser and verify. Open the Casushi mobile site, sign in, and go straight to the responsible play page. The £50 weekly figure should appear with the same effective date you screenshotted in step 2. If it does not, stop depositing through the browser and contact support with both screenshots before you play again.
Step 6: Test with a small deposit. Make a £10 cashier deposit through the browser and check your remaining weekly allowance in the app. The two figures should move together. If the app shows £40 left and the browser still shows £50, the limit is sitting at device level and needs escalating to support.
Step 7: Repeat after updates and cache clears. Run the browser check again after any app update, after clearing your phone’s cache, and whenever you add the site to your home screen shortcut on a new device. It takes two minutes and catches drift before it costs you.
What operators and players should check before relying on mobile play tools
Before you trust any deposit limit to hold, ask the boring questions. The case above shows that a limit which looks correct in one place can behave differently in another, and the gap is usually in session handling rather than in the number you typed. Use the checklists below as a quick audit.
For operators: cross-channel enforcement questions
- Is the limit stored against the account ID and enforced server-side on every deposit request, regardless of whether the request comes from the Casushi app, the Casushi mobile site or an in-browser session?
- Does the cashier reject a deposit that would breach the cap even when the client sends a stale session token? If the check happens only in the app’s local state, it is not a limit, it is a suggestion.
- Are cookies and session identifiers scoped so that clearing them cannot reset limit state? A new session should inherit the account’s existing limits immediately, with no grace period.
- Does the mobile lobby include the welcome offer alongside a clear, visible summary of any active limits, so the player sees the cap before opting in rather than after?
- Are responsible gambling tools surfaced identically across iOS casino software and Android browser play? Compare the two side by side on the same account and confirm the same figures appear.
- Is there a log the support team can pull showing every deposit attempt, the channel it came from, and whether it was allowed or blocked? Without that, disputes become guesswork.
- Does the responsive site detect screen dimensions automatically without altering limit logic? Layout adapts; enforcement must not.
For players: verification steps
- Set your limit in account settings, not in a device menu. Then sign out completely on every device.
- On Casushi iPhone, reopen the Casushi app, check the limit figure, and confirm it matches what you set. If the app supports Face ID logins, re-authenticate rather than relying on a cached session.
- On Casushi Android, clear cookies and site data in the browser, then sign in to the Casushi mobile site and check the same figure. Repeat in a private or incognito window as a control.
- Test with a small deposit that would breach the cap. It should be refused on every channel. If it goes through anywhere, stop and contact support before depositing again.
- Turn off push notifications for a day and confirm your limits still apply. Notifications are a prompt, never a control.
- Re-check after any app update or after switching between the Casushi casino app and browser play. Updates can reset local preferences even when the server record is intact.
One note on downloads: Apple users download the Casushi app from the App Store, while Android users access the Casushi site through a mobile browser. Casushi does not publish a standalone Android APK file, so any APK claiming to be the app is not an official route and should not be trusted with your login. This website operates as an information page only, so verify limits inside your own account rather than taking any guide’s word for it.
The short version: a limit you cannot see enforced on a second device is not yet verified. Check it, test it, and only then rely on it.
Before you next open a mobile casino, spend five minutes proving your limit travels with your account rather than your device. Sign in to the Casushi mobile site in a private browser window, set or check your weekly deposit cap in the account settings, then make a small test deposit and watch the remaining allowance drop. Close the tab, reopen the site normally, sign in again and confirm the same figure appears. Do the same in the Casushi app on your iPhone or Android handset. If the numbers match across all three entry points, your limit is sitting at account level where it belongs. If any session shows a fresh allowance, treat it as a red flag and contact support before you deposit again.
Keep a short written record of what you set and when: the cap amount, the date, the channels you tested and the response you got from the cashier screen. It takes a minute and gives you something concrete to quote if a browser session ever ignores the cap again. While you are in the settings, switch on the other responsible gambling tools the Casushi mobile site offers, such as session reminders and time-outs, and check whether they follow you between the Casushi app and browser play in the same way. Apple users who download the Casushi app from the App Store can also enable Face ID logins, which makes it quicker to sign back in and verify that your limit is showing correctly after a browser session. Android users who access the Casushi site through a mobile browser should clear cookies at the end of each session, or use a private window, so stale session data cannot build up. Remember that Casushi does not publish a standalone Android APK file, so any download prompt claiming otherwise is not the real thing. This website operates as an information page only and does not take deposits or hold accounts, so always verify limits inside the casino itself. Set a calendar reminder for the first of each month to repeat the check, and if a limit ever fails to apply, stop playing, screenshot the evidence and escalate it the same day.