Configure Analytics Preferences and Privacy in the TokenBison Developer Console

The short answer

TokenBison enables anonymous website analytics by default in the console to track performance and interaction metrics. However, these analytics do not collect sensitive data such as passwords, API keys, or prompt content. Developers can explicitly disable tracking at any time through the Analytics preferences panel.

Data Collected by Console Analytics

The developer console uses anonymous website analytics by default. These analytics record specific allowlisted paths, interaction events, approximate device categories, referral origins, campaign labels, active session time, and scroll depth. These metrics are processed using random browser and session identifiers to help understand website performance.

Strict Exclusion of Sensitive Developer Data

To preserve developer security, console analytics explicitly exclude sensitive personal and application information. The tracking tools do not collect passwords, active API keys, message content, form values, or full page URLs. This ensures that your programmatic configurations and credentials remain isolated from the performance monitoring layer.

How to Disable Dashboard Tracking

Developers can manage their settings via the Analytics preferences dashboard. TokenBison automatically respects existing opt-out choices and browser Do Not Track headers. When you turn analytics off, the platform clears queued events and removes the local analytics identifiers entirely.

Evidence and boundaries

These are documentation references and proposed evaluation workflows, not measured model rankings or a guarantee of savings. Check the current catalog and policies before use.

Put the guide into practice

Review current model prices, then make a small API request with public or non-sensitive sample data. Compare the output against your own acceptance criteria.

Continue learning

• secure LLM API
• AI gateway log retention