Research report · LICENSING

Can Players Complain? We Audited 8 Curaçao Casinos

Seven of the eight Curaçao-licensed casino offerings we reviewed published a clear first step for making a complaint. None exposed every element of the complaint process described by the Curaçao Gaming Authority. We confirmed only 9 of 72 disclosure checks in full. That is a finding about what a player could verify on public pages on 11 September 2026—not a legal ruling that an operator failed to follow its licence behind the scenes.

11 SEP 2026
Published
2026-09-11
Fact-checked
BullsRank Editorial
Updated

TL;DR

  • We audited eight tracked casino domains against nine public-disclosure checkpoints derived from the Curaçao Gaming Authority's Player Complaints Policy Guidelines.

  • Seven operators clearly published an email, live-chat route or complaints page. MyStake displayed a Dispute Resolution link in indexed navigation, but the relevant content returned a country block from our audit location.

  • We did not locate a public official complaint form for any of the eight offerings.

  • None of the eight publicly reproduced the complete CGA timing ladder for ordinary and responsible-gambling complaints.

  • Cloudbet was the only offering where we confirmed a specifically named service described as independent ADR.

  • None of the reviewed pages explicitly said that ADR would be free to the player.

  • Thunderpick was the only offering where we confirmed both parts of the CGA explanation: the authority does not mediate an individual dispute, but players may report suspected regulatory breaches.

  • “Not found” means not found in the pages we reviewed. It does not prove that a control is absent from an operator's internal process or account-only interface.

What Curaçao's complaint rules ask operators to disclose

The Curaçao Gaming Authority's Player Complaints Policy Guidelines describe a complete path from customer support to independent alternative dispute resolution. The policy says the complaints procedure must be visible on the operator's site and clearly outlined in its terms.

We translated that public-document requirement into nine checks. The audit asks whether a player can see the information before a dispute—not whether the operator submitted separate material to the regulator.

ID

Public-disclosure check

What counted as confirmed

D1

Complaint route

A visible email, live-chat route, form or complaints page

D2

Official complaint form

A downloadable or online form for submitting the complaint

D3

Six-month window

A clear six-month period tied to settlement or the incident

D4

Internal timing

Measurable acknowledgement and substantive-response deadlines

D5

Written final decision

A final answer in writing with reasons or supporting evidence where relevant

D6

Named independent ADR

An identifiable external provider, not merely “an authority” or generic arbitration

D7

Free ADR

An explicit statement that the player pays no ADR fee

D8

Correct CGA role

Both facts: the CGA does not decide individual disputes, and regulatory concerns may still be reported to it

D9

Human handling

A stated human-handling rule for complex and responsible-gambling complaints

The benchmark is demanding because the official policy is demanding. Ordinary complaints are supposed to be acknowledged within one week and assessed and answered within four weeks, with one possible four-week extension after prior written notice. Responsible-gambling complaints have shorter targets. Unresolved cases must have access to independent ADR free of charge, with the operator bearing the cost. Complex and responsible-gambling complaints should be handled by a human rather than AI.

The authority also draws a line that many public explanations blur. The CGA says it “does not mediate in individual disputes.” It may still use reports about malpractice or licence breaches for supervision and enforcement. Sending a player to the regulator as if it were the appeal body is therefore not the same as naming an ADR provider.

What we audited

The cohort was frozen from BullsRank's live identity data on 11 September 2026. We included offerings where the tracked domain had an established link to a Curaçao licence in that snapshot: Stake, Shuffle, Cloudbet, Roobet, MyStake, KatsuBet, Rollbit and Thunderpick.

This is an offering-level audit. The unit is the tracked domain and the public complaint information attached to it, not every brand owned by the same company and not every licence held elsewhere in a group.

For each offering we reviewed the public terms, complaints or dispute-resolution page surfaced by the operator. We did not create accounts, submit complaints, contact support or infer unpublished procedures. The review used these statuses:

  • Confirmed: the required information appeared explicitly in a reviewed public source.

  • Partial: related information appeared, but a required element was missing or the scope did not match the checkpoint.

  • Conflicting: the public wording was internally unclear or conflicted with the role described by the CGA.

  • Not found: the information was not located in the reviewed public sources. This is not proof of absolute absence.

  • Blocked: the relevant content could not be retrieved from the audit location, so no adverse inference was made.

The companion CSV contains all 72 cells, the source URL, the review date and the reason for every status.

Results: 9 of 72 checks confirmed in full

