AI MODEL AGGREGATION / SMALL-TEAM GUIDES
Data handling and log retention in AI gateway architectures
Understand how AI gateways handle, route, and retain API prompt content and token logs during multi-model aggregation.
The short answer
AI gateway services process prompts, inputs, files, code, and outputs to execute requests and maintain logs. TokenBison retains API content and detailed request or response logs for up to 30 days by default before deletion or de-identification.
Data Elements Processed by the API
When independent teams pass payloads through an aggregated model layer, the platform processes specific API content items including prompts, inputs, files, source code, and generated outputs. This data processing is necessary to provide the core API service, maintain usage logs, execute troubleshooting workflows, prevent system abuse, and supply technical support to the developer.
Understanding Default Log Retention Periods
API content and granular request or response logs do not persist indefinitely. By default, these detailed logs are retained for up to 30 days, after which they are deleted or de-identified. A longer retention timeframe only occurs if reasonably necessary for an active security investigation, a specific legal obligation, an unresolved dispute, or a dedicated feature explicitly selected by the user.
Managing Your Historical Console Logs
Developers maintain control over their visible log history on the platform. You can delete available logs directly inside the management console or initiate a deletion request by contacting support via email. This workflow allows small teams to keep their active logging footprint compact during the prototyping and deployment phases.
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.
TokenBison privacy policy · reviewed 2026-09-24
API content and detailed request/response logs: retained for up to 30 days by default, then deleted or de-identified, unless a longer period is reasonably necessary for an active security investigation, legal obligation, dispute, or a feature you have chosen. Usage and billing records: retained for up to 7 years where reasonably necessary for accounting, tax, fraud prevention, legal, and audit purposes. Account and support information: retained while your account is active and thereafter for the period reasonably necessary for the purposes above.
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.