What data leaves your device

The flow

1. Your machine - the wrapper reads the API response's usage field
2. Batched push - metadata events are batched and sent to /ingest over HTTPS
3. Tokeven servers - cost is computed, data is stored with org-level isolation
4. Dashboards - you view aggregated analytics, never raw prompt content

Transport security

All data is transmitted over HTTPS (TLS 1.2 or later). Ingest tokens are validated by hashing the presented token and comparing against the stored SHA-256 hash.

Data retention

Individual usage events are deleted 365 days after the call they describe, whether or not your account is still open. When an organization is deleted, its usage data is purged within 30 days; billing records such as savings history are kept. See Privacy Policy §7.