Privacy

Controller. The controller is the entity named in the Imprint of this site, reachable at the address given there. What is processed. Account and organisation data you provide (name, email address, a scrypt hash of your password, organisation name and slug); API key records (name, scopes, creation and last-use times, and a scrypt hash of the key — the key itself is shown once and never stored in clear); request metadata for every call (model requested and model used, endpoint, region, sovereignty class, token counts, latency, cost estimates, timestamps); trace records that group those calls; audit-log entries for account, key and policy changes; and aggregate usage counts. Prompt and completion bodies are not stored. Zero retention is the default and the only implemented setting: a request that asks for a non-zero retention policy is refused rather than silently ignored. IP addresses are not stored in clear — they are hashed with a deployment secret before they are written. Purposes and legal bases. Performance of a contract (Art. 6(1)(b) GDPR) for providing the API, the console and the catalogue; legitimate interests (Art. 6(1)(f) GDPR) in securing the service, preventing abuse and metering usage; legal obligation (Art. 6(1)(c) GDPR) where records must be kept; consent (Art. 6(1)(a) GDPR) for anything optional, which you can withdraw at any time. Recipients. Inference is performed by the endpoint that serves a request. Which endpoint that is follows from the routing policy and is recorded in the response: a first-party endpoint in an EU region, or a partner endpoint operated outside the EU. Every model card and every response names the region and the sovereignty class. Further recipients are the hosting provider that operates this site and the mail transport used for account messages. This site loads no advertising or cross-site tracking service and no third-party analytics script. Transfers outside the EU. A request routed to a partner endpoint is processed outside the EU by that operator. The residency filter exists so that you can forbid this: a policy that admits only EU classes will not route to such an endpoint, and a request that nothing satisfies is refused rather than rounded up. Retention. Prompt and completion bodies: not stored at all. Account, organisation, key and audit data: kept while the account exists, and deleted with it. Request metadata and traces: kept for the operation of the console in which you read them, then deleted. You can export your account data and the audit log from the console at any time. Your rights. Access, rectification, erasure, restriction of processing, data portability, objection, and the right to lodge a complaint with a supervisory authority. Write to the address given in the Imprint. There is no automated decision-making and no profiling for advertising.