Contact the Editors
For account related requests, use the BC.Game support section inside the platform or mobile application, if it is available to you.
Contact Rules and Data Safety
You can contact the editorial team at [email protected]. Before sending your message, make sure it concerns an article, interface explanation, navigation guide, or editorial correction.
Never send us:
Screenshots can be helpful, but they must be edited first. Remove your name, email address, username, account ID, wallet address, balance, QR codes, payment references, and any other personal information.
| Safe information to include | Information to remove |
| Page URL | Passwords and authentication codes |
| Article heading | Account ID and username |
| Device type | Bank and payment details |
| Browser or application version | Full wallet addresses |
| General screenshot of a menu | Personal documents and QR codes |
| Description of the visible problem | Deposit or withdrawal references |
Message Triage: Choose the Right Route
Choosing the correct contact route helps prevent delays. Editorial questions should be sent to this portal, while account and financial issues must be directed to BC.Game support.
| Type of request | Where to write | What to include | Expected response time |
| Error in a published guide | Editorial portal | Page URL, incorrect sentence, suggested correction | 24 to 72 hours |
| Missing or outdated button in a guide | Editorial portal | Page URL, device, screenshot without personal data | 24 to 72 hours |
| Indonesian translation issue | Editorial portal | Original wording, affected section, suggested wording | 24 to 72 hours |
| Unclear navigation instruction | Editorial portal | Step number, device type, description of confusion | 24 to 72 hours |
| Suggestion for a new topic | Editorial portal | Proposed topic and why it may help Indonesian readers | 2 to 5 business days |
| Account login problem | BC.Game support | Account identifier requested through the official support process | Depends on BC.Game |
| Bonus not credited | BC.Game support | Promotion name and relevant account details through official channels | Depends on BC.Game |
| Deposit not received | BC.Game support | Payment reference through the secure support section | Depends on BC.Game |
| Withdrawal delay | BC.Game support | Withdrawal reference and requested verification details | Depends on BC.Game |
| Identity verification issue | BC.Game support | Documents only through the official secure verification channel | Depends on BC.Game |
Do not send account or payment information to our editorial email. We cannot forward sensitive data to BC.Game or investigate individual transactions.
What We Can Improve With Your Feedback
Useful feedback helps us make guides clearer for readers in Indonesia. It is especially helpful when platform menus, labels, or mobile layouts change.
You can report:
- A step that is difficult to understand
- A button that no longer appears where the guide describes it
- A menu name that has changed
- An English or Indonesian translation error
- A term that requires a clearer explanation
- A difference between the desktop and mobile interface
- A topic that should be covered in a future guide
- A screenshot that shows an interface change without personal data
A strong correction message usually contains three elements:
- The exact page URL
- A clear description of what appears to be incorrect
- The wording or navigation step currently visible on your device
How Editorial Requests Are Reviewed
When we receive a content report, the editorial team checks the published page, compares the reported issue with the visible interface where possible, and reviews related guides for the same outdated information.
Our process includes:
- Recording the request in the editorial review queue
- Checking whether the issue affects users in Indonesia
- Updating the article when the correction can be confirmed
- Adding or changing the “Last updated” date after a meaningful revision
- Replying when more non sensitive information is required
Most editorial reports are reviewed within 24 to 72 hours. Complex interface differences may require additional checks, particularly when a feature is shown only to selected users, devices, or account types.