Perplexity AI
Perplexity AI, Inc. · EFROS US AI Vendor Governance Index entry
Composite governance score
F = inadequate posture for any regulated workload. Re-evaluate before procurement.
About this vendor
Answer engine combining proprietary retrieval with multiple foundation models (GPT, Claude, Sonar). Differentiated on citation-grounded responses over raw chat.
- Enterprise tier
- Perplexity Enterprise Pro, Perplexity API (Sonar)
- Consumer tier
- Perplexity Free, Perplexity Pro
- Vendor homepage
- https://www.perplexity.ai
Twelve-axis governance scoring
Each axis is scored Yes / Partial / No / N/A against public evidence — vendor trust portals, BAAs/DPAs, SOC 2 report cover pages, published methodology documents. N/A applies when the axis is structurally inapplicable (foundation models, for example, defer Section 1557 to the downstream healthcare deployer).
| Axis | Status | EFROS note | Source |
|---|---|---|---|
| BAA / DPA available | No | No BAA available as of May 2026 — Perplexity is not a HIPAA business associate. Do not use for PHI workflows. | Perplexity Privacy Policy |
| Training-data opt-out | Partial | Enterprise Pro contract terms exclude customer data from training. Consumer tiers: opt-out available via account settings. | Perplexity Enterprise Privacy |
| US data residency option | No | No documented US data residency configuration for enterprise customers as of May 2026. | Public posture review |
| SOC 2 Type II report | Partial | Perplexity has publicly claimed SOC 2 Type II completion. Report distribution via direct request, not a self-serve trust portal. | Perplexity Enterprise security page |
| ISO/IEC 42001 attestation | No | No ISO/IEC 42001 attestation. | Public posture review |
| NIST AI RMF self-attestation | No | No public NIST AI RMF self-attestation. | Public posture review |
| Colorado AI Act readiness | No | No Colorado AI Act compliance statement. | Public posture review |
| HHS-OCR Section 1557 readiness | N/A | Section 1557 is deployer responsibility for any clinical use — but the absence of a BAA makes Perplexity unsuitable for PHI use cases. | HHS-OCR Section 1557 — deployer scope |
| FRB SR 11-7 readiness | N/A | SR 11-7 is deployer responsibility for any banking use. | FRB SR 11-7 — deployer scope |
| ABA Formal Op 512 readiness | N/A | ABA Op 512 is practitioner responsibility for any legal research use. | ABA Formal Op 512 — practitioner scope |
| Subprocessor list public | Partial | Perplexity uses multiple model vendors as subprocessors (OpenAI, Anthropic, Mistral). Subprocessor list available to enterprise customers under NDA. | Perplexity Enterprise Privacy |
Trust-center maturity
No self-serve trust portal. Enterprise security documentation available on request. Material gap for regulated buyers.
Source: Perplexity Enterprise
Deep dive
Overview
Perplexity is best understood as an answer-engine layer that fans out to multiple foundation models behind the scenes. The governance gap is structural: Perplexity inherits some posture from upstream models but doesn't sign HIPAA BAAs and doesn't publish a Colorado AI Act / NIST AI RMF posture. Strong for general research, weak for regulated workflows.
Strengths
- Citation-grounded responses reduce hallucination risk vs. raw chat
- Enterprise contract excludes customer data from training
- SOC 2 Type II claim
Weaknesses
- No BAA — disqualifies for PHI
- No US data residency option
- No NIST AI RMF, ISO 42001, or Colorado AI Act statement
- No self-serve trust portal
Best-fit use case
General-purpose research use cases where the citation-grounded format is a real advantage and no regulated data is involved.
Avoid when
Any PHI, regulated financial data, or privileged legal content. Do not deploy in clinical, banking, or law firm production workflows without an alternative.
Operator's take
Deploy Perplexity AI when general-purpose research use cases where the citation-grounded format is a real advantage and no regulated data is involved. The composite score of 19 (grade F) reflects a mixed posture for regulated US workloads. Skip the vendor when any PHI, regulated financial data, or privileged legal content. Do not deploy in clinical, banking, or law firm production workflows without an alternative. In every deployment, treat the cells above as a snapshot — the acquisition that gets to production safely is the one that re-verifies the trust-center posture before contract signature and rebuilds the matrix at renewal.
How this scoring is computed
The composite score blends eleven scoreable axes (BAA, training opt-out, US data residency, SOC 2, ISO/IEC 42001, NIST AI RMF, Colorado AI Act, Section 1557, SR 11-7, ABA Op 512, subprocessor transparency) with the trust-center maturity score. Axes marked N/A are excluded from the denominator so vendors are not penalized for sector-inapplicable axes. The vendor's primary sector amplifies the most relevant axes — healthcare vendors weight Section 1557 ×2, legal vendors weight ABA Op 512 ×2, banking vendors weight SR 11-7 ×2 — so the composite reflects what matters in the actual buying context.
Read the full methodology →Disagree with this scoring?
EFROS publishes scoring rationale per cell with a public source. If you have evidence that a specific axis should score differently — a new BAA, a new certification, a documented policy change — submit a formal challenge below. We re-score and publish the result with the next quarterly edition (or as a mid-quarter changelog entry if the change is material).
Disagree with a score?
Every cell in the EFROS Index is source-cited. If you have a public source that contradicts a score for Perplexity AI, submit a formal challenge — we re-verify against the source and respond within 14 days.
Other vendors in Foundation model
Same category, scored on the same twelve axes. Useful for head-to-head shortlisting.
Take the scoring into production
The Index tells you the posture. These engagements turn the posture into a deployable program — vendor selection, governance policy, sector overlay, audit-ready evidence.