Lumenfall is committed to protecting your data. This page explains what data we collect and how the providers that power our platform handle your prompts and generated content.Documentation Index
Fetch the complete documentation index at: https://docs.lumenfall.ai/llms.txt
Use this file to discover all available pages before exploring further.
Lumenfall
What we collect
Lumenfall collects metadata only - we do not store your prompts or generated responses, except if you tell us to. For each request, we log:- Timestamp and latency breakdown
- Model and modality
- Provider selected (including fallback attempts)
- Endpoint called
- Response status code
- Cost and pricing breakdown
- Request and response sizes
- Usage metrics (token counts)
- Client IP region and processing location
- API key identifier (not the key itself)
- Error messages (if the request failed)
What we don’t collect
- Prompts: Your input text is never stored
- Responses: Generated images and outputs are not retained
- Uploaded files: Image inputs for editing requests are not stored
Exception: Logging of upstream errors
When requests to providers fail, we will store error responses to help you debug. You can see the outputs in the dashboard. These error responses do not contain generated media.Providers
When you make a request through Lumenfall, your prompt is sent directly to the underlying provider. Each provider has their own policies around data retention and training on inputs.Provider data policies
| Provider | Model caching | Abuse monitoring | Trains on API data | Policy |
|---|---|---|---|---|
| Google Vertex AI | 24 hours | 30 days if flagged | No | Docs |
| Google Gemini API | None | 55 days | No | Docs |
| OpenAI | None | 30 days | No | Docs |
| Replicate | None | 1 hour | No | Docs |
| fal.ai | None | 7 days | No | Docs |
| Fireworks AI | None | None | No | Docs |
| Runware | None | 30 days | No | Docs |
| xAI | None | 30 days | No | Docs |
| Alibaba Cloud | None | 30 days | No | Docs |