Perplexity Search History Disappeared? Fixes

I would start with the simplest answer: if perplexity search history disappeared, the most likely causes are not a catastrophic data wipe but an account mismatch, incognito session, moved Library view, disabled memory setting or retention rule that makes the old Threads invisible. The surprising part is that the difference between recoverable and gone can be only 24 hours in incognito, 14 days for logged-out Threads, or one Apple Relay address that looks nothing like the email you remember using.

This guide is written for a signed-in user who expected Perplexity AI to preserve research history across web, desktop, iOS and Android. It separates reversible visibility problems from real deletion events, then shows the precise checks that should happen before contacting support. During our 2026 evaluation, we treated missing history as a chain of evidence: identity, browser mode, Library navigation, settings, plan limits, retention and support escalation. That order matters because every later step becomes harder if the first one is wrong.

The practical verdict is clear. Search history is not one object inside Perplexity. It is a combination of Threads, Library entries, saved items, Spaces, Collections, Memory, browser sessions and account identity. When any one layer changes, users often describe the whole archive as “gone”. In most cases, the fix is not recovery software. It is proving that the same account, normal mode and correct Library view are active.

Why Perplexity Search History Disappeared in 2026

The first diagnostic step is to stop using the word history as if it describes one database. Perplexity calls ongoing conversations Threads. Its Help Center says a Thread includes the first question, follow-up queries, responses and sources, and that Threads are stored in History where a user can view and continue past conversations. That makes History closer to a private research archive than a browser log. It also means a missing item can be caused by account identity, interface navigation or retention behaviour rather than a single broken history feature.

In our hands-on testing on Chrome and the iOS app, the most common false alarm appeared when the user was signed in but not signed in as the same identity used earlier. Apple Relay, Google sign-in, email magic links and case-sensitive email handling can create parallel account paths. Perplexity specifically warns users to ensure the account email is identical on every device and notes that email casing can matter. That is unusually strict compared with many consumer apps, so it deserves to be the first check rather than an afterthought.

The second false alarm is mode confusion. Perplexity incognito, Chrome private browsing and logged-out searching are three different states with similar symptoms. A query can feel normal while it is being made, but it may not land in the long-term Library that a signed-in user expects. Official guidance says Threads created while logged out are automatically deleted after 14 days and cannot be recovered by Perplexity support. Incognito is stricter: Perplexity says incognito Threads expire within 24 hours and are not recoverable.

For users cleaning up older records rather than trying to recover them, the site’s Perplexity history deletion guide is the closest internal companion because it explains where Library deletion controls normally live.

Symptom	Most Likely Cause	First Check	Recovery Chance
All Threads missing on one device	Different account or Apple Relay identity	Compare exact profile email and casing	High if correct account exists
Only yesterday’s private searches missing	Incognito or private browser mode	Exit incognito and check normal Library	Low after 24 hours
Old logged-out query missing	Logged-out retention expiry	Check browser history for original URL	Low after 14 days
History hidden after UI update	Library or sidebar navigation change	Open Library or hover Home/Sidebar	High
Files missing in private mode	Incognito visibility limitation	Open normal session and check files	High if not expired

The Account Email Check Comes First

Account mismatch is the highest-yield fix because it is invisible from the search screen. A user can be signed in, see a profile icon, run Pro searches and still be looking at a different Perplexity account from the one that contains the lost Threads. This is especially common when someone uses Google sign-in on desktop, Apple sign-in on iPhone and a one-time email link on another browser.

Perplexity’s own troubleshooting article gives the clearest rule: the email address associated with the account must be exactly the same on all devices. The same article adds that email casing matters, giving the example that email@mail.com and Email@mail.com are different. It also warns iCloud+ users that a Pro subscription may be linked to an Apple Relay or Hide My Email address rather than the visible personal email they expect.

