company · privacy

Privacy Policy

We believe observability tooling should be transparent about what it observes. This policy explains what data tokentrace collects, why, and how you can control it.

Last updated: May 2026
important · trace data

By default, tokentrace captures the full content of every LLM request and response — including prompts, completions, system messages, and any data passed to the model. This data is stored in your traces and visible in the dashboard.

If your prompts or completions contain personally identifiable information (PII), you can disable content capture per-call using the redactInputs and redactOutputs options, or strip PII globally via the piiRedaction SDK config. See the SDK docs →


What we collect

Trace data — when you use the tokentrace SDK, each LLM call generates a trace containing:

Account data — when you sign up:

Usage analytics — we collect anonymized product usage (page views, feature interactions) to improve the dashboard. No request content is included.


Disabling PII capture

If your application handles sensitive user data, you have two options:

Metadata (model, tokens, latency, cost) is always captured regardless of redaction settings — it contains no user content.


How we use your data

We do not sell your data, use your LLM traces to train models, or share content with third parties outside of what's required to operate the service.


Data retention


Third-party subprocessors

We use a small number of infrastructure providers to operate the service. Data may be processed by them under equivalent or stronger privacy protections.


Your rights

You can request export or deletion of your data at any time by emailing privacy@tokentrace.app. We will respond within 30 days.


Contact

Questions about this policy: privacy@tokentrace.app