This provision establishes that businesses using Perplexity AI's API or enterprise services are the 'controllers' of personal data (they decide what data is processed and why), while Perplexity AI acts as the 'processor' (it handles data only on the business's instructions).
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
The controller-processor designation determines who bears primary legal responsibility for data protection compliance and how data subject rights must be handled. Under GDPR, the controller (the business customer) retains accountability for ensuring the processor meets required standards.
Interpretive note: The actual clause text was not available due to document truncation; this analysis is based on the document's stated purpose and standard DPA structure.
Individual data subjects whose information flows through a business's Perplexity AI integration would need to direct rights requests (such as access or deletion) to the business, not directly to Perplexity AI, unless the DPA establishes a separate mechanism.
How other platforms handle this
At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.
If you are located in the European Economic Area, Switzerland, or the United Kingdom, you have the right to access, correct, or erase your personal data; the right to restrict or object to our processing of your personal data; the right to data portability; and, where our processing is based on your...
We may display advertisements on our Services and those advertisements may be targeted to your interests based on your personal information. We may share your personal information with advertising partners for interest-based advertising purposes. You may opt out of interest-based advertising by visi...
Monitoring
Perplexity AI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
(1) REGULATORY LANDSCAPE: GDPR Article 28 requires a binding contract between controller and processor specifying the subject matter, duration, nature, and purpose of processing. This provision is designed to satisfy that requirement. Supervisory authorities in EU member states enforce Article 28 compliance and may audit whether processor agreements meet the required specificity. (2) GOVERNANCE EXPOSURE: Medium. The controller-processor framing is standard, but the practical sufficiency depends on whether the documented processing instructions are specific enough to satisfy GDPR Article 28(3) requirements. Vague or overly broad instruction language could expose the customer controller to regulatory challenge. (3) JURISDICTION FLAGS: Heightened exposure for EU/EEA customers and UK customers subject to UK GDPR. California customers should verify whether the DPA's provisions satisfy CCPA/CPRA service provider contract requirements, which are distinct from GDPR Article 28. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams should confirm that all data flows into Perplexity AI services are covered by the DPA's scope, and that internal records of processing activities (ROPA) are updated to reflect Perplexity AI as a processor. The DPA should be executed prior to any personal data transfer. (5) COMPLIANCE CONSIDERATIONS: Legal teams should verify that the scope of 'documented instructions' is operationally defined and that any deviation from those instructions by Perplexity AI triggers a notification obligation under the DPA.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The controller-processor designation determines who bears primary legal responsibility for data protection compliance and how data subject rights must be handled. Under GDPR, the controller (the business customer) retains accountability for ensuring the processor meets required standards.
Individual data subjects whose information flows through a business's Perplexity AI integration would need to direct rights requests (such as access or deletion) to the business, not directly to Perplexity AI, unless the DPA establishes a separate mechanism.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.