The technical implication is simple but easy to miss. A missing Library can be a successful login into the wrong identity, not a failed login. During our 2026 evaluation, the fastest proof was not opening settings generally, but taking a screenshot of the profile email on every device and comparing the visible address character by character. On desktop, Perplexity says users should click the profile picture at the bottom left, select My Account, and read the email displayed there. On Mac, the Help Center points users through the sidebar pane and Manage Account link.

Do not reset passwords, clear the browser or uninstall the app before this comparison. Those actions may erase useful local context while doing nothing to locate the real account. The right workflow is to identify the email that owns the missing Threads, sign out of the current account, sign back in using the original method, then open Library again. If an Apple Relay address is involved, save it in a password manager label so the same account can be reproduced later.

Readers who suspect the issue began with authentication friction should also compare this process with the site’s Perplexity login problems fixes because cookie, magic-link and browser-state errors often masquerade as missing history.

Account Scenario	What It Looks Like	What to Verify	Best Next Move
Google on desktop, Apple on iPhone	Both devices appear signed in, but histories differ	Profile email and Apple Relay address	Use the same sign-in provider everywhere
Email case mismatch	One account shows empty Library	Exact uppercase and lowercase characters	Sign in with the original casing
Work and personal accounts	Pro appears on one account, Threads on another	Subscription page and Library contents	Avoid switching mid-research
Shared browser profile	Threads disappear after someone else signs in	Current avatar and account page	Create separate browser profiles
One-time passcode confusion	Magic link opens another browser session	Email recipient and active browser profile	Open link in intended browser profile

Private Mode Is Not a Backup Archive

Incognito should be treated as a temporary session, not a privacy-preserving version of normal Library. Perplexity’s Incognito Mode Troubleshooting page says users can exit incognito by clicking the incognito icon at the top right. More importantly, the same official page states: “All incognito threads expire within 24 hours and are not recoverable.” That single sentence should change how researchers use the feature. It is a privacy mode for short-lived exploration, not a safe place to run work that must be cited next week.

Chrome private browsing adds another layer. A user can open Perplexity in Chrome Incognito without using Perplexity’s own incognito toggle, or they can use the Perplexity incognito mode inside a normal browser window. In both cases, the visible search experience can feel normal while persistence changes. The most reliable test is to close every private window, open a standard browser window, go to Perplexity, confirm the account email, and then open Library directly.

The practical edge case is a query that produced a public or shareable thread URL before the session expired. If the URL is in browser history, email, Slack or notes, it may still be viewable depending on how it was created and shared. If it was a private incognito Thread and no saved URL exists, support cannot rebuild it from memory. That is not a browser-cache problem. It is the product’s retention rule.

For sensitive research, the safer compromise is to use a normal signed-in session, disable data training where available, avoid saving unnecessary personal details, and delete Threads after exporting the useful citations. Enterprise plans add stronger controls, including data never being used for model training, admin controls, audit logs and configurable retention. Individual users should assume incognito is ephemeral by design.

For mobile users, the distinction is easier to miss because the app compresses navigation, so the iPhone Perplexity workflow is useful when comparing where Library and account controls appear on iOS.

Where Library, Threads, Spaces and Collections Now Overlap

The 2026 interface can make history feel missing because Perplexity now has several organisational layers. Threads are the conversation units. Library is the personal archive. Spaces are project workspaces that can group Threads, files and collaboration settings. Collections organise research into topic clusters. Memory may remember preferences or context, but it is not the same as a visible list of past Threads.

This distinction matters when a user says, “my history disappeared.” If the user means the left sidebar no longer shows a chronological list, the data may still exist in Library. If the user means a Space no longer shows a Thread, it may have been saved in the personal Library instead. If the user means the system no longer remembers a preference, that is a Memory problem rather than a Thread problem.

During our hands-on testing, the fastest recovery pattern was to search by location rather than memory. Open Library first, then filter or sort if the controls are available. Check Spaces if the missing work belonged to a project. Check Collections if the user intentionally saved a result into a topic folder. Only after those locations fail should deletion or retention be suspected.

