Trust Center
Clear answers on how Modelflare handles your data and keeps it secure.
At a glance
API request and response content
In the standard API relay path, request and response content is processed transiently and is not stored as a long-term business record in the application database.
Havenbyte model training
Havenbyte does not use Customer Content to train, fine-tune, distill, benchmark, or improve models developed or operated by Havenbyte.
Short-lived request diagnostics
These records contain parameter summaries and diagnostic metadata, not complete request or response content.
Request Archive
When specifically authorized and enabled, Request Archive may store limited diagnostic copies of original and service provider request bodies. Its current default expiry is 168 hours.
How requests move
Customer application
Your application, coding agent, or internal tool sends a request using your API Key.
Modelflare API
The gateway authenticates the request, validates access, and applies the selected routing and metering rules.
Selected service provider
The request is sent only to the model or infrastructure provider needed for the route you selected.
Response returned
The response returns through Modelflare. We record request-level usage, status, latency, and cost metadata.
Data handling
API request and response content
Processed transiently to perform the request and sent to the selected model or infrastructure provider.
Not stored as a standard long-term business record in the application database.
Usage and billing metadata
Model, route, token counts, cache usage, fees, status, timing, errors, and request identifiers used for metering and operations.
No single fixed period applies; retained only as reasonably necessary for billing, support, security, disputes, and legal obligations.
Short-lived request diagnostic records
Parameter summaries and diagnostic metadata for authorized troubleshooting and reliability analysis; not complete request or response content.
Designed to expire after 72 hours.
Request Archive
A separate diagnostic feature that may store limited copies of original and service provider request bodies only when specifically authorized and enabled.
Disabled by default; current default expiry is 168 hours when enabled.
Customer-selected persistent features
When you use a feature that requires storage, such as Image Workbench, the necessary content and assets are retained.
Until you delete it or another disclosed retention rule applies.
Account and support records
Login identifiers, preferences, security records, support messages, and attachments needed to operate and protect your account.
While needed to operate the account or resolve a support matter, and afterward only as reasonably necessary for security, disputes, and legal obligations.
Payment data
Supported payment providers process payment methods, billing, refunds, disputes, and risk signals.
The payment provider’s retention terms apply. Modelflare does not store full payment card numbers.
Security safeguards
Authentication and access control
Administrative and customer functions require authenticated access with role- or ownership-based authorization. Sensitive operations have additional restrictions.
Credential protection
Supported sensitive credentials are encrypted at rest or verified using non-plaintext mechanisms, as appropriate.
Encrypted transport
Public service endpoints use encrypted transport. Customers should connect only through official HTTPS endpoints.
Data minimization
Operational logs focus on metadata. Request-body diagnostics are separate and disabled by default.
Analytics boundaries
Allowlisted analytics fields exclude prompts, request and response bodies, API Keys, passwords, cookies, and secrets.
Controlled operations
Production changes use controlled, versioned, and validated procedures, supported by investigation and incident-communication processes.
Service providers
Model provider selected for the request
Generate and return the result requested by the customer.
Yes—only the content needed for the selected request.
Cloudflare and applicable infrastructure providers
Network delivery, security, connectivity, hosting, and protected storage.
May process or transmit content as necessary to deliver the service.
Stripe and supported payment providers
Payments, invoices, refunds, disputes, and fraud controls.
No API request or response content in their ordinary service role.
OAuth, bot-protection, and account-risk providers
Login, identity verification, bot protection, and account-risk assessment.
No API request or response content in their ordinary service role.
PostHog and X measurement
Allowlisted page, product, and account metadata for service improvement.
No prompts, API request or response content, API Keys, passwords, or secrets.
Resend and support providers
Deliver service email and process support content submitted by the customer.
Support content when you submit it; no API request or response content in their ordinary service role.
Shared responsibility
- Keep API Keys out of client-side code, public repositories, and shared logs.
- Use separate keys, quotas, expiration, and access limits for different projects and environments.
- Monitor request and cost records, and rotate any credential that may have been exposed.
- Choose model routes according to the sensitivity of your data and the applicable provider terms.
- Do not submit specially regulated data unless the use case and safeguards have been approved in writing.
- Validate model output for your own product, legal, and security requirements.