Unique password
Do not reuse email, banking or social passwords for another account.
ACCOUNT PROTECTION
Account security depends on the destination, password, device, connection and behaviour around recovery messages. This page provides independent checks and never asks for a BH678 password, OTP, PIN or bank credential.
Do not reuse email, banking or social passwords for another account.
An OTP authorises an action and should never be forwarded to another person.
Read the complete address and resist urgent messages or copied support identities.
Create a long, unique password and store it in a trusted password manager if appropriate. Recovery email, phone and backup codes should remain under your control. Do not send a screenshot that reveals a code or account identifier.
If you did not start a recovery action, do not approve it.
An OTP is not ordinary support information. It can approve login, recovery or a transaction. No person needs to know it to explain a public help article. A card PIN or bank password should never be entered into a gaming-related support message.
Impersonation may use copied colours, logos and familiar words. Inspect the entire address and be cautious with attachments, shortened links, screen-sharing requests and remote-control apps. Urgency is a common pressure tactic.
Use an updated operating system and browser, a screen lock and a network you understand. Public Wi-Fi can make privacy harder to assess. Remove unknown apps or profiles and review permissions after any installation.
No. Treat every OTP, PIN and password as private, even if a message appears urgent.
Check the full address, spelling, connection details and unexpected requests before taking action.
No. It does not need a bank password, card PIN or account credential.