BYOK Risk Disclaimer

Last updated: September 3, 2026

1. What is BYOK

"Bring Your Own Key" (BYOK) is a feature that lets you call OpenAI GPT, Anthropic Claude, Google Gemini, and similar third-party models using YOUR OWN API credentials. ORVEXA provides a unified endpoint and routing layer but is NOT a reseller of these models.

2. Your Relationship Is With the Upstream Provider

You must have a direct account with the provider and accept their terms (OpenAI Business Terms, Anthropic Commercial Terms, Google Gemini Terms).
Billing for BYOK usage appears on YOUR upstream account. ORVEXA does not mark up BYOK Token consumption and does not bill you for the upstream tokens themselves. ORVEXA may separately charge a platform service fee where disclosed.
Provider quotas, rate limits, content policies, model deprecations, and data handling policies apply directly to you.

3. Key Handling & Security

BYOK keys are encrypted at rest (AES-256-GCM) and only decrypted when proxying your requests.
We never sell, rent, or share your BYOK keys.
You are responsible for rotating/revoking keys if compromised. You can revoke ORVEXA's access at any time by deleting the key in the dashboard AND at the provider.
ORVEXA is not responsible for charges resulting from a key compromise caused by your actions (e.g. phishing, malware, sharing credentials).
When a BYOK key is used, requests are sent directly to that provider's official API endpoint (e.g., api.openai.com, api.anthropic.com, generativelanguage.googleapis.com). ORVEXA does not route BYOK requests through any third-party relay or reseller, and never uses your key for ORVEXA's own accounts or purposes.

No SLA / No Warranty for BYOK Models. Upstream availability, latency, and quality are outside ORVEXA's control. ORVEXA does not guarantee that a BYOK model will remain available, that the provider will not change its API, or that calls will succeed. Credits consumed on failed BYOK calls are handled per the Refund Policy: server-side failures before upstream Token use are auto-returned; once upstream has consumed Token, no refund.

4. No SLA / No Warranty for BYOK Models

ORVEXA provides no service-level agreement or warranty for BYOK models. The upstream provider controls availability, latency, and quality. ORVEXA does not guarantee that a BYOK model will remain available, that the provider will not change its API, or that calls will succeed.

5. Data Flow When Using BYOK

When you make a request using a BYOK model, the following flow occurs:

Request → ORVEXA gateway (auth, rate limit, logging metadata).
Decrypted BYOK key is used to authenticate with the upstream provider.
Request is forwarded to the upstream provider.
Response is returned to you through ORVEXA.

Prompt content is transmitted to the upstream provider under their terms. ORVEXA does not store prompt content by default.

6. Prohibited Uses with BYOK

The Acceptable Use Policy applies to BYOK usage. Additionally, you must not use BYOK to violate the upstream provider's terms, including their usage policies, geographic restrictions, or restrictions against automated scraping/red-teaming. Doing so may result in termination and is your sole responsibility.

7. Pricing & Credits Clarification

Item	Billed by ORVEXA?	Notes
Upstream tokens	Billed by provider directly	Tokens consumed using your own API key are billed directly by the upstream provider at their standard rates. ORVEXA does not charge for token usage under BYOK—only a small platform fee applies.
ORVEXA platform/routing fee	Yes	ORVEXA charges a platform service fee of US$0.05 per 1,000,000 tokens consumed (input + output), with the first US$5 per calendar month (UTC) free. The current rate is always shown in your dashboard and may be adjusted by the administrator.
Failed calls before upstream	Auto-refunded	Per Refund Policy
Failed calls after upstream consumed tokens	Billed by provider directly	Per Refund Policy

8. Limitation of Liability Specific to BYOK

In addition to the cap in the Terms of Service, ORVEXA is not liable for: actions of the upstream provider, suspended or closed upstream accounts, leaked keys due to your endpoint/devices, or loss of data sent through upstream.

9. Acknowledgement

By enabling BYOK, you confirm that you have read, understood, and agree to this disclaimer AND each relevant upstream provider's terms.

10. Contact

For questions about this disclaimer, contact hello@orvexaproject.com or write to ZEVCHEN AI LIMITED, Hong Kong.

This document was originally drafted in English. Translations are provided for convenience only. In the event of any inconsistency between the English version and any translation, the English version shall prevail and govern.