The difference between folders and shared workspaces is clearer in the site’s Perplexity Collections guide, which treats Collections as thematic curation rather than a raw chronological history list.

For team accounts, the companion Perplexity Spaces guide helps explain why a Thread can be visible inside a project workspace but absent from a user’s expected personal flow.

Object	What It Stores	Typical Visibility	Why Users Think It Disappeared
Thread	One conversation with follow-ups and sources	Private unless shared	Wrong account or deleted Thread
Library	Saved and historical research records	User account only	Sidebar or navigation moved
Space	Project workspace with files and Threads	Private or collaborative	Thread saved outside the Space
Collection	Thematic grouping of saved research	User-controlled	Item filed under topic rather than chronology
Memory	Preferences and contextual signals	Settings-dependent	Memory disabled or not invoked

Browser and App State Fixes That Actually Matter

Once identity and mode are verified, the next layer is browser state. Cookies bind a sign-in session to a browser profile. Cached scripts can hold an old interface state. Extensions can block authentication redirects or hide storage prompts. A VPN can place the browser in a different network context from the one where a magic link was opened. These factors rarely delete Threads, but they can prevent the correct account view from loading.

The least destructive fix is to open a normal Chrome window, disable aggressive privacy extensions for Perplexity, and load the Library page after confirming the profile email. If that fails, try another browser profile before clearing all browser data. Clearing all history and cookies may solve a login loop, but it can also remove browser-history evidence that might contain a lost logged-out Thread URL. That trade-off matters because Perplexity points users to browser history when a logged-out Thread is lost.

On mobile, app state issues are simpler but still real. Force close the app, confirm network access, update the app, sign out only after recording the visible account email, then sign back in with the same provider. Reinstalling should be a late step because it can remove local traces and introduces a new risk: the user may sign in with a different method when setting up the app again.

The performance bottleneck is not usually Perplexity’s model layer. It is session integrity. A model can answer a new query perfectly while the UI is still showing the wrong account’s empty Library. That is why a clean diagnostic process beats repeated searching. Searching from the wrong account simply creates more Threads in the wrong place.

Settings, Memory and Data Controls to Check

Perplexity’s newer Memory and history controls create a second source of confusion. Memory can influence personalisation, while Search History and Threads determine what the user can revisit. Turning off a storage-related setting may not erase everything already saved, but it can stop future work from appearing the way the user expects. Conversely, turning Memory back on will not recreate Threads that were never saved or that expired in incognito.

The clean test is to separate visibility from intelligence. First, can the Thread be found as a record in Library? Second, does Perplexity remember user preferences or previous interests during new prompts? If the answer to the first question is no and the second is yes, Memory is not the missing object. If the answer to the first is yes and the second is no, the history exists but personalisation is not being applied.

Perplexity’s enterprise pricing page now lists configurable memory permissions for admins and users, data retention options, audit logs, SSO, SCIM and team insights. That tells enterprise users an important fact: admins may control how data is retained or exposed in organisation accounts. For a work account, a missing Thread may reflect workspace policy, not personal error. Individual users have fewer administrative layers but should still check data collection opt-out settings and account deletion status.

The support escalation package should include screenshots of the account page, Library view, platform, browser or app version, and whether incognito was active. Avoid sending sensitive Thread content unless requested and necessary. The goal is to prove account identity and session context, not to disclose private research unnecessarily.

Plan Limits, Pricing and Hidden Constraints

Pricing rarely explains a missing search history by itself, but plan limits shape the environment in which history is created. Free, Pro, Education Pro, Max, Enterprise Pro, Enterprise Max and Sonar API do not have identical limits, privacy defaults or support paths. Perplexity’s Help Center states that Free users get basic support, while Pro, Education Pro and Max receive priority support through Discord and Intercom. Enterprise Pro and Enterprise Max receive dedicated support. That difference matters when a user needs help investigating an account-level issue.

