Contact Us
Messages from readers help keep this site accurate and useful, so we are always glad to hear from you. Perhaps a detail on one of our pages no longer matches what a casino shows at sign-up, or an explanation of verification or withdrawal limits left you with more questions than answers. Either way, our team wants to know.
How to reach us
The simplest route is email: [email protected]. A short subject line helps us direct your message, for example "Correction", "Feedback" or "Site question". If you are reporting an error, please include the page address and, where possible, the source showing the up-to-date information, such as a casino's published terms.
What we can help with
- Corrections: outdated bonus terms, payment methods, game details or licensing information on a brand page.
- Feedback: suggestions on how we explain sign-up, deposit limits, identity checks or wagering rules.
- General questions: how the site works, how pages are updated, or anything else about our content.
What we cannot do
We are an independent information site, not a casino operator. We have no access to anyone's player account and cannot help with deposits, withdrawals, bonus disputes, verification requests or account closures. For any of these, please contact the casino's own support team directly, usually through live chat or the help section on its website. Keeping a record of your conversations and transaction references with the operator can be useful if a problem needs escalating.
When to expect a reply
We read every message and aim to respond within a few working days. Messages that flag factual errors are prioritised, as accuracy matters most to readers comparing sites. Busier periods can occasionally mean a slightly longer wait, and we appreciate your patience.
Any personal details you send us are used only to deal with your enquiry, as set out in our privacy policy.
This site is intended for readers aged 18+ only. If gambling is causing you concern, free and confidential support is available from GamCare and BeGambleAware.
