Before You Write: Quick Safety Check
Before sending any message, review this checklist:
- Do not send passwords.
- Do not send OTP codes.
- Do not send 2FA or verification codes.
- Do not send bank card or bank account data.
- Do not send UPI details.
- Do not send document photos or ID scans.
- Do not send your full phone number.
- Do not send your home address.
For screenshots, keep them minimal:
- Crop out anything unrelated.
- Hide account ID.
- Hide balance.
- Hide contact details.
- Hide any personal or financial data.
If a screenshot cannot be cleaned safely, do not send it.

Topics We Can Review
The editorial team can review content issues related to this site, including:
- Whether an instruction is clear
- Whether a menu path makes sense
- Where a setting is usually found
- Whether the wording is confusing
- How notifications are described
- What a term means in the interface
- Why two element names may differ
- Suspicious external links shown on this site
- Translation issues
- Problems with tone, structure, or presentation
The scope is limited to site materials and how they explain interface-related topics.
Requests We Do Not Handle
We do not handle:
- Account recovery
- KYC or verification cases
- Bonus or promo disputes
- Deposits
- Withdrawals
- Chargeback requests
- State-by-state legality checks
- Winning advice
- Betting strategies
- Requests for a “working link”
- Requests for a “mirror”
- Requests for a “current domain”
Do not send these requests to the editorial channel.
Choose the Right Request Format
1) Factual error in an article
Subject line: Factual error on page
What to include: Page URL, exact quote, and a short explanation of what is incorrect
What you’ll get: A review of the reported line and, if confirmed, a correction in the article
2) Unclear step or confusing instruction
Subject line: Unclear step in guide
What to include: Page URL, step number or quoted line, and what part is hard to follow
What you’ll get: A readability review and possible rewrite for clarity
3) Wrong term, label, or translation
Subject line: Term or translation issue
What to include: Page URL, the exact term used, and the term or wording that appears more accurate
What you’ll get: A terminology check and, if needed, an editorial update
4) Interface does not match the guide
Subject line: Interface mismatch
What to include: Page URL, section name, what the guide says, and what you see instead
What you’ll get: A check of the article against the described interface change, with an update if the mismatch is valid
5) Suspicious external link on this site
Subject line: Suspicious link report
What to include: Page URL, where the link appears, and why it looks unsafe or misleading
What you’ll get: A safety review of that link and removal or correction if needed
6) General editorial feedback
Subject line: Editorial feedback
What to include: Page URL if relevant, brief comment, and the specific part of the content you want reviewed
What you’ll get: A read by the editorial team and consideration for future updates
Message Privacy
Incoming messages are used only to answer the feedback and improve site materials.
Your data is not sold. Access to correspondence is limited. Only the minimum information needed to review the report is kept.
Where applicable, you may ask for the correspondence to be deleted. To do that, use the same editorial channel and identify the message you want removed without sending extra personal data.