AI Tool Profile
Perplexity Passport: Plans & Data Boundaries
Perplexity launched Deep Research as a research mode that runs many searches, reads sources, reasons through the material, and returns a structured report.
Verification & Sources
- Evidence state
- Recheck due
- Source links
- 2
- Freshness
- Needs recheck: checked June 8, 2026
- Last updated
- August 26, 2026
What this evidence state means
- Definition
- The claim was previously checked, but its review window expired or a material change may have invalidated it.
- Required provenance
- The prior evidence and check date are retained, together with the expiry or change signal that triggered recheck.
- Owner
- Kingy freshness queue owner and assigned editorial reviewer
- Freshness rule
- This is already outside its freshness rule. It must not be presented as current until reviewed against current evidence.
- Disputes and corrections
- Use “Suggest a correction” on the record. Kingy editorial reviews the cited evidence, records material corrections, and changes or removes the state when it is not supported.
Key source checks
Suggest a correction
Kingy Product Passport · public-copy candidate
Perplexity
Perplexity consumer controls, Enterprise protections and API terms are three separate boundaries.
Bottom line
Perplexity documents consumer AI data retention as enabled by default with a prospective opt-out, while Enterprise plans have a separate no-training statement.
Before you use it
Confirm the plan family and whether a control affects future data only; do not carry consumer or Enterprise claims into the API Platform.
What can change
Plan names and limits can change; consumer prices, quotas and Sonar API behavior remain outside this Passport.
What the official sources support
availability
Perplexity distinguishes Standard (Free), Pro, Max, Education Pro, Enterprise Pro and Enterprise Max subscription families; the API Platform is separate.
Applies to: Current answer-product plan guide; API excluded · Evidence: perplexity-plans
privacy
Perplexity says AI data retention for consumer Free, Pro and Max accounts is enabled by default and can be disabled for future data in settings.
Applies to: Consumer accounts; opt-out is prospective per source · Evidence: perplexity-data
privacy
Perplexity says Enterprise data is never used for AI model training and documents separate retention protections.
Applies to: Enterprise plans; consumer and API excluded · Evidence: perplexity-data
Scope
Perplexity consumer and enterprise answer-product subscriptions, with plan family stated.
Excluded: Perplexity Sonar API pricing and behavior; plan availability not listed for the reader’s account or geography
Evidence still missing
- Consumer price and exact quotas are omitted pending locale/account review.
- No Kingy test of the opt-out control or retention behavior.
- Sonar API data handling remains a separate Passport gap.
Official sources
- Which Perplexity subscription plan is right for you? — Perplexity
- Data Collection at Perplexity — Perplexity
- Enterprise pricing and billing FAQ — Perplexity
Freshness and corrections
Source checked 2026-08-09. No correction form or intake is enabled. Until a public correction workflow has an owner and retention policy, corrections are handled only through a separately authorized editorial process.
The Kingy Brief
Follow The Kingy Brief.
One consequential launch, one pricing, limit, or shutdown change, one hands-on test, one exact prompt or Test Pack, and one try / watch / skip verdict.
Free · Choose your subjects · Double opt-in · Unsubscribe anytime
Tool Links
Launch History
Introducing Perplexity Deep Research
Perplexity launched Deep Research as a research mode that runs many searches, reads sources, reasons through the material, and returns a structured report.
- Launch readiness
- 6.9 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Perplexity launched Deep Research, a mode that runs many searches, reads sources, reasons through the material, and returns a structured report (perplexity.ai). It is…
Introducing Perplexity Pages
Perplexity introduced Pages, a publishing surface that turns research sessions into shareable, structured articles.
- Launch readiness
- 6.4 / 10
- Demo evidence
- Not scored yet
- Creator-story fit
- Not scored yet
Score definitions and rubric
These are launch-record readiness heuristics, not product ratings.
Launch readiness
How complete and reviewable the launch record is, not the quality of the product.
Inputs and weights: Launch date 15%; qualifying source 10%; what launched 10%; demo 15%; category 10%; audience 10%; editorial assessment 10%; traction evidence 10%; creator or audience fit 10%.
Evidence inputs: Reviewed launch metadata, public source links, demo links, taxonomy, audience, editorial notes, and recorded traction signals.
Demo evidence
Whether the record contains useful, reviewable demonstration evidence; it is not a rating of product output quality.
Inputs and weights: Working demo URL 45%; video walkthrough 25%; clear description of what launched 10%; audience 10%; editorial assessment 10%.
Evidence inputs: Demo and video URLs plus the reviewed launch description, audience, and editorial notes.
Creator-story fit
Whether a launch has enough demonstrable evidence and audience relevance for a useful creator story; it does not predict views or guarantee coverage.
Inputs and weights: Demo evidence 25%; visual creator category 15%; audience 15%; editorial assessment 15%; traction evidence 10%; pricing clarity 10%; API or open-weight evidence 10%.
Evidence inputs: Reviewed demo, category, audience, editorial, traction, pricing, API, and open-weight fields.
- Scale
- 0.0–10.0. A present qualifying input receives its published weight; a missing input receives zero. Scores are rounded to one decimal.
- Assigned by
- Suggested by the deterministic field-completeness helper and assigned or approved by a Kingy editorial reviewer.
- Rubric and check date
- Rubric version P0-2026-08-10. The record’s “Last verified” date is the score check date. Checked: 2026-06-08.
- Confidence and missing data
- Confidence depends on source completeness. “Not scored yet” means no reviewed value; “Needs review” means the value or score set failed validation.
- Freshness
- Recalculate after a material launch, source, demo, pricing, audience, or traction change and during the record freshness review.
- Disputes
- Use “Suggest a correction” on the record and cite the relevant evidence. Commercial relationships cannot buy or alter a score.
Perplexity introduced Pages, a publishing surface that turns research sessions into shareable, structured articles (perplexity.ai). Researchers, Creators, and Students got a clear output format…