Casinia Casino — player complaint #14903, 2026-06-17: other
Casinia Casino: a player complaint filed on 2026-06-17, about other, 6,000 CHF in dispute. Published on Casino Guru. One of 37 complaints filed in English about this operator. The text below is the player's own words, as published on the source site.
All complaints about Casinia Casino: statuses, disputed sums, risk index →
The player from Switzerland attempted to change her registered email address with Casinia but did not receive a response after submitting the necessary documents and bank statements. She sought assistance as her account balance remained inaccessible. We requested additional information and evidence of communication with the casino to investigate the issue further. However, due to the player's lack of response to our inquiries and reminders, the complaint was closed at that time. The player could reopen the complaint in the future if she wished to continue seeking assistance.
Complaint data
- Case number
- #14903
- Filed
- 2026-06-17
- Status
- Status unknown
- Category
- Other
- Disputed sum
- 6,000 CHF
- Place among complaints about Casinia Casino
- 22 of 37 by date, newest first
- Source
- Casino Guru — original ↗
- Text
- 88 words, as published
All 37 English-language complaints about Casinia Casino — as a list by date; the summary, statuses and disputed sums are on the operator page.
Similar complaints about Casinia Casino
- Casinia Casino - Player cannot close account and is seeking refund. 2026-08-04 50 EUR Under review
- Casinia Casino - Player’s winnings have been confiscated. 2026-08-02 4,200 EUR
- Casinia Casino - Player’s account keeps getting reopened without consent. 2026-07-28 4,883 EUR Resolved
The same complaint about other operators
- Stake 383 complaints in English
- Bovada 167 complaints in English
- Paddy Power 138 complaints in English
- BetFury 132 complaints in English
- Parimatch 127 complaints in English
← Back to Casinia Casino in NeRating
How the risk index is calculated and how complaints are labelled — the method behind this section.