Privacy and your data
What FluxRouter does with your requests: where they go, what Flux keeps, and what it never does.
This page explains, in plain terms, what happens to the requests you send FluxRouter. The Privacy Policy is the authoritative source and takes precedence over this summary.
Where does my request go?
Flux is a routing gateway. When you send a request, Flux sends it to the model provider that serves it and returns that provider's response to you. Your prompt reaches the provider as you sent it: Flux does not strip personal data from it first. Each provider's own terms apply to the requests it serves.
Flux can trim and tidy a request on the way, but it does not change what you are asking.
If your use case needs limits on which providers may handle your data, email support at fluxrouter dot ai to discuss the options, or pin a model so every request goes to one provider you have chosen. See Let Flux pick, or pin a model.
What does Flux keep?
- Usage records, so the dashboard can show your usage and billing can charge for what you used: which model answered, token counts, cost and timing.
- A PII-scrubbed copy of prompts in its logs for a limited period (see the privacy policy), never the raw prompt, to operate and support the service.
- Your conversation text, if Flux Memory is on for your key: the messages and replies themselves, encrypted, until you delete them. See the privacy policy, "Flux Memory".
- Outcome signals from live traffic, such as whether a request succeeded, which Flux uses to measure routing quality.
Does Flux train models on my data?
No. Flux never trains a model on your data.
Does Flux sell my data?
No.
Questions
For privacy questions or data requests, email support at fluxrouter dot ai.