ModelRush Privacy Policy
Last updated September 16, 2026A clear account of accounts, API usage, prompts and media, provider processing, retention, and your privacy rights.
1. Scope and roles
This Privacy Policy applies to the ModelRush site, accounts, dashboard, APIs, SDKs, and support channels. For prompts, inputs, and outputs submitted by organization customers, ModelRush acts as a service provider or processor following customer instructions. For account administration, security, billing, and product operations, ModelRush acts as a data controller.2. Information we collect
ModelRush processes the following categories to provide, protect, and improve the service. The specific information depends on the features you use, selected models, and account configuration.• Account and identity data: name, email, organization, role, and account identifiers returned by identity providers such as Clerk• Payment and transaction data: plan, billing address, invoices, tax information, and payment status; full card details are generally held by the payment processor• Usage and device data: IP address, browser, device, cookies, page interactions, security signals, and approximate location• API and operational metadata: request_id, time, model, route, tokens or media seconds, latency, errors, cost, and key identifier• Customer Content: prompts, code, files, images, video, audio, reference media, and model outputs• Support and communications: tickets, email, feedback, and diagnostics you choose to provide
3. Why we use information
We process information where needed to provide contracted services, based on consent, to meet legal obligations, or for proportionate legitimate interests.• Authenticate users and provide model calls, routing, async jobs, and downloads• Measure usage, manage credits, issue bills, and prevent fraud• Secure the platform, troubleshoot requests, provide support, and maintain reliability• Understand product use and improve interfaces, documentation, routing, and performance• Comply with law, enforce terms, and respond to rights requests
4. Prompts, inputs, and outputs
Customer Content is sent to the model provider you select or the provider selected by a routing policy to fulfill the request. ModelRush identifies the model and provider that processed a request in request records. ModelRush does not use Customer Content to train ModelRush-owned models unless you explicitly opt in.Third-party providers process Customer Content according to the specific model, account plan, and provider terms. Applicable content logging, retention, and zero-data-retention options are shown in model details, account settings, or an order. If those commitments conflict with this Policy, the commitment providing stronger protection to you controls.5. Sharing and service providers
We disclose only the information needed to operate the service to model providers, cloud infrastructure, identity, payment, analytics, advertising-measurement, monitoring, customer-support, and professional-service vendors. For registrations, checkouts, and top-ups attributable to an ad click, we may send Google or Meta a limited conversion event; for payment conversions, we may also send transaction value, a pseudonymous order identifier, and the advertising click identifier. For OpenAI advertising measurement, we may send limited registration and first top-up events, a SHA-256 pseudonymous account identifier, amount and currency, and an advertising click identifier when available. This integration does not send raw email addresses. We do not send prompts, uploads, or generated media. We also disclose information when required by law, to protect rights and safety, during a corporate transaction, or at your direction and consent. We do not sell personal information.6. Retention and deletion
We retain information as described for service delivery, billing reconciliation, security investigations, dispute resolution, and legal obligations. Customer Content follows the period shown in account settings, model details, an order, or the Data Retention Policy; prompts and uploads on standard services also enter a private encrypted archive without automatic expiration. Operational metadata follows security, observability, and billing needs, while financial and transaction records follow applicable law.When information is no longer needed, we delete or anonymize it. Verified deletion requests are applied to the long-term archive through a manual process, although legal holds, fraud prevention, security events, or disputes can create delays. Closing an account does not remove records we are legally required to retain.7. International transfers and security
ModelRush and its vendors may process information outside a user's country. Where required, we use standard contractual clauses or other lawful transfer mechanisms. We use organizational and technical safeguards including encryption in transit and at rest, access controls, key isolation, logging, and incident response. No system can guarantee absolute security.8. Cookies and analytics
The site uses necessary cookies for sign-in, language, and security, and uses analytics to understand product performance. Advertising click identifiers may be stored temporarily in a first-party cookie to attribute a later registration, checkout, or top-up to the relevant ad.9. Your choices and rights
Depending on your location, you may have rights to access, correct, delete, export, or restrict personal information, object to certain processing, withdraw consent, and complain to a regulator. Organization customers will usually address their end users' requests about Customer Content first, with reasonable ModelRush assistance under a data-processing agreement.• Correct profile information or close an account in settings• Rotate or revoke API keys and adjust available log settings• Request access, export, or deletion of applicable personal information• Opt out of non-essential marketing; service and security notices may still be sent