From a4e9b954190f6632d0c709a6caf4651f7736d71d Mon Sep 17 00:00:00 2001 From: satori Date: Sat, 11 Jul 2026 00:53:55 -0700 Subject: [PATCH] Clarify Perplexity startup network traffic --- CHANGELOG.md | 4 ++++ PRIVACY.md | 4 +++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 99258c1..7e106a0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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. diff --git a/PRIVACY.md b/PRIVACY.md index c8d2ac5..90f35f7 100644 --- a/PRIVACY.md +++ b/PRIVACY.md @@ -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.