Self-exclusion tools and how to use them
What self-exclusion does
Self-exclusion is a formal request that a gambling operator stop accepting your custom, usually for a fixed minimum period, and that it take reasonable steps to prevent you from opening a new account or depositing during that time. It is not merely a preference you can switch off when you change your mind. That is the entire point. A deposit limit, by contrast, is a softer control: it caps how much you can put in over a day, week or month, but it can often be raised or removed at short notice. A loss limit works similarly. A time-out, or cooling-off period, sits somewhere in between and typically lasts from a day to a few weeks. Self-exclusion is the hardest of these tools, and the one most worth understanding before you need it.
What self-exclusion actually does depends on where you are. On a licensed operator in a regulated market, the mechanism is usually defined in law or in the conditions of the licence. The operator must close or suspend your account, stop marketing to you, and generally must not let you reopen until the exclusion period has run its course. Some jurisdictions require a cooling-off delay after the period ends before you can play again, precisely so that an impulsive decision cannot undo the exclusion the moment it expires. Others require the operator to remove your details from marketing lists and to make reasonable efforts to detect attempts to open a second account under a slightly different name or email address.
On an offshore or crypto-native sportsbook, the picture is different, and it is worth being blunt about that. Many such sites offer a self-exclusion button in the account settings, and many do honour it while you are logged in. But the enforcement is contractual and technical rather than regulatory. There is usually no external authority checking that the exclusion was applied, no one to escalate to if it was not, and no shared database preventing you from simply signing up again with a new wallet address and a fresh email. A self-exclusion on an offshore site is a genuine commitment device, but it is a commitment you are making largely to yourself, with the operator's cooperation rather than its obligation.
It helps to separate two ideas that get muddled. The first is exclusion from one operator: you cannot use that specific brand. The second is exclusion from gambling more broadly, across many operators, often coordinated by a national scheme or a regulator. The first is easy to arrange and easy to circumvent. The second is harder to arrange, harder to circumvent, and far more useful if the goal is to stop gambling altogether rather than to stop using one particular site. Most of the practical advice below is about how to move from the first towards the second, and where the gaps are.
Finally, a word on what self-exclusion is not. It is not a cure, and it is not a substitute for support. It is a fence, and fences can be climbed. Its value comes from putting friction between an impulse and an action: the minutes or days it buys you are often enough for the urge to pass. Used well, and combined with the other tools in this guide, it can be genuinely effective. Used alone, on a site with no real enforcement, it can create a false sense of security. Treat it as one layer, not the whole wall.
Site-level cooling-off
Site-level cooling-off is the entry point for most people, because it is the tool every operator offers and the one you can set within minutes. The usual form is a time-out: you tell the site to lock your account for a set period, commonly twenty-four hours, seven days, or thirty days, and during that window you cannot log in, deposit or bet. The account is not deleted; it is frozen. When the period ends, access returns automatically unless you extend it. On a well-run site, a time-out cannot be reversed early, which is exactly what makes it useful. On a poorly run one, support may agree to unlock it if you ask nicely, which defeats the purpose.
The short time-out is best understood as a circuit breaker rather than a solution. If you notice yourself chasing losses late at night, or you have had a few drinks and the bets are getting larger, a twenty-four or forty-eight hour lock does something a deposit limit cannot: it removes access entirely for long enough to interrupt the pattern. The trade-off is that it is short. By the time it lifts, the original trigger may have faded, but so may your resolve. A week is often a better default than a day for anyone who has noticed a recurring problem rather than a single bad evening.
Longer site-level exclusions, often six months or a year, are the more serious version. These are usually framed as self-exclusion proper rather than a time-out, and on regulated operators they come with obligations: no marketing, no reopening before the term ends, and sometimes a mandatory cooling-off period afterwards during which you still cannot play even though the exclusion has technically expired. The reason for that cooling-off is behavioural. The moment an exclusion ends is precisely when someone who has been struggling is most likely to return impulsively, so a further delay forces a second, cooler decision.
There are edge cases worth knowing. If you have a balance sitting in the account when you self-exclude, the operator should let you withdraw it, but it may not let you bet it, and some sites will hold it until the exclusion ends. Withdrawing before you exclude avoids that limbo. If you have an open bet or a bonus with wagering conditions attached, exclusion can complicate both: the bet may stand and settle, and the bonus may be forfeited. Read the terms, or ask support in writing, before you pull the lever, so you are not surprised by what happens to money already in play.
It is also worth being honest about the limits of a single-site tool. Excluding from one sportsbook does nothing about the other five you have accounts with, and nothing about the next one you might open. If your gambling is concentrated on one site, a site-level exclusion may be enough. If it is spread across several, or if you have a habit of opening new accounts when one closes, site-level tools will frustrate you without actually stopping the behaviour. That is the signal to look at the broader schemes in the next section.
Multi-operator schemes
A multi-operator self-exclusion scheme does what a single site cannot: it applies your exclusion across many operators at once, usually every licensed operator in a given market. The best-known examples are national schemes run or mandated by regulators, where you register once and the participating brands are obliged to check your details and refuse you. The mechanism is typically a shared register. When you sign up or log in, the operator checks your name, date of birth and address against the register; a match means the account is blocked or closed. The strength of the scheme depends entirely on how many operators participate and how rigorously they check.
These schemes matter because they close the most obvious loophole. Site-level exclusion assumes you will not simply walk to a competitor. A multi-operator scheme assumes you will, and blocks it. For someone whose problem is not one brand but the activity itself, this is the difference between a gesture and a barrier. The registration process is usually straightforward: you provide identifying details, choose an exclusion period, and confirm. The period is often a minimum of six months, sometimes a year, and extensions are usually easy while shortening is not, if it is possible at all.
The catch is coverage. A national scheme covers the operators licensed in that country, and only those. Offshore sites, crypto sportsbooks and unlicensed operators are typically outside it, because they are outside the regulator's reach. So a multi-operator scheme can be very strong against the regulated market and completely silent about the offshore one. If a meaningful share of your gambling happens on unlicensed sites, the scheme will not catch it, and you need the additional layers described below. It is still worth registering, because it removes the easy, licensed options and makes the remaining ones more deliberate.
There is also a practical question of how the register treats you over time. Some schemes keep you on the register for the full exclusion period and remove you automatically; others require you to actively request removal, and some add a further cooling-off before you can be removed. A few allow you to extend indefinitely, which some people use as a long-term commitment. The variation is significant, so it is worth reading the specific rules of the scheme you are joining rather than assuming they match another country's. If you are unsure, the scheme's own help pages or a gambling support service can clarify.
For a Netherlands-based reader, the practical implication is that the national licensed market has its own exclusion arrangements, while the offshore and crypto sites you might also use generally sit outside them. That is not a reason to skip the scheme; it is a reason to treat it as one layer among several. Registering removes the frictionless options and forces any relapse to be a conscious, multi-step act. That friction has value even when it is not airtight, because problem gambling is often driven by speed and ease rather than by a settled decision to gamble.
Device and bank blocks
The tools on your own devices and accounts are the ones no operator controls, which is precisely why they are worth setting up. A gambling-blocking app or a DNS filter installed on your phone, tablet and laptop can stop the sites from loading at all, at the network level, before any operator's self-exclusion even comes into play. These tools work by maintaining lists of gambling domains and blocking them, and the better ones let a trusted person, not you, hold the password that would disable them. That last detail is what gives them teeth: a block you can switch off in thirty seconds is a speed bump, not a barrier.
The obvious weakness is the same as with any blocklist: new domains appear constantly, and crypto sportsbooks in particular rotate addresses and mirror sites. A determined person with technical knowledge can often find a way around a DNS filter, and a less determined person can simply use a different device, a different network, or mobile data instead of home wi-fi. So device blocks are best seen as raising the cost of a relapse, not eliminating it. They work well against the impulsive, unplanned visit, which is the common case, and poorly against a sustained, deliberate search.
Bank and payment blocks address the money rather than the site. Some banks let you block gambling transactions outright, either permanently or for a set period, and some card issuers will decline gambling merchants on request. This is powerful because it attacks the funding step, which every deposit requires. But it has a well-known gap in the crypto context: a bank block does nothing about funds already sitting in a crypto wallet, and nothing about peer-to-peer transfers or exchanges that are not classified as gambling merchants. If your deposits run through a bank card to a licensed site, a bank block is a strong layer. If they run through a self-custody wallet, it is close to irrelevant.
There are softer versions of the same idea. Removing saved card details from browsers and sites, deleting the apps, and unsubscribing from marketing emails all reduce the number of prompts that lead back to gambling. None of these is a barrier on its own, but together they change the default. The goal is to make the path back to a deposit long enough that a conscious decision is required at several points, rather than a single tap. Each additional step is another chance to stop.
The trade-offs are real. Device and bank blocks can be inconvenient, they can be circumvented, and they can lull you into thinking you are protected when a specific route remains open. The honest framing is that they are most effective in combination, set up in advance, and ideally with someone else holding the keys. A block you set for yourself, that you can remove yourself, on a device you control, is the weakest form. The same block with a password held by a partner or friend, on every device, with the bank instructed as well, is a genuinely meaningful barrier.
Limits of exclusion on offshore sites
This is the section that matters most for anyone using crypto sportsbooks, and it is the one most often glossed over. On an offshore site, self-exclusion is a feature the operator chooses to offer, not a duty it owes. There is no regulator to complain to if it is ignored, no shared register it must consult, and usually no meaningful identity check that would stop you opening a second account. The operator may honour your exclusion faithfully, and many do, because it is cheap and it looks responsible. But the enforcement rests on their goodwill and their systems, not on an external authority with the power to penalise them.
The practical consequence is that a self-exclusion on an offshore site is easy to undo, sometimes by design. You can often register a new account with a different email address, and on a wallet-first site that does not require identity documents, there may be nothing linking the new account to the old one. Even where the operator tries to detect duplicates, matching on email and IP address is trivial to defeat. This is not a criticism of any particular site so much as a structural feature of the no-KYC model: the same anonymity that protects a legitimate user's privacy also removes the hooks that make exclusion enforceable. Dexsport, the wallet-first book we recommend, is honest about this trade-off, and it is the reason we treat offshore self-exclusion as a useful commitment device rather than a guarantee.
There is a further asymmetry. Licensed operators face consequences for failing to apply an exclusion: fines, licence conditions, reputational damage. Offshore operators face almost none. If a site ignores your request, or quietly reopens your account, your realistic options are limited. You can complain, you can leave a review, you can stop using the site, but you cannot force compliance. This means the burden of vigilance falls on you at exactly the moment when you are least able to carry it. Anyone relying solely on an offshore self-exclusion to control their gambling should understand that they are relying on the operator's cooperation, which is not the same as a rule.
The crypto dimension sharpens all of this. A traditional offshore sportsbook at least sees your name, your bank and your address, which gives it something to match on. A wallet-first book may see only a wallet address, and a determined user can generate a new one in seconds. Deposits from a self-custody wallet leave no bank record that a payment block could catch. So the two strongest external controls, identity-based registers and bank blocks, are both weakened or absent. What remains is the operator's own willingness to enforce, plus whatever device and personal controls you have put in place.
None of this makes offshore self-exclusion worthless. It makes it partial. Used as a first step, set alongside device blocks, a bank block where deposits run through a bank, and a multi-operator scheme for the licensed sites you also use, it adds a real layer of friction. Used alone, as the only control, on a site with no external oversight, it can give a false sense of safety. The correct mental model is a chain of barriers, each imperfect, whose combined effect is to slow you down. The offshore exclusion is one link. It should not be the only one.
Setting one up today
The order in which you do this matters, because some steps are easier before others and some close doors you may still need. Start by withdrawing any balance you want to keep, and settle or accept whatever happens to open bets and bonuses, before you exclude. Once an account is frozen, getting money out can become slower and more awkward, and a bonus with unmet wagering conditions is often lost. Clear the decks first, then set the controls. It is a small piece of admin that saves a larger annoyance later.
Next, set the site-level tools on every operator you use, not just the one that prompted this. A time-out of a week or more is a reasonable default if you are unsure; you can extend it, and extending is usually easy while shortening is not. Where a longer self-exclusion is offered, and you have noticed a recurring pattern rather than a single bad night, take the longer option. Then register with the multi-operator scheme for your licensed market, so the regulated sites are covered in one move. If you are in the Netherlands, that means the national arrangements for licensed operators; the scheme's own pages will confirm the current process and periods.
Then handle the money and the devices. Ask your bank to block gambling transactions, or use whatever block your bank offers, and remove saved card details from browsers and sites. Install a gambling-blocking app or DNS filter on every device you gamble from, and have someone you trust hold the password. Delete the sportsbook apps, unsubscribe from the marketing emails, and turn off notifications. None of these is decisive alone, but each removes a prompt or a route, and the cumulative effect is a path back to a deposit that requires several deliberate steps rather than one.
Finally, tell someone. A friend, a partner, or a support service. Self-exclusion works best when it is not a secret, because the people around you can notice the warning signs and can hold the passwords you cannot. If you are using an offshore book, be realistic about what its exclusion can and cannot do, and lean harder on the layers it cannot touch. And if you find yourself repeatedly working around your own controls, that is information worth acting on: it suggests the problem is larger than any single tool, and that professional support is the next step. This is not legal advice, and rules differ by jurisdiction, so check the specifics where you are. Gambling is for adults only, 18+, and if it stops being fun, or stops being a choice, support is available and worth using.
This guide was researched, written and fact-checked by the SafePlay Wire editorial desk before publication. Last reviewed 13.10.2026. Spotted something wrong? Tell us.