The matrix below is deliberately not converted into an operator score. A missing public sentence and a defective real-world complaint process are not the same thing.

Legend: Y confirmed · P partial · C conflicting · N not found in reviewed sources · B blocked.

Operator

D1

D2

D3

D4

D5

D6

D7

D8

D9

Confirmed

Stake

Y

N

N

N

N

N

N

N

N

1

Shuffle

Y

N

N

P

N

N

N

C

N

1

Cloudbet

Y

N

N

N

P

Y

N

N

N

2

Roobet

Y

N

N

P

N

N

N

N

N

1

MyStake

P

B

B

B

B

B

B

B

B

0

KatsuBet

Y

N

P

N

N

P

N

N

N

1

Rollbit

Y

N

N

N

N

N

N

N

N

1

Thunderpick

Y

N

C

P

P

P

N

Y

N

2

Total

7

0

0

0

0

1

0

1

0

9

Across the complete matrix, 9 cells were confirmed, 9 were partial, 2 were conflicting, 44 were not found in the reviewed sources and 8 were blocked. The eight blocked cells all belong to MyStake and were kept out of the negative count.

The first complaint step is usually easy to find

The basic contact route was the strongest part of the sample. Stake, Shuffle, Cloudbet, Roobet, KatsuBet, Rollbit and Thunderpick all told players where to start. Stake and Rollbit named live chat or support addresses. Roobet separated general support from a complaints mailbox. KatsuBet published a dedicated complaints page as well as a complaints section in its terms.

That matters. A procedure cannot work if the player cannot begin it. It is also the least expensive part of the system to publish, which may explain why it is much more common than the later stages.

MyStake requires a narrower statement. Its public navigation exposed a Dispute Resolution label in indexed results, but the page returned HTTP 403 with a country-block response from our audit location. We recorded the visible route as partial and marked the remaining checks blocked. We did not turn access failure into a finding against the operator.

Forms and measurable internal deadlines were the largest gaps

We did not locate an official complaint submission form for any offering in the sample. A generic support email is not the same as a form that captures the complainant, account, disputed event, date, category and supporting material.

We also could not confirm the complete internal timing disclosure at any offering. Several pages contained something adjacent to it:

  • Shuffle said acknowledgement and a substantive response would follow separate Complaints Handling Procedures, but the reviewed terms did not expose the dates or a working link to that policy.

  • Roobet used 30 days as the point after which an unresolved dispute moves toward arbitration, but did not publish the one-week acknowledgement and four-week response structure.

  • Thunderpick published approximate acknowledgement and resolution times for its external “DRO” stage, not the operator's internal stage.

  • Stake said it would endeavour to resolve a complaint promptly. “Promptly” is not a deadline a player can calendar.

KatsuBet published a one-year period for claims or causes of action. We marked that partial rather than conflicting because the clause does not clearly say it is the operator's implementation of the six-month regulatory complaint window. Cloudbet separately tells users to notify it about some bet matters within 30 days; its complaints clause does not publish the CGA six-month period.

These distinctions are not pedantry. A deadline must identify the event that starts the clock, the unit of time, the stage it governs and what happens if more time is needed.

ADR was mentioned more often than it was fully explained

Cloudbet was the clearest result in this part of the audit. Its terms name “CADRE, an independent dispute resolution service” and require an internal final response or a reasonable unresolved period before referral. We still did not locate a public statement there that the process is free to the player or a complete internal timetable.

Thunderpick referred to a Dispute Resolution Office and to approved ADR providers, but the reviewed text did not identify a legal provider clearly enough for a player to verify whom to contact. KatsuBet linked to the AskGamblers complaints service; the page did not establish that service as the operator's CGA-certified ADR provider. Both were therefore partial, not confirmed.

Roobet referred to arbitration under Curaçao law without naming the provider. Stake and Rollbit pointed to court remedies. A court clause may preserve a legal route, but it does not disclose the independent ADR service required by the CGA policy.

None of the eight reviewed offerings explicitly told the player that ADR would be free. That sentence is operationally important: a player deciding whether to challenge a withheld balance may abandon the process if cost is unknown.

Only one page explained the CGA's role completely

Thunderpick was the only offering where we confirmed the two-part regulator explanation. Its terms say the CGA does not mediate an individual dispute, while preserving the player's right to contact the authority about suspected regulatory breaches.

