Privacy

Terms / Acceptable use

Privacy

Last updated 2026-10-24

  • Account details from checkout: the email address and the amount paid, as our payment processor reports them.
  • API keys as a salted hash, with the key name, status, limits and timestamps. The key itself is shown once and not stored.
  • One usage record per request: request id, model, token counts by class, the source of those counts, and the charge.
  • The ledger of balance changes: top-ups, charges, refunds and disputes.
  • SHA-256 fingerprints, never the text, of each request and response, so a signed receipt can show what was billed; and of large system prompts, kept 7 days, to find prompts many accounts send and cache them for everyone.
  • Where your first visit came from: the referring site, the link’s campaign tags and the page you landed on, saved with your account when your first sign-in creates it, and passed to our payment processor with each checkout.