Contact Us
Contacting the review team
This page governs how you can reach the people who write and maintain this independent review of Inetbet, and it does not cover any matter relating to your player account, your deposits or your winnings with the casino itself. Those questions belong to Inetbet’s own support channels, not here.
The team reads and replies in English. Write your message in plain English and you will be understood.
What never belongs in a message
Do not send financial details through this form. No account numbers, no card numbers, no bank identifiers, no wallet addresses. Do not send passwords, PINs, security answers or one-time codes. Do not attach scans of your passport, driver licence, utility bill or any other identity document.
No review team needs that material to answer a question about a casino. Anyone who asks for it through a contact form is not acting on behalf of this site. A legitimate request for documentation will always come through the casino’s own verified verification process, never through an editor’s inbox.
Treat every unsolicited request for such details as a red flag and stop the conversation.
If gambling is causing you difficulty
The contact form is the wrong place for help with problem gambling. The editors cannot intervene in your play, pause your account or arrange a break from Inetbet, and no message sent here will reach the casino’s responsible-gambling team.
If you are struggling, go directly to the responsible-gambling resources listed on this site. They offer confidential support, practical tools and, where appropriate, self-exclusion programs. Those services exist for exactly this situation and they act faster than any contact form ever could.
You are not alone in this, and the help is free.
What you can expect
Messages are read in the order they arrive, and a reply comes back as soon as the team can manage. Turnaround depends on volume, so do not expect an answer within any fixed window.
Keep your question concise and specific, and the reply will be more useful. Vague queries get vague answers.