Last reviewed: September 26, 2026 · Based on current OpenAI security documentation.
If you want to check your ChatGPT login history, ChatGPT now provides security tools that make it easier to review recent account activity. Security History can show recent security events such as sign-ins, sign-outs, password changes, multi-factor authentication changes, passkey changes, and other security-setting activity. Active Sessions is different: it helps you review sessions that are still associated with your account and sign unfamiliar sessions out.
To check your ChatGPT login history on the web, open Settings → Security and login → Security history. Review the event type and time together with any available device and approximate location information. To see sessions that are currently active, open Settings → Security → Active sessions. Menu wording can vary as ChatGPT interfaces are updated.
The important distinction is simple: Security History helps answer “What happened?” while Active Sessions helps answer “What is still signed in?” This guide explains how to use both, what an unfamiliar device or location may mean, and what to do if you believe someone else accessed your ChatGPT account.
- Can you see your ChatGPT login history?
- How to check ChatGPT login history
- What Security History shows
- Security History vs Active Sessions
- How to see devices logged into ChatGPT
- What to do about an unknown device or login
- 7 ChatGPT account security checks
- What ChatGPT login history does not prove
- Frequently asked questions
Can You See Your ChatGPT Login History?
Yes. ChatGPT now provides a Security History area for reviewing recent security events associated with your OpenAI account.
According to OpenAI, Security History can include events such as sign-ins, sign-outs, password changes, changes to multi-factor authentication (MFA), passkeys, and other security settings. Available records may also include time, device, and approximate location information.
That makes Security History useful when you are trying to answer questions such as:
- Did someone sign into my ChatGPT account?
- Was my password or authentication setup changed?
- Do I recognize the device associated with a sign-in?
- Does the timing match something I did?
- Should I secure the account because an event looks unfamiliar?
Your ChatGPT login history is not the same as your conversation history. It is also different from ChatGPT Computer History, which relates to computer activity used as context on supported systems.
How to Check ChatGPT Login History
OpenAI’s current instructions place ChatGPT Security History inside the account security settings on the web.
-
Open ChatGPT.
Sign in to the OpenAI account whose activity you want to review. -
Open Settings.
Use your account menu to open ChatGPT’s settings. -
Select Security and login.
Look for the section containing your account security and sign-in controls. -
Select Security history.
This opens the list of recent security-related account events available for your account. -
Review each event in context.
Check the event type and time together with any device and location information shown.
Do not judge an event from the location alone. Compare the event type + time + device + approximate location. OpenAI notes that some device or location details can be approximate or unavailable.
If every event matches your own activity, you may not need to take additional action. If you see a sign-in, authentication change, password change, or other event you do not recognize, move to the security-response steps later in this guide.
What Does ChatGPT Security History Show?
Think of Security History as a recent record of important account-security events rather than a complete record of everything you have done in ChatGPT.
| Security event | Why it may matter |
|---|---|
| Sign-in | Helps you identify when account access occurred and whether the available device or location information looks familiar. |
| Sign-out | Can help explain why a previously active session ended. |
| Password change | An unexpected password change deserves immediate attention. |
| MFA change | A multi-factor authentication change you did not make can be a significant warning sign. |
| Passkey change | Check whether you recognize when and why the passkey configuration changed. |
| Other security-setting changes | Review any unfamiliar security modification together with the time and device information provided. |
Security History is most useful when you combine several clues. For example, an unfamiliar city by itself is weaker evidence than an unfamiliar city, unfamiliar device, unexpected sign-in time, and a security-setting change that you did not perform.
ChatGPT Security History vs Active Sessions
This is the most important difference to understand when checking ChatGPT account activity.
| Feature | Main question it answers | What it covers |
|---|---|---|
| Security History | What security-related events happened? | Recent sign-ins, sign-outs, password changes, MFA changes, passkey changes, and other security events. |
| Active Sessions | Which known sessions are currently active? | Signed-in browser or first-party OpenAI app sessions known through session management. |
| Chat History | Which conversations are in my account? | Your saved ChatGPT conversations, subject to your settings and product behavior. |
| Computer History | What supported computer activity has been captured as context? | A separate feature from account sign-in and session security. |
If your question is “Did somebody access my account?”, start with Security History.
If your question is “Is another device still logged into my account?”, check Active Sessions.
If you are researching the separate computer-context feature, use our guide to ChatGPT Computer History and privacy controls instead.
How to See Which Devices Are Logged Into ChatGPT
To review devices logged into ChatGPT, use the Active Sessions area rather than relying only on Security History.
- Open ChatGPT Settings.
-
Open Security.
Depending on the current interface, security controls may appear under a closely related security-and-login label. - Select Active sessions.
-
Review each available session.
When available, OpenAI may show browser or device information, first-party app context, approximate location, sign-in date and time, trusted-device status, and whether the row represents your current session.
A session can represent a signed-in browser session or a first-party OpenAI application session. OpenAI also notes that one browser row can sometimes represent sessions across multiple first-party OpenAI products.
A row marked as your current session is the session you are using now. OpenAI says you cannot end that current session from its individual row. To end it, sign out normally or use the option to log out of all sessions.
How to Log Out an Unknown ChatGPT Device or Session
If an active session looks unfamiliar and the individual logout option is available:
- Open Active sessions.
- Find the session you do not recognize.
- Select Log out.
- Confirm the logout.
If the session is marked as a trusted device, the confirmation may also remove its trusted-device status.
How to Log Out of All ChatGPT Sessions
If you are unsure which session is responsible—or you simply want to reset access across your devices—you can use Log out of all sessions.
This signs you out across active sessions, including the one you are currently using. OpenAI says it may take up to approximately 30 minutes for other ChatGPT sessions to be logged out.
Logging out an unfamiliar session is useful, but it should not be your only response if you believe another person obtained your credentials. Review your password or sign-in method, authentication settings, Security History, and account recovery options as well.
What If You See an Unfamiliar ChatGPT Login or Device?
An unfamiliar item deserves investigation, but it does not automatically prove that your account was hacked.
OpenAI states that device and location details can be approximate or incomplete. Networks, mobile connections, VPNs, browser changes, app sessions, and other technical factors can also make account activity look different from what you expect.
Use this decision process instead of reacting to one field alone.
Example: Strange Location, Familiar Device
Imagine that Security History shows a sign-in from a nearby city rather than your exact location, but the time, browser, and device correspond to something you recognize.
That mismatch by itself is not enough to conclude that another person accessed your account because OpenAI explicitly describes location information as approximate.
Example: Unknown Device Plus Security Change
Now imagine you see a device you do not recognize, at a time you were not using ChatGPT, together with an authentication or security-setting change you did not make.
That combination deserves a much faster response. Review Active Sessions, secure your credentials, verify your authentication methods, and follow OpenAI’s account-security guidance.
7 ChatGPT Account Security Checks to Do Now
If your ChatGPT login history contains something unfamiliar—or you simply want to tighten account security—work through these seven checks.
1. Review Security History
Look for sign-ins, sign-outs, password changes, MFA changes, passkey changes, and other security events that you do not remember performing.
2. Review Active Sessions
Open Active Sessions and compare the available device, browser, app, location, and sign-in information with the devices you actually use.
3. End Sessions You Do Not Recognize
Log out unfamiliar individual sessions when possible. If you cannot confidently identify the correct session, use the all-sessions logout option.
4. Change an Exposed or Reused Password
If you use a password to sign in and think it may have been exposed, shared, guessed, or reused somewhere else, replace it with a strong, unique password.
Never paste your real password, verification code, recovery key, or authentication secret into ChatGPT while troubleshooting. See our AI privacy checklist for what not to share with ChatGPT.
5. Review Multi-Factor Authentication
MFA adds another verification step to the sign-in process. Check whether your authentication settings are still configured the way you expect, especially if Security History shows a change you did not make.
6. Review Other Signed-In Environments
Think beyond your primary computer. Check old phones, tablets, work computers, shared browsers, travel devices, temporary browser profiles, and any other environment where you may previously have signed in.
If you use AI features inside broader browsing workflows, our AI Browser Checklist explains how to reduce account and browsing-session exposure.
7. Contact OpenAI If Activity Still Looks Unauthorized
If your review still points to activity you did not authorize, follow OpenAI’s official account-security instructions and contact OpenAI Support through the Help Center.
CHATGPT ACCOUNT SECURITY CHECK □ Review Security History □ Compare event time, device and approximate location □ Review Active Sessions □ Log out sessions I do not recognize □ Change my password if it may be exposed or reused □ Review MFA, passkeys and sign-in methods □ Contact OpenAI Support if unexplained activity remains
What ChatGPT Active Sessions May Not Show
Active Sessions is useful, but it is important to understand its scope.
According to OpenAI, Active Sessions does not show or manage every possible third-party connection. Its current documentation specifically says it does not show or manage:
- Third-party app sessions
- Connected apps
- “Sign in with ChatGPT” sessions used only for third-party services
- Codex CLI sessions
Active Sessions also focuses on sessions known through session management. A recently signed-out session is not the same thing as a currently active session, which is another reason Security History and Active Sessions should be used together.
OpenAI currently says Active Sessions is not available for accounts linked to an organization’s SSO sign-in, including SAML or OIDC. If you use a managed workplace account, your available security controls may therefore differ from those on a personal account.
What ChatGPT Login History Does Not Prove
Account-security information is most helpful when its limitations are clear.
An Unfamiliar Location Does Not Automatically Mean Someone Hacked Your Account
OpenAI describes location information as approximate. Treat it as one clue, not definitive proof of who accessed an account.
Security History Is Not Your Chat History
A security-event record tells you about account-security activity. It does not mean that every action taken inside every conversation is recorded there.
Active Sessions Is Not a Complete List of Every Connected Service
OpenAI excludes several third-party and external-session categories from the Active Sessions view. Do not assume that the screen is a universal inventory of every service that has ever interacted with your OpenAI account.
A Familiar Device Does Not Make Every Event Safe
Look at the complete context. If a familiar browser appears beside an unexpected security-setting change, investigate the event rather than dismissing it solely because the device name looks familiar.
Missing Details Do Not Automatically Mean Something Is Wrong
OpenAI says some session, location, or device details may be unavailable or incomplete. Missing information by itself should not be treated as proof of compromise.
ChatGPT Login History vs Suspicious Activity Alerts
A suspicious activity alert is not the same thing as Security History.
OpenAI may display security alerts when it detects unusual or potentially risky behavior, such as unexpected sign-in behavior, unusual usage patterns, or multiple concurrent sessions. OpenAI also notes that these alerts can be cautionary and do not necessarily prove wrongdoing.
If you receive an alert, use Security History and Active Sessions as evidence-gathering tools rather than guessing what happened from the warning alone.
I noticed account activity that I do not recognize in my OpenAI account. I reviewed my Security History and Active Sessions and secured the account. Unrecognized event type: Approximate date/time: Device or browser shown: Approximate location shown: Security steps I have already taken: Please help me review the suspected unauthorized activity. I have not included my password, verification codes, recovery keys, or other authentication secrets.
When contacting support, share enough non-secret information to identify the issue, but do not send your password, one-time verification code, recovery secret, or other credentials.
How to Read ChatGPT Account Activity Without Panicking
A useful way to review ChatGPT account activity is to separate weak signals from stronger combinations of evidence.
| What you notice | How to interpret it | Reasonable next step |
|---|---|---|
| Different nearby location only | Location can be approximate. | Compare the time and device before drawing a conclusion. |
| Familiar device at expected time | Likely consistent with your normal use, though context still matters. | Confirm the event type matches something you did. |
| Unknown active session | Requires attention because the session is still shown as active. | Log it out and review account security. |
| Unexpected password, MFA, or passkey change | Potentially significant security event. | Secure the account immediately and investigate related activity. |
| Unknown device + unknown time + security change | Multiple signals do not match your behavior. | Use the suspected-compromise response steps and contact support if needed. |
How to Reduce Future ChatGPT Account Risk
Checking your ChatGPT login history is useful after something looks wrong, but preventative account habits are more valuable over time.
- Use unique sign-in credentials rather than reusing the same password across websites.
- Enable multi-factor authentication when available and appropriate for your account.
- Do not share passwords, verification codes, passkeys, recovery information, or authentication secrets.
- Review Active Sessions periodically after using shared, temporary, or unfamiliar devices.
- Log out when you finish using ChatGPT on a computer you do not control.
- Be cautious with emails or links asking you to enter account credentials.
- Investigate unexpected security-setting changes rather than relying only on location data.
If you regularly use ChatGPT for everyday work, also read How to Use ChatGPT Effectively for practical usage and privacy habits.
Official OpenAI Security Resources
Because account-security features can change, use current first-party documentation when a menu, limitation, or security procedure differs from what you see.
Keeping Your OpenAI Account Secure
Covers Security History, account security practices, and responding to suspected unauthorized access.
Managing Active Sessions in ChatGPT
Covers active sessions, trusted devices, individual logout, logout-all behavior, availability, and current limitations.
OpenAI Suspicious Activity Guidance
Explains security alerts and the steps OpenAI recommends when account activity appears unusual.
ChatGPT Login History FAQs
Can I see my ChatGPT login history?
Yes. On the web, OpenAI’s current guidance says to go to Settings → Security and login → Security history. Security History can show recent security events such as sign-ins, sign-outs, password changes, MFA changes, passkey changes, and other account-security changes.
How do I check who logged into my ChatGPT account?
Start with Security History and compare the event time, device information, and approximate location with your own activity. Then check Active Sessions to see whether an unfamiliar session is still active. The information can help you investigate access, but approximate device or location data should not be treated as definitive proof of a person’s identity.
How do I see devices logged into ChatGPT?
Open ChatGPT Settings, go to the Security area, and select Active sessions. When available, session rows can show device or browser information, first-party OpenAI app context, approximate location, sign-in time, trusted-device status, and whether it is your current session.
What is ChatGPT Security History?
Security History is an account-security feature that shows recent security events associated with your OpenAI account. It is designed for reviewing events such as sign-ins, sign-outs and changes to important account-security settings.
What is the difference between Security History and Active Sessions?
Security History focuses on past security events. Active Sessions focuses on sessions currently known as active. Use Security History to understand what happened and Active Sessions to determine which sessions may still be signed in.
Can I log ChatGPT out of another device?
Yes, when an individual session has a logout option, you can end that session from Active Sessions. You can also use Log out of all sessions to sign out across active devices. OpenAI says logout propagation across other ChatGPT sessions may take up to about 30 minutes.
Why does my ChatGPT login location look wrong?
OpenAI says location information can be approximate or unavailable. A location mismatch alone is therefore not enough to prove unauthorized access. Compare the location with the time, device, event type, and your own activity.
What should I do if someone else may be using my ChatGPT account?
Review Security History and Active Sessions, remove unfamiliar sessions, change your password if you use one and think it may be compromised, review your authentication methods, and contact OpenAI Support if unexplained activity remains.
Bottom Line
ChatGPT login history is now much more useful for account-security checks. Use Security History when you need to understand recent sign-ins or security-setting changes, and use Active Sessions when you need to see which known sessions are still active.
Do not treat a strange location as automatic proof of account compromise. Compare the event type, time, device, approximate location, and active-session information together. If several details do not match your activity, secure your account and follow OpenAI’s official suspected-compromise guidance.
For broader privacy protection, continue with our 15 things you should never share with ChatGPT and the AI Browser Safety Checklist.
