Data Retention & Enterprise Zero Data Retention Policy
Last updated August 9, 2026We minimize what we keep. Standard services retain content only briefly for service delivery; enterprise zero-data-retention configurations enabled by written agreement retain no Customer Content after processing.
1. Retention principles
ModelRush retains data only as long as needed to provide the service, protect the platform, calculate charges, resolve disputes, and meet legal obligations. Retention reflects data sensitivity, purpose, customer configuration, model-provider requirements, and applicable law.2. Prompts, uploads, and generated outputs
Prompts, references, and uploads on standard routes are generally retained in ModelRush-controlled active systems for up to 7 days. Generated outputs and their Provider file references are retained for no more than 24 hours after request completion, then removed from the ModelRush active database; request, billing, and usage metadata remains subject to the periods below. Model details, an order, or an enterprise agreement may specify a shorter, different, or no-content-retention period.3. Request and operational metadata
Operational metadata such as request ID, model, provider, routing reason, time, latency, status, usage, cost, errors, and security signals is generally retained for up to 13 months for billing, reliability, fraud prevention, support, and audit. We seek to keep full Customer Content out of operational metadata.4. Account, billing, and support data
Account profile data is kept while the account is active and handled under the Data Deletion Policy after closure. Tax, invoice, and payment records are retained as required by law, commonly for up to seven years. Support records are generally kept for up to three years for follow-up, quality control, and dispute handling.5. Security and abuse records
Logs and evidence related to unauthorized access, abuse, fraud, or security incidents may be retained for up to 24 months. They may be kept longer where a continuing investigation, legal hold, or real-world safety risk requires it. Access is limited to authorized personnel with a business need.6. Third-party model providers
Models called through ModelRush may be processed by independent providers. Content logging, training use, and retention can differ by model, region, account tier, and route. Review the data practice shown in model details before choosing a model. Deletion by ModelRush does not automatically shorten a provider's lawfully applicable period.7. Enterprise zero data retention
Zero data retention applies only to compatible routes explicitly identified and enabled by a written enterprise order or data-processing addendum. When enabled, ModelRush does not intentionally write Customer Content to persistent active storage after processing, though minimum content-free operational, billing, and security metadata may remain.8. Backups and disaster recovery
Encrypted backups follow a rolling cycle and are generally overwritten within 35 days. Data remaining in a backup after deletion is not used for ordinary business. If a backup must be restored for disaster recovery, deletion instructions are reapplied.9. Legal holds, deletion, and updates
A court order, regulatory requirement, payment dispute, security incident, or reasonably anticipated litigation may pause normal deletion. We resume deletion when the hold ends. You may submit a request under the Data Deletion Policy. Material changes to this policy will carry a new date and be communicated through the site, dashboard, or account notice.Legal and privacy questions
Contact legal@modelrush.ai
ModelRushOne integration, intelligent routing, transparent billing. Model infrastructure for developers and agents.ยฉ 2026 ModelRushAll systems operational