On April 1, 2026, an anonymous user filed a class action lawsuit against Perplexity AI, Google, and Meta in a San Francisco federal court, according to an investigation published by Ars Technica. The accusation: the AI search engine was sharing complete user conversations with both ad giants — including when users activated "Incognito Mode."
The 135-page complaint, available in full, reveals that ad trackers (Meta Pixel, Google Ads, DoubleClick) were embedded directly in Perplexity's code. The result: every question asked to the AI engine was transmitted to Google and Meta before Perplexity even processed it.
Incognito mode was a "sham"
The most explosive finding: even paid users who enabled Incognito mode had their conversations shared — along with their email addresses and other personal identifiers. The plaintiff calls this feature a "sham."
Non-subscribed users were even more exposed. Their initial prompts were shared via a URL that gave Google and Meta access to the entire conversation thread, not just the first message.
Among the data transmitted: discussions about investment decisions, legal advice, and medical questions. The complaint highlights that Perplexity is designed to encourage users to upload sensitive documents — medical records, financial statements — as conversations progress.
What this means for GEO and AI visibility
If you're optimizing content to appear in Perplexity's answers (GEO), this lawsuit changes the game on three fronts:
- User trust is shaken. Users who migrated to Perplexity "to escape Google tracking" now discover their queries ended up at Google anyway. If the case succeeds, expect an exodus toward alternatives like Gemini or tracking-free AI search engines.
- Perplexity query volume may decline. Fewer users means fewer GEO citations. Businesses betting exclusively on Perplexity for AI visibility need to diversify toward ChatGPT Search and Gemini.
- Regulation is coming. This class action adds to a growing list of AI data lawsuits (ChatGPT logs recently shared with news organizations, leaks via Google Search). The EU AI Act will soon require transparency obligations for AI engine data flows.
What you should do now
For marketing leaders and SEO consultants, three concrete actions:
- Audit your multi-engine GEO strategy. If your content is optimized for just one AI engine, you're vulnerable. Structure your data (schema.org, FAQ, long-form content with sources) to get cited by ChatGPT, Gemini AND Perplexity.
- Monitor Perplexity referral traffic in your analytics. If this lawsuit triggers a user migration, your GEO traffic will redistribute. Identify now which AI crawlers are actually accessing your site.
- Double down on E-E-A-T content. In a climate of distrust toward AI engines, content signed by identifiable experts with verifiable sources will be favored by all engines — AI and traditional alike.
Our take
The irony is brutal: Perplexity built its brand on being the search engine "without Google's ad model." Yet Google and Meta's ad trackers were running in the background all along. If confirmed, this doesn't just hurt Perplexity — it damages the credibility of the entire "independent AI search" segment. For your clients, the message is clear: don't put all your GEO eggs in one basket. Diversify, structure, and above all — verify.
Sources
- → Ars Technica — Full investigation on the Perplexity class action
- → Full complaint (PDF) — Doe v. Perplexity AI, 135 pages
- → Local News Matters — Complaint analysis and tracker identification
Growth and SEO content strategist, I founded Cicéro to help businesses build lasting organic visibility — on Google and in AI-generated answers alike. Every piece of content we produce is designed to convert, not just to exist.
LinkedIn