◉The Clock Desk Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band 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. The subject of this desk is the clock an account runs on, so its own interest is stated here rather than left for a footer: one link funds the site, and no operator, game or regulator is named, rated or recommended anywhere on it.
The Clock Desk / Questions
The FAQ, in full

The questions, in full

Twelve questions a reader arrives with, answered directly. Each answer sits under the same rule as the rest of the desk: a time is given with its zone, and every figure comes from the eight samples with the arithmetic shown on the numbers page.

Open the partner accountRead the time clauses
Account spec
Questions
12
Schema
FAQPage from the same array
Figures
from the eight samples
Named operators
none
the boundaryThe instant the account's day is measured from. On the samples it is 00:00 UTC, which is a different wall-clock moment for every reader.
the countdownWhat a window is measured from and whether day one counts. A window advertised as 30 days delivers 29 days 23 hours 59 minutes on the sample.
the calendarThe working-day clock money moves on, with its cut-off, its weekends and its holidays. One working day covered 87 hours 30 minutes on the sample.
Direct answerThe short version: your account runs on the operator's clock, normally UTC; a daily allowance returns at that boundary wherever you are; a countdown is measured from the credit and nothing pauses it; a cut-off is one instant on the operator's clock; and a working day is a calendar, not a duration. Each of those is worked through below.

The answers below and the FAQPage structured data on this page are generated from one array, so the markup cannot describe an answer the page does not show. Where an answer quotes a figure, the figure is from the samples, and the full working is on the numbers page.

The questions, in full

q01

Which day does a daily limit reset on?

The operator's day, which is stated in the terms and is usually 00:00 to 00:00 UTC. On sample A that makes the account day 13:00 to 13:00 local for a reader in UTC+13, midnight to midnight for a reader in UTC+0, and 16:00 to 16:00 for a reader in UTC-8. Only one of the three sees the reset at midnight, and it is not the one in the middle.

q02

How long do I actually wait after hitting a daily loss limit?

It depends on when you hit it, not on the size of the limit. On sample B a 200.00 limit that resets at 00:00 UTC was hit at 09:40 UTC by a reader in UTC+13, who then waited 14 hours 20 minutes, and at 22:00 UTC by a reader in UTC-8, who waited 2 hours. The same limit, the same reset, 12 hours 20 minutes of difference.

q03

Does a 30-day bonus window really last 30 days?

It lasts 29 days 23 hours 59 minutes if the day of the credit counts as day one, which is the standard convention for a window described as "within 30 days". On sample C that is 719 hours 59 minutes 59 seconds, and the deadline falls on 31 March for a reader in UTC+13 and 30 March for a reader in UTC-8, so the same instant produces two different local dates.

q04

Does a countdown pause while I am not playing?

Not on any of the 40 pages of sample G. None suspends a credit window for inactivity, for a pending verification or for a maintenance window. On sample C the window is consumed at 0.1389% an hour, which is 3.33% a day, so a third of a day of the window is gone before day one ends.

q05

Why was my bet refused when my screen still showed time left?

Because the line is on the operator's clock and your device is only a display. On sample D the cut-off was 15:00:00.000 UTC, a bet received at 14:59:59.940 was accepted and one at 15:00:00.060 was refused, and a device 3.2 seconds slow showed 14:59:56.800 at the moment the operator's clock read 15:00:00.000. The window that decided it was 120 milliseconds wide.

q06

How long is one working day really?

Between 23 hours and about 87 hours, depending on the day you ask. On sample E a request on Friday at 17:30 missed a 16:00 UTC cut-off and the following Monday was a public holiday, so the money moved on Tuesday and 87 hours 30 minutes had elapsed. A request on Monday at 10:00 in the same system took 23 hours. Both are one working day, and the ratio is 3.65.

q07

Is the timestamp on my transaction written in my time zone?

No. It is written by the operator, normally in UTC, and on sample G none of 40 invented terms pages states which zone the stored record uses. Your device converts it for display, which is a convenience. Where a deadline and a record disagree, the record is the one the rules were applied on, and it is the one a query is answered from.

q08

What happens to the account day when the clocks change?

Nothing happens to the account day; something happens to your display. On sample H an allowance resetting at 00:00 UTC reads as 00:00 local in a UTC+0 winter and 01:00 local in a UTC+1 summer, and across the change night 24 hours of real time reads as 25 hours on the wall clock. In the autumn the same day reads as 23. None of the 40 sample pages mentions daylight saving at all.

q09

Is an hour of play the same on every product?

No. On sample F an hour is 90 live-table rounds at 40 seconds each, 300 electronic hands at 12 seconds, or 1,200 slot spins at 3 seconds, so the same 60 minutes is 13.3 times as many units of play on the fastest product. A session timer announces 60 minutes on all three, because it counts the wall clock rather than the units.

q10

Does a maintenance window stop a bonus expiring?

Not on the sample. None of the 40 pages suspends a countdown for an outage, and none of them suspends one for a pending verification either. The window is a property of the credit, so it expires on its own schedule whether or not the site is reachable, and the account day boundary is not moved by an outage either.

q11

Why do two pages describe the same window differently?

Because one counts elapsed time and the other counts a calendar. "Within 24 hours" is a duration and "within one working day" is a day on a calendar with cut-offs, weekends and holidays, and on sample E those two descriptions covered 23 and 87.5 hours for requests on the same system. Neither description is wrong; they answer different questions.

q12

Can I find out which clock my account runs on before I need it?

Yes, and it is the one belief on the myths page that stands. The boundary is stated somewhere in 9 of the 40 sample pages, every transaction record carries the operator's own timestamp, and the conversion from the operator's zone to your own is arithmetic you can do once and keep. What is missing is the sentence, not the information.