Privacy Policy
Last updated: October 2, 2026
Overview
Fuelline (fuelline.dev) is an OpenAI-compatible API gateway that routes requests to third-party model providers. This policy explains what data we process when you use the Fuelline API or website, why we process it, and the choices you have.
We designed Fuelline to need as little personal data as possible: we do not require accounts, we do not log prompt or completion content, and we do not use trackers.
What we collect
API request metadata
For every API request we store a usage record containing:
- a short, non-reversible prefix of your API key (used to attribute usage to a key);
- the model id and the upstream provider that served the request;
- token counts, computed cost, latency, time-to-first-token, and error classification;
- whether the request was streamed and which failover attempt succeeded.
- for authenticated chat requests, a server-generated request id, start/end times, HTTP status and final outcome after retries (including stream errors and interruptions).
These records power billing, the public pricing catalog, and reliability monitoring. They are not linked to your identity beyond the API key used.
API keys
API keys are stored only as SHA-256 hashes for verification. Each key record also keeps a short display prefix (the first few characters of the key) so usage can be attributed in the admin interface — the full key cannot be reconstructed from it. Keys are supplied via server environment configuration and are never exposed through the API.
Sticky session data
To keep conversations on the same serving route (preserving prompt caches), we store a SHA-256 hash of your session identifier — never the identifier or message content itself. These records expire automatically after 10 minutes.
Website access logs
Standard server and infrastructure logs (IP address, timestamp, requested URL) may be kept for security and abuse prevention, and are rotated automatically.
What we do not collect
- Prompt and completion content. We do not log, store, or train on the text of your requests or the model's responses.
- Personal accounts. There are no sign-ups, profiles, or passwords.
- Payment details. Billing is handled out-of-band; no card data touches our systems.
- Advertising or analytics trackers. The website sets no cookies and loads no third-party tracking scripts.
Upstream providers
To answer a request, Fuelline forwards your request body (including prompt content) to a third-party model provider from our curated set of upstreams. This is necessary to provide the service — without it, no request can be served. Upstream providers process that content under their own privacy policies. We choose reputable providers, send requests only over HTTPS, and attach anti-substitution headers where supported.
If your prompts contain personal data, you are responsible for having the legal basis to share it with the model provider.
How we use data
- Operating the service: routing, failover, rate and abuse protection.
- Billing and usage reporting for API key holders.
- Monitoring reliability, latency, and cost of upstream providers.
We do not sell data, do not share it with advertisers, and do not use it for model training.
Retention
- Usage records and client request outcomes: kept for 90 days, then automatically deleted.
- Sticky session hashes: expire after 10 minutes.
- Health-check history: kept for 90 days, then automatically deleted.
- Infrastructure logs: rotated automatically.
Security
- API keys are verified against SHA-256 hashes; plaintext keys are never stored in the database.
- All traffic is served over HTTPS; upstream calls reject non-HTTPS URLs.
- Provider credentials are injected from environment configuration and never exposed via the API or admin interface.
- Administrative access is restricted by a secret token.
Cookies & tracking
The Fuelline website does not use cookies, local storage for tracking, or any third-party analytics or advertising scripts. The API is stateless apart from the short-lived sticky session hashes described above.
Your rights
You may at any time, via privacy@fuelline.dev:
- request a copy of usage data associated with your API key;
- request correction or deletion of that data;
- ask which upstream providers may have processed your requests;
- withdraw consent and have your API key revoked.
We respond to verified requests within 30 days.
Changes to this policy
If we change this policy, we will update the date above and, for material changes, notify active API key holders before the change takes effect.
Contact
Privacy questions and requests: privacy@fuelline.dev