Tools are not the programme
Regulated operators offer deposit limits, time-outs, reality checks and self-exclusion. In Britain, financial limits, reality checks for online gaming, time-outs and self-exclusion are all licence requirements for online operators. Their presence is table stakes and tells you almost nothing about whether an operator is protecting anyone.
What matters is whether the tools are found, used, and effective, and those three are separate questions with separate answers. A tool available in a settings menu three levels deep, offered in a paragraph nobody reads, with a default of no limit and a friction gradient that makes increasing easier than decreasing, is technically present and practically absent.
This lesson is about the design decisions that determine whether a tool does anything, because those decisions are where the difference between operators actually lies.
The limit family
Four distinct controls are frequently conflated, and the differences matter.
Deposit limits cap money transferred in over a period. The most widely offered and the easiest to understand. They do not cap losses, because a customer can recycle winnings indefinitely without depositing again.
Loss limits cap net losses over a period. They bind on the outcome rather than the input, which makes them the most directly protective of the four, and also less commonly offered than deposit limits, partly because they are harder to explain and partly because they bite hardest. British technical standards accept deposit, spend or loss limits, over periods that should include 24 hours, 7 days and one month, so a loss limit is one option among several rather than a requirement.
Stake limits cap the size of an individual bet or spin. They constrain loss rate rather than total loss, which makes them particularly relevant on high-frequency products.
Session and time limits cap duration. Useful against dissociation and against the extended sessions that appear in the marker set, and weak against a customer losing quickly.
A programme offering only deposit limits is offering the weakest useful member of the family. The question to ask of any operator is which of the four it offers, at what granularity, and whether a customer can find them.
Defaults do more work than availability
This is the highest-leverage design fact in the whole of responsible gambling, and it is regularly ignored.
Take-up of opt-in tools is low. In 2022 the Behavioural Insights Team reported that only around 1 in 5 UK gambling accounts used deposit limits, and more than 1 in 3 of those set limits above £50,000. Most customers never open the settings menu. The customers most at risk often decline a limit, set one too high to bind, or raise or remove it later, which is how the authors of a Finnish randomised trial interpreted their own results.
Defaults change this completely, because they do not require the customer to act. The design options form a ladder of increasing effect.
Opt-in with no default is the weakest and the most common. Nothing happens unless the customer acts.
Forced choice at registration requires the customer to set a limit or explicitly decline before completing sign-up. Take-up rises substantially, because the decision has been moved from something the customer must seek out to something they must address. In that Finnish trial, 45 per cent of customers prompted at registration set a limit, against 6.5 per cent of unprompted customers, although a one-off, voluntary prompt with no cap on the amount did not reduce their losses over 90 days: take-up is necessary, not sufficient. British technical standards now present setting a limit as the default choice and require the customer to act to decline, and Australia's national framework requires online wagering providers to ensure new customers set a deposit limit or opt out of setting one.
A default limit that can be raised is stronger again. The customer is protected from the outset and must act to remove the protection, which reverses the direction of effort. In a 2022 online experiment with 2,114 UK adults, a mandatory limit with a pre-set default produced the lowest limits of any design tested, and participants did not report feeling overly restricted by it.
A hard cap that cannot be exceeded is a regulatory instrument rather than a customer tool, and several jurisdictions have introduced them for specific products or customer groups. Britain has capped online slots stakes at £5 per game cycle for adults aged 25 and over, and £2 for those aged 18 to 24, since April and May 2025; Germany's 2021 State Treaty sets a cross-operator deposit limit of €1,000 per calendar month, which an operator may raise for an individual customer only under conditions set by the regulator, including no signs of problem gambling and proof that the customer can afford it.
The commercial objection to defaults is that they suppress revenue from customers who would have deposited more and could afford to. That is true and it is the honest trade. The relevant counter is that the suppressed revenue is disproportionately drawn from the customers most likely to be harmed, because those are the customers whose deposits would have exceeded a sensible default.
Friction asymmetry: the single most testable thing
If you audit one aspect of an operator's tools, audit this.
Decreases should be immediate. Increases should be delayed.
A customer lowering a limit is exercising a protective decision, and it should take effect the moment they make it. A customer raising a limit is removing a protection, usually at the moment it has just bound, which is usually the moment they are least well placed to make the decision. A cooling-off period before an increase takes effect, commonly twenty-four hours or longer, allows the decision to be made by a person in a different state. British technical standards make this explicit: increases only after a cooling-off of at least 24 hours and a positive confirmation from the customer at the end of it, and reductions implemented immediately.
The design detail matters. A delay that can be cancelled by contacting support is not a delay. A delay that is waived for a customer who complains is not a delay. A prompt offering to raise the limit at the moment it binds is the opposite of a delay, and it appears in real products.
The same asymmetry test applies across the whole interface. Count the taps to increase a deposit limit and the taps to set one. Count the taps to deposit and the taps to self-exclude. Where the protective action takes more effort than the risky one, the interface is working against the policy. This is the logic behind British standards that require operators to minimise the clicks needed to reach limit-setting facilities and forbid customers from cancelling a withdrawal request.
Cooling-off and time-outs
A time-out is a short self-imposed break, typically from twenty-four hours up to several weeks, during which the account cannot be used for gambling. British online operators must offer time-outs of 24 hours, one week, one month or another period the customer reasonably requests, up to six weeks. It is deliberately lighter than self-exclusion and is the right tool for a customer who wants to interrupt a pattern rather than stop.
Three design points determine whether it functions.
Marketing must stop too. A customer on a time-out who continues to receive promotional email and push notifications is being actively worked against by the operator during the period they asked for protection. This is basic and it is still found in reviews.
It must not be reversible on request. A time-out a customer can end by contacting support is a time-out that ends the first time the customer wants it to, which is the moment it was protecting them from.
Return should not be celebrated. A reactivation bonus at the end of a break is an inducement targeted precisely at a customer who identified a need to stop.
Reality checks
A reality check interrupts play at a set interval with a statement of elapsed time and, in better implementations, net position. The customer acknowledges it to continue. In Britain, online gaming customers must be able to set the frequency of a reality check showing elapsed time, which they must acknowledge before it leaves the screen; the guidance adds an exit option and a link to account history, but net position is not required.
The mechanism works by breaking flow, and the design decisions all bear on whether flow is actually broken.
Interval matters: a check every hour on a product with several hundred events per hour is barely an interruption. Content matters: elapsed time alone says less than elapsed time plus the amount won or lost, because net position is the fact a customer in the middle of a session is least likely to have tracked. Dismissal matters: a check acknowledged reflexively with the same tap used to spin is not registering at all, and requiring a distinct action is the difference between an interruption and wallpaper. Offering a stop option matters, because the customer who wants to stop should not then have to find how.
The honest evidence position is more qualified than either side tends to claim. A 2021 meta-analysis of 18 studies of pop-up messages found medium short-term effects on behaviour, with the largest effects from messages personalised to the customer's own play and weaker ones from generic messages, but 14 of the 18 studies were run in laboratories, only two tested people gambling their own money in a real setting, and the authors found too few studies involving problem gamblers to judge the effect on them. A reality check informs; unlike a limit, it does not bind. They are worth having and they are not a programme.
Self-exclusion
Self-exclusion is the strongest customer-initiated tool: a binding commitment, for a defined minimum period, during which the operator must prevent the customer from gambling and must not market to them.
Two forms exist and the difference is the whole point.
Operator-level exclusion covers the brands of one operator. Its weakness is obvious: the customer opens an account elsewhere, frequently within minutes, and the operator that excluded them has protected its own record rather than the customer.
Multi-operator exclusion covers every licensed operator in a market through a central register. This is the version that works, and its existence is one of the clearest markers of a mature regulatory regime. Where such a scheme exists, an operator's obligation is not only to honour it but to check it, and failures appear in enforcement. Britain's online scheme, GAMSTOP, lets a person exclude from every British-licensed online operator for six months to five years; in 2020 the Gambling Commission suspended two operators' licences for failing to integrate it.
Several design features determine effectiveness in either form.
Registration must be simple. A person self-excluding is frequently in distress. A process requiring a phone call during office hours, or a form with fields the customer cannot complete, will lose people who were ready to act. British online operators must let customers self-exclude both through customer services and through an automated process.
The minimum period must be meaningful. Very short exclusions are close to time-outs. In Britain the code of practice expects the minimum self-exclusion offered to be between six and twelve months, with the option of at least five years.
Reinstatement must require effort and delay. The end of a period should not be automatic reactivation. A cooling-off period after the request, a positive act by the customer, and no marketing during either, is the standard shape. Automatic reactivation plus a welcome-back offer is the failure mode these rules are written to prevent. In Britain an online self-exclusion stays in place for at least seven years after the chosen period unless the customer takes positive action by phone or in person, followed by a one-day cooling-off, and no marketing may be sent until the customer asks for or agrees to it.
Balances must be returned. A customer who self-excludes should receive their balance rather than losing access to it, which sounds obvious. The British code makes it explicit: operators must close the accounts and return any funds, and merely blocking withdrawals while still accepting bets is not sufficient.
Marketing suppression must survive system boundaries. The most common technical failure is a self-excluded customer remaining on a marketing list held in a separate platform, or being re-imported from a suppressed segment during a migration. This is a data-engineering problem with a compliance consequence, and it is worth a dedicated test. British operators must remove or flag a self-excluded person in every marketing database within two days, and in 2023 an operator paid £490,000 after its app sent a promotional push notification to devices linked to self-excluded accounts.
What self-exclusion does not cover
Being clear about the gaps is part of using the tool honestly.
It covers licensed operators in the scheme's jurisdiction. It does not cover unlicensed sites, which remain available. It does not cover land-based venues unless a separate scheme exists: in Britain, GAMSTOP's online register is separate from its scheme for betting shops. It does not cover a determined person using another individual's account, which is why account-sharing detection matters more in this population than elsewhere. And it does not address the underlying difficulty, which is why referral to treatment and support at the point of exclusion is part of the process rather than an optional courtesy.
Blocking software installed on the customer's own devices and bank-level gambling blocks that stop card payments to gambling operators sit alongside exclusion and close some of these gaps. An operator's role is to know they exist and to tell customers about them, as the British code expects operators to tell customers that blocking software is available and link to further information, particularly at the point of self-exclusion, which is when the customer is most motivated to use them.
Measuring whether tools work
Most reporting in this area measures the wrong thing.
Weak. Number of customers who set a limit. Number of tools promoted. Percentage of accounts with any tool active. These measure availability and marketing, not effect.
Better. Take-up as a share of customers offered, which distinguishes availability from adoption. Retention of limits over time, since a limit raised within a week is a different event from one held for a year. Proportion of limits that bind, since a limit set far above the customer's actual play is decorative. Behaviour change after a limit is set, measured against the customer's prior pattern.
Best. Comparison against a defensible counterfactual. Staged rollouts of a default, A/B tests of prompt design and placement, and natural experiments created by product changes all allow a causal claim. Testing the design of a tool is ethically straightforward in a way that withholding protection is not, and it is under-used.
A specific and revealing metric: what proportion of customers who raise a limit had the increase prompted by the operator's own interface at the moment the limit bound? If that number is not zero, the product is undoing the policy, and nobody has noticed because nobody measured it.