Keep control of credentials, codes and devices
Passwords, verification and control of a device have different roles in account security. Unexpected codes, unfamiliar access messages or urgent demands for private information are reasons to pause, understand the situation and choose an appropriate response.
Warning signs and first responses
A single sign does not prove unauthorised access, but these situations deserve attention.
| Topic | What to know | Practical context |
|---|---|---|
| Unexpected code | You did not start a request | Do not share it; check the relevant service |
| Unfamiliar device | An access message you do not recognise | Compare the time and activity with your own use |
| Urgent money demand | Payment claimed to restore access | Stop and verify through an established contact |
| Unfamiliar address | Changed spelling or an unknown link | Open the known address yourself |
Different secrets have different roles
A unique, long password limits the effect of credentials exposed elsewhere. A distinctive passphrase is preferable to a simple change of a reused word or a birth date. If you use a password manager, protect its main password and the device that unlocks it as well.
A one-time code is part of a verification process, not something to give to someone claiming to verify you. Do not send a password or code to a person presenting themselves as support. If you did not initiate the request, do not approve it merely because the message looks familiar.
Email and phone access can be important to recovery. An old number, shared mailbox or unlocked notification screen can weaken that control. Use security options actually provided by the relevant service; reading this guide does not itself change an account setting.
Extra care on a shared device
When borrowing a phone, avoid saving credentials in the browser. Sign out of the relevant service after use and close sensitive tabs. Private browsing does not guarantee protection from every kind of access or monitoring on a device controlled by someone else.
Do not install remote-control software or share your screen at an unfamiliar person's request. If that has already happened, end the connection and check important accounts from a trusted device. When keeping evidence, hide codes and personal details.
Priorities when something seems wrong
Stop the suspicious action
Do not follow the link, send money or share a code. Note the time and claimed sender.
Check what you control
Use a trusted device to examine the relevant account, email, recovery contact and available sessions.
Contact the responsible party
Report account issues to that service. For a link or wording problem on ao999, email us without private credentials.
Account security questions
Why avoid reusing a password?
Credentials exposed at one service may be tried elsewhere. Use a distinct password for each important account.
Should I send a verification code to support?
Keep codes and passwords private. Verify a contact through a known route rather than relying on their claimed identity.
Does an unfamiliar access message prove a compromise?
Not on its own. Compare its time, device and activity, then take protective steps if uncertainty remains.
How can I share a screenshot safely?
Hide phone numbers, email addresses, codes, balances and unrelated personal information. Keep the error and relevant time visible.