Hello everyone,
I’m reaching out for advice after a troubling experience with Bullsbet.io Casino. I’ve been a loyal online casino player for years, but this time, it seems like the casino is actively avoiding paying my winnings.
Here’s the situation: I recently won €17,000 at Bullsbet.io, but my withdrawal was denied due to an alleged “multiple accounts” issue. The casino cited my IP, device details, and cookies—even though I’ve only ever accessed my account through my private, contracted internet. I’m very careful after a similar false flag experience at another casino while using public Wi-Fi. I’d played at Bullsbet.io for three months with no issues until last week when they had major system problems.
During that period, my wagers only registered at 50%, some games became inaccessible, and I was even locked out of my account. I reported these issues immediately, but with my bonus expiring in 48 hours, I had to keep playing. A friend in the casino affiliate industry suspects Bullsbet.io might be using an in-house detection tool that can misidentify users—especially iPhone users like me.
Casino Guru reviewed my case as an “independent investigator” but ultimately backed Bullsbet.io, dismissing my complaint without substantial evidence. After reading about similar experiences from other players, I’m starting to think these accusations might be used to avoid paying winnings.
My Questions:
-Does anyone know if Bullsbet.io uses third-party detection tools? It appears they don’t, which raises concerns.
-How can I appeal this decision or bring in an external authority? Both
Bullsbet.io and Casino Guru seem unwilling to assist further.
-Could someone in the industry reach out to Bullsbet.io on my behalf? I’m willing
to offer a success fee if it leads to my payout.
After years of loyalty, this situation is incredibly frustrating. Any advice or support would mean a lot, and I’d urge caution to anyone considering Bullsbet.io.
Thanks for reading, and let’s stand up for fair play!
Edited by user Monday, October 28, 2024 6:01:58 PM(UTC)
| Reason: Not specified