Terms of Service

Effective date: June 4, 2026  ·  Last updated: October 27, 2026

These Terms of Service ("Terms") govern your access to and use of the Rouva service ("Service") provided by Rouva ("we", "us", or "our"). By creating an account or using the Service, you agree to be bound by these Terms.

1. Description of Service

Rouva is a managed AI gateway that routes requests to third-party AI providers on your behalf, using API keys you provide. Supported providers currently include Anthropic, OpenAI, Google (Gemini), DeepSeek, Mistral, Moonshot AI, xAI, Alibaba Cloud, Z.ai and MiniMax. The Service includes intelligent model routing, spend tracking, spend caps, quality scoring, budget alerts and team workspaces.

How we handle personal data and the content of your requests is described in our Privacy Policy, which forms part of these Terms.

2. Eligibility

You must be at least 13 years old to use the Service. By using the Service, you represent that you have the legal capacity to enter into a binding agreement.

3. Account Registration

You must provide accurate and complete information when creating an account. You are responsible for maintaining the confidentiality of your account credentials and Rouva gateway keys, and for all activity that occurs under your account or with your gateway keys. Notify us immediately at support@rouva.io if you suspect unauthorized access.

4. API Key Handling

You may store third-party provider API keys with Rouva to enable request routing. By doing so, you acknowledge and agree that:

• You are responsible for ensuring your API keys are valid and in good standing with the respective providers, and that your use of each provider complies with that provider's terms.
• Rouva stores your API keys encrypted at rest using AES-256 encryption. Keys are decrypted only in memory when Rouva makes a request on your behalf.
• Rouva never logs or exposes your API keys in plaintext.
• You retain full ownership of your API keys. Rouva uses them only to operate the Service for you, including the requests described in Section 5.
• You are responsible for all usage and charges incurred on your third-party provider accounts through the Service, including the requests described in Section 5.
• You should revoke and replace any API key you believe has been compromised.

5. Requests Rouva Makes on Your Behalf

Rouva does not simply pass your requests through unchanged. Depending on your settings, the Service may:

