Twelve documents, read 26 August 2026
What the terms promise about answering you, and which deadlines they do set
Not one document read for this index names a support channel or a period inside which the operator must reply. The periods these contracts do contain — 30 calendar days at one row, 14 at another — run the other way, and they end in confiscation or suspension rather than in an apology.
Support is the part of an operator a reader is most likely to need and the part these documents describe least. That is not a rhetorical opening: it is the reading.
What the documents say about reaching anybody
Four documents were opened for Stake.com on 26 August 2026: the terms of service, the verification clause at 4.8, the territorial clause published at the licences page, and the register entry for permit OGL/2024/1451/0918, held by Medium Rare N.V.
None of them names a support channel. None of them sets a period inside which the operator answers a message, reviews a document, or reaches a decision.
Across the twelve rows compared here the picture is the same, with one exception. Support channels are recorded for a single row — live chat and email, read from the operator's own pages on 25 August 2026 — and eleven rows carry nothing, because nothing was opened that stated it.
A channel is published where marketing lives. It is not in the contract, and it is therefore not a commitment.
The three clocks in these contracts, and who they bind
There are deadlines in this material. Every one of them counts down against the customer.
| Where | Period | Clause | What happens at the end |
|---|---|---|---|
| Bets.io | 30 calendar days | 5 | account suspension until documents arrive; confiscation where they prove false |
| Vave | 14 days | 8.7 | documents demanded before payout, at the operator's discretion |
| Oshi, in the wider library | 40 days | 12 | winnings may be confiscated |
Three periods, three consequences, and all three fall on the person waiting to be paid.
Now the other side of the ledger. Across the hundred operators in this library, 49 verification clauses have been read, and three of the 49 attach a period of any kind. Not one document read anywhere sets a period inside which the operator has to finish reviewing what it asked for.
So the asymmetry is not an accident of which rows landed in this table. It is the drafting convention of the trade: a duty on the customer with a date attached, and a discretion on the operator with none.
For this operator specifically, clause 4.8 reserves the right to request documentation at any time and to restrict service, payment or withdrawal until identity is sufficiently determined. There is no threshold in it and no clock. What the clause does contain, read out in full, is on the verification clause.
Two addresses that answer without a support desk
If the contract will not commit to replying, the useful question is what a reader can settle alone. This index holds two such addresses per operator, at most.
The first is a register entry. Nine of the twelve rows print a permit number that resolves in a register kept by somebody other than the operator, and it returns a company name and a status on the morning it is typed in. That is the only third-party record this reading holds on any of these businesses. Two of the nine come back with the permit revoked, which is precisely the sort of thing a support desk is unlikely to volunteer.
Whether the authority behind a register accepts complaints from players is a separate question, and this reading has not opened it. The entry is a record, not a desk.
The second is the page a territorial clause is published at. Thirty-nine operators in the hundred print one, and where it exists a reader can quote the operator's own list back at it without asking anybody anything. For Stake.com that clause names one country, and what a list of that length does and does not settle is worked through on the territorial clause.
What a published response time would look like
It would be a sentence with a number in it, in a numbered clause, saying how long the operator has to answer a documented request and what follows if it does not. Something in the shape of the customer-side clauses above, pointing the other way.
No document read for this index contains one. That absence is worth stating as a finding rather than as a complaint, because it is measurable and it is uniform: twelve rows, four documents apiece where they opened at all, and zero operator-side periods.
An operator that answers in four minutes is entirely possible, and several probably do. What is not possible is holding one to it.
What this index will not tell you
It will not tell you which support desk is good. That needs an account, a problem, and somebody willing to report what happened, and this desk holds none of the three: no account with any operator named here, no bets, no experience of its own.
It will not rank rows on channels either, because a channel recorded for one row and unrecorded for eleven is not a comparison, it is a reading list.
What it does hold is the material above: the clocks that exist, the direction they run in, and the two addresses that answer without anybody's help. What four documents can settle about an operator, and where each one stops, is on the four questions inside one word.