How Long Does LlamaIndex Keep Your Data? Retention by Plan
Last checked Nov 16, 20268 verified quotes5 source documentsRead by Claude Haiku 5.5 · quotes verified by code
Data retention
Input files and parse/extraction outputs deleted within 48 hours after processing
How to opt out
Not stated
Plan by plan
“All plans” means the vendor’s documents do not distinguish plans for this question.
| Question | Free | Pro / Plus | Enterprise |
|---|---|---|---|
| Data retention | Input files and parse/extraction outputs deleted within 48 hours after processing | Input files and parse/extraction outputs deleted within 48 hours after processing | Not stated |
| How to opt out | Not stated | Not stated | Not stated |
| Trains on your data | Does not train | Does not train | Does not train |
| Human review of your data | Not stated | Not stated | Not stated |
Data retention
- FreeInput files and parse/extraction outputs deleted within 48 hours after processing
- Pro / PlusInput files and parse/extraction outputs deleted within 48 hours after processing
- EnterpriseNot stated
How to opt out
- All plansNot stated
Trains on your data
- All plansDoes not train
Human review of your data
- All plansNot stated
What LlamaIndex says, word for word
Open a field to read the vendor’s sentence, its source and our confidence.
Data retentionFreeInput files and parse/extraction outputs deleted within 48 hours after processing
“Except as you agree under separate terms, input files and parse or extraction outputs are deleted no later than 48 hours after processing completes, unless you delete them sooner.”
Unless deleted sooner; stored LlamaCloud data kept until deleted
Data retentionPro / PlusInput files and parse/extraction outputs deleted within 48 hours after processing
“Except as you agree under separate terms, input files and parse or extraction outputs are deleted no later than 48 hours after processing completes, unless you delete them sooner.”
Unless deleted sooner; stored LlamaCloud data kept until deleted
Data retentionEnterpriseNot stated
The vendor’s documents we read do not say this. We show “Not stated” instead of guessing.
How to opt outAll plansNot stated
The vendor’s documents we read do not say this. We show “Not stated” instead of guessing.
Trains on your dataAll plansDoes not train
“Except as a customer agrees under separate terms, we do not use Customer Content to train or fine-tune artificial intelligence or machine learning models, or to improve our services.”
Except where a customer accepts separate terms
Trains on your dataFreeDoes not train
“Except as you agree under separate terms accepted under Section 4.4, we do not use User Content to train or fine-tune any artificial intelligence or machine learning model.”
Self-serve Terms of Service
Trains on your dataPro / PlusDoes not train
“Except as you agree under separate terms accepted under Section 4.4, we do not use User Content to train or fine-tune any artificial intelligence or machine learning model.”
Self-serve Terms of Service
Human review of your dataAll plansNot stated
The vendor’s documents we read do not say this. We show “Not stated” instead of guessing.
Change history
No changes detected since we started tracking LlamaIndex on Nov 16, 2026 (version 1). We re-check its documents regularly.
Sources we read
- Privacy policyPrivacy and Security | Developer Documentation
- Trust / securityTrust Center - LlamaIndex
- AI & data usageCustom GPT Training Guide: EmbedAI + LlamaIndex | LlamaIndex
- Privacy policyPrivacy Notice
- TermsTerms of Service
More on LlamaIndex
Other ai coding assistants
AI Coding Assistants that don’t train on your data →Informational, not legal advice. Every verdict is what the vendor’s own documents state, quoted word for word. Read the cited source before you decide, and check your own contract: negotiated terms can differ.