// privacy architecture
An LLM API gateway without prompt logging
Basktre proxies model requests and immediately discards prompt and response bodies. Limited operational metadata remains necessary for billing, reliability and abuse prevention.
What Basktre stores—and does not store
| Data | Stored by Basktre? |
|---|---|
| Prompt body | No |
| Response body | No |
| Model used | Yes |
| Input and output token counts | Yes |
| Cost, status and timestamp | Yes |
| User/API-key identifier | Yes |
Request lifecycle
- Basktre authenticates the API key.
- The requested or automatically selected model receives the request.
- The upstream provider returns the generated response.
- Basktre returns it without retaining either content body.
- Limited usage metadata supports billing and operations.
Understand the provider boundary
No-logging describes Basktre’s handling. The selected upstream provider necessarily processes request content and its own current privacy and retention terms apply.
Read the complete Privacy Policy.
Frequently asked questions
How can Basktre bill without storing prompts?
Billing uses model identifiers and token counts rather than prompt or response bodies.
Do upstream model providers process request content?
Yes. Basktre must forward content to the selected provider to produce a response. That provider’s current data terms and controls apply.
Start with $1 in free API credit
No card required. Use one key across a growing model catalog with no additional Basktre token markup.
Start building