Perplexity
Perplexity AI · AI search
Public sources reviewed . Risk classification and recommended policy are Ayliea's subjective assessments — not vendor certifications.
Scope of this recommendation
Perplexity Enterprise search; consumer accounts and autonomous browser/computer features require separate review.
Public documentation review only. Current audit reports, certificate scope, executed contracts and customer settings were not independently examined. An omitted assurance claim is not evidence that the vendor lacks it.
- Storage and processing locations
- Confirm contracted storage and processing locations, including search and model subprocessors.
- Retention and ZDR scope
- Enterprise session attachments are generally deleted after seven days, but sessions persist unless deleted. Projects and other repositories have separate retention; provider ZDR does not delete Perplexity history.
- Vendor-reported audits / certifications
- SOC 2 Type II
Why this rating
Enterprise data is not used to train Perplexity models, and provider agreements prohibit training. Use for approved research with query minimization; do not assume all uploaded material or search history is zero-retention.
Considerations before deploying
- Review file, session and Project retention separately and verify admin-control eligibility.
- Keep confidential search terms out of public-web queries; validate citations before relying on answers.
- Enforce managed accounts through identity controls rather than blocking the shared service domain.
Sources
- Enterprise privacy and retention (www.perplexity.ai)
- Enterprise offering and assurance claims (www.perplexity.ai)
Need a vendor review for your use case?
A scoping call defines the systems, data flows and vendor evidence to review for your use case.