Data handling
What Worg's own service keeps about each request, and what it does not. Every request to the API passes through this service.
What Worg records
For every request that reaches a lane, Worg records metadata for billing, usage and limits:
- Time of the request and its request ID
- Organization, workspace and key
- The lane that served it, and the combo name if you called one
- HTTP status and error code, and whether it streamed
- Token counts: input, cached input, output, and reasoning when the lane reports it
- The rates applied and the cost
- Latency and time to first byte
API keys are stored only as a SHA-256 hash.
What Worg does not store
- Prompts and outputs. The text passes through Worg on its way to the lane and back and is not written to the database or to logs.
- IP addresses. Worg's server keeps no access log, removes client address headers before a request reaches the API, and its log lines hold only the method and path.
Both are checked by automated tests in Worg's codebase: one sends a request and a stream with marked prompt and output text, then searches every database table for them; another checks that a client address cannot reach a log line.
What this page does not cover
The model behind each lane runs at an inference provider. How long that provider keeps data, and where it is processed, is not covered here. Worg will state it per lane only once it is confirmed in writing.
A request to a model name alone or to a combo can be served by any of its lanes, so it gets the handling of whichever lane answered. To keep a request on one lane, call that lane's ID.