GET IN TOUCH
Please fill out the form below and we will reach out to you
Before contacting support
Contact pages work best when the question is specific. Before sending a message, write down the page or topic you were reading, the app or club name involved, and the exact point that needs clarification. A short, clear message is easier to answer than a broad request with missing context.
For club-related questions, include only practical details: the club ID or listing you are checking, what source gave you that information, what rule or setup step is unclear, and whether you need help finding the right support path. Do not send sensitive account details through a general contact form. If a platform has an official support channel, use that channel for account-specific issues.
Good questions to ask
- Is this guide still current for the latest app version?
- Which page explains club IDs or referral IDs in plain language?
- What should I check before trusting a club listing?
- Where can I find the safest route for official app support?
If your message is about a correction, include the page URL and the sentence that looks outdated. That helps keep the site accurate for other readers. If your message is about a club comparison, focus on structure and source clarity rather than promises or outcomes.
Contact FAQ
Can I ask for help understanding a club ID?
Yes. Keep the question focused on terminology, source clarity, and how to verify current instructions.
Should I share account-specific details here?
No. Use official app or platform support for private account matters.
What makes a useful correction request?
Send the page URL, the outdated phrase, and the safer or more current wording if you know it.
Can I suggest a guide topic?
Yes. Topic suggestions are useful when they describe a recurring player question or confusing term.
How to write a better support question
A useful support question explains the situation without oversharing. Start with the guide or page you were reading, then describe the exact term, club listing, or setup step that confused you. If you are asking about a club ID, include whether the question is about finding the ID, checking whether it is current, or understanding how referral information is different from club information.
Good messages are short but complete. They give enough context for a helpful answer and avoid private account details that belong only in official platform support. If you are unsure whether a detail is sensitive, leave it out and ask where that type of question should go.
Simple message template
Page I was reading: [URL]. Topic I need clarified: [club ID, referral ID, app setup, support route, or rules]. What I already checked: [source or page]. My question: [one specific question].
What happens after a correction request?
Correction requests are most useful when they point to a specific sentence, outdated link, or unclear instruction. The page can then be reviewed, updated, and checked again publicly. This process keeps the site focused on current, practical guidance rather than stale copied information.
When to use official support instead
Use official app or platform support for account access, private settings, identity checks, app errors, or anything that requires looking inside a private account. This site can help explain public terminology and reading paths, but it should not replace the proper support route for private matters.
Response expectations
Most contact requests should be treated as editorial or guidance questions. A helpful reply points the reader to the most relevant guide, explains which detail should be verified, and avoids asking for private account information. If the topic belongs with official platform support, the safest answer is to direct the reader there instead of collecting sensitive details through the website.