“Customer may not use the Services to create, receive, maintain, transmit, or otherwise process any information that includes or constitutes "Protected Health Information"...unless Customer and Perplexity have executed a Business Associate Agreement.”
This provision prohibits use of the Perplexity API to process Protected Health Information as defined under HIPAA unless a separate Business Associate Agreement has been 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
Without a Business Associate Agreement, any use of the Services involving Protected Health Information is prohibited, creating a compliance risk for customers operating in healthcare-adjacent contexts.
Under this clause, Customers are contractually prohibited from transmitting or processing Protected Health Information via the API unless a Business Associate Agreement is separately executed with Perplexity. The agreement does not indicate whether Perplexity offers a BAA as a standard commercial option.
How other platforms handle this
Don't share false or misleading claims that could cause harm.
Prohibited User Content includes...material that...constitutes intentionally false and inaccurate information...or promotes information that you know is false or misleading or promotes illegal activities...
upload or make available (1) unsolicited advertising, promotional materials, or spam, (2) any personal, financial, or sensitive information (such as government IDs, social security numbers, or health data) without proper authorization
"Customer may not use the Services to create, receive, maintain, transmit, or otherwise process any information that includes or constitutes "Protected Health Information"...unless Customer and Perplexity have executed a Business Associate Agreement.Excerpt from Perplexity AI's Perplexity API Terms of Service
1) REGULATORY LANDSCAPE: This provision directly engages HIPAA, specifically the Privacy Rule at 45 C.F.R.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Without a Business Associate Agreement, any use of the Services involving Protected Health Information is prohibited, creating a compliance risk for customers operating in healthcare-adjacent contexts.
Under this clause, Customers are contractually prohibited from transmitting or processing Protected Health Information via the API unless a Business Associate Agreement is separately executed with Perplexity. The agreement does not indicate whether Perplexity offers a BAA as a standard commercial option.
ConductAtlas has identified this type of provision across 238 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.