Code requests
Do not give a one-time code to someone claiming to provide support; it is an authentication secret.
Use a long, unique password. A leak at one service can affect other accounts sharing the same password. Protect a password manager with a strong master password as well.
Access to email and phone can be as important as the account itself. Where the genuine service offers additional verification, understand its instructions before enabling it. This page does not guarantee such a feature at a particular service.
Unexpected password notices, unfamiliar devices and changed contact details are warning signs. Open the correct address independently rather than following the message link. Refreshing a browser is not a sufficient response to a security issue.
Avoid an unfamiliar or possibly compromised device.
Check control of the associated email and phone.
Follow the service’s real security or recovery process and retain relevant records.
Be particularly cautious when urgency, secrecy and unexpected payment demands appear together.
Do not give a one-time code to someone claiming to provide support; it is an authentication secret.
Do not let an unfamiliar person control your screen or install software.
Requests to pay a personal account to unlock access are suspicious; verify independently.

If you enter a password on a false page, inspect other accounts using it. Change to unique passwords from a trusted device. Where session management exists, end unfamiliar sessions.
Retain times, messages and addresses, but redact secrets in screenshots. Use recovery guidance if access is lost, and contact the relevant financial provider about unauthorised financial activity.
Change it promptly after suspected exposure; uniqueness and length matter.
Do not share it. Verify the request by opening the genuine service independently.
No. Session expiry can be normal; unexplained changes are a separate warning sign.
Use the cause-based steps on the account recovery page.