129,985 characters, read 2 September 2026
A fourteen-day deadline to write in, and no address in the clause that sets it
Four of this operator's documents were served live and read in full on 2 September 2026, running to 129,985 characters between them. They contain a deadline for the customer to report a problem, a deadline after which a result can no longer be queried, and no undertaking whatever about how quickly the operator replies.
Support is the part of an operator that reviews describe from experience and documents describe hardly at all. This site holds no experience of any operator, so the question has to be put to the documents: what does this contract undertake about answering a customer?
Four of them were served live to our capture machine and read in full on 2 September 2026. The terms run to 75,770 characters, the betting rules to 32,099, the privacy and security page to 15,835 and the responsible gaming page to 6,281.
Across those 129,985 characters, the number of undertakings about response time is zero.
Where do these documents even live?
Not where a reader would guess. Eight conventional addresses were tried first — /en/legal/terms, /legal/terms, /en/legal/privacy, /en/legal/betting-rules, /en/legal/bonus-terms, /en/legal/responsible-gambling, /en/legal/aml-policy and /content/responsible-gambling — and all eight returned the site's own 404 page.
The documents sit under /content/ instead, and the sub-policies a reader might expect to find as separate files are anchors inside the same terms page: a KYC section, an anti-money-laundering section, a dispute-resolution section, an accounts-payouts-and-bonuses section and a self-exclusion section.
There is no standalone KYC document and no standalone AML document. Both are headings in one page.
That structure is worth knowing before a dispute rather than during one, because a reader searching for “the AML policy” of this operator will find nothing under that name and may conclude, wrongly, that none exists.
What deadline does the contract actually set?
One that runs against the customer, and it is short.
Clause 6.18 states that in the event of an error or malfunction in funds transfer, the customer is under an obligation to inform the operator within 14 days from the date when the error or malfunction occurred, and that any complaints filed after this period will not be considered.
Fourteen days to notice, and nothing on the other side of the clause.
The company takes on no matching deadline to acknowledge, to investigate or to answer. That asymmetry is normal in this market and it is rarely printed this plainly, which makes clause 6.18 more useful than a support page: it is the sentence a customer would be held to, and it is the sentence a customer can hold up.
There is a second thing missing from it. A clause obliging someone to inform a company inside two weeks does not say where to send the message. No email address, no ticket form and no channel is named in the clause, in the section around it, or anywhere else in the 129,985 characters read.
Why can the help centre not fill that gap?
Because it is not a document. The help address returned a 3,857-character shell, and the answers a reader would see in a browser are drawn in afterwards by the client from somewhere else.
A shell is not evidence of an answer, so no help-centre content for this operator is recorded here.
This is a recurring shape rather than an accident of one site. Contract text is static and quotable; help content is rendered, versioned invisibly and changed without a trace. When an operator puts its response-time promise in the second place and its complaint deadline in the first, the promise is the part that can be withdrawn silently.
The same split explains a blank elsewhere in our record: the cashier screen carries the coin list, the networks, the per-coin minimums and the confirmation counts, and all of it needs an account. What the terms do commit to on the money side is on the payout terms.
Which clocks does this contract actually run?
Three, and every one of them measures the customer.
Fourteen days, under clause 6.18, to report an error in a funds transfer, after which a complaint will not be considered.
Forty-eight hours, under the betting rules, after which published results are final and no queries will be entertained. Those rules carry headings rather than numbered clauses, so that sentence travels with its document name and the date it was read rather than with a clause number, and it is labelled that way wherever this site uses it.
Twelve months, under clause 5.3, before an account with no deposit, withdrawal or wager is deemed dormant. After the eleventh month an email warns that the balance will be set to zero in thirty days; at twelve months the balance is zeroed. That is not a fee — it is the whole balance.
Three precise clocks, none of them pointing at the company.
A fourth clock would be the one a reader is looking for: how long the operator has to answer, to release a payout, or to finish a verification it started. That clock is absent from the document. What the operator may ask for while it runs — government-issued ID and proof of residency at its sole discretion, under clause 21.1 — is set out on the account holds page.
What does the operator commit to answering at all?
One thing, and it belongs to the responsible-gaming side rather than to support.
The self-exclusion section is an anchored part of the same terms page, which means it is contract text rather than help content: a heading a reader can cite. The responsible gaming document that accompanies it runs to 6,281 characters, the shortest of the four read, and it is the only place in the bundle where the operator describes a service to the customer rather than a right over the customer.
Everything else in these documents is drafted as a permission. The operator may request documents, may restrict the manner in which a withdrawal is processed, may conclude a withdrawal by an alternative method at its discretion, and may apply a wagering requirement of at least five times a deposit where it suspects the service is being used as a mixer.
A contract of permissions with three deadlines, all of them the customer's.
What can a reader do with an unpublished response time?
Two things, and the first costs nothing.
Send anything time-critical in writing, to whatever channel the account itself offers, and keep the sent copy with its date. Clause 6.18 makes the date of the notification the thing that matters, and the party who has to prove it made the deadline is the customer.
The second is to read the deadline before the incident rather than after it. Fourteen days sounds generous until a transfer error is noticed on the fifteenth, and the clause is drafted to end the matter there.
How this site reads an operator, what it refuses to claim, and why a figure without a clause number stays off the page are set out on the method. The operators read on the same rules sit on the alternatives page.