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

Subprocessor Engagement

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

Perplexity AI may engage third-party companies (subprocessors) to help it deliver services, and is typically required to notify business customers before adding new subprocessors. Customers may have a limited period to object.

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)

Subprocessors are downstream vendors who also access or process personal data. The terms governing how and when customers are notified of new subprocessors affect whether businesses can maintain adequate oversight of their data supply chain.

Interpretive note: The actual subprocessor clause text was unavailable due to document truncation; the analysis reflects standard DPA structure and the document's stated subject matter.

Consumer impact (what this means for users)

Personal data processed through a business's Perplexity AI integration may be shared with third-party subprocessors. The DPA's notice mechanism determines whether the customer business has a meaningful opportunity to object before that sharing occurs.

How other platforms handle this

Mistral AI Medium

Mistral AI will provide reasonable notice to the Customer of any changes to the list of Subprocessors prior to engaging such Subprocessor. The Customer may only object in writing to Mistral AI's appointment of a new Subprocessor within ten (10) days of such notice by providing a written objection to...

Windsurf Medium

Crusoe (Sees code data for inference): We manage Crusoe's compute for training some of our custom models, as well as hosting some of our custom models. Modal (Sees code data for inference): We manage Modal's compute for training some of our custom models, as well as hosting some of our custom models...

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(2) and (4) require that processors obtain controller authorization before engaging subprocessors and that subprocessors are bound by equivalent data protection obligations. A notice-and-objection model (rather than prior written consent for each subprocessor) is permitted under GDPR but requires a clear objection window and escalation path. (2) GOVERNANCE EXPOSURE: Medium. If the DPA uses a general authorization model with notice rather than specific prior consent, customers have limited ability to block subprocessor additions before they take effect. This is common in cloud and SaaS DPAs but creates operational tension for customers with strict vendor approval processes. (3) JURISDICTION FLAGS: EU/EEA customers face heightened exposure if subprocessors are located in third countries without an adequacy decision, requiring reliance on SCCs or binding corporate rules. UK customers must separately assess UK GDPR transfer requirements post-Brexit. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and legal teams should request the current subprocessor list at contract execution and establish an internal process to review subprocessor change notifications within the objection window specified in the DPA. The DPA should specify the consequences if Perplexity AI adds a subprocessor over a customer's objection, typically allowing contract termination. (5) COMPLIANCE CONSIDERATIONS: Customers should map all subprocessors disclosed by Perplexity AI into their own records of processing activities and assess each subprocessor's security posture and geographic location. Transfer impact assessments may be required for subprocessors in jurisdictions without EU adequacy decisions.

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 may evaluate whether subprocessor engagement practices constitute unfair or deceptive handling of consumer data under Section 5 of the FTC Act
    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-010529
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-010529
Captured: 2026-05-11 11:35:57 UTC
SHA-256: 271ab14fbd8645ff…
URL: https://conductatlas.com/platform/perplexity-ai/perplexity-data-processing-addendum/subprocessor-engagement/
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 Subprocessor Engagement clause do?

Subprocessors are downstream vendors who also access or process personal data. The terms governing how and when customers are notified of new subprocessors affect whether businesses can maintain adequate oversight of their data supply chain.

How does this clause affect you?

Personal data processed through a business's Perplexity AI integration may be shared with third-party subprocessors. The DPA's notice mechanism determines whether the customer business has a meaningful opportunity to object before that sharing occurs.

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.