Start with the device and account name
Before filling in an account field, check which browser profile is active and whose name appears in any suggestion. This matters on a family phone and on computers shared at work. A recognised website can still be showing another person’s saved entry. If an existing session belongs to someone else, do not open its private records to work out whose it is.
Keep a verification request with its original action
Read the purpose shown in a verification message. Did you actually start the sign-in or change that the message describes? If the request arrived unexpectedly, leave the code unused and open the service through the route you already know. A person who contacts you through a separate chat should not need the code that authorises an action on your device.
Finish a session deliberately
Use the account destination’s sign-out control when you have finished on a borrowed device. Check the remaining tabs and remove any private file you downloaded during the session. Review browser suggestions that relate to your own account without deleting another user’s saved data. Closing a page can hide the screen while leaving a signed-in session available to the next person.
Share a symptom without sharing access
A support message can say that a button returned to the same page or that a recovery link had expired. Neither description needs a password or a screenshot of a verification message. Before sending an image, inspect its notification bar and visible address for private information. For a request about account ownership, go to the destination that holds the account and follow its own recovery process.
Before handing back the phone, return to its tab overview and check that the account screen is no longer visible.