The current enterprise pricing page lists Pro at $17 per month when billed annually, Enterprise Pro at $34 per month per seat when billed annually, and Enterprise Max at $271 per month per seat when billed annually. The Help Center also references Enterprise Pro starting at $40 per month or $400 per year per seat, which reflects non-annual or standard seat framing. Because pricing and limits change, procurement teams should verify the active checkout page before relying on any published comparison.

The plan matrix is still useful for troubleshooting. Enterprise plans add organisation file repositories, internal knowledge search, advanced seat management, SSO and SCIM, dedicated support and admin-controlled retention. Enterprise Max increases file repository scale to 10,000 personal files and 5,000 files per Space, adds 15 videos per month and provides the highest access to advanced models. Those capabilities can change where work lives. A file-backed answer may be inside a Space, repository or app connector rather than a personal chronological Library.

For users trying to decide whether missing features are really plan limits, the site’s Pro versus Free comparison gives a useful consumer-level framing before escalating to enterprise documentation.

Plan	Public Price Signal	History-Relevant Notes	Support Path
Free	$0	Limited Pro searches and basic Library when signed in	Basic Help Center
Pro	$17/month annual on enterprise pricing page	More advanced models, file answers under published limits	Priority support
Education Pro	Discounted education plan in Help Center	Student or educator verification required	Priority support
Max	Advanced individual tier	Highest individual access and early features	Dedicated or higher priority support
Enterprise Pro	$34/seat/month annual on enterprise page	SSO, SCIM, org repository, admin controls	Dedicated support
Enterprise Max	$271/seat/month annual on enterprise page	Highest limits, retention controls, audit logs, larger repositories	Dedicated support
Sonar API	Pay-as-you-go credits	No web/app Pro features or complimentary API credits	API support path

A Step-by-Step Recovery Workflow for Missing Threads

The recovery workflow should preserve evidence before it changes state. Start by writing down the platform, browser, app version and the exact time the Thread was last seen. Then capture the visible profile email. If multiple accounts are possible, check each one deliberately rather than guessing. Do not create new searches in the suspected wrong account until the original account has been located.

Next, exit all private modes. On Perplexity, click the incognito icon if it is active. In Chrome, close private windows and open a normal profile. On iOS or Android, force close and reopen the app normally. Load Library, then check Threads, Spaces and Collections. If the missing Thread was created as part of a work project, check whether the organisation or Space contains it. If it was a file-based answer, search the file repository or Space rather than only the personal Library.

1. Confirm the exact profile email on every device, including Apple Relay or Hide My Email addresses.
2. Exit Perplexity incognito and browser private mode before checking Library.
3. Open Library directly and review Threads from newest to oldest where filters are available.
4. Check Spaces and Collections if the work belonged to a project or topic folder.
5. Search browser history for the original Thread URL before clearing cache or cookies.
6. Verify Search History, Memory and data settings, separating visible Threads from personalisation.
7. For enterprise accounts, ask an admin about retention, SSO, SCIM, permissions and workspace policies.
8. Send support screenshots only after the account, mode, Library and browser-history checks fail.

This order is designed to avoid self-inflicted loss. Clearing cookies too early can remove the only trace of a logged-out Thread URL. Reinstalling an app too early can push a user into the wrong sign-in method. Contacting support without a profile screenshot slows the case because support must first establish account identity.

Users on a free account should also understand what account creation unlocks; the site’s free Perplexity access guide notes why signed-in use matters for history, Collections, Spaces and cross-device sync.

When History Is Truly Gone

Some scenarios are not recoverable through the interface. Perplexity’s support article says logged-out Threads are automatically deleted after 14 days and cannot be recovered. Its incognito troubleshooting article says incognito Threads expire within 24 hours and are not recoverable. A user-deleted Thread may also be gone if the interface offers no trash or undo for that deletion path. Account deletion requests add another finality risk because account data may be removed under retention rules.

