Get in Touch
The contact form exists for a specific set of purposes. Content-related questions and corrections sit at the top of the list.
Found an error in an article? A multiplier number that doesn’t match the current version of the game. A screenshot that shows an old interface. A term used in a way that doesn’t align with what the game actually displays. These corrections are the most valuable type of message the form receives. Casino games update. Providers change things. An article written three months ago might not reflect today’s reality. Reader reports catch discrepancies that the internal review cycle hasn’t reached yet.
Questions about game mechanics are welcome too. If an article explains something in a way that doesn’t quite land — the description of provably fair verification feels unclear, the multiplier math section needs more examples, the difference between demo and real-money mode isn’t obvious enough — that feedback shapes how the content gets revised. The goal is clarity. If something isn’t clear, the writing needs to improve.
Suggestions for new content help the editorial team prioritise. Which games need coverage. Which topics come up in search results but don’t have a dedicated page on the site. Which aspects of existing pages could use deeper treatment. The team can’t cover everything at once, but knowing what readers are looking for helps decide what gets written next.
Reports about technical issues with the site itself are useful too. A page that won’t load. An image that doesn’t display. A link that leads to a 404 error. A layout that breaks on a specific phone model or browser. The team doesn’t always catch these things from the inside, especially across the range of devices and browsers that visitors use.
General feedback about the site’s tone, structure, or approach lands in the same inbox. If the writing feels too technical, too casual, too long, or too short — that’s worth knowing. The site evolves based on how readers experience it, not just on what the team thinks works.
One category of messages falls outside the scope: business proposals, partnership requests, and advertising inquiries. The site handles these separately. If a message of this type arrives through the general form, it gets routed accordingly, but response times may differ from standard content inquiries.
Contact Form
The primary channel is the contact form on this page. Three fields. A name. An email address. A message.
The name is for addressing the response. First name is enough. A handle or a screen name works too. The field exists so the reply doesn’t start with an impersonal greeting.
The email address is where the reply goes. If there’s a typo in the email, the response disappears into nothing. From the reader’s side, it looks like nobody answered. From the team’s side, the reply was sent but bounced. Double-checking the email before hitting send prevents this.
The message field has no strict format. A correction can be one sentence: “The RTP listed on the Mines page says 96% but the game shows 97%.” A suggestion can be a paragraph. A question can be a few lines. Length doesn’t determine priority. Clarity does. A short, specific message gets processed faster than a long one that takes multiple readings to understand.
Messages sent through the form go to the editorial inbox. They are not published anywhere on the site. The form is not a comment section or a public discussion. Each message is a private communication between the sender and the team.
The form does not require registration. No account creation. No login. No verification beyond what the visitor chooses to include in the message.
Attachments are not supported through the standard form. If a correction requires a screenshot — for example, showing that a game interface looks different from what the article describes — the sender can describe the discrepancy in text, and the team will verify by checking the game directly. If an image is essential and the text description isn’t sufficient, the team can provide an email address for follow-up in the initial reply.
Response Time
The team works on a regular schedule. Messages sent during working hours on weekdays usually get a response within 24 to 48 hours.
Simple corrections — a wrong number, a broken link, a typo — tend to get handled on the faster end. The team reads the message, checks the claim against the current game or site, makes the fix if confirmed, and sends a short reply.
Questions that require research take longer. If someone asks why a particular multiplier works the way it does, the team may need to load the game, run some rounds, check the math, and write a response that actually answers the question. A couple of working days is typical for these.
Complex requests — suggestions for entirely new pages, detailed feedback on editorial approach, or questions that touch on regulatory topics — may get a two-part response. First, a short acknowledgement that the message was received and is being reviewed. Then, a full response after the team has had time to consider the request properly.
Weekend and holiday messages sit in the inbox until the next working day. They don’t disappear. They don’t get deprioritised. They just wait for the team to come back online.
No message goes unanswered. Even if the team can’t do what’s being asked — if the request falls outside the site’s scope, for example — the sender gets a reply explaining why and, where possible, pointing toward a more appropriate resource.
The team does not promise instant responses. Real-time chat support doesn’t exist on this site. The editorial team is small. Quality of response matters more than speed. A well-researched answer that arrives in two days serves the reader better than a vague reply that arrives in two hours.
Important Notice
This site is an information resource about online casino games. It does not operate any casino or gambling platform. It does not process financial transactions of any kind. No deposits. No withdrawals. No bet placement. No balance management. No account creation or recovery.
Messages about account problems need to go to the relevant platform’s support team. If a visitor’s casino account is locked, the deposit didn’t arrive, a withdrawal is stuck, or a bonus didn’t activate — none of these can be resolved through this site’s contact form. The team has no access to any casino operator’s systems. No ability to look up accounts. No authority to intervene in disputes between players and platforms.
The same applies to game outcomes. If a round ended unexpectedly, if the multiplier looked wrong, if the provably fair verification produced a result the player doesn’t understand — the platform’s support team is the first stop. This site can explain how provably fair systems work in general. It cannot investigate a specific round on a specific platform.
Payment processors, cryptocurrency exchanges, and wallet providers have their own support channels. Questions about transaction fees, processing times, or conversion rates belong with those services, not with this site.
For platform-specific questions, the team can sometimes point the visitor toward the right support channel — “BC Game support is available through live chat at bc.game” or “Spribe publishes their game specifications on their provider portal” — but the team cannot take action on the visitor’s behalf.
Being direct about what the site can and cannot do prevents frustration on both sides. The team would rather say “we can’t help with this, here’s who can” than accept a request it has no ability to fulfil.
Privacy Note
Personal data sent through the contact form is used for one purpose: responding to the message.
The name and email address sit in the editorial inbox for the duration of the conversation. They are not added to a mailing list. Not shared with marketing partners. Not used for retargeting or advertising. Not sold to data brokers.
The site does not send promotional emails. Submitting a message through the contact form does not subscribe the sender to anything. The only email that arrives in response is the reply to the specific message sent.
After the conversation ends, the data stays in the inbox archive. It is not extracted for secondary use. If the sender wants the data deleted, a follow-up message through the same form requesting deletion is enough. The team processes the request and confirms when it’s done.
Sensitive information should not be included in contact form messages. Passwords, one-time codes, payment card numbers, bank account details, cryptocurrency wallet keys, identity documents, or any personal financial data — none of this belongs in a message to the editorial team. If a message containing sensitive data arrives, the team deletes it without processing and notifies the sender.
No member of the editorial team will ever ask for login credentials, payment details, or identity documents. Any communication claiming to come from this site and requesting such information is fraudulent and should be ignored.
The full privacy policy is published on a separate page and covers technical data collection, cookies, analytics, and visitor rights in detail. The privacy note here covers only the contact form specifically.
What Happens After You Write
A message arrives in the editorial inbox. A team member reads it. Depending on the content, one of several things happens.
If the message reports a factual error, the team checks the claim against the current state of the game or the site. If the error is confirmed, the article gets updated. The sender receives a reply confirming the fix. If the claim turns out to be incorrect — the article was right after all — the sender gets an explanation of why.
If the message asks a question about game mechanics, the team researches the answer. Sometimes this means opening the game and testing the mechanic directly. Sometimes it means reviewing the provider’s published specifications. The reply includes the answer and, where applicable, a note that the relevant article has been updated to cover the question for future readers.
If the message suggests a new topic, the team logs the suggestion. Not every suggestion turns into a published article immediately. Some get added to the editorial queue for the next content cycle. Others get combined with similar requests to form a single comprehensive page. The sender receives a reply acknowledging the suggestion and, if timing allows, an estimate of when it might be covered.
If the message falls outside the site’s scope — account problems, payment issues, platform disputes — the team replies with a clear explanation of why the request can’t be handled here and, where possible, a pointer toward the right support channel.
Every message gets a response. The response may not always be what the sender hoped for, but it arrives. The inbox doesn’t have a delete-without-reading policy. Every message is read by a person, not filtered by an algorithm.