How does ModelRiver protect my API keys and account?
Updated
Your provider keys are encrypted, your ModelRiver API keys are never stored in readable form, every connection uses HTTPS, and you can turn on two-factor sign-in. Here's what that means in practice.
How are my OpenAI, Anthropic and other provider keys stored?#
Encrypted with AES-256-GCM. After you save a key it's never shown again; the console shows only the last four characters, and the API never returns it. Keys are kept per project.
How are my ModelRiver API keys stored?#
Only as a one-way hash. The full key is shown once, when you create it, so even ModelRiver can't show it to you later. Keys can expire and can be revoked instantly.
How do I secure my login?#
- Turn on two-factor authentication (an authenticator app) in your account settings. It's available on every account.
- Sign in with a password or with Google or GitHub.
- Give teammates the lowest role they need. See Who on my team can change what?
What other protections are in place?#
- HTTPS on every connection; plain HTTP is redirected.
- Each organization's data is kept separate from every other.
- Rate limits per project and per IP address.
- Webhooks signed with HMAC-SHA256, so your server can check they came from ModelRiver.
- Card details are handled by Stripe and never reach ModelRiver.
- Daily backups, with restores tested.
How do I report a security issue?#
Email team@modelriver.com with the details and steps to reproduce it. Please give us reasonable time to fix it before disclosing it publicly. We won't take legal action against good-faith security research.