THE SHORT ANSWER

Signing out of your Google Account on a date's device does not remove a passkey you created there. You need to review your own authentication and recovery factors through your account's official settings rather than relying only on the ordinary device-session list. Work through each passkey and sign-in or recovery method you can see, and remove the passkey tied to the other person's device where the platform allows it.

Have a username or photo?

Find public social profile clues with our TraceSeek app.

Why the device-session list is not enough

It is natural to assume that signing out, or checking the list of devices signed in to your account, closes the story. It does not. A passkey you created on a date's device is a stored credential on that hardware, and signing out does not itself remove it. Someone who can unlock that device may still be able to reach the account. That is why the ordinary device-session view, on its own, can give a misleading sense of closure: it shows sessions, not the full set of credentials that can open your account. [Google Account Help: passkeys on personal versus shared devices]

  • Treat the session list as one view among several, not the final word on access.

Review your own factors from official settings

Open your account's security settings directly from a device you control, rather than through a link someone sent you, and review your authentication and recovery factors one by one. Keep this review separate from any conversation with the person. Before removing anything, note which factors you recognise so you do not lock yourself out.

  • Open your account security settings directly rather than through a link someone sent you.
  • Write down which factors you recognise before removing anything, so you do not lock yourself out.

What the official guidance actually says

Google's own help pages frame passkeys as something to create only on devices you personally own and use, not on shared devices. The same guidance notes that signing out does not remove a passkey, and that adding a passkey does not remove your existing authentication or recovery factors. Those factors should be reviewed separately using your own account settings. Read together, these points mean the review has two halves: the passkeys stored on other hardware, and the recovery and sign-in methods that remain attached to your account. [Google Account Help: passkeys on personal versus shared devices]

Separating observation, limit, and decision

When you open the settings, you will see a list of methods. Each entry is an observation: a factor exists. Its limit is that the listing tells you the factor is attached to the account, not who has used it or what they intend. Keep the practical decision distinct from both, and make it from the settings rather than from assumptions about the other person. The table below shows how to keep those three things apart while you work.

observationlimitnext step
A passkey appears that you created on someone else's deviceThe entry shows the credential exists; it does not show who has unlocked the device or whenRemove that passkey through your account settings if the option is offered
Your recovery methods include a phone number or address you no longer controlThe listing confirms the method is attached, not that anyone has used itUpdate the recovery details to ones you currently control
The session list looks clearThe source says signing out does not itself remove a passkey, so sessions are not proof of removalContinue the review of authentication and recovery factors rather than stopping here

If a control is unavailable, record and stop

Interface layouts change, and some options may not appear where you expect, or may not be available to you at all. If you cannot find or use a documented control, record that it was unavailable and stop at that boundary rather than improvising. Use the official current help pages for your account. Do not share passwords, one-time codes, or recovery details with the other person, and do not attempt to access their device or accounts to remove anything yourself.

  • Note what you could not find or use, with the date.
  • Check the official help pages for the current steps.
  • Avoid sending codes or recovery details to anyone, including the date.

Repeat the review later

A single review is a snapshot. Factor lists and recovery settings can change over time, so return to your security settings on a calm, regular schedule and check that every method listed is one you recognise and control. Keep the review small: recovery details, passkeys, and any other sign-in methods you see. The aim is not to build a case about the other person but to keep your own account openable only by you. [Google Account Help: passkeys on personal versus shared devices]

A couple more questions

Does signing out of my Google Account on their device remove the passkey?

No. Signing out does not itself remove a passkey you created on that device, and someone who can unlock it may still be able to reach the account. Review and remove the passkey through your own account settings where that option is offered.

Is checking the device-session list enough to confirm my account is secure?

No. Sessions and stored credentials are different things, so a clear session list does not cover a passkey stored on another device. Review your authentication and recovery factors separately through your account settings.

Will removing my passkey also reset my other sign-in and recovery methods?

Not necessarily. Adding a passkey did not remove your existing authentication and recovery factors, so treat them as separate items and review each one using your own account settings.

What should I do if I cannot find the passkey option in my settings?

Record that the control was unavailable and stop at that boundary. Use the official current help for your account rather than trying workarounds or asking the other person to change settings on their device.

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.