The policy states that it only covers LlamaIndex's data practices as a controller, and explicitly excludes from its scope any personal data LlamaIndex processes on behalf of enterprise customers acting as processors; individuals whose data is processed in that context must direct requests to the relevant customer rather than to LlamaIndex.
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
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.
Under this clause, individuals whose personal data is processed by LlamaIndex at the direction of an enterprise customer cannot direct data subject requests to LlamaIndex and must instead contact the relevant customer organization for information about how their data is handled.
Cross-platform context
See how other platforms handle Controller-Processor Scope Exclusion and similar clauses.
Compare across platforms →"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
1) REGULATORY LANDSCAPE: The controller-processor distinction is a fundamental concept under GDPR, which imposes distinct obligations on controllers and processors including the requirement for a Data Processing Agreement between them.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
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.
Under this clause, individuals whose personal data is processed by LlamaIndex at the direction of an enterprise customer cannot direct data subject requests to LlamaIndex and must instead contact the relevant customer organization for information about how their data is handled.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by LlamaIndex.