Perplexity AI · Perplexity Data Processing Addendum · View original document ↗

Controller-Processor Relationship

Medium severity Low confidence Inferredfromcontext Unique · 0 of 325 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for Perplexity AI Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

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.

Consumer impact (what this means for users)

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

Atlassian Medium

We collect and receive information as a data controller for our own purposes and as a data processor on behalf of our customers. When our customers use our products to process data about their end users and employees, we act as a data processor on their behalf. Our customers, as data controllers, de...

Mistral AI Medium

Mistral AI is authorized to process the Personal Data as Controller for the purposes of: Automated moderation, including abuse monitoring on our APIs (except, in this last case, when zero data retention has been activated), to enforce the Agreement.

Egnyte Medium

Egnyte is a data controller with respect to personal data it collects from visitors to its website and through its marketing activities. Egnyte acts as a data processor with respect to the content and data that customers store within the Egnyte platform. In that capacity, Egnyte processes data on be...

See all platforms with this clause type →

Monitoring

Perplexity AI has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.

Start Watcher free trial Or create a free account →
ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

(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.

Track 1 platform — free Try Watcher free for 14 days

Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.

Applicable agencies

  • FTC
    The FTC has jurisdiction over unfair or deceptive data practices by US-based processors and may evaluate whether processor agreements adequately protect consumer data
    File a complaint →

Applicable regulations

EU AI Act
European Union
CCPA/CPRA
California, USA
Colorado AI Act
US-CO
CAN-SPAM
United States Federal
ePrivacy Directive
European Union
EU AI Act - High Risk Provisions
EU
FTC Act Section 5
United States Federal
GDPR
European Union
UK GDPR
United Kingdom

Provision details

Document information
Document
Perplexity Data Processing Addendum
Entity
Perplexity AI
Document last updated
May 11, 2026
Tracking information
First tracked
May 11, 2026
Last verified
May 11, 2026
Record ID
CA-P-010528
Document ID
CA-D-00763
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
271ab14fbd8645ff8aa1ce98ae597b6e8c3c4b080ade9dc4706fad0960a19089
Analysis generated
May 11, 2026 11:35 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Perplexity AI
Document: Perplexity Data Processing Addendum
Record ID: CA-P-010528
Captured: 2026-05-11 11:35:57 UTC
SHA-256: 271ab14fbd8645ff…
URL: https://conductatlas.com/platform/perplexity-ai/perplexity-data-processing-addendum/controller-processor-relationship/
Accessed: May 13, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Related Analysis

Professional Governance Intelligence

Need to monitor specific governance provisions?

Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Professional free trial

Or start with Watcher →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Perplexity AI's Controller-Processor Relationship clause do?

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.

How does this clause affect you?

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.

Is ConductAtlas affiliated with Perplexity AI?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.