Perplexity can be used at work only under specific conditions. Our verdict for a typical 50–500 person company handling client or regulated data, assessed 29 July 2026: Limited. Excellent for research on public topics, and the Enterprise tier states it never trains on enterprise customer data — but on a personal account the consumer notice governs, and the query itself can leak strategy. The subtle leak is the query itself: "acquisition targets in [niche] under $20M" typed into a consumer account is confidential strategy leaving the building.
This verdict reflects Perplexity AI’s published terms as we read them on 29 July 2026. A vendor can change its terms the day after; the primary sources below are how you check.
| Vendor | Perplexity AI |
|---|---|
| Category | AI search |
| Our tier verdict | Limited (assessed 29 July 2026) — Excellent for research on public topics, and the Enterprise tier states it never trains on enterprise customer data — but on a personal account the consumer notice governs, and the query itself can leak strategy. source |
| Trains on your data? | Depends on plan / settings Depends on the tier. Perplexity states it never trains its LLMs on enterprise customers’ data, and its consumer privacy notice lists improving or creating its services "including our AI models" among its uses — with the notice expressly not applying to Enterprise and API offerings. source |
| Data retention | Perplexity’s Enterprise page advertises configurable file retention with automatic file deletion in as little as one day; consumer history follows the consumer privacy notice and account settings. source |
| Admin controls | Enterprise adds SSO and SCIM, user management over who can upload, download and share, and audit logs of user activity. Personal accounts have none of it. source |
| Compliance certifications | SOC 2 Type II, stated on Perplexity’s Enterprise page source |
| HIPAA / BAA | Not publicly documented — Not publicly documented as a BAA. Perplexity’s Enterprise page asserts the product is "GDPR and HIPAA compliant", but a compliance claim is not a Business Associate Agreement: we found no published BAA route, terms or request process. Treat that sentence as your cue to ask for the signed document, not as the document. |
Depends on the tier. Perplexity states it never trains its LLMs on enterprise customers’ data, and its consumer privacy notice lists improving or creating its services "including our AI models" among its uses — with the notice expressly not applying to Enterprise and API offerings.
Retention: Perplexity’s Enterprise page advertises configurable file retention with automatic file deletion in as little as one day; consumer history follows the consumer privacy notice and account settings.
Not publicly documented as a BAA. Perplexity’s Enterprise page asserts the product is "GDPR and HIPAA compliant", but a compliance claim is not a Business Associate Agreement: we found no published BAA route, terms or request process. Treat that sentence as your cue to ask for the signed document, not as the document. As a rule: no signed Business Associate Agreement means no protected health information (PHI) — a BAA is the gate, not the security posture. A vendor can hold every certification on the market and still be the wrong place for PHI, because what makes PHI processing lawful for a covered entity is the contract, not the encryption.
Comparing vendors on this specifically? See BAA status for all 26 tools →
SOC 2 Type II, stated on Perplexity’s Enterprise page. Treat that as the vendor’s own statement and ask for the current report under NDA — a SOC 2 report has a defined scope and a fixed audit window, and neither is visible from a badge on a trust page. A certification is also not a contract: it describes how Perplexity runs its controls, not what your agreement with them permits.
HIPAA is the gate: Not publicly documented as a BAA. Perplexity’s Enterprise page asserts the product is "GDPR and HIPAA compliant", but a compliance claim is not a Business Associate Agreement: we found no published BAA route, terms or request process. Treat that sentence as your cue to ask for the signed document, not as the document. Until a BAA is confirmed in writing, treat Perplexity as off-limits for anything containing PHI — patient names, appointment details, clinical notes, even "anonymized" summaries that could be re-identified.
For SEC/FINRA-regulated firms the questions are recordkeeping and confidentiality: can communications through Perplexity be captured for books-and-records requirements, and do the data terms hold up in vendor due diligence? Enterprise adds SSO and SCIM, user management over who can upload, download and share, and audit logs of user activity. Personal accounts have none of it.
The privilege question comes first: entering client-confidential facts into any third-party AI service must be evaluated as a potential disclosure. Because training and retention on Perplexity depend on account type and settings, assume client matter data is off-limits unless your firm controls the account and has verified the terms.
Every vendor claim above traces to a document the vendor publishes, and every document below is one we actually opened and read — each carries the date we read it. All of them were read on 29 July 2026. The verdict date on this page is not a build stamp and is not "today": it is the oldest of those dates, because a verdict is only as current as the stalest document under it. Rebuilding the site does not move it.
Where a fact is not in one of these documents, the page says so rather than filling the gap. That is why some rows read "not publicly documented" or "not established from a primary source" instead of naming a certification or rounding an open question to a convenient answer.
Why the tier verdict is "generic": Limited is the right starting classification for most 50–500 person companies — but a healthcare company, a law firm, and a SaaS startup should not have identical tool lists. The $79 policy kit classifies Perplexity and 25 other tools specifically for your industry, company size, and the data your team handles.
And a verdict has a shelf life: vendor data policies change quietly — a terms update can move a tool between tiers overnight. This page states what we read on 29 July 2026. The $149/mo Monitor plan exists precisely because that date keeps receding.
Perplexity can be used at work only under specific conditions. Our verdict for a typical 50–500 person company handling client or regulated data, assessed 29 July 2026: Limited. Excellent for research on public topics, and the Enterprise tier states it never trains on enterprise customer data — but on a personal account the consumer notice governs, and the query itself can leak strategy. The subtle leak is the query itself: "acquisition targets in [niche] under $20M" typed into a consumer account is confidential strategy leaving the building.
Depends on the tier. Perplexity states it never trains its LLMs on enterprise customers’ data, and its consumer privacy notice lists improving or creating its services "including our AI models" among its uses — with the notice expressly not applying to Enterprise and API offerings.
Not publicly documented as a BAA. Perplexity’s Enterprise page asserts the product is "GDPR and HIPAA compliant", but a compliance claim is not a Business Associate Agreement: we found no published BAA route, terms or request process. Treat that sentence as your cue to ask for the signed document, not as the document. As a rule: no signed Business Associate Agreement means no protected health information (PHI) — a BAA is the gate, not the security posture. A vendor can hold every certification on the market and still be the wrong place for PHI, because what makes PHI processing lawful for a covered entity is the contract, not the encryption.
SOC 2 Type II, stated on Perplexity’s Enterprise page. Treat that as the vendor’s own statement and ask for the current report under NDA — a SOC 2 report has a defined scope and a fixed audit window, and neither is visible from a badge on a trust page. A certification is also not a contract: it describes how Perplexity runs its controls, not what your agreement with them permits.
We classify Perplexity as Limited for a typical 50–500 person company, assessed 29 July 2026. Excellent for research on public topics, and the Enterprise tier states it never trains on enterprise customer data — but on a personal account the consumer notice governs, and the query itself can leak strategy. Your own classification should reflect your industry, data types, and which plan or account type your company actually uses.
New to the topic? Start with what shadow AI is — definition, examples and risks, then measure your own exposure with the shadow AI scorer.
Your team is using Perplexity. Does your AI policy cover it?
Most policies name a handful of tools and go stale the month after they are written. Two ways to find out where yours stands: check an existing policy for gaps in 30 seconds, or generate a policy that classifies Perplexity by name — free preview, no account. Starting from scratch? The free 14-section AI acceptable use policy template is the document itself, ungated.
A 4-document AI policy kit — acceptable use policy, tool tier list, acknowledgment form, manager FAQ — that classifies Perplexity and 25 other tools for your company, industry, and data. Generated in about 10 minutes.
Generate my policy kit →We re-check vendor terms monthly and alert you when Perplexity’s data policy changes — plus regenerate your whole kit so it never goes stale. This directory is a snapshot — Monitor is the live feed.
See Monitor plan →Already have an AI policy? Check it for gaps in 30 seconds →