Open your Google Account's devices and sessions view, read each entry as a device plus its sessions rather than a single sign-in, and interpret recent times cautiously: a recent timestamp can reflect background synchronization rather than a person actively using the device. Sign out only the sessions you no longer recognize as yours, then change your password if you are unsure who had access.
Find public social profile clues with our TraceSeek app.
Start with what a session entry actually represents
A session is an authorized connection between a device and your account, and one device can hold more than one session. That means a single phone or laptop may appear as several entries, or one entry may stand for more than one session. Before you decide anything, read the list as device-plus-session pairs and note which devices you can account for from your own use. A partner's laptop you borrowed for an evening is expected; a device model you have never owned deserves a second look. [Google Account Help: Devices with account access]
Separate three questions before you act
Most anxiety after borrowing a device comes from blending questions. Keep them apart: (1) Is this device one I expect to have access? (2) Is this session still active, and do I want it to remain? (3) Does the timing tell me anything about a person's behavior? The first two are practical decisions you can make with the list in front of you. The third is usually not answerable from a timestamp alone, so treat it as an open question rather than a conclusion.
- Write the device names you recognize on paper before opening the list, so you are not deciding while surprised.
- Mark each entry as mine, borrowed, unknown, or unsure.
Read recent timestamps as activity signals, not intent
A recent time on a session can reflect background synchronization rather than a person actively using the device. Mail clients, calendar apps and similar services refresh on their own schedules, so a timestamp near the moment you are looking does not mean someone opened, read or acted on a message. Similarly, an older timestamp does not prove a device is unused. Use timestamps to sort entries, not to reconstruct another person's actions. [Google Account Help: Devices with account access]
| observation | limit | next step |
|---|---|---|
| A session shows a time minutes ago | May be automatic background sync, not a person at the keyboard | Leave it unless the device itself is unfamiliar |
| One device appears more than once | A device can have multiple sessions | Sign out only the sessions that are not yours |
| A device name is unfamiliar | Names can be generic or outdated after updates | Sign it out, then change your password |
| A borrowed device still appears | Access may persist after you hand it back | Decide whether it should remain and sign out if not |
Sign out deliberately, one session at a time
You can sign out individual sessions, which lets you remove access from a device or a specific connection without disturbing everything else. Work through your marked list: sign out unknown and unsure entries and any borrowed device that should no longer hold access. Recheck the list afterward, because signing out a session ends that connection but does not by itself explain how it began. If several unfamiliar sessions share a device or location, sign out all of them before moving on. [Google Account Help: Devices with account access]
- Sign out unfamiliar sessions first, then borrowed devices you have returned.
- After signing out, change your account password if you cannot explain how access started.
- Review connected apps separately if you want a fuller picture of third-party access.
Decide about the partner conversation separately
Your session review answers an access question, not a trust question. If you borrowed a partner's device, the useful output is a clear list of what still has access and what you removed. Whether to raise the topic with them is a separate choice you can make after the technical picture is settled. If you do raise it, describe what you observed and what it cannot show, rather than presenting a timestamp as evidence of reading.
- Hypothetical wording: "I checked my account sessions after using your laptop and saw a device I didn't recognize, so I signed it out. I'm not sure what it was."
- Avoid opening with an accusation; ask about access rather than intent.
Keep the review small and repeatable
A short review after lending or borrowing devices is more useful than a deep audit under stress. Note the date, the sessions you removed and any entry you chose to keep, so a future review has a baseline. If unfamiliar access returns after you signed out and changed your password, treat that as a reason to review your recovery options and connected apps rather than to re-examine timestamps for meaning they may not carry. [Google Account Help: Devices with account access]
A couple more questions
A session shows activity from a few minutes ago. Does that mean someone read my messages?
Not necessarily. A recent time can reflect background synchronization rather than a person actively using the device, so the timestamp alone cannot establish that anyone opened or read anything. Check whether the device is one you expect to have access, and act on the access question rather than the timing.
Why does one phone or laptop appear several times in my sessions?
A single device can have multiple sessions, so repeated entries are normal and do not by themselves indicate extra people or suspicious behavior. Sign out only the specific sessions you no longer want rather than assuming the whole list is compromised.
I borrowed a partner's device and signed in. What should I do now?
Find that session in your devices list and sign it out once you no longer need it, since access can persist after you hand the device back. If you cannot tell which entry corresponds to it, change your password and review the remaining sessions.
Should I confront my partner based on a recent timestamp?
A timestamp is weak ground for a claim about someone's actions, because automatic syncing produces recent times too. Decide about the conversation separately from the technical review, and if you raise it, describe the observation and its limits instead of asserting what it proves.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.