Acceptable Use Policy

This Acceptable Use Policy (the “AUP”) is incorporated by reference into the Recovea Terms of Service, any master service agreement, and any order form or statement of work (together, the “Agreement”). It states the rules for what you and your users may and may not do with, or route through, the Recovea inline LLM cost gateway. It lets Recovea respond to abuse without renegotiating the Agreement, and it protects the gateway, other tenants, and the upstream model providers you route to.

How this is written. This AUP matches the build as it exists today, not the roadmap. Recovea does not log prompt or completion bodies by default (“no-bodies-by-default”), so Recovea generally cannot see the content you route; enforcement is metadata- and report-driven, not content moderation. Recovea is a neutral, multi-provider, bring-your-own-key passthrough: each upstream provider’s own terms and usage policies — not Recovea — govern the actual content rules for routed traffic, and Recovea cannot guarantee any provider’s acceptance of any request. Nothing here implies Recovea actively scans, reviews, filters, or moderates your content.

1. Scope and definitions

This AUP protects (a) the Recovea Service and infrastructure, (b) other Recovea tenants sharing that infrastructure, and (c) the upstream model providers your traffic is routed to. It applies to you and to every person or system that accesses the Service under your account or API keys (your “Authorized Users”), and to all traffic, content, configuration, and instructions you submit to or route through the Service (“Routed Traffic”). You are responsible for compliance by all Authorized Users and for all activity under your account. Capitalized terms not defined here have the meaning given in the Agreement.

“Upstream Provider” means any third-party model provider (for example, OpenAI or Anthropic) to which you direct Routed Traffic using your own provider API key. “Metadata” means the content-free operational records Recovea keeps by default (model, token counts, cost, timestamps, route, status), as distinct from prompt or completion bodies, which Recovea does not log by default.

Recovea operates on a no-bodies-by-default basis and generally does not have access to the content of Routed Traffic. Recovea is not the arbiter of your prompts, completions, outputs, or applications. The obligations in this AUP are yours; Recovea’s enforcement is exercised on the limited, content-free signals available to it and on reports it receives.

2. Prohibited content and uses

You will not, and will not permit any Authorized User or end user to, use the Service or submit or route any Routed Traffic to:

• Break the law — violate any applicable law or regulation, including export-control, sanctions, anti-money-laundering, consumer-protection, or data-protection laws.
• Infringe rights — infringe or misappropriate any third party’s intellectual property, privacy, publicity, or other rights, or route content you lack the rights or lawful basis to process.
• Spread harmful code — transmit, generate, store, or route malware, ransomware, or any code designed to disrupt, disable, overburden, gain unauthorized access to, or impair any system or data.
• Attack the Service or any provider — attempt to breach, disable, or interfere with the security or integrity of the Service, Recovea’s infrastructure, or any Upstream Provider’s systems, including unauthorized penetration testing, denial-of-service, credential stuffing, or injection attacks.
• Attack or probe other tenants — access, probe, scan, enumerate, deanonymize, degrade, or interfere with any other tenant’s data, traffic, accounts, configuration, cache, savings, or quality of service.
• Defeat metering or integrity controls — tamper with, falsify, or game the Service’s metering, cost attribution, baselining, quality-gate, or ledger mechanisms; spoof usage, costs, model identifiers, or savings; or otherwise impair the records billing and savings reporting depend on.
• Reverse engineer — derive the source code, models, methods, non-public APIs, routing logic, or verification methodology of the Service, except where that restriction is prohibited by law.
• Build a competing product from access — use the Service’s behavior, outputs, savings results, routing decisions, verification methodology, dashboards, or Metadata to build a product that competes with Recovea’s cost-optimization, savings-measurement, or savings-verification functionality. This does not restrict your own internal use of your own Customer Data and ledger history as permitted by the Agreement.
• Otherwise abuse the Service — send unlawful spam, impersonate Recovea or others deceptively, or act in any way that exposes Recovea, another tenant, or an Upstream Provider to legal liability or material operational risk.

These prohibitions are contractual restrictions on you, not a representation that Recovea detects them. Because of no-bodies-by-default, Recovea generally cannot inspect content and does not warrant that it will detect, prevent, or block prohibited content or uses. Detection and compliance with each Upstream Provider’s content rules remain your responsibility.

3. Restricted data

Unless expressly agreed with Recovea in writing (for example, in the DPA or an order form, with any required safeguards), you will not submit or route: protected health information or other data subject to HIPAA or comparable laws; cardholder or payment-card data subject to PCI DSS; or other specially regulated or “special category” data, including government identifiers, financial account credentials, biometric or genetic data, precise geolocation, or children’s personal data. This mirrors and is read together with the DPA; if the DPA states a different allocation for a category, the DPA controls for personal-data processing. Recovea’s no-bodies-by-default posture means Recovea cannot and does not screen Routed Traffic for restricted data — keeping it out is your responsibility.

4. Tenant, infrastructure, and operational protections

• No volume or rate abuse. Do not impose an unreasonable load on the Service or its infrastructure. Recovea may apply reasonable rate, concurrency, or volume limits to protect the Service and other tenants.
• No resale of access. Do not resell, sublicense, rent, time-share, or operate the Service as a service bureau for any third party that is not an Authorized User acting on your behalf, except as a signed order form expressly permits.
• No credential sharing across entities. Do not share your account, API keys, or credentials with separate legal entities; each distinct organization must be provisioned under its own agreement.
• Provider spend stays yours. Because the Service uses your own provider keys, you remain responsible for your own provider spend, rate limits, and quotas; Recovea does not assume your provider charges and (consistent with the fail-open design) does not hard-stop your underlying provider relationship.

