Start by deciding what kind of message you need to send
A website message is most useful for issues such as a broken internal link, a page that does not render correctly, an outdated sentence, a navigation problem, or a correction to information published on this site. Account status, password recovery, identity verification, transaction history, and private balances belong to the service that controls that account.
Useful website-report details
- The page or section where the issue occurred.
- The device type and browser name.
- The approximate time of the problem.
- The exact visible error wording.
- Whether the same problem appears in the normal system browser.
This context can help reproduce a website problem without exposing account secrets.
Information to leave out
Do not send passwords, OTPs, recovery codes, bank passwords, card PINs, full payment-card details, or full identity documents through a general website message. If a screenshot is needed to show a layout or error, crop or cover account identifiers and secret codes first.
Account-specific issues need account-specific records
If an external page loads correctly but the account is locked, rejected, under review, waiting for verification, missing a transaction, or showing a membership state you do not understand, the account service has the records needed to investigate. A general website message cannot see or change those private records.
Contact details must be verified before publication
No public email address, phone number, or support handle has been supplied for this website in the current project information. Rather than publish a guessed address, this page explains what to prepare and where the problem belongs. If verified website contact details are added later, they should be shown consistently here and in the relevant support area.
Urgent credential exposure is different from ordinary contact
If you think a password, OTP, recovery code, bank password, or payment credential has been exposed, secure the affected account or payment method through a channel you independently verify. Do not wait for an ordinary website-content response before taking steps to protect a compromised credential.
