The documented way to address old account access on a shared device is to review Active sessions in security settings, then log out of the relevant individual session or all sessions. These controls address sessions associated with the account, but they do not establish that the shared device has been cleared of saved sign-in information or other local traces.
How to check it
The session-management guidance provides a direct review process:
- The user opens Active sessions in the account’s security settings.
- They review the recent sessions and trusted devices associated with the account, paying particular attention to unfamiliar or no-longer-wanted entries.
- They log out of the relevant individual session, or select the documented control for logging out of all sessions.
A trusted-device entry is included in the review, but its presence is not described as proof that the device is currently signed in—or that no other access remains.
What the logout controls do not confirm
The guidance confirms that individual-session and all-sessions logout are available. It does not say that either option removes browser-saved passwords, automatic sign-in settings, local storage, open tabs, history, downloaded files, screenshots, or other files on the device.
It also does not explain how to remove a trusted-device entry or what effect removing one would have. A session logout should therefore not be treated as a complete device cleanup.
What still needs checking
Before leaving the shared device, the user should confirm:
- The intended account is signed out.
- Saved credentials cannot restore access without a deliberate sign-in.
- No other account or service remains signed in.
- Sensitive content has not been left in tabs, history, downloads, screenshots, or local files.
These are separate device-level checks, not additional controls documented in the session-management guidance.