◉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 / the break
The heaviest protection instrument

The break the operator can impose

A break is the only protection response that removes access entirely, and it is the one a player is most likely to meet with no warning at all. The sampled policy allows a break to be placed without the player consent, in three lengths - 24 hours, seven days and 30 days - and records none of them as shortened. What makes a break defensible is not its length; it is that the length is stated and the date at which it is reconsidered is stated with it.

Desk spec
accounts reviewed
4,000
placed on a break
480
share on a break
12.0%
24 hours
320
seven days
112
30 days
48
shortened before expiry
0
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

A mandatory break is a protection response that removes access to the account for a stated period, and a sampled policy places one without the player consent. Its three lengths are 24 hours, seven days and 30 days, and across 4,000 reviews 480 accounts met one. In the sample none was shortened before it expired, so the stated end date is the whole of what a player can rely on.

Why a break does not ask first

Every lighter response in this pipeline can be applied to an account that is still in use, so the player can respond to it while it is happening. A break cannot: if the operator asked first, the account would necessarily remain fully open during the period when the pattern was judged to be at its most acute. That is the argument for placing a break without consent, and it is the same argument for stating its length: an instrument that removes access has to have a stated end, or it becomes an indefinite restriction arrived at by a different route.

The sampled policy places a break in 480 of 4,000 reviews (12.0%). Not one of the 480 was shortened before it expired, which is worth reading as a finding rather than a footnote: the lengths were set correctly often enough that no case in the sample needed the end moving. A different desk might report a different number, and the honest thing is to say that this one reports zero.

The three lengths, and what each one is for

Sample F: the breaks in the sampled desk
LengthWhat it is forReversiblePlaced
24 hoursa short interruption; the pattern is recent and the evidence thinon review320
Seven daysenough time for the pattern to be judged after the facton review112
30 daysa long break where a shorter one was tried and did not holdon review48

Two-thirds of the breaks in the sample were 24 hours, which is the shape a proportionality ladder should have: the heaviest instrument used least, and the lightest used most. A policy whose 30-day breaks outnumbered its 24-hour ones would be describing something other than a graded response.

Worked example / sample F

  1. reviews: 4,000
  2. breaks placed: 480, which is 12.0% of reviews
  3. of the 480: 320 at 24 hours, 112 at seven days, 48 at 30 days
  4. 320 / 480 = 66.7% at the shortest length
  5. 48 / 480 = 10.0% at the longest
  6. recorded on the account for 12 months: 96, which is 20.0% of the breaks
One break in five left a mark on the account for a year beyond the break itself. That is the part of a break that is not reversed when the break ends, and it is the part a player is least likely to be told about.

What a break does, and does not, touch

  • It stops play. It does not take the balance, and it does not cancel a bet that has already settled.
  • A pending withdrawal is normally still processed, because a break is a protection measure rather than a dispute over money.
  • An open bet continues to settle unless the policy says otherwise, and its outcome is credited as usual.
  • It does not end the account. A break is temporary by design, and the account returns to its previous state when it expires.
  • It does not answer an appeal. If the break was wrong, the remedy is the appeal - what you are owed covers the route.
  • It is recorded. In the sample, 96 of 480 breaks carried a 12-month note on the account.

That last point is the one to ask about when a break is placed, because it outlasts the break. A 24-hour pause is a small thing; a 12-month note that a protection decision was taken may affect how a later review reads the same account.