Reference
What leaves your process
The SDK builds every record from a fixed allowlist. This is the complete list of what is sent:
| Sent | Examples |
|---|---|
| Provider, API and model names | openai, chat, gpt-4o |
| Token counts reported by the provider | input, output, cache read, cache write, reasoning |
| Character counts | system prompt, tool definitions, input, output |
| Timings | start, end, time to first token |
| Outcome | finish reason, HTTP status, exception class name, whether a stream completed |
| Tool names | the name of each tool the model called, and how many tools were defined |
| Salted hashes | of the request, system prompt, tool definitions, newest input, output, and each tool call |
| Run id and step number | made locally |
| Labels you set | feature, customer, environment |
| SDK details | SDK version, and an 8-character check value derived from your salt |
Never sent: message text, system prompts, tool descriptions and schemas, tool arguments, tool results, model output, images, exception messages, your provider API keys, and the salt.
Hashes
The part of your key after the dot is a salt. It stays in your process. Every hash is an HMAC-SHA256 keyed with it. Without the salt, a hash cannot be matched to text, including by Zexl, and hashes from different workspaces cannot be compared. If you lose the key, the salt cannot be recovered; a new salt starts a new hash history.
Things to know
- Tool names and model names are sent as they are. Do not put secrets in tool names.
- The feature label defaults to
module.function. Set it yourself if your function names are sensitive. - Lengths are sent. They show how long a prompt was, not what it said.
On the server
- The intake checks every record against its own allowlist and drops anything else, even from senders that are not the SDK.
- Send keys can only send. Read keys can only read one workspace. Revoked keys stop working within a minute.
- Every query is limited to the workspace you are a member of.
How this is tested
A leak test plants marker strings in every place content can appear (system prompt, messages, images, tool definitions and results, responses, streamed chunks, error bodies) and fails if a marker or the salt appears in any byte the SDK sends. It gates every release.