• Route to a different model — when intelligent routing or a routing override applies, your request may be sent to a different model or provider than the one you named, among the providers connected to your account (or, for workspace members, the workspace owner's account).
• Retry with an alternative model — if a provider returns an error, the request may be retried with another model.
• Summarize long conversations — older turns of a long conversation may be condensed by an additional request to an Anthropic model, made with your Anthropic API key.
• Check your API keys — when you save a key, Rouva confirms it works with a free model-list request to that provider. No prompt is sent and nothing is billed to your account.
• Read your usage — Rouva may use your Anthropic key to read your usage and cost figures from Anthropic's usage API. This only reads data and does not generate any output.
• Add prompt-caching markers — for requests to Claude models, Rouva may add Anthropic prompt-caching markers to the system prompt, the tool definitions and, in long conversations, the conversation prefix. When caching takes effect, Anthropic bills the cached input at its cache-write and cache-read rates instead of its normal input rate.
• Modify formatting — whitespace and blank lines in your messages may be trimmed before forwarding.
• Omit sampling settings a model rejects — some Claude models reject temperature and top_p; for those Rouva supports (currently Opus 4.7 and newer, Sonnet 5 and newer, Haiku 5.5, and Fable, as listed in the documentation), Rouva leaves those settings out of requests to them rather than have the request fail.
• Request text-only output — for Qwen omni models, Rouva asks the provider for text output only, as the Service doesn't return audio.
• Limit thinking length — for Qwen models that think by default (currently Qwen3.7 Plus and Qwen3.8 Flash), Rouva sets the provider's thinking budget to 32,768 tokens, so a request's cost can be bounded. Your max_tokens still limits the answer.

Requests made with your API keys are charged to your provider account. Rouva also classifies requests and scores response quality using its own accounts with third-party services; these are not charged to you.

Spend figures, savings, spend caps and budget alerts are calculated from Rouva's own pricing data and token counts reported by providers. They are estimates for convenience and control, not invoices: your provider's bill is authoritative and may differ. We do not guarantee that a cap or alert will take effect before a particular charge is incurred.

6. Workspaces

A workspace owner may invite other users as members. If you own a workspace:

• Members' requests are made with your provider API keys, and you are responsible for all charges they incur on your provider accounts.
• You are responsible for the members you invite, the spend caps and model allowlists you set, and for removing members who should no longer have access.
• You can see each member's name, email address, spend, request counts and models used, and you must use that information only to administer your workspace.
• You must remove all members before you can delete your account.

If you are a workspace member, your requests are processed under the owner's provider accounts, the owner can see the usage information described above, and the owner may change your caps and allowlists or remove you at any time.

7. Tool Handlers and Your Endpoints

If you register tool handler endpoints (for example, with the /api/gateway/run endpoint), Rouva will send tool-call names and arguments generated by the model to those endpoints. You are responsible for those endpoints, for what they do with the data they receive, and for any actions they take. Rouva does not review or control them.

8. Acceptable Use

You agree not to use the Service to:

• Violate any applicable law or regulation
• Generate illegal, harmful, abusive, harassing, defamatory, or fraudulent content
• Circumvent or abuse rate limits or usage policies of Rouva or any third-party AI provider
• Reverse-engineer, scrape, or attempt to extract proprietary information from the Service
• Introduce malware, viruses, or other malicious code
• Impersonate any person or entity
• Use the Service in any way that could damage, disable, or overburden our infrastructure

We reserve the right to suspend or terminate accounts that violate these rules without prior notice.

9. Service Availability

We strive to maintain high availability but make no guarantees of uninterrupted service. The Service is provided on a best-effort basis. Downtime may occur due to maintenance, third-party provider outages, or events outside our control.

We are not liable for any losses resulting from service unavailability, including but not limited to failed API requests, delayed routing, or missed alerts.

10. Third-Party Providers

The Service depends on third-party AI providers, and on third-party services Rouva uses to operate (listed in our Privacy Policy), whose availability, pricing, and policies are outside our control. We are not responsible for:

• Changes to third-party provider pricing or model availability
• Downtime or errors from third-party APIs
• Content generated by third-party AI models
• Policy changes that affect how your requests are processed by those providers

11. Intellectual Property

The Rouva name, logo, and Service software are owned by Rouva and protected by applicable intellectual property laws. You may not copy, modify, distribute, or create derivative works from our software without written permission.

You retain ownership of all content you submit through the Service.

12. Disclaimer of Warranties

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE ERROR-FREE, SECURE, OR CONTINUOUSLY AVAILABLE.

13. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, ROUVA SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO LOSS OF PROFITS, DATA, OR BUSINESS OPPORTUNITIES, ARISING OUT OF OR IN CONNECTION WITH YOUR USE OF THE SERVICE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

OUR TOTAL CUMULATIVE LIABILITY TO YOU FOR ANY CLAIMS ARISING UNDER THESE TERMS SHALL NOT EXCEED THE GREATER OF (A) THE AMOUNT YOU PAID US IN THE THREE MONTHS PRECEDING THE CLAIM OR (B) $50 USD.

14. Indemnification

You agree to indemnify and hold harmless Rouva and its officers, employees, and agents from any claims, damages, or expenses (including reasonable legal fees) arising from your use of the Service, your violation of these Terms, or your violation of any third party's rights.

15. Termination

You may terminate your account at any time by deleting it from your profile page in the Rouva dashboard, or by contacting us at support@rouva.io. Workspace owners must first remove their members (see Section 6). We may suspend or terminate your access at any time, with or without cause or notice. Upon termination, your right to use the Service ceases immediately. You remain responsible for charges incurred on your provider accounts before termination. Sections 4, 6, 12, 13 and 14 survive termination.

16. Changes to These Terms

We may update these Terms from time to time. We will notify registered users by email when material changes are made. Continued use of the Service after changes take effect constitutes acceptance of the revised Terms.

17. Governing Law

These Terms are governed by the laws of the State of California, United States, without regard to its conflict of law principles. Any disputes shall be resolved exclusively in the state or federal courts located in California.

18. Contact

For questions about these Terms, contact us at:

• Email: support@rouva.io
• Website: rouva.io