The emotional trap is to keep refreshing the Library as if a missing Thread will reappear. The more useful question is whether the Thread ever entered a durable account archive. Signed-in normal mode is the strongest evidence that it did. Logged-out mode, private browser mode and Perplexity incognito are weak evidence. A share URL, browser-history entry or exported source list can sometimes salvage the work product even when the original Thread is not restorable.

For research-heavy users, prevention beats recovery. Export or copy citations from important answers into a notes system at the end of each research session. Save important Threads into Collections or Spaces with descriptive names. Avoid running client, legal, medical or financial research in incognito unless the purpose is deliberately temporary. Use separate browser profiles for work and personal accounts so a session cannot silently drift across identities.

Privacy concerns should not be ignored. In April 2026, Local News Matters reported a proposed class action over alleged data sharing and quoted Perplexity chief communications officer Jesse Dwyer saying, “We have not been served any lawsuit that matches this description so we are unable to verify its existence or claims.” The allegation is separate from routine history recovery, but it reinforces a practical rule: do not put sensitive data into any AI product unless the retention and privacy model matches the risk.

If a missing history problem began after cancelling or changing billing, compare the account state with the site’s subscription cancellation routes before assuming the archive itself was deleted.

Technical Features, Specs and Integrations That Affect History

Perplexity’s product surface is no longer just a web search box. The platform includes Threads, Library, Spaces, Collections, file Q&A, Search modes, Research, Create files and apps, Comet Assistant, Computer, Model Council, Memory, enterprise repositories, app connectors and Sonar API. Each feature can produce or consume context differently. A missing-history complaint should therefore ask which surface generated the work in the first place.

The March 2026 Perplexity changelog says Computer for Enterprise and Computer in Slack became available to Enterprise Max and Pro subscribers. It describes Computer as running multi-step workflows across research, coding, design and deployment, routing tasks across 20 specialised models and connecting to more than 400 applications. It also lists examples involving Snowflake, Salesforce and HubSpot, plus Slack DMs and channel mentions. That expands the places where research outputs may appear: not only Library, but Slack, dashboards, app updates and structured results.

The same changelog says Comet Enterprise includes an AI-native browser with Comet Assistant for in-page research, summarisation and autonomous multi-step tasks such as booking flights, managing email and filling forms. It says enterprise administrators can deploy Comet through MDM, configure hundreds of browser policies and control which actions the agent can take. Bring Your Own Connector adds support for external tools and data sources through the Model Context Protocol, with OAuth, API key or open authentication options.

For developers, Sonar API is a separate surface. The Help Center says the API is designed for developers and businesses, uses pay-as-you-go credits, has no access to advanced models or Pro features within the web or app interface, includes no complimentary API credits, and has no data logging or storage. That means an API answer will not magically appear in the Perplexity web Library unless the developer explicitly stores it elsewhere.

Feature or Integration	Documented Capability	History Implication
Threads	Conversation history with follow-ups and sources	Primary unit users expect to recover
Library	Private place to view previous Threads	First destination for missing history
Spaces	Project workspace with files and collaboration	Thread may live in project context
Collections	Topic-based organisation	Saved item may be filed outside chronology
Comet Assistant	Browser assistant for in-page tasks	Outputs may sit in browser workflow
Computer	Multi-step workflows across 20 specialised models	Results may appear in apps or Slack
Slack Integration	DMs and channel mentions for workflows	Research may be posted to Slack
MCP Connectors	OAuth, API key or open authentication	Context may come from external systems
Sonar API	Pay-as-you-go developer access with no data storage	Developers must store their own logs

What Recent AI Search Research Adds to the Problem

History recovery is not only a convenience issue. It affects verification. When a user cannot retrieve the Thread that produced a cited answer, they lose the chain of prompts, sources and follow-up reasoning that made the answer auditable. This matters more in generative search than in classic web search because the answer is a synthesis, not just a link list.

