Skip to content

Clarify Perplexity startup network traffic #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adamnold merged 1 commit into from
Jul 11, 2026
Merged

Clarify Perplexity startup network traffic #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Changelog

## Unreleased

- Corrected the privacy document after a clean-profile hostname audit showed that Perplexity loads Google sign-in and several third-party service resources during initial startup.

## v1.1.0 — 2026-07-11

- Updated from Electron 31 to exact Electron 43.1.0 and electron-builder 26.15.3.
Expand Down
4 changes: 3 additions & 1 deletion PRIVACY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

The wrapper adds no AAHA analytics. It disables Chromium component updates, background networking, domain-reliability reporting, Breakpad, Translate, Optimization Hints, Media Router, and Secure DNS; known Google update/telemetry hosts are blocked.

Perplexity must still contact perplexity.ai, CDNs, model/search infrastructure, authentication providers, connectors, and linked sources. Google or Apple traffic may occur when the user deliberately selects those sign-in methods. Blocklists reduce known optional traffic but are not proof of zero third-party traffic.
Perplexity must still contact perplexity.ai, CDNs, model/search infrastructure, authentication providers, connectors, and linked sources. A clean-profile audit on 2026-07-11 showed that the Perplexity page loads accounts.google.com during initial startup, before the user selects a sign-in method. It also contacted Cloudflare Insights, Datadog, Singular, and Eppo hosts controlled by Perplexity's web application. Apple traffic may occur when Apple sign-in is selected. The wrapper does not control these service-level design choices, and blocking identity-provider resources would break the promised Google sign-in path.

Blocklists reduce known Chromium update and telemetry traffic but are not proof of zero Google or third-party traffic. AAHA_NETWORK_AUDIT=1 can be used to review current hostname behavior because Perplexity may change its web application independently.

The local profile at ~/.config/Perplexity contains cookies, sessions, cache, local storage, and preferences. Normal uninstall preserves it; --purge removes it and signs the wrapper out without deleting the Perplexity account.
Loading