Data retention

Last updated: 28 September 2026

Request content (both tiers)

At present, the EU tier and the Global tier are both processed exclusively in the EU and follow the same rules. The Global tier has lower priority. It will only move to worldwide capacity for API keys whose owners explicitly opt in, after at least 30 days' notice.

	Both tiers
Content of requests and responses (state, questions, images, probabilities)	Not stored. Held in volatile memory while the request runs. Never written to logs, databases, disk or other persistent storage.
Technical prefix cache	Intermediate values of recent requests may stay in GPU memory until overwritten by later requests, at the latest until the server restarts, to speed up similar requests. Never persisted, never readable through the API, isolated per model instance.
Image URLs you send	Fetched once by our gateway; neither the URL nor the image is logged
Retry protection (optional Idempotency-Key)	For 24 hours: a keyed (HMAC) digest of the request body, the request ID, status and usage receipt. No content, no answer.
Suitable for personal data	Yes, under our DPA
Used to train models	No

Data we keep as the service provider

Data	Retention
Usage records (request ID, time, key ID, model, tier, token count, decisions, latency, status, price)	13 months in detail, then aggregated per day, model and tier
Server and security logs with IP addresses	14 days, longer only for individual entries needed to investigate a specific incident
Account data	While the account exists; deleted within 30 days after closure
Sign-in links	15 minutes
Abuse-prevention hashes for promotional credit (only while the launch offer is active)	24 months
Invoices and accounting records	8 to 10 years as required by § 257 HGB and § 147 AO
Support emails	Normally 3 years after the end of the year of last contact
Encrypted database backups (no request content)	Rolling 30 days
Website statistics	Not collected — we use no analytics or tracking service

Details and legal bases: Privacy Policy.