Perplexity Comet
Perplexity AI, Inc. · perplexity.ai/comet
Comet keeps browsing data on the device by default and gives owners strong in-product controls: site blocklists, permission prompts before logins and purchases, a Stop button, and editable memory. The agent itself (assistant logic, instructions, model routing and memory) runs on Perplexity's servers and cannot be exported, inspected or run independently, so it fails most portability, auditability and verifiability tests. AI data retention for training is on by default for consumer plans.
- Browsing data stored locally by default
- Per-site blocking and allow/prohibit controls for assistant actions
- Pauses for permission before logins and purchases; Stop button
- Memory can be viewed, searched and deleted
- Self-serve data export and account deletion
- Assistant runtime is closed and cloud-dependent; no agent export
- System instructions not disclosed; no complete, tamper-evident action record
- Model choice limited to Perplexity-hosted models, gated by plan
- AI training data retention enabled by default (opt-out)
- Post-deletion retention no longer time-bound in the privacy notice
All 34 findings
Comet desktop browser with the Comet Assistant, as documented in September 2026 under the Perplexity Privacy Notice of July 2, 2026. Free, Pro and Max consumer plans; Enterprise controls noted where relevant.
Portable · Can you leave, and take the whole agent with you?
8%- P1Round-trip portability
Incomplete, delayed and not restorable: 'Export my data' delivers a ZIP of threads by email without instructions, connectors or logic, and Perplexity documents no import.
Fail - P2Complete export
Threads come through the account export and browsing data sits in the local profile, but assistant instructions, model routing, connector credentials and executable logic stay with Perplexity, as does anything that identifies the agent.
Partial - P3Independent execution
The browser runs locally, but the Comet Assistant's inference and agent logic run on Perplexity's servers. No exportable agent runs on an open-source runtime.
Fail - P4Identity continuity
Assistant identity is the Perplexity account, and nothing lets others verify it is the same agent without Perplexity.
Fail - P5No kill switch
The Assistant needs a Perplexity account and servers, and features are gated by plan, so the provider can disable or degrade it.
Fail - P6Capability independence
Memory, connectors, background assistants and agentic browsing are Perplexity-hosted services that do not survive a move to another model provider.
Fail
Transparent · Can you see everything the agent is, with ordinary tools?
25%- T1Open storage format
Local browsing data uses Chromium's on-device storage (largely SQLite and JSON), which ordinary tools can read. Assistant memory and threads sit in Perplexity's cloud in undocumented formats.
Partial - T2No hidden instructions
Perplexity does not show owners the Comet Assistant's system prompt or the tool instructions it adds to the model context.
Fail - T3No shadow memory
Queries sent to the Assistant are processed and kept by Perplexity, crash reports and IP data are collected, and consumer data is kept for model improvement by default. Provider-held data therefore exists outside owner-inspectable state.
Fail - T4Complete action history
The Assistant sidecar shows its reasoning and steps as it works, and threads persist in the account, but no complete record of every action and tool call is documented as available to the owner or leaving with the export.
Partial - T5Readable logic
The Assistant's executable logic is proprietary and server-side. Owners can save prompts and shortcuts but cannot read the agent logic.
Fail - T6No third-party influence channel
Perplexity says it does not send prompts or conversation content to advertisers, and it confirmed in 2026 that it is winding down its ads programme (sponsored follow-up questions). Owners cannot see or switch off how merchant and publisher partnerships affect ranking, and web-page content can inject instructions, as Brave's prompt-injection research showed.
Partial
Auditable · Can you reconstruct exactly what the agent did?
0%- A1No unrecorded actions
No durable record of every consequential Assistant action is documented, nor that an action which cannot be recorded does not proceed.
Fail - A2Tamper evidence
Threads and local history can be deleted without a trace, and no other way to detect changes to an action record is documented.
Fail - A3Separation from the audited
Perplexity does not document whether the Assistant, which operates the browser, can alter or delete records of its own actions such as threads or history.
Unverified - A4Readable with ordinary tools
There is no audit trail of Assistant actions. Only threads, through the account export, and local browser history can be read.
Fail - A5Corroborated interactions
No record of the Assistant's exchanges with other agents or services is documented that could be matched against a counterpart's record.
Fail
Verifiable · Can you prove the agent runs what it claims?
0%- V1Open, reproducible runtime
Comet is built on open-source Chromium, but Comet and its Assistant are proprietary and have no published reproducible builds.
Fail - V2Active config is inspectable config
Owners can see their settings but not the effective server-side configuration, such as system prompt, routing and model versions.
Fail - V3Attributable messages
The Assistant acts through the owner's web sessions and Perplexity-held connector grants; recipients have no way to verify a message came from this agent under the owner's authority.
Fail - V4Independently checkable record
No action record with checkable integrity exists, so nothing can be verified with open tools.
Fail - V5Comparable state
Agent state is split between the local profile and Perplexity's cloud, where memory and configuration are not fully exposed, so the owner cannot verify whether the whole state changed.
Fail
Modifiable · Can you change anything, without asking?
33%- M1Instructions
Owners can set personalization preferences and memories that shape responses. They cannot read or rewrite the Assistant's system instructions.
Partial - M2Memory
Saved memories can be viewed, searched, filtered, deleted or turned off in Settings. Content-level editing and provider-side derived data are not fully exposed.
Partial - M3Logic
Owners can create reusable prompts or shortcuts, and custom skills in the separate Perplexity Computer product. The Assistant's executable logic cannot be changed.
Partial - M4Tools and permissions
Owners can allow or prohibit history access, navigation and site interaction, and can block specific sites. Pro, Max and Enterprise users can add custom remote MCP connectors.
Partial - M5Model choice
Paid plans can pick among Perplexity-hosted models, for example Claude Sonnet or Opus for the agent. Local or open-weight models are not supported, and Free users cannot choose.
Fail - M6No gatekeeping
Model selection, custom connectors and parallel background assistants are limited to paid tiers.
Fail
Controllable · Is your word final?
50%- C1Communication boundaries
Owners can block sites and disallow site interactions for the Assistant, and connector access needs approval. There is no documented control over recipients or channels, and whether site blocks are enforced outside the model has not been independently verified.
Partial - C2Approval gates
Owners can have the Assistant ask before acting, per task or always. It pauses before logins and purchases, but the sensitive-action pause depends partly on the Assistant recognizing the action, and an 'Always Allow' mode removes confirmations.
Partial - C3Immediate halt
The Assistant has a Stop button, and Perplexity documents that users can stop the agent at any time or pause its access.
Pass - C4Data sovereignty
Browsing data stays local by default, but crash reports and IP data are sent even in Incognito. 'AI Data Retention' for model improvement is enabled by default on Free, Pro and Max, which is opt-out rather than opt-in.
Fail - C5Credential custody
Passwords and payment methods stay in the local browser, and Perplexity says the Assistant does not access them. Connector grants such as Gmail are held by Perplexity, can be revoked, and do not travel with the owner.
Partial - C6Full deletion
Account deletion is self-serve, and Comet's help center describes permanent erasure after 30 days. The July 2026 privacy notice replaced its 30-day commitment with retention 'as long as reasonably necessary'.
Partial
Vendors and the public can dispute any finding with evidence. Disputes and their resolutions are published.