Typical corrections we can act on include:
- Outdated descriptions of a section or menu that has changed
- Incorrect terminology or a mislabelled feature
- Broken or unclear explanations of how the interface is organised
- Structural changes we haven’t yet reflected in our content
If your issue concerns your account or your use of the platform, this is not the right place, and the section below explains where such requests go instead.
Communication Safety & Data Restrictions
For your own protection, never send sensitive information through this channel. We do not need it, we do not want it, and no legitimate content correction ever requires it. Please do not send any of the following:
- Passwords of any kind
- One-time codes (OTP or 2FA)
- Banking or payment details
- Identity documents
- Seed phrases or private keys
Before attaching a screenshot, hide or crop any personal information it might contain, such as your name, account number, balance, or email address. A correction can almost always be made from the interface itself without exposing anything private. If a message ever asks you to share the data above to “verify” a request, treat it as a scam, because we will never ask for it.
Response Workflow & Timing
We aim to review and respond to editorial submissions within 24 to 48 working hours. That timeframe covers most straightforward corrections, such as a mislabelled section or an outdated description.
Some requests take longer. If a submission is complex, touches several areas, or requires us to re-check the live interface before confirming a change, the review may extend beyond the standard window. In those cases the extra time goes toward getting the correction right rather than fast, since accuracy is the whole point of this channel.
Request Classification System
Not every message belongs here, so we sort incoming requests into two clear categories. Only one of them is something we can act on.
| Request type | Examples | How it is handled |
| Informational | Interface descriptions, terminology, text, page structure | Reviewed by our editorial team |
| Operational | Account access, payments, verification, in-platform problems | Not handled here; directed to the platform’s official support, where one exists |
Informational requests are our remit and we process them directly. Operational requests fall outside what an independent information site can do, so we cannot resolve them and will point you toward the operator’s own official channels instead.
Required Information for Processing
To act on an editorial correction quickly, we need enough context to reproduce and verify the issue. The more precise the details, the faster the fix. Helpful submissions usually include:
| Detail | Why it helps |
| Device | Phone, tablet, or desktop |
| Operating system | For example, Android, iOS, Windows, or macOS |
| Browser or app version | To match what you saw |
| Exact steps taken | The sequence that led to the issue |
| Description of the problem | What is wrong and what you expected |
| Screenshot without personal data | A visual reference, with private details cropped |
With these in hand, we can locate the exact content, confirm the error, and correct it accurately rather than guessing.
Data Privacy & Handling Policy
Everything you send through this channel is used for a single purpose: improving the accuracy of our content. Submissions are not used for anything else, and they are not shared for unrelated purposes. Our handling approach is deliberately minimal:
- We do not collect or store sensitive user data.
- We do not request passwords, codes, financial details, or private keys.
- We use reports only to verify and correct the information on this site.
Keeping the data we handle to the absolute minimum is intentional. The less sensitive information that ever changes hands, the safer the process is for everyone, and an editorial correction simply doesn’t need more than the interface-level detail described above.