A 2026 audit by Mowafak Allaham and Nicholas Diakopoulos examined ChatGPT, Copilot, Gemini and Perplexity across 712 real-world queries in public-interest domains. The paper reports evidence of AI-generated sources being cited across all four systems and estimates that around 16 percent of cited sources in the study were synthetic sources. The authors warn of a “risk of harm” when generative search engines treat AI-generated sources as equivalent to authoritative sources. That finding makes thread persistence part of trustworthiness: users need to revisit what was cited and why.

Aravind Srinivas, Perplexity’s co-founder and CEO, wrote on LinkedIn in early 2026, “We fixed search over your history (past threads) on Perplexity. Works really well now.” That product direction is important because it acknowledges that history search is not a side feature for power users. It is a core part of how a research engine becomes useful over time. If past Threads are hard to locate, users repeat work, lose citations and increase the chance of relying on memory rather than evidence.

The information-gain lesson is practical. Save important research into named Collections at the point of confidence, not after the project is over. Add a short final prompt asking Perplexity to summarise the sources used and the unresolved questions. Then copy that summary to an external research log. This creates redundancy without depending on scraping, unofficial extensions or fragile browser caches.

What to Send Perplexity Support

Support escalation should be precise. A vague message saying “my history disappeared” forces support to investigate account identity, platform, mode, plan and deletion status from scratch. A useful ticket gives evidence in the same order as the recovery workflow. Include the profile email screenshot, the platform, browser or app version, whether incognito was active, whether multiple accounts exist, the approximate time the Thread was created, and screenshots of the empty Library, Space or Collection view.

Do not include passwords, payment card details or sensitive prompt contents. If the missing Thread involved confidential information, describe the topic at a high level and say that sensitive contents can be provided through an approved secure support channel if required. For enterprise accounts, involve the admin early because SSO, SCIM, retention, permissions and organisation repositories can determine what support is allowed to view or restore.

The strongest support evidence is a browser-history URL for the missing Thread. Even if the Thread cannot be recovered, the URL can help support identify whether it belonged to a logged-out session, a different account, an organisation space or an incognito path. Screenshots of account emails across devices are the second strongest evidence because they reveal mismatches that users often miss.

If the issue affects Pro or subscription access as well as history, state that clearly. Perplexity’s Help Center groups thread access and Pro feature access in the same troubleshooting article because both can come from account mismatch. A user may think subscription loss and history loss are separate bugs, when both are caused by signing into a different account from the one that owns the subscription and Threads.

Takeaways

• Check the exact profile email first, including Apple Relay or Hide My Email addresses and letter casing.
• Treat Perplexity incognito as temporary because official guidance says incognito Threads expire within 24 hours.
• Search browser history before clearing cookies if the Thread may have been created while logged out.
• Open Library, Spaces and Collections separately because each can hold different parts of the research workflow.
• Distinguish Memory from visible Thread history so a personalisation issue is not mistaken for archive loss.
• Use named Collections or Spaces for important projects instead of relying on a raw chronological sidebar.
• Enterprise users should ask admins about retention, SSO, SCIM, permissions and organisation repositories.
• Contact support with screenshots, platform details and timestamps only after account, mode and Library checks fail.

Our Content Testing Methodology

This troubleshooting guide was compiled by replicating the recovery sequence across the Perplexity web interface in Chrome and the iOS account flow, then cross-checking each step against current Perplexity Help Center documentation, the Enterprise pricing page, the March 2026 changelog and indexed Perplexity Hub interface guides. We tested for account mismatch, Library navigation, incognito visibility, browser-history preservation, Memory confusion, Spaces and Collections routing, and plan-limit interpretation. Pricing, support paths, file caps, Comet, Computer, MCP and Sonar API statements were included only when supported by official documentation or clearly labelled as subject to change.

Conclusion

Perplexity search history disappearing is usually a visibility and identity problem before it is a permanent-loss problem. The decisive checks are unglamorous: confirm the exact account email, exit incognito, open Library directly, look inside Spaces and Collections, preserve browser history, and separate Memory from visible Threads. Those steps solve the majority of cases without destructive resets.

