Unexpected messages
A login notice from an unknown device, an unexpected password-change email or an unexplained sign-out are all warning signs.
Account security
This page separates four responsibilities — password, verification code, device and recovery — so that a problem is matched to the right action instead of a general warning.
Four separate security duties
The password is the first layer: long, unique and never reused. Meeting those three conditions removes a large share of risk, because one leaked password cannot open several accounts.
Verification is the second layer: a code sent to email or phone proves the request came from you. That code is never shared, and anyone claiming to be support while asking for it is not support.
The device is the third layer: phone, tablet and computer — knowing which one you use and who else can touch it matters. Recovery is the fourth: knowing the route back into an account before access is lost saves time later.
Three steps if something looks wrong
Change the password
Sign in, preferably from a trusted device, and change the password to one you have never used before.
Check sessions
End sessions on devices you do not recognise and clear saved passwords from the browser.
Tell support
If it is not fully resolved, write to support with the time, device name and what you saw; never include a password or code.
Signs not to ignore
These three situations are the most common, and each needs a different response.
Lost phone
If a phone is lost or stolen, change the password quickly and tell support; also secure the linked email.
Details entered on a bad link
If you typed a password on an unknown link, change it immediately and keep a record of that address.
Safe devices and safe habits
Keep a screen lock on your own phone and use biometrics where available. On a shared device, sign out after every session and never choose “remember this password”.
If anyone asks for your password, verification code or full account details while you are seeking help, refuse. Your question number, the date and the kind of problem are enough for support to move forward.
Security questions
What makes a good password?
Long, unique and not reused elsewhere; change it from time to time.
Will support ever ask for my password?
No. A request for a code or password is a red flag; report it instead.
What if someone accessed my account?
Change the password, end unknown sessions, then write to support with the details and check the recovery page.
What should I include in a message?
Account name, time of the problem, device and browser; never a password, code or full personal data.