Most complaints about casino alerts start with a wrong assumption: that one switch controls everything. It does not. On a phone, Casushi notifications are governed by three separate layers, each with its own owner and its own persistence. The device operating system holds the permission to display anything at all. The Casushi app or mobile site holds its own marketing preferences. Your Casushi account holds the consent record that sits alongside responsible play tools and the rest of your account settings. Only that last layer is contractual, and it is the only one that survives a reinstall. Treat the other two as disposable and you will stop being surprised when alerts reappear after an update.
Layer one: OS-level permission is a blunt instrument
Start with the phone itself. On iOS, the relevant path is Settings, then Notifications, then the Casushi app if it is installed, or Safari and your browser of choice if you play through the mobile site. On Android, it is Settings, then Apps, then Casushi, then Notifications, with a separate channel section on newer versions of the operating system. The permission you grant here is binary in practice: either the app may push notifications or it may not. There is no meaningful way to say “send me withdrawal confirmations but nothing about Big Bass Splash” at this layer.
That bluntness is why the OS switch is the least useful of the three for managing a casino bonus relationship. It is a fire door, not a dimmer. If you revoke it, you lose everything, including the alerts that actually matter, such as a verification request or a withdrawal status change. If you leave it on, you have handed the app permission to interrupt you whenever its marketing logic decides to. The permission also resets in practice more often than people expect: a reinstall, a major OS upgrade, or clearing app data can all put the prompt back in front of you.
What the OS layer will and will not remember
The OS remembers that you once said yes or no, and it generally respects a no until something changes the app’s identity. It does not remember why you said no, and it has no concept of your Casushi account, your deposit history, or the fact that you asked to be left alone during a self-exclusion period. Those distinctions live further up the stack. A skeptic’s rule of thumb: never rely on the phone’s settings to enforce a decision about gambling marketing, because the phone does not know you are a gambler.
One practical wrinkle for UK players: if you use the Casushi app, the permission applies to the app. If you play in a browser, it applies to the browser, and browser-level notification prompts are easy to dismiss by accident and fiddly to find again later. Decide which route you actually use before you go hunting through menus, because fixing the wrong one is a common waste of ten minutes.
Layer two: in-app marketing preferences are local and fragile
Inside the Casushi product, there is usually a preferences area where you can toggle categories of communication: promotional pushes, bonus reminders, game launch announcements, and so on. This layer is more granular than the OS switch and less durable than your account record. It lives with the app installation or the browser session. Uninstall the app, reinstall it, and you should assume those toggles return to their defaults until you check them again.
This is the layer most people confuse with consent. It is not consent in any legal or contractual sense; it is a product setting. The distinction matters because the Casushi welcome offer, which requires a £10 deposit and £10 staked on slots to unlock 40 free spins on Big Bass Splash, is tied to your account, not your handset. Turning off promotional pushes in the app does not withdraw anything from your account record, and turning them back on does not re-opt you into anything you previously refused at account level.
Where the promo code fits into this layer
The promo code WELCOME2026 is entered during registration or in the cashier, and it is an account-level action, not a device-level one. That is worth stating plainly because the layers get muddled in practice. A player who registers on a laptop, installs the Casushi app a week later, and then wonders why the welcome offer terms look unfamiliar has usually just met the difference between a local setting and an account record. The code, the £10 deposit, the £10 staked on slots, and the resulting 40 free spins all attach to the account. Free spin winnings are paid as cash with no wagering, which is a genuinely useful term and one you will not want to lose track of because of a notification toggle.
My advice on this layer is to treat it as cosmetic. Set it to whatever makes your phone tolerable, then forget it, because it will not survive a reinstall and it will not protect you from anything. The settings that do the real work are one level further in.
Layer three: account-level consent is the one that counts
Your Casushi account holds the consent record for email and SMS marketing, and it sits in the same administrative space as the responsible play tools: deposit limits, loss limits, session reminders, time-out and self-exclusion. https://casushi-online.uk/ offers additional context worth reviewing. This is the layer that matters, and it is the only one that is contractual. Withdraw consent here and it stays withdrawn across devices, reinstalls, and new handsets. Change it here and the change is recorded against your account, not against a piece of software on your phone.
Casushi is licensed by the UKGC, and the licence is held by Solaya Group Limited. That licensing arrangement is why the account-level record exists at all. UKGC-licensed operators operate under rules that treat marketing consent as a documented, revocable choice, and casino regulation in the United Kingdom expects the operator to be able to show what you agreed to and when. The OS permission on your iPhone does not satisfy any of that. It is a display setting. The account record is the audit trail.
This is the information gain worth internalising: if you want a durable change to what Casushi sends you, make it in the account, then verify it by email or live chat. Do not make it by swiping a toggle in the app and hoping. The app toggle is a convenience for the operator and a trap for the player who assumes it is the source of truth.
There is a secondary benefit to keeping consent decisions at account level. Responsible play tools and marketing consent sit close together, and that proximity is useful. If you have set a deposit limit or taken a time-out, you want the marketing side to reflect that state rather than run on a separate track. The account layer is where those two conversations meet. The device layer knows nothing about either.
The checklist, plus the withdrawal and support details worth pairing with it
Run this in order, and run it again after any reinstall, OS upgrade, or change of handset. The order matters because each layer overrides the one before it in different ways, and checking them out of sequence produces false confidence.
- Device OS permission. Check Settings on the phone and confirm whether Casushi (app or browser) is allowed to send notifications at all. Decide deliberately rather than leaving it on by default.
- In-app marketing preferences. Open the Casushi product, find the notification or marketing section, and set the categories you want. Note that these are local and will not survive a reinstall.
- Account-level email and SMS consent. Log in, open account settings, and confirm what is recorded against your account for email and SMS marketing. This is the contractual setting and the only one that persists.
- Responsible play tools. While you are in account settings, review deposit limits, session reminders, and any time-out in place. Consent and limits should tell a consistent story.
- Verification and withdrawal readiness. Confirm your identity documents are approved so that a withdrawal is not delayed by casino verification later. Alerts about a pending withdrawal are the one category most players actually want.
- Support confirmation. If you have changed consent and want certainty, ask casino support by live chat or email to confirm the change on your account record. Keep the reply.
The last two items connect to a part of the Casushi guide that covers withdrawal times and payment methods, and it is worth reading alongside this checklist. Notification settings and cashout friction are related frustrations. A player who has verified early and knows which casino payment methods clear fastest spends less time refreshing an app for status updates, which reduces the temptation to leave every alert switched on just in case.
On the games side, the casino games lobby at Casushi covers slots, live casino, roulette, blackjack and game shows, and the promotional calendar includes Drops & Wins 2026 and a daily promotional game called Daily Catch. Those are exactly the features that generate push notifications, so if you find the volume irritating, the fix is at account level, not on the phone. A daily game is designed to bring you back daily; that is the product working as intended, and the only honest counter is a deliberate consent choice rather than a grudging tolerance of pings.
One more note for anyone weighing up the app: the Casushi app is a convenience, not a requirement, and the notification layers behave slightly differently depending on whether you install it or play in a browser. If you are the sort of player who reinstalls apps to clear clutter, stay browser-first and manage everything at account level. You will lose nothing important and you will spend far less time re-ticking boxes that were never the real setting anyway.
Work through the six items once, write down what you chose, and diarise a recheck for the next time you change phones. The OS permission and the in-app toggles will drift; the account record will not. Keep your consent decisions where the licence lives, keep your verification tidy so withdrawals do not nag you, and treat every push notification as a convenience you can revoke rather than a feature you have to endure.