Data & logging

This page briefly explains, from a developer's point of view, how request data is handled. The legally binding terms are in the Privacy Policy and the Terms of Service.

What we record

Each request records the metadata needed for billing and troubleshooting:

Time, model, API key used and client IP; Input / output / cache token counts, cost, latency and whether it was streamed; Whether it succeeded, and the error type if not.

This data is used for billing, usage statistics, abuse prevention and troubleshooting. You can see your own records on the dashboard's Usage page.

Request content

ZeroToken does not use your request content to train models; To fulfil a request, prompts and outputs are sent to the corresponding upstream model provider, whose own policies govern how they handle data; The site may temporarily retain some request content for safety review, abuse prevention or debugging; the scope and retention period are described in the Privacy Policy.

Protecting your data

Don't send unnecessary sensitive personal data in prompts; Use separate keys per project so you can audit and revoke them independently; Restrict where a key can be used from with an IP allowlist.

Deleting data

To delete your account and related data, contact the site administrator or make a request as described in the Privacy Policy.