Platform features
Data retention
How long request logs and failure diagnostics are kept, and how to shorten it for your account.
Modelflare keeps request history so you can reconcile usage, and deletes it on a schedule rather than accumulating it forever.
Consume and error logs
Section titled “Consume and error logs”Consume and error entries are kept for the site retention period, then permanently deleted by a cleanup that runs once a day at 04:00 server time. A monthly summary entry stays in your log list for every month that was cleaned, so historical request counts, tokens, and spend do not disappear with the detail rows.
Choose a shorter period
Section titled “Choose a shorter period”Profile → Log retention lets you follow the site default or pick 7, 30, 60, 180, or 365 days for your own logs. You can never pick a period longer than the site limit. Shortening asks for confirmation, takes effect on the next daily run, and cannot be undone for rows that are already deleted.
What is never deleted by retention
Section titled “What is never deleted by retention”Top-up, refund, redemption, account, and system records sit outside the retention policy. They are financial and audit history, not request detail.
Failure diagnostics
Section titled “Failure diagnostics”When a request fails terminally, or when a channel attempt fails before a fallback recovers it, the gateway stores one copy of the original request JSON for incident diagnosis and deletes it after 12 hours. A request that succeeds without a failed attempt is never stored this way. The copy never includes your Authorization header or any upstream credential, and it is not exposed through the log APIs.
Account and privacy
Section titled “Account and privacy”Data handling outside request logs — account information, analytics, providers, and the no-training commitment — is covered by the Privacy Policy.