◉The Duty To Step In protection duty Open the partner account
Monitor defined signals Act proportionately Record the decision Appeal outside the desk that decided
paid
Affiliate disclosure. The partner link in the masthead and beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about the disclosures an operator owes a player should not leave its own funding unsaid: one link funds the site, no operator is named, rated or recommended anywhere on it, and it describes no real account, regulator or person.
The Duty To Step In / questions
Answered directly

The questions

Ten questions a player or a curious reader is most likely to arrive with, each answered in a form that can be quoted on its own. Every answer is drawn from the mechanism and the ten samples described on the rest of the desk.

Desk spec
questions
10
samples used
10
answers with arithmetic
6
runtime javascript
none
affiliate placements
disclosed
audience
18+
step 01
monitor

Read the signals

Five comparisons the account already supports, run continuously rather than after a complaint. 6,000 flags in the sample, 96.0% of them relative to the account own history.

step 02
act

Choose a response

Nothing, a message, a limit or a break, or a restriction - one of four, graded by how much it takes from the player. 960 of 4,000 reviews in the sample changed access.

step 03
record

Write it down

Signals, crossing dates, rule version, path, response and outcome - one record per review, including the 1,600 that ended with nothing done.

step 04
answer

Take the appeal

A route outside the desk that decided. 480 appeals in the sample, 176 of them upheld, which is 36.7% - high enough that the route does real work.

Direct answer

The questions on this page cover what a protection duty is, who decides, why a limit appears with no warning, whether a break has an end, what happens to a withdrawal during one, what a player can appeal, and where the operator obligation stops. Each answer stands alone, and the figures in them come from the ten invented samples.

The questions, in full

q01

What is an operator protection duty?

It is a licence obligation, usually written as three parts: monitor play against defined signals, act on what the monitoring finds, and record the decision and its basis. It is a duty about the account rather than about the person, which is why a review begins when a rule is met rather than when someone becomes worried.

q02

Why did my account get reviewed?

Because a rule was met. In a sampled policy three rules open a review: two flags inside 14 days, one high-severity flag such as a self-reported problem or a session over 12 hours, or spending above four times the affordability band the account declared. Those three accounted for 2,800, 720 and 480 of 4,000 reviews.

q03

Does a limit mean I won too much?

Not in a protection review. A protection limit comes from a signal about the size or pace of play - a session length, a spend ratio, an interval between a loss and a deposit - and none of those is an outcome. If a limit followed a successful run, it is more likely a commercial decision by the operator, which is a different mechanism with a different appeal route.

q04

How long does a mandatory break last?

It has a stated length. In the sampled policy there are three: 24 hours, seven days and 30 days, and across 4,000 reviews the split was 320, 112 and 48. None of the 480 breaks in the sample was shortened before it expired, so the stated end date is the part a player can rely on - ask for it if it is missing.

q05

What happens to my withdrawal during a break?

A pending withdrawal is normally still processed, because a break is a protection measure rather than a dispute over money. A break stops play; it does not take the balance, and a bet that has already settled stands. What a break can leave behind is a note on the account - 96 of the 480 breaks in the sample carried a 12-month record.

q06

Can I appeal a protection decision?

Yes, and it is worth doing. Of 480 appeals in the sample, 176 (36.7%) were upheld. An appeal that addresses the specific signal - the crossing date, the threshold, the declared band - is more likely to succeed than one that disputes the decision as a whole. Ask for the record first, then answer the signal.

q07

What am I entitled to be told?

Under a policy of the kind modelled here: notice that a decision was taken, a reason naming the rule and the period rather than the phrase unusual activity, an appeal to somebody outside the deciding desk, and access to the record the decision rests on. The exact entitlement depends on the licence covering the account, and nothing here is legal advice.

q08

Does the operator watch me personally?

No. The rule reads comparisons the account already produces, and 96.0% of the flags in the sample came from a comparison rather than a person looking. The only absolute signal in the sample is one the player states directly - a self-reported problem flag - and it accounts for 240 of 6,000 flags, or 4.0%.

q09

Can a protection review happen to someone who is fine?

Yes, and the sample puts a number on it: 1,600 of 4,000 reviews ended with no action, 1,280 of those because the change was a one-off event and 224 because of a data error such as one device counted as two. A rule set that acts early will contact some players who did not need it - that is the trade it is making, not a malfunction.

q10

Where does the operator duty stop?

At what the operator can see: its own accounts, its own play data, for as long as the account is open. It cannot read play at another operator - 72 of 360 missed cases in the sample were patterns split across two accounts - and it cannot force treatment or police its own licence. The regulator handles the licence, support charities handle help, the bank handles payments and a clinician handles health.