Skip to content
ORYNX

Privacy policy

What ORYNX stores, what it never stores, and who else processes your data.

Last updated 20 September 2026

Summary

  • ORYNX does not store your prompts, completions, files or images. They pass through memory only, apart from provider error messages that quote part of a request (see Error diagnostics).
  • ORYNX does store request metadata so it can bill you and show your usage.
  • The model providers that run the models process your content and may retain it under their own policies.

What passes through but is never stored

The content of your requests and responses: messages, system prompts, tool definitions and results, files, images and audio. ORYNX forwards this content to the model provider and streams the answer back to you. It is not written to a database, to disk or to any log. The one exception is a provider's error message, described under Error diagnostics below, which can quote part of a request.

What ORYNX stores

Request metadata, for every API request:

  • time, model, API format and whether the response was streamed
  • token counts (input, cached input, cache writes, output, reasoning) and the cost
  • duration, HTTP status and an error category if the request failed
  • the kind of client, taken from the User-Agent header
  • a shortened prefix of the calling IP address, for abuse prevention
  • an ORYNX request id, and the id the provider returned, used to reconcile billing

Key records: a keyed hash of your key (never the key itself), the last four characters, credit, spend, expiry, allowed model families and optional limits.

Error diagnostics: when a model provider returns an error, the provider's error message may be kept for up to 7 days to investigate problems. Some providers quote part of the request in their error messages.

How long ORYNX keeps data

Request metadata is kept for up to 180 days after each request, for billing and disputes. Hourly usage totals may be kept longer in aggregate form. Key records are kept for as long as needed to honour billing and rotation history.

Model providers

To answer a request, ORYNX sends it to the company or service that runs the model you chose (for example the providers of Claude, GPT, Gemini, Grok, DeepSeek, Kimi or GLM, or services operating them). They process your content under their own terms and privacy policies and may keep it for a period, for example for safety and abuse monitoring. Do not send personal or confidential data that you are not permitted to share with them.

This website

  • The site does not use advertising or analytics trackers.
  • It stores your theme in your browser's local storage.
  • Key lookup sends your key once over HTTPS to check it. The key is not stored in your browser, not put in the URL and not logged. Lookups are rate limited using a one-way hash of your IP address that expires within a day. The lookup form may show a Cloudflare Turnstile check, which is subject to Cloudflare's privacy policy.
  • The site is served through Cloudflare, which processes connection data to protect and deliver it.

Security

Keys are stored only as keyed hashes. Traffic is encrypted in transit. Access to request metadata is limited to ORYNX operators.

Questions

To ask about your data or to request deletion of records linked to your key, contact the person or team who issued your key.