Official documentation checked October 14, 2026.
Perplexity documents an account-wide Sign out of all sessions control. Its current public instructions do not establish the detailed “Connected Devices” table, individual Revoke buttons or IP-address list described by the older version of this article. Use the verified session control instead of searching for an unsupported menu.
For a lost or shared device, session sign-out is one part of account protection. It does not erase files downloaded to that device or secure an email account that someone else can still use to sign in again.
Choose the action that matches the device situation
If you still have the device and only want to stop using Perplexity there, use its ordinary sign-out control. If you no longer control a device, use account-wide sign-out from a trusted device and then address the lost device and sign-in provider separately.
The official Account Settings guide distinguishes signing out of the current browser from signing out of every device and browser. It does not promise that a table will enumerate all device models or identify an intruder for you.
Use the documented account-wide sign-out
- On a trusted device, open Perplexity Account settings.
- Check the email address to confirm the affected account.
- Save any unfinished work you need to retain.
- Select Sign out of all sessions and read the confirmation presented by the service.
- Be prepared to authenticate again on trusted devices, including the device used to request sign-out.
Do not confuse this with deleting sessions from the Library. In that context, “sessions” can mean saved conversations; deleting them removes content rather than serving as the sign-in security action.
Protect the identity used to sign in again
Perplexity’s account-security guide says it does not support creating an account password. Therefore, “change your Perplexity password” is not a verified recovery step. Secure the mailbox or Google/Apple identity used for authentication.
For Google, review devices with account access and enable or review two-step verification. For Apple, review two-factor authentication and trusted devices. Follow the provider’s recovery process if access is compromised. These provider controls are separate from Perplexity’s own session sign-out.
If a managed work device is involved, tell IT promptly. Do not remove management, disable authentication requirements or remotely erase a device without the appropriate ownership and organizational process.
Verify without claiming more than you observed
On another device you control, revisit a protected Perplexity function after sign-out and check whether authentication is required. Record what happened and when. A successful check on that device is useful evidence, but cannot prove the condition of an inaccessible device or every retained token.
If an old tab still displays previously loaded text, do not treat that alone as proof of an active session. Conversely, do not assume that closing a tab or uninstalling the app revoked every remote session. Check a fresh authenticated action using nonsensitive material.
Escalate unexpected access with useful details
If account-wide sign-out is missing or appears ineffective, use the Support → Contact route in Account settings. Provide the account email, time, affected app/browser and the test result. Do not send authentication codes, browser cookies or complete session exports.
Keep shared devices signed out and use a private, protected sign-in identity. Account sharing creates avoidable exposure and is discouraged by Perplexity’s security guidance. A monthly search for an unverified device-list screen is less useful than checking access when a device is lost, transferred or no longer trusted.
Glad it helped. Take a short break with a game:
Sorry about that. Search for the exact error message, or look for a tool that checks your device: