Zero data retention: engy does not store your prompts or your model outputs, and never uses them for training. This page states exactly what is and is not kept.
Effective 2026-07-02 · contact [email protected]
Prompts, completions, tool-call arguments and results, images, embeddings: the content of your requests and responses. Content passes through the gateway to a GPU worker, is processed in memory, and is gone when the response is delivered. No request or response content is ever used to train, fine-tune, or evaluate models.
| data | purpose | retention |
|---|---|---|
| usage metadata per request: timestamp, model, token counts (prompt / cached / completion), cost, latency | billing, capacity planning, the usage view in your dashboard | kept while your account exists |
| account data: email, salted password hash, API key hashes and prefixes, credit balance | authentication and billing | kept while your account exists; deleted on request |
| operational logs: connection metadata and error events, no message content | debugging, abuse prevention | rotated on a short schedule |
engy is a verified-inference network: a sample of responses is cryptographically audited to prove the exact advertised model produced the output. An audit record stores the response's token IDs and the verification result, never the prompt. Audit records are purged within 30 days.
Requests reach us through Cloudflare (TLS termination and DDoS protection; Cloudflare processes traffic per its own policies). Inference runs on GPU workers we operate; workers hold request content in memory only and keep no copy.
Email [email protected] to delete your account and its stored data, or to ask anything about this policy. Material changes to this policy will be posted on this page with a new effective date.