AI MODEL AGGREGATION / SMALL-TEAM GUIDES
Manage API log retention and data deletion in an AI gateway
Learn about the log retention policies, default storage periods, and manual deletion methods for API request content within an AI gateway architecture.
The short answer
TokenBison retains API content and detailed request/response logs for up to 30 days by default, after which they are deleted or de-identified. Developers can manually delete available logs via the console or request deletion by contacting support. This helps small teams maintain standard data handling cycles while using unified AI model endpoints.
Default Retention Periods for AI Requests
When building applications with a unified AI model provider, request details are processed to manage token usage and facilitate troubleshooting. By default, API content and detailed request or response logs are retained for up to 30 days. After this 30-day window, TokenBison deletes or de-identifies the logs automatically, unless a longer retention period is explicitly required for an active legal obligation, dispute, or a specific feature chosen by the user.
Manual Control and Log Deletion Methods
For small teams and independent developers who need tighter control over their data lifecycle, automated expiration is not the only option. You can actively manage and delete available logs directly inside the console interface. Alternatively, developers can submit a deletion request via email to hi@tokenbison.com. It is important to note that any deletion requests are subject to standard technical limitations and legal or financial obligations, such as retaining minimal records for billing accuracy and fraud prevention.
Data Handling Across Third-Party Inference Providers
When utilizing a multi-provider gateway, API inputs, outputs, and critical metadata are sent to the external model providers needed to fulfill your specific request. Once information is forwarded to fulfill an inference call, that data also becomes subject to the respective third-party provider's own retention and privacy practices. Small teams should review these upstream policies alongside the gateway's storage timelines when designing production data flows.
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.