This policy explains what data bestokens collects, why, and how long we keep it. We designed the Service to hold as little of your data as possible.
1. What we collect
- Account data: email address, hashed password, display name, account creation date.
- Billing data: top-up amount, payment method type, transaction identifiers from Creem or NOWPayments, credit balance and ledger entries.
- Usage metadata: model id, token counts (prompt, completion, cached), latency, HTTP status, API key id, timestamp.
- Technical data: IP address, country, user agent — retained transiently for rate limiting and abuse prevention.
2. What we do not store
We do not store the content of your prompts or model completions. Request and response bodies pass through our edge workers in memory and are discarded after the response is returned. We do not use your prompts to train models.
Upstream providers receive your prompt content in order to generate a response, and their own privacy terms apply to that processing. Where a provider offers a zero-retention endpoint we route to it by default.
3. Why we process data
- To provide the Service and meter usage accurately.
- To prevent fraud, abuse and circumvention of rate limits.
- To comply with legal, tax and accounting obligations.
- To send transactional email (receipts, security notices). We do not send marketing email without consent.
4. Retention
Usage metadata is retained for 30 days, then aggregated. Billing records are retained for as long as required by tax law (typically 7 years). Account data is deleted within 30 days of account closure, except records we must keep for legal or accounting reasons.
5. Sharing
We share data with: upstream model providers (prompt content only, to fulfil your request); Creem and NOWPayments (to process payment); our cloud infrastructure provider (Cloudflare) as data processor; and authorities where legally required. We do not sell personal data.
6. Your rights
Depending on your jurisdiction you may have the right to access, correct, export or delete your personal data, to object to processing, and to lodge a complaint with a supervisory authority. Send requests to [email protected]; we respond within 30 days.
7. Security and contact
API keys are stored as one-way hashes and cannot be recovered — only rotated. Traffic is encrypted in transit with TLS 1.2+. Contact: [email protected].