This provision prohibits Customer from processing Protected Health Information through the Services unless a Business Associate Agreement has been separately executed between Customer and Perplexity.
This analysis describes what Perplexity AI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This clause establishes a prerequisite BAA requirement for any healthcare-adjacent use case, and non-compliance creates both contractual breach exposure and potential HIPAA regulatory liability for Customer organizations that process PHI without the required agreement in place.
The updated terms now apply to multiple Perplexity enterprise products (not just Enterprise Pro and Max), and Perplexity reserves the right to add, remove, or modify which services are covered at its sole discretion, with continued use constituting acceptance. The terms introduce automatic data sharing with third-party marketing partners for advertising purposes, though Perplexity states it does not share Customer Content. New provisions govern usage-based billing and seat count changes, including immediate effectiveness of seat increases with prorated charges and seat decreases taking effect at renewal without refund. You can review product-specific terms for Comet and Agentic services, and you may request cessation of Perplexity Controlled Information use if it conflicts with applicable data privacy laws.
View change record →This addition establishes explicit guardrails for healthcare data and creates a pathway for HIPAA compliance through BAA, critical for enterprise customers in regulated industries.
View full change record →Under this provision, Customer organizations in healthcare or adjacent industries must confirm execution of a Business Associate Agreement with Perplexity before using the Services in any workflow involving Protected Health Information as defined by HIPAA.
Cross-platform context
See how other platforms handle HIPAA Protected Health Information Restriction and similar clauses.
Compare across platforms →"Customer may not use the Services to create, receive, maintain, transmit, or otherwise process any information that includes or constitutes 'Protected Health Information', as defined under the HIPAA Privacy Rule (45 C.F.R. Section 160.103), unless Customer and Perplexity have executed a Business Associate Agreement.Excerpt from Perplexity AI's Perplexity Enterprise Terms
1.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This clause establishes a prerequisite BAA requirement for any healthcare-adjacent use case, and non-compliance creates both contractual breach exposure and potential HIPAA regulatory liability for Customer organizations that process PHI without the required agreement in place.
Under this provision, Customer organizations in healthcare or adjacent industries must confirm execution of a Business Associate Agreement with Perplexity before using the Services in any workflow involving Protected Health Information as defined by HIPAA.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.