5. Each provider’s policies govern content

For all Routed Traffic, you must comply with the then-current terms, usage policies, content policies, and rate limits of each Upstream Provider you route to (for example, OpenAI’s and Anthropic’s usage policies). The provider’s policies — not Recovea — govern the content rules for your prompts and completions. Recovea routes your traffic to your chosen provider on your own key and is a neutral passthrough: it cannot guarantee that any provider will accept, complete, or refrain from rejecting any request, and is not responsible for provider availability, model behavior, refusals, moderation, pricing, or output. If a provider suspends, throttles, or terminates your access, that is between you and the provider, does not relieve your obligations to Recovea, and (where it stems from a policy violation) is also a breach of this AUP that triggers your indemnity under §9.

6. Your end users and downstream apps

You are solely responsible for your own products and applications that use the Service, and for the acts of your Authorized Users and end users. You must ensure they use the Service in compliance with this AUP, the Agreement, applicable law, and the applicable provider policies, and you are responsible for maintaining your own acceptable-use and content controls for your end users. Recovea is not, and does not provide, an end-user-facing content-moderation layer. All Routed Traffic under your account is attributed to you regardless of which end user originated it.

7. How Recovea detects and responds

Recovea does not monitor, review, scan, or moderate the content of Routed Traffic by default, is not obligated to monitor it, and any right it exercises under this AUP is a right and not a duty. Enforcement is based on the limited, content-free signals available — principally Metadata (anomalous volume, rate, error, or cost patterns; signs of metering circumvention or attacks) — together with reports and notices Recovea receives from you, other tenants, Upstream Providers, or third parties.

Where Recovea reasonably believes (based on those signals) that a violation has occurred or is imminent, or that there is a genuine security, legal, or operational risk, Recovea may investigate using available Metadata and reports; suspend the affected route(s) while preserving the rest of your traffic; suspend your account or access in whole; apply or tighten rate, concurrency, or volume limits; require you to remediate within a stated period; and preserve relevant content-free records and cooperate with lawful requests.

Recovea will give notice where practicable and work in good faith to restore affected routes once the issue is resolved. It may act without prior notice where prior notice would worsen a security, legal, or operational risk, allow ongoing harm, or is impractical (for example, an active attack or a binding legal demand), and will then give notice as soon as reasonably practicable.

Because the gateway is designed fail-open, suspending an affected route or your Recovea access reverts that traffic to your own provider on your own keys (passthrough), rather than blocking your underlying application. Suspension removes Recovea’s optimization/metering layer for the affected scope; it is not a mechanism for Recovea to take your application offline, and Recovea does not purport to police your direct relationship with your Upstream Provider.

8. Reporting violations

Report suspected violations — abuse, security issues, or infringement — to security@recovea.ai (or legal@recovea.ai for legal and infringement notices). You will promptly notify Recovea if you become aware of any actual or suspected violation, any compromise of your account or keys, or any security incident involving the Service, and will reasonably cooperate with Recovea’s investigation (Recovea’s own visibility is limited to Metadata and reports).

9. Indemnification

Your use of the Service in violation of this AUP, applicable law, or an Upstream Provider’s terms or policies is an indemnified matter under the Agreement. Without limiting the Agreement’s indemnification provisions, you will defend, indemnify, and hold harmless Recovea and its affiliates, officers, and personnel from third-party claims, losses, and reasonable expenses arising out of (a) Routed Traffic, (b) any violation of this AUP by you or your users, or (c) any violation of an Upstream Provider’s terms or policies in connection with Routed Traffic. This section ties to, and does not expand beyond, the indemnification and the limitations of liability in the Agreement (including the fees-paid cap and the exclusion of consequential damages).

10. Suspension and termination

In addition to any rights in the Agreement, Recovea may suspend or terminate your access — in whole or per route — for a violation of this AUP or to address a genuine security, legal, or operational risk, with notice where practicable (and, for emergencies, without prior notice per §7). Recovea will, where practicable, prefer the narrowest effective measure — suspending the affected route(s) before the account — and will restore access in good faith once the issue is resolved. Suspension or termination does not relieve accrued payment obligations and (per §7) reverts affected traffic to your provider rather than taking your application down; termination otherwise follows the Agreement’s termination, export, and deletion provisions, including the honest carve-out under which account data, Metadata, and any opt-in bodies are deletable while the content-free, append-only ledger and audit records persist. Recovea is not liable for any suspension, termination, or route revert taken in good faith under this AUP and the Agreement.

11. Changes to this AUP

Recovea may update this AUP — for example, to address new abuse vectors, new provider requirements, or new Service capabilities — and will give notice of material changes (by posting the updated AUP with a new effective date and/or notifying you through the dashboard or by email). Changes are effective as of the stated date and apply going forward; continued use after the effective date is acceptance.

12. Honest disclaimers

Recovea does not actively scan, review, filter, or moderate the content of Routed Traffic by default, generally cannot see prompt or completion content, and is not the arbiter of your outputs or applications. Enforcement is metadata- and report-driven. Each Upstream Provider’s terms and policies — not Recovea — govern the content rules; Recovea is a neutral passthrough, cannot guarantee provider acceptance of any request, and is not responsible for a provider’s decisions, refusals, moderation, availability, or output. This AUP creates rights for Recovea and obligations for you; it does not expand Recovea’s warranties, and the Agreement’s “AS IS” / “AS AVAILABLE” disclaimers, the no-savings-guarantee, and the limitations of liability apply.

Contact

Questions: legal@recovea.ai. Security and abuse reports: security@recovea.ai.