Effective Date: October 24, 2026
ModelRiver Inc. ("ModelRiver") uses the subprocessors below to provide its services. Each one only receives the data it needs for the purpose listed, under a written agreement with data protection terms at least as protective as our Data Processing Agreement.
Subprocessors
| Subprocessor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services | Application hosting, PostgreSQL database (Amazon RDS), secrets storage, database backups | All customer data, including request logs, provider credentials (encrypted) and account data | United States (us-east-1) |
| Cloudflare | DNS, TLS termination, DDoS protection and content delivery for all web and API traffic | All data sent to or from ModelRiver passes through in transit | Global network |
| OpenAI | Content moderation for guardrails: prompt text is checked when ModelRiver's own classifier can't decide | Text from AI requests, only in that case | United States |
| Stripe | Payments, subscriptions and invoicing | Account owner's name and email, organization name, usage counts for billing | United States |
| Resend | Transactional email (verification, password reset, invitations, billing emails) | Recipient email address and name, email content | United States |
| Sentry (Functional Software) | Error monitoring | Crash and job-failure reports. Request bodies, job arguments, headers, cookies and stack-frame values are removed before sending | United States |
Planned change: we are moving transactional email from Resend to Amazon Simple Email Service (AWS, United States). We will update this page before the switch.
Services for our website and your account
These process data about people who visit our website or sign in to the console, not the data you send through the API:
| Service | Purpose | Location |
|---|---|---|
| Google (Google Analytics, Google Tag Manager) | Website and console usage analytics | United States |
| Google, GitHub | Sign-in, only if you choose "Continue with Google" or "Continue with GitHub" | United States |
AI providers and endpoints you choose
When you connect an AI provider with your own API key (for example OpenAI, Anthropic, Google, Azure OpenAI, Amazon Bedrock, Mistral, Cohere, xAI, DeepSeek, Groq, Qwen, Kimi, MiniMax or a custom endpoint), ModelRiver sends your requests to that provider on your instructions and under your own agreement with them. The same applies to webhook and callback URLs you configure. These are not ModelRiver subprocessors: you choose them and you control what they receive.
Changes to this list
We will update this page at least 30 days before a new subprocessor starts processing customer data, and email the owners of paid organizations about the change. In an emergency, for example to keep the service running or secure, we may add a subprocessor sooner and will tell you as soon as we can. If you object to a new subprocessor on reasonable data protection grounds, tell us at [email protected]; if we can't resolve it, you may end your subscription as described in our Data Processing Agreement.
Contact
Questions about our subprocessors: [email protected]
Last updated: October 24, 2026