Shuffle's terms direct an unresolved or unsatisfactory complaint to the CGA without explaining the non-mediation boundary. We marked that conflicting because a player could reasonably read it as an appeal route. The other reviewed pages did not provide the complete explanation.

This is a fixable disclosure problem. The accurate ladder is:

  1. submit the formal complaint to the operator;

  2. receive the operator's final decision;

  3. use the operator's named independent ADR provider if unresolved;

  4. report suspected malpractice or licence breaches to the CGA for supervisory purposes, without presenting the CGA as the body that awards compensation in the individual case.

For a practical walkthrough, see Curaçao Casino Complaints: What the 2026 Rules Require.

What operators could fix without changing a single case outcome

Most of the missing disclosure can live on one versioned page linked from the footer and terms. A usable page would contain:

  • the official complaint form;

  • the six-month submission window and the event that starts it;

  • acknowledgement, response and extension deadlines for ordinary complaints;

  • the shorter responsible-gambling timetable;

  • a promise of a written final determination with reasons;

  • the legal name, contact details and process of the operator's independent ADR provider;

  • a clear statement that ADR is free to the player;

  • the exact role of the CGA;

  • the human-handling rule for complex and responsible-gambling complaints;

  • a visible version date and archive of replaced procedures.

This helps operators as much as players. It channels complaints into a consistent record, reduces support improvisation, defines when a case is ready for ADR and makes the business's own handling easier to audit. It also prevents customer-service language from accidentally promising a remedy the regulator does not provide.

What this audit does not prove

This research measures public disclosure, not complaint outcomes. We did not test response times by filing complaints. We did not inspect policies available only after login, evidence submitted privately to the CGA, staff training, case files or ADR contracts.

The cohort is small and deliberately narrow: eight tracked domains with an established Curaçao licence relationship in BullsRank's 11 September snapshot. It is not a census of all Curaçao licensees. The Curaçao register census covers the regulator's full register for a different question.

Pages can change after the review date. Geography and bot protection can also change what is visible. MyStake demonstrates why access failures need their own status rather than being scored as absence.

Finally, the nine checks are our operational translation of the CGA document, not a regulator-issued scoring system. We publish the cells and sources so readers can disagree with a classification without having to trust a hidden index. That evidence-first approach is described in the BullsRank methodology.

Bottom line

The reviewed operators usually told players how to open a complaint. The public trail became much thinner after that first message. Forms, measurable internal deadlines, reasoned written decisions, free ADR, the regulator's exact role and human handling were rarely disclosed in a way we could confirm.

The result should not be read as “seven bad casinos and one good casino.” Cloudbet and Thunderpick confirmed the most individual checkpoints, but neither exposed a complete process in the pages reviewed. The useful market signal is simpler: the first contact step is common; the end-to-end complaint path is not yet consistently visible.

Sources

The underlying measurements behind this report, as a CSV. Reuse it — just cite us.

Download CSV
BullsRank Editorial. “Can Players Complain? We Audited 8 Curaçao Casinos.” BullsRank, 11 SEP 2026. https://bullsrank.com/research/curacao-casino-complaints-adr-audit
Can I complain directly to the Curaçao Gaming Authority?
You may report suspected malpractice, licence breaches or whistleblowing concerns to the CGA. The authority says it does not mediate or decide an individual gambling-transaction dispute. The resolution path normally starts with the operator's formal process and then moves to the operator's named independent ADR provider.
How long do I have to file a Curaçao casino complaint?
The CGA guideline gives a player up to six months from settlement of the bet or the incident. That is the regulatory benchmark. An operator's public terms may contain other deadlines for bet queries, legal claims or internal escalation, so identify exactly which event and process each deadline governs.
How quickly should a Curaçao casino answer a complaint?
For most complaints, the CGA guideline calls for written acknowledgement within one week and assessment and response within four weeks. One additional four-week extension is possible after prior written notice. Responsible-gambling complaints have shorter acknowledgement and best-efforts resolution targets because player well-being may be at risk.
Is ADR free for a player at a Curaçao casino?
The CGA policy says unresolved complaints should be escalatable to independent ADR free of charge, with the operator bearing the process costs. In this audit, we did not locate that promise on any of the eight reviewed offerings' public pages. That is a disclosure finding, not proof that a provider would charge.
Does “not found” mean the casino has no complaint procedure?
No. It means the information was not located in the public sources and access conditions described in this audit. A procedure may exist behind login, in a support workflow or in material submitted privately to the regulator. We separate missing public evidence from evidence that a process does not exist.

Last modified .