Provision record
LlamaIndex · LlamaIndex Privacy Policy · View original document ↗

Controller-Processor Scope Exclusion

High confidence Unique · 0 of 343 platforms
Stay ahead of the changes
Track LlamaIndex and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what LlamaIndex'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)

Generated by a model from the captured document; not read by a person

This provision establishes a structural limitation on the scope of data subject rights exercisable directly against LlamaIndex, creating a dependency on enterprise customers' own privacy notices and processes for end users of LlamaIndex-powered products.

Recent Activity

This document changed recently

Medium Oct 16, 2026

The updated policy establishes explicit protections for data accessed through Google Workspace API connections. LlamaIndex states it will not use this data to train generalized AI models, will not sell it to data brokers or information resellers, will encrypt it in transit and at rest, and will limit access to authorized personnel and service providers. Users can disconnect Google Drive at any time to stop data access, though previously synced data remains in LlamaIndex services unless separately deleted.

View change record →

Cross-platform context

See how other platforms handle Controller-Processor Scope Exclusion and similar clauses.

Compare across platforms →
▸ View Original Clause Language DOCUMENT RECORD
"
This Privacy Notice describes our privacy practices where we are acting as the controller of personal data. However, this Privacy Notice does not cover or address how our customers may process personal data when they use our services, or how we may process personal data on their behalf in accordance with their instructions where we are acting as their processor. As a result, we recommend referring to the privacy notice of the customer with which you have a relationship for information on how they engage processors, like us, to process personal data on their behalf. In addition, we are generally not permitted to respond to individual requests relating to personal data we process on behalf of our customers, so we recommend directing any requests to the relevant customer.

Excerpt from LlamaIndex's Privacy Policy

Provision details

Document information
Document
LlamaIndex Privacy Policy
Entity
LlamaIndex
Date stated by the document
Aug. 24, 2026
As printed in LlamaIndex’s text (version CA-V-007642), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
July 11, 2026
Text quoted from version
CA-V-004734, captured July 11, 2026
Record ID
CA-P-074217
Document ID
CA-D-000807
Evidence Provenance
Source URL
Wayback Machine
Extracted-text SHA-256 (version CA-V-004734)
c4e66bffc6d528e092684fd478d7ae9500efb79fed7348943f4ddbb964801fc1
Analysis generated
July 12, 2026 14:34 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-004734, captured July 11, 2026 (checked Oct. 5, 2026)
Not the current version. The document's current version is CA-V-007642, captured Oct. 16, 2026; this clause has not been re-checked against it.
Citation Record
Entity: LlamaIndex
Document: LlamaIndex Privacy Policy
Record ID: CA-P-074217
Version: CA-V-004734
Captured: 2026-07-11 13:43:54 UTC
SHA-256: c4e66bffc6d528e0…
URL: https://conductatlas.com/platform/llamaindex/llamaindex-privacy-policy/provision/CA-P-074217/controller-processor-scope-exclusion/
Accessed: Nov. 10, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

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.

Frequently Asked Questions

What does LlamaIndex's Controller-Processor Scope Exclusion clause do?

This provision establishes a structural limitation on the scope of data subject rights exercisable directly against LlamaIndex, creating a dependency on enterprise customers' own privacy notices and processes for end users of LlamaIndex-powered products.

Is ConductAtlas affiliated with LlamaIndex?

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