The harder truth is that some Threads are designed not to persist. Incognito sessions expire quickly. Logged-out Threads have a limited recovery window. Deleted records may not have an undo path. As Perplexity expands into Comet, Computer, Slack, MCP connectors and enterprise repositories, users also need a clearer mental map of where research outputs live. The future of AI search will not be only about better answers. It will be about durable, auditable workspaces that let people find the answer again, inspect the sources again and understand the context that produced it. Until those layers become simpler, disciplined account hygiene and external research logs remain the safest backup.

FAQs

Why did my Perplexity search history disappear?

The most likely causes are a different account, Perplexity incognito, browser private mode, a moved Library view, disabled history-related settings, deleted Threads or retention expiry. Start by confirming the exact profile email and opening Library in a normal signed-in session.

Can Perplexity recover incognito Threads?

Perplexity’s official incognito troubleshooting page says incognito Threads expire within 24 hours and are not recoverable. If you need a record later, do not run that research in incognito.

Where is Perplexity history now?

Perplexity history is normally accessed through Library or Threads. Depending on the interface, you may need to use the left sidebar, hover navigation controls, or open the Library area directly. Spaces and Collections can hold related saved work.

Does Perplexity save history when I am logged out?

Logged-out Threads are not as durable as signed-in Threads. Perplexity says logged-out Threads are automatically deleted after 14 days and cannot be recovered, so browser history may be your only useful trace.

Why are my Perplexity Threads empty on iPhone?

The most common explanation is a different sign-in method, especially Apple Relay or Hide My Email. Compare the exact iPhone profile email with the desktop account before reinstalling the app.

Can clearing cache restore Perplexity history?

Sometimes cache and cookies fix a broken session view, but clearing them can also remove browser-history evidence. Verify account email and save useful URLs before clearing site data.

Is Perplexity Memory the same as search history?

No. Memory can influence personalisation and context, while search history or Threads are visible records of past conversations. Turning Memory on does not recreate expired or deleted Threads.

What should I send Perplexity support?

Send screenshots of your profile email, empty Library or Space view, platform, app or browser version, approximate creation date, and whether incognito or multiple accounts were involved. Avoid sensitive prompt details unless support specifically requires them.

References

Allaham, M., & Diakopoulos, N. (2026). Synthetic sources?: Auditing generative search engine citations for evidence of AI-generated sources. arXiv. https://arxiv.org/abs/2605.23684

Camacho, A. (2026). Incognito mode troubleshooting. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/12639758-incognito-mode-troubleshooting

Camacho, A. (2026). Troubleshooting access to threads and Pro features. Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11464164-troubleshooting-access-to-threads-pro-features

Local News Matters. (2026, April 2). Class-action lawsuit alleges Perplexity sent user chats to Google, Meta without consent. https://localnewsmatters.org/2026/04/02/class-action-lawsuit-alleges-perplexity-sent-user-chats-to-google-meta-without-consent/

Perplexity AI. (2026). Perplexity Enterprise pricing. https://www.perplexity.ai/enterprise/pricing

Perplexity AI. (2026). What is a Thread? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10354769-what-is-a-thread

Perplexity AI. (2026, March 13). What we shipped: March 13, 2026. https://www.perplexity.ai/changelog/what-we-shipped—march-13-2026

Reuters. (2026, May 28). CNN files lawsuit against Perplexity alleging unlawful content distribution. https://www.reuters.com/legal/litigation/cnn-files-suit-against-perplexity-alleging-unlawful-content-distribution-2026-05-28/

Srinivas, A. (2026). We fixed search over your history (past threads) on Perplexity. LinkedIn. https://www.linkedin.com/posts/aravind-srinivas-16051987_we-fixed-search-over-your-history-past-threads-activity-7427089384727859200-KQ0D/