Blog
How to Confirm Group-Wide Self-Exclusion at Sister Casinos
You ask one casino to close your account for six months, then a week later a promotional email lands from a brand you have never played at, on the same platform, with the same games. That is the gap most players miss: a self-exclusion is only as wide as the licence and group structure behind it. If you are searching for Ruby Fortune sister sites because you want a break rather than a new place to play, the question worth asking is whether an exclusion at one brand actually covers the rest of the group.
Short answer: sometimes yes, sometimes not automatically. Ruby Fortune and many casinos like Ruby Fortune run on shared platforms under common ownership, but a block applied at one domain does not always propagate to every sister brand without a request in writing. This guide shows how to confirm group-wide self-exclusion instead of trusting a single-site button, how to phrase the request to support at each sister site, and what proof to keep if a site like Ruby Fortune still lets you log in.
Expect concrete steps: a support ticket template, a checklist for matching brands to the same operator, and the escalation route when a sister casino ignores the block. None of this requires a deposit, and you can start before you close your account. If you are comparing Ruby Fortune alternatives for any reason other than play, do the exclusion check first.
How Self-Exclusion Works Across Ruby Fortune Sister Sites
Ruby Fortune runs on the Microgaming (now Games Global) platform, and it sits inside a cluster of brands operated under shared licensing arrangements. That structure is the reason a self-exclusion request can travel further than the site where you made it. The brands people list as Ruby Fortune sister sites are typically not independent businesses with separate compliance departments. They share account systems, payment processing and, in most cases, a single responsible gambling policy covering every domain in the group.
Practically, that means an exclusion flagged on one brand can propagate to casinos like Ruby Fortune across the same operator. The mechanism is usually a central player record keyed to your identity: name, date of birth, address, email and sometimes payment details. When support marks that record as excluded, the flag is read by every brand pulling from the same database. A block placed on one site alone, without the group flag, is the weak version. It stops you logging in there and does nothing at the next domain you try.
Licensing adds a second layer. Group brands often hold registration with more than one regulator, and the rules on what self-exclusion must cover differ by jurisdiction. Ontario is the clearest example: the listed casinos in this space are not available to Ontario players, so an Ontario resident cannot open an account at most Ruby Fortune alternatives in the first place. Players outside Ontario deal with offshore casino operators licensed in places like Malta or Kahnawake, where group-wide exclusion is expected but the enforcement mechanics vary. Ask support which licence covers your account before you assume the exclusion is automatic everywhere.
Two things routinely trip people up. First, sister sites of Ruby Fortune may run on the same platform but under a different operating entity for a specific market, which splits the player database. Second, a «cooling off» period of 24 hours to six weeks is not the same as self-exclusion, and some support agents will apply the softer option unless you say otherwise. Use the words «self-exclusion» and «all brands in the group» explicitly.
The takeaway for anyone weighing a break: the shared platform is your ally, but it is not a guarantee. Verify the flag rather than trust it. The next section covers how to confirm group-wide coverage instead of a single-site block.
Confirming a Group-Wide Exclusion Instead of a Single-Site Block
A self-exclusion request is only as strong as the scope written on it. Ask support for «self-exclusion» and many agents will action a single-account block on that brand, log it, and move on. That block stops you at one domain. It does nothing at Ruby Fortune sister sites running the same wallet, the same account database, or the same parent licence. If the goal is a real break, the request has to name the group and come back to you in writing with the scope spelled out.
Steps to confirm the scope before you rely on it
- Name the group, not just the brand. In your first message, write that you want exclusion applied across all casinos operated under the same licence and account system, and list the sister domains you know of. Vagueness is where single-site blocks slip through.
- Ask for the scope in writing. Request an email or chat transcript that states which brands are covered and the exact start and end dates. A chat window you close is not proof. A timestamped email is.
- Test one sister site after 24 to 48 hours. Try to log in to a second brand in the group. If the exclusion is live, the account should be blocked or the login refused. If you get in and can deposit, the block was single-site.
- Check the marketing side too. Group-wide exclusion should also stop promotional emails and SMS from every brand in the group, not just the one you contacted. Ask for that in the same request.
- Confirm the minimum term. Most operators set a fixed period, often six months to five years, and will not lift it early. Get the end date confirmed so you know when the block expires without you having to chase it.
Two trade-offs are worth knowing. First, a group-wide block will usually cut you off from every brand under that licence, including ones you might have wanted to keep. That is the point, but decide before you send the request. Second, some operators treat a request to one brand as consent to block the group, while others require a separate message per site. If the first reply is ambiguous, reply and ask directly: «Does this cover all casinos in the group, yes or no?» A one-word answer is easy to get and easy to keep.
Keep every reply. If a sister site later lets you back in, that paper trail is what turns a complaint into something a regulator can act on.
Step-by-Step: Requesting Exclusion Through Support at Each Sister Site
Self-exclusion is not a button you press once and forget. At group-operated brands it is a request you make, in writing, to a support agent who then applies it to an account. Do it site by site, keep the wording identical, and you remove the gaps that let a sister casino stay open to you.
Start with live chat or email at the first brand. State three things plainly: your full name, the email or username on the account, and the phrase «self-exclusion, not a cool-off.» A cool-off is a temporary lock of a day or a week. Self-exclusion is a longer block, usually six months to five years depending on the operator, and it is the one that should carry across the group. Ask the agent to confirm the length and whether it applies to all brands under the same licence.
Then repeat the request at each sister site where you hold an account. You cannot assume one agent will flag your email across every brand, even when the platforms share a wallet or a licence. Send the same message, keep a copy, and note the ticket number each time. The table below shows what to expect from common contact routes.
| Contact route | Typical response time | What to ask for | Trade-off |
|---|---|---|---|
| Live chat | Minutes | Written confirmation of group-wide exclusion and its end date | Fast, but transcripts can be lost if you do not save them |
| Email support | 24 to 48 hours | A reference number and a copy of the exclusion on file | Slower, but gives you a dated paper trail |
| Account settings tool | Instant | Site-level block only | Rarely covers sister brands, so follow up by chat |
| Phone line | Same call | Verbal confirmation plus a follow-up email | No record unless you request the email |
Use this checklist before you close the chat window:
- Name every sister site in the same message, including Imperial Wins, Lucky Nugget, Gaming Club, Mummys Gold, River Belle and Grand Mondial, and ask the agent to confirm each one is covered.
- Ask whether the block applies to deposits only or to login and play as well.
- Request the confirmation in writing and save the transcript or email.
- Note the start and end dates so you know when the block lapses.
- Ask what happens to any pending withdrawal or bonus balance.
If an agent says the group cannot apply a block across brands, ask for that in writing too. It tells you which sites you still need to contact individually.
Checking Ruby Fortune Alternatives and Sister Sites for Coverage
Before you send an exclusion request, map the brands you actually hold accounts with. The casinos below are frequently listed as Ruby Fortune sister sites or Ruby Fortune alternatives, and each one carries its own welcome offer terms:
- Imperial Wins offers a welcome offer up to $1000 plus 150 Free Spins, and requires a $10 minimum deposit.
- Lucky Nugget offers a welcome offer up to C$200 with a C$1 minimum deposit.
- Gaming Club offers a welcome offer up to C$200.
- Mummys Gold offers a welcome offer up to $500.
- River Belle offers a welcome offer up to $800.
- Grand Mondial offers 150 Free Spins.
- NightRush offers a welcome offer up to $100.
- Brango offers a 1 Free Spin welcome offer.
That list is not a single family. Some of these brands sit on shared platform infrastructure with Ruby Fortune, which is why a group-wide exclusion can travel between them. Others are independent offshore casino operators that simply look similar to a shopper comparing casino welcome bonus pages. Brango, for instance, runs on different software and licensing than the Microgaming-linked brands, so an exclusion at Ruby Fortune will not automatically reach it. Note also that the listed casinos are not available to Ontario players, which changes the picture if you are in that province.
Here is how to check coverage without guessing. First, open the footer of each site and note the licence number and the name of the operating company. Brands under the same group usually show the same company or a closely related subsidiary, and often the same licence issuer. Second, read the responsible gambling page and look for wording about «all brands operated by» or a linked list of sister casinos. A single-site policy will say the exclusion applies to that account only. Third, ask support in writing: «Does this self-exclusion cover every casino operated by your group, including [name the brands]?» Keep the reply. Fourth, cross-check the group’s own corporate site, which typically lists every consumer brand it runs.
Two shortcuts save time. Use the same email address across brands where you can, since support teams search by email and it makes a group block easier to trace. And treat a shared loyalty or wallet login as a strong hint of shared operations, though not proof. If a site refuses to name its operator or gives vague answers about sister sites of Ruby Fortune, assume the exclusion stops at that brand and plan accordingly.
Documenting Your Exclusion and Knowing What to Do If It Fails
Get the confirmation in writing before you close the chat window. A support agent saying «done» is not evidence. Ask for an email that names your account, the date and time the exclusion takes effect, whether it covers the whole group, and the duration you selected. If the first reply is vague, reply once with the specific wording you need: «Please confirm in writing that my self-exclusion applies to all brands operated under this licence, not only this domain.» A written record matters because a dispute two weeks later comes down to what was documented, not what was said.
Keep a simple log. One line per brand: casino name, date requested, agent name or ticket number, effective date, and the expiry date. Screenshot the confirmation email and store it outside your inbox. If you asked for a six-month exclusion, note the exact date it lifts so you are not surprised by a marketing email in month seven.
Then test it. Wait 24 to 48 hours, clear your cookies, and try to log in to each sister site on your list. You should be blocked at the login screen or at deposit. If a brand still lets you through, do not assume it will sort itself out. Send that brand’s support the original confirmation and ask for the block to be applied within 24 hours. Most operators treat an active exclusion as binding across their portfolio, so a gap usually means the request was logged on one account and never propagated.
If the second request fails, escalate. Check the licence shown in the site footer. Brands licensed by the Kahnawake Gaming Commission or the Malta Gaming Authority publish a complaints route; the MGA, for example, expects you to complain to the operator first and gives the company eight weeks to respond before you file with the regulator. Attach your confirmation email, the ticket numbers, and a dated note of the failed login attempt. Regulators respond to documented timelines, not to frustration.
One limit worth knowing: casinos listed on this page, including Imperial Wins, Lucky Nugget, Brango, Gaming Club, Mummys Gold, River Belle, NightRush and Grand Mondial, are not available to Ontario players, so Ontario residents cannot use this route for those brands and should rely on iGO-registered sites. For everyone else, the pattern holds. Written confirmation, a dated log, a login test, then the regulator. Anything less and you are trusting a chat window to protect you.
Before you close the browser, do one concrete thing: write a single email to support at every brand you hold an account with, listing all the sister sites in one message and asking for a group-wide exclusion with a written confirmation sent back to you. Keep that reply, note the date and time you sent the request, and save a screenshot of your account login screen showing the block. If you want a paper trail that holds up, send the same request from the email address registered to each account so support can match it without back-and-forth. Set a reminder for 48 hours later to check that every login fails, including the ones you rarely use. Accounts you opened years ago and forgot about are the ones that slip through.
While you wait, treat the whole group as closed rather than testing each brand one by one. If a site still lets you deposit after the confirmation date, reply to your original email with the account details and the date, and ask for the block to be reapplied. No response within seven days means it is time to escalate: send the same correspondence to the licensing regulator named in the casino’s footer, along with your confirmation email. That record is also what you need if you later ask for a deposit refund on the grounds the exclusion was ignored. The work takes maybe 20 minutes, and it is the difference between a request that covers one site and one that actually covers the group.