Submit your complaint
Registered users provide operator context, issue type, chronology, and evidence.
Player protection
The complaint system exists to make operator behavior visible after the click. Registered users can submit complaints, track statuses, and follow updates in My Complaints without turning the product into a drama feed.
How it works
Users need the workflow explained plainly before they hand over chronology or evidence.
Registered users provide operator context, issue type, chronology, and evidence.
The case is checked for completeness and routed into the right handling path.
Users can follow submitted, triage, mediation, resolved, unresolved, invalid, or ignored states.
Case history, notifications, and next-step guidance stay available in the account area.
Public complaint metrics
The public layer shows complaint-system health through calm metrics, not through outrage-heavy dashboards.
Public complaint-system trust signal.
Public complaint-system trust signal.
Public complaint-system trust signal.
Visible median across public complaint history.
Recent case-status feed
These are public summaries only. Full chronology, evidence, and next steps stay inside the private case view.
bet365
User reported payout delay after additional verification request. Case remains in active handling.
Pinnacle
User reported that a high-value withdrawal remained stalled during source-of-funds review. Case is in active handling.
Betway
User disputed mismatch between landing-page wording and applied bonus restriction. Case resolved after term clarification and adjustment.
Stake
User reported no meaningful operator engagement on account restriction follow-up. Complaint status was marked ignored.
Fonbet
User reported that a higher-balance withdrawal moved into deeper KYC checks after earlier account verification. Case remains in active handling.
PARI
User reported a visible limit cut after a profitable high-volume period and disputed the lack of meaningful explanation. Case remains active.
Trust and privacy boundary
This boundary is one of the main reasons the complaint system feels serious instead of voyeuristic.
FAQ
FAQ exists to lower uncertainty around eligibility, privacy, and status logic.
Only registered users can submit complaints in MVP. The public hub remains readable to everyone, but filing and tracking cases is account-based.
Only sanitized public signals and selected summaries may appear publicly. Full case detail, evidence, and chronology stay in the private account-area case view.
Submitted means received, triage means under routing/review, mediation means active handling, resolved means handled satisfactorily, unresolved means no resolution, invalid means the case could not be accepted, and ignored means no meaningful operator engagement was recorded.
That depends on evidence quality, issue type, and operator engagement. The public metrics show median visible resolution time, while the private case page shows the current next step.
Next step
Registered users can start a complaint and then follow updates from My Complaints.
The public/private split is useful. It shows the system is real without turning complaints into spectacle.
That is the intent. Complaint surfaces should feel procedural and privacy-aware, not sensational.
Discussion
Users can ask about the process without exposing private case detail.
Comments on the complaint hub should stay calm and procedural, not emotional or accusatory.