1. Open the account’s official device controls
Reach the account through its independently known website or app. Avoid using a sign-in link from an unexpected security message as the starting point. Confirm which account you are reviewing, particularly when personal and project accounts are available in the same browser.
Google’s documented example is its account Security & sign-in area, with Manage all devices under Your devices. The view includes current and recent sessions. Other services may expose different controls and retention periods, so use the documentation for the account you actually hold.
Sources: [1]
2. Compare entries with your known access
List the devices, browsers, and approved apps you normally use for this account. Include a retired phone, a recent browser-profile change, or a shared computer you used temporarily. Keep this inventory private and limited to what you need for the review.
Google explains that multiple sessions can belong to one device, including separate browsers, apps, or sign-ins. A repeated device name is therefore not enough to identify a duplicate or an intruder. Open the available details and compare them with your actual recent activity.
Sources: [1]
3. Interpret times and locations together
Google says displayed activity times can include background synchronization, and a listed location may be nearby rather than exact. Read the device, browser, time, and place together before drawing a conclusion. An unfamiliar detail deserves review without being treated as conclusive evidence of compromise.
Write down the specific uncertainty: a device you do not own, a browser you have not used, or access after a device was retired. Distinguish a remembered event from a guess. If you cannot establish that an entry is yours, do not dismiss it merely because one other field looks plausible.
Sources: [1]
4. Follow the provider’s supported action
For a retired session or unfamiliar access, use the official controls and current security guidance. Google provides sign-out controls and directs unfamiliar-device cases to its account-security process. Read the action’s scope before confirming it so you understand which session or device is affected.
Avoid experimenting with destructive device-management actions during a routine access review. Remote sign-out and erasing a device are different tasks. Preserve access to your legitimate recovery methods, and use the existing recovery process if the provider asks you to reauthenticate. Do not share verification codes or passwords in a review note.
Sources: [1]
5. Confirm the resulting status
Return to the device list and check the recorded status after a supported sign-out action. Keep a minimal note of the date, the reason for the action, and any unresolved issue. Avoid storing screenshots that expose more account or location information than the review needs.
Do not infer that sign-out removed files already downloaded onto a device, or that a recent-session view is a complete forensic history. If unfamiliar activity remains, continue through the provider’s official security or recovery guidance. This article explains a review process; it has not inspected your account or established that any session is unauthorized.
Your quick checklist
- The correct account is opened through a known official route.
- Known devices and browsers are compared with the list.
- Times and locations are interpreted in context.
- Unfamiliar access follows the provider’s security process.
- Resulting status and unresolved questions are recorded minimally.
Sources & scope
Google supports the example controls and session-detail limitations. The comparison and minimal-note workflow is ATN editorial guidance. No account was inspected, and sign-out is not represented as erasing previously downloaded material.
- Google Account: See devices with account access (opens in a new tab)Source checked October 10, 2026
Published October 10, 2026. No affiliate links or paid placements in this guide.
