Security & Privacy
We only promise what we can control. Every statement below reflects how the apilane system actually runs.
API key management
Your API key is used for routing and billing. You can create, disable, or delete keys from the console at any time. Deleted keys stop working immediately and in-flight requests fail.
Request logs
apilane logs each call model name, timestamp, quota consumed, and key identifier for billing and usage statistics. We do not log prompt content or model response content.
Prompt forwarding
apilane is an API gateway: your request is forwarded to upstream model providers and the response is returned unchanged. We cannot control whether those providers store or process your prompts. Evaluate risk before sending sensitive information.
Response passthrough
We do not rewrite, filter, or inspect model responses. What the model returns is what you receive.
FAQ
Does apilane store my prompts?
No. apilane itself does not store or log prompt content. However, requests are forwarded to upstream model providers and we cannot guarantee what those providers do.
Does apilane store my API key?
API keys must be stored in an encrypted form so the system can route and bill requests. You can delete them from the console at any time.
Am I charged for failed requests?
No. You are only charged for calls where the upstream returns a successful response. Network timeouts and HTTP errors are not charged.
How can I protect my data?
Avoid submitting sensitive information in prompts that you would not want a third-party API to see. Rotate or delete unused API keys regularly.