Terms of Service — Zion Router

Document status: Final publication draft
Jurisdiction: Vietnam
Last updated: 2026-04-26
Effective date: 2026-04-26
Operator: Truong Quoc Tuan — Individual business operator / Cá nhân kinh doanh
Website: https://zionrouter.com

Zion is currently operated by Truong Quoc Tuan as an individual business operator. Transaction receipts are provided for payment confirmation only and are not VAT invoices unless expressly stated otherwise.

This document is the English publication draft for Zion Router. A Vietnamese version should be prepared for Vietnam-facing users. For users located in Vietnam, the Vietnamese version should prevail to the extent required by applicable law.

1. Acceptance of Terms

By creating an account, clicking an acceptance button, generating an API key, making a payment, or using any feature of Zion Router (the Service), you (User, you) agree to be bound by these Terms of Service (the Terms) and the accompanying Privacy Policy.

If you do not agree to these Terms, do not create an account, make a payment, generate an API key, or use the Service.

These Terms form a binding agreement between you and the operator of Zion Router (Zion, we, us, our), as identified in Section 17.

1.1 Electronic acceptance and records

You agree that these Terms may be accepted electronically, including through account registration, dashboard confirmation, API-key generation, payment, or continued use of the Service. To the extent permitted by applicable law, electronic records, system logs, invoices, receipts, dashboard events, email notices, and support communications may be used as evidence of the transaction and your acceptance of these Terms.

1.2 Business users

If you use the Service on behalf of a company, organization, or other legal entity, you represent that you have authority to bind that entity. In that case, User means that entity, and consumer-protection rights applicable only to individual consumers may not apply.

2. Service Description

2.1 What Zion Router is

Zion Router is a multi-model AI API routing platform that provides unified access to third-party AI model providers through a single API interface. The Service is designed to let Users authenticate with one Zion API key, select supported models or routes, and pay through prepaid credits or subscription allowances.

The Service may include:

issuing a virtual API key prefixed with zr- to authenticate requests to Zion's /v1/* endpoints;
routing, forwarding, or proxying API requests to third-party AI model providers (Upstream Providers);
presenting model availability, provider routes, rate limits, pricing, and usage information in the dashboard or API;
tracking usage, credits, plan allowance, request metadata, and payment records;
charging the User's account in USD-denominated credit according to model usage; and
providing dashboard, billing, support, privacy controls, and usage-management functions.

Zion acts as an intermediary technical routing, billing, and developer-access layer. Zion does not guarantee that any specific Upstream Provider, model, route, endpoint, feature, latency, geography, data-retention mode, or price will remain available.

2.2 What Zion Router is not

Zion Router is not, during Phase 1:

the developer, trainer, owner, or primary operator of the third-party AI models made available through the Service;
a company that guarantees the continued availability, performance, safety behavior, data-retention practice, or output quality of any third-party model or provider route;
an orchestration, agent, memory, or enterprise AI platform;
an enterprise SaaS provider offering SSO, SCIM, SOC 2, dedicated SLAs, or custom enterprise contracts; or
a guarantor of model output accuracy, safety, legality, availability, or suitability for any specific purpose.

If Zion later offers Zion-operated models, fine-tuning, hosted models, or other AI infrastructure under Zion's own control, the applicable dashboard terms, model notices, or updated Terms will identify those services separately.

2.3 No professional advice or output guarantee

Outputs generated through the Service are produced by the selected Upstream Provider and model route. Outputs may be inaccurate, incomplete, biased, unsafe, offensive, outdated, or unsuitable for your purpose. You are solely responsible for evaluating, validating, and lawfully using any output before relying on it.

You must not rely on outputs as legal, medical, financial, tax, safety-critical, or other regulated professional advice without review by a qualified professional.

2.4 Phase 1 upstream provider scope

During Phase 1, Zion routes requests only to OpenAI models and APIs that are made available through Zion's dashboard, API documentation, or official product interface.

Additional third-party AI providers, such as Anthropic, Google, or others, may be added in future phases. Until a provider is listed as available in Zion's dashboard, API documentation, or official product interface, that provider is not part of the active Service.

2.5 Provider routes, data policies, and routing controls

Different Upstream Providers may apply different terms, usage policies, privacy practices, abuse-monitoring systems, data-retention rules, geographic restrictions, model behaviors, and pricing. By choosing a model or allowing Zion to route a request to a model, you acknowledge that the relevant Upstream Provider may process the request under its own policies.

Where available, Zion may provide provider labels, privacy indicators, routing preferences, or data-retention controls. These controls are provided for transparency and routing convenience. They do not replace the applicable provider terms and do not guarantee that a provider's external policies will remain unchanged.

Zion may add, remove, rename, substitute, restrict, or re-route models and providers for operational, pricing, security, legal, abuse-prevention, or upstream-availability reasons.

3. Account Registration and Security

3.1 Eligibility

To create an account, you must be at least 18 years old or the age of majority in your jurisdiction, whichever is higher. By registering, you represent that you meet this requirement.

The Service is not directed at children. If we learn that a minor has created an account, we may suspend or delete the account.

3.2 One account per person

Each natural person may maintain one active account unless Zion expressly approves otherwise. Creating multiple accounts to circumvent rate limits, abuse controls, payment restrictions, suspensions, or Upstream Provider rules is prohibited.

3.3 Accurate information

You agree to provide accurate, complete, and current information at registration, including a valid email address, and to keep that information up to date.

3.4 Account security

You are responsible for safeguarding:

your account credentials;
OAuth identities;
Telegram binding or other support-channel bindings;
virtual API keys generated through your account; and
all devices, systems, and software used to access the Service.

You are responsible for all activity conducted through your account, whether authorized by you or not, except where caused by Zion's proven fault or as otherwise required by applicable law.

You must promptly notify Zion of any suspected unauthorized access, leaked API key, compromised account, or suspicious transaction.

API keys must not be shared publicly, committed to public repositories, embedded in distributed client binaries, published in frontend code, or otherwise exposed. Zion is not responsible for usage or charges caused by leaked, shared, or mishandled keys, except where required by applicable law.

3.5 Email verification

Email verification may be optional during Phase 1 and may become mandatory later. Zion may require email verification, additional security checks, or payment verification as a condition of continued use.

4. Acceptable Use

4.1 Prohibited uses

You must not use the Service, and must not direct the Service to generate, facilitate, distribute, or assist with:

content or activity that is illegal under Vietnamese law or any law applicable to you;
content or activity prohibited under Vietnamese cybersecurity laws, including content that infringes national security, public order, social safety, or lawful rights and interests of organizations or individuals;
false information, impersonation, coordinated inauthentic behavior, mass disinformation, or election manipulation;
child sexual abuse material, sexual exploitation of minors, or any content that sexualizes minors;
non-consensual intimate imagery, including synthesized or deepfake depictions of real individuals;
harassment, threats, stalking, doxxing, targeted abuse, or unlawful defamation of individuals or organizations;
malware, ransomware, credential theft, phishing, intrusion tooling, denial-of-service assistance, or attacks on systems, networks, or infrastructure without lawful authorization;
bypassing access controls, geographic restrictions, account limits, payment restrictions, sanctions controls, rate limits, or technical restrictions imposed by Zion or any Upstream Provider;
reconstructing model weights, extracting proprietary system prompts, training data, confidential information, or trade secrets of an Upstream Provider where prohibited by that provider's terms;
illegal gambling, illegal drugs, prostitution, human trafficking, weapons trafficking, or other prohibited activities under applicable law;
activity that violates the applicable terms, usage policies, or safety rules of any Upstream Provider; or
any other use that Zion reasonably determines creates legal, security, operational, payment, or reputational risk.

4.2 Upstream Provider compliance

Your use of the Service must comply at all times with the terms of service, usage policies, safety policies, and technical limits of the Upstream Provider that processes your request, as updated from time to time.

If an Upstream Provider notifies Zion that your usage violates its policies, or if Zion reasonably believes such violation occurred, Zion may suspend, restrict, or terminate your access with or without prior notice.

4.3 Rate limits and technical boundaries

Zion may enforce rate limits, token limits, request limits, model limits, concurrency limits, plan limits, and anti-abuse controls. You must not attempt to circumvent these controls, including by:

creating multiple accounts;
pooling or reselling API keys without authorization;
distributing load across accounts to evade limits;
using automation to evade captcha, lockout, verification, or anti-abuse mechanisms; or
manipulating headers, identifiers, payment references, or technical metadata to bypass controls.

Attempts to circumvent technical controls are a material breach of these Terms.

4.4 Abuse investigation and limited review

Zion does not routinely or proactively review prompt or response content. By default, Zion is designed to process prompt and response content only transiently for request routing and response delivery, as described in the Privacy Policy.

However, Zion may review limited request content, metadata, account data, or transaction data where reasonably necessary to investigate abuse, security incidents, lawful requests, payment fraud, service integrity issues, sanctions or compliance concerns, or violations of these Terms, subject to the Privacy Policy and applicable law.

4.5 Enforcement

Zion may enforce this Section by warning, rate-limiting, suspending, terminating, blocking requests, revoking API keys, freezing payment-related functions, or taking other reasonable measures. Zion may also cooperate with Upstream Providers, payment providers, hosting providers, or competent authorities where required or permitted by applicable law.

5. Payment Terms

5.1 Credit-based billing

The Service operates primarily on a prepaid credit model. You purchase credit in advance, and API requests consume credit according to the applicable per-model price, plan allowance, minimum fee, and billing rules in effect at the time of the request.

5.2 Supported settlement methods

During Phase 1, Zion may support one or more settlement methods, subject to availability, jurisdiction, compliance review, provider rules, risk review, and operational limitations.

The currently supported settlement methods will be displayed in the dashboard at the time of top-up or checkout. Zion may add, suspend, restrict, delay, manually review, refuse, or remove settlement methods at any time.

For Vietnam-facing launch, Zion expects to support Vietnam bank transfer as the primary settlement method. Any digital asset, crypto asset, stablecoin, token, Binance Pay, blockchain transfer, or similar settlement method is subject to Section 5.4 and may be unavailable or restricted.

5.3 Currency and exchange rates

Internal accounting is denominated in USD. Displayed amounts may be shown in USD, VND, or another supported currency depending on locale and dashboard configuration.

Where VND is displayed, the exchange rate is locked when the invoice or payment instruction is generated and does not adjust during the payment window.

5.4 Digital asset and crypto settlement

Zion is operated from Vietnam by Truong Quoc Tuan as an individual business operator. Under Vietnamese law and regulatory guidance, digital assets, crypto assets, stablecoins, tokens, and similar virtual assets are not recognized as legal tender or lawful payment instruments in Vietnam.

Accordingly, Zion does not represent, offer, or treat any digital asset, crypto asset, stablecoin, token, or blockchain transfer as legal tender, money, electronic money, or a lawful payment instrument in Vietnam.

Crypto-based settlement options, if displayed or operationally supported, may be unavailable, restricted, delayed, refused, or replaced with an alternative settlement method where required by Vietnamese law, operator compliance requirements, third-party provider rules, sanctions controls, risk review, or operational limitations.

Zion reserves the right to refuse, reverse, delay, manually review, or require an alternative settlement method for any crypto-related transaction.

If a crypto-related transfer is operationally accepted, it may be final once broadcast and confirmed on-chain. You are responsible for sending the correct token, amount, network, wallet address, and any required memo, reference, or invoice identifier. Zion is not responsible for losses caused by sending funds to the wrong address, wrong network, unsupported token, incorrect amount, missing reference, or incompatible wallet, except where caused by Zion's proven fault or as otherwise required by applicable law.

5.5 User responsibility for local compliance

You represent and warrant that your use of any digital asset, crypto asset, stablecoin, token, blockchain transfer, or related settlement method complies with the laws and regulations applicable to you, including the laws of your country of residence, citizenship, incorporation, operation, and payment origin.

You are solely responsible for determining whether any crypto-related transaction is lawful in your jurisdiction. Zion is not responsible for any loss, restriction, penalty, tax, reporting obligation, account limitation, or legal consequence arising from your use of crypto-related settlement methods where such use is restricted or prohibited.

5.6 Sanctions and restricted jurisdictions

The Service is not available to any person or entity that is located in, organized under the laws of, ordinarily resident in, or acting on behalf of any jurisdiction subject to comprehensive sanctions or similar restrictions, including Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions of Ukraine.

You must not use the Service if you are subject to sanctions, listed on any sanctions-related list, or owned or controlled by a sanctioned person or entity under sanctions programs administered by relevant authorities, including the United States Office of Foreign Assets Control (OFAC), the United Nations, the European Union, the United Kingdom, or Vietnam.

Zion may screen, block, suspend, terminate, refund, freeze, or refuse transactions and accounts where required by sanctions controls, payment-provider requirements, risk review, or applicable law.

5.7 Network fees

Zion may absorb or charge network fees depending on the payment method and current commercial policy. Any applicable network-fee treatment will be shown or referenced before payment where practicable. Zion may change this policy with notice.

5.8 Pricing

Per-model pricing, subscription price, request floor, plan allowance, rate limits, and supported models are set by Zion and may change. Price changes do not retroactively change charges for already-completed requests.

A minimum fee of USD 0.0001 may apply to each successful request, regardless of token count, model, subscription status, or free-tier flag, unless the dashboard or plan terms state otherwise. Failed requests caused by upstream error, rate limit, invalid key, or insufficient balance are not billed unless expressly disclosed otherwise.

5.9 Receipts and taxes

Zion does not currently issue VAT invoices. If official VAT invoices become available in the future, Zion will notify Users and update the invoicing process accordingly.

You are responsible for determining and complying with your own tax obligations arising from your purchase or use of the Service. Zion does not provide tax advice and does not withhold or remit taxes on your behalf except where required by applicable law.

6. Subscription Plans

6.1 Daily refill model

Subscription plans follow a daily refill model. Each paid plan is billed per day and includes a daily allowance of tokens, USD value, requests, or other usage units. Unless stated otherwise, the daily allowance resets at UTC 00:00 and does not roll over. Unused allowance forfeits at reset.

Current plans, prices, allowances, rate limits, supported models, and available provider routes are displayed on the pricing page and/or in the dashboard at the time of subscription or top-up. The pricing page and dashboard are the controlling source for current commercial terms.

Plan details, prices, allowances, rate limits, allowed models, and available provider routes are admin-configurable and may change for future billing cycles.

6.2 Daily quota exhaustion

If an active daily-plan request is estimated to exceed your remaining daily allowance, it may be rejected before upstream with HTTP 402 Payment Required or a similar error. Top-up balance is not used as automatic overflow while active daily allowance is exhausted.

6.3 Manual renewal only

Zion does not auto-renew subscriptions during Phase 1. Zion does not store payment methods and does not initiate recurring charges. To continue a subscription after expiry, you must explicitly re-subscribe through the dashboard payment flow.

Zion may send renewal reminders by email, dashboard notice, Telegram, or other supported channel. These are courtesy notices. Failure to deliver or receive a reminder does not extend the subscription or prevent expiry.

6.4 Grace period

A 3-day grace period may apply after subscription expiry. During grace:

daily subscription allowance is zero;
paid-model requests are billed from top-up balance at the normal Zion price;
the minimum per-request floor continues to apply; and
free-tier models, if any, remain accessible only under their separate cap.

After the grace period ends, the account transitions to a no-plan state. You may re-subscribe at any time unless the account is suspended or terminated.

6.5 Upgrades and downgrades

An upgrade is effective immediately unless the dashboard states otherwise. You may be charged the full price of the new plan and a new billing cycle may begin. The applicable charge, effective date, and billing effect will be displayed before you confirm the upgrade.

A downgrade is effective at the end of the current billing period unless the dashboard states otherwise. You retain the current plan allowance through that period. Unused allowance is not refunded unless required by applicable law or expressly approved under Section 7.

6.6 Cancellation

Because renewal is manual during Phase 1, cancellation generally requires no action. If you do not re-subscribe, your plan expires at the end of the paid period, after which grace-period and no-plan rules apply.

6.7 Trial credit

Zion does not currently offer trial credit. New accounts begin with a zero balance; you must purchase credit before making any chargeable API call. Zion may reintroduce trial credit at its sole discretion and will document any such offer in the pricing documentation linked from these Terms.

7. Refund Policy

7.1 General rule

Except where required by applicable law or expressly stated in this Refund Policy, payments are generally non-refundable after credit, subscription access, or other digital access has been delivered.

This Section does not limit any mandatory consumer rights under Vietnamese law, including rights arising from non-delivery, incorrect delivery, material service defect, fraud, misrepresentation, or other circumstances where refund or remedy cannot lawfully be excluded.

7.2 Always refundable cases

Subject to verification, the following cases are eligible for refund or correction:

Duplicate payment — the same invoice was paid twice or an obvious duplicate payment occurred.
Zion technical error — payment was successfully received but credit was not delivered, wrong credit was delivered, or the account was charged incorrectly due to Zion's system error.
Confirmed unauthorized transaction — an unauthorized payment occurred through your account or payment method, subject to identity, account, and payment verification.
Mandatory legal requirement — a refund or remedy is required by applicable law, court order, or competent authority.

7.3 Discretionary goodwill cases

The following cases may be considered at Zion's discretion and are not guaranteed unless required by applicable law:

user error reported within one hour of payment;
wrong amount or wrong payment reference where funds are recoverable;
major Zion-controlled service outage lasting more than 24 hours during an active subscription period; or
exceptional circumstances where Zion determines that refund, credit correction, or goodwill credit is commercially appropriate.

7.4 Generally non-refundable cases

Unless required by applicable law or expressly approved by Zion, the following are generally not refundable:

change of mind after purchase;
credit that has already been consumed;
subscription period already activated and used;
unused daily allowance at cycle end;
price complaints after purchase;
switching to another provider;
inability to use a specific model because of an Upstream Provider change outside Zion's reasonable control;
credit forfeited after account deletion, except as stated in Section 8; or
loss caused by sending crypto to the wrong address, wrong network, unsupported token, or missing payment reference.

7.5 Refund request process

You may submit a refund request through the dashboard or support channel. Zion may request identity verification, payment proof, transaction hash, bank transfer details, invoice ID, account email, and other information reasonably necessary to verify the request.

Zion's internal non-binding target is to respond within 7 days and resolve approved refund cases within 14 days after receiving all required information. This target is not a service-level agreement.

Approved refunds may be processed, at Zion's discretion and subject to payment-method limitations, as:

credit added back to your Zion balance;
bank transfer;
crypto transfer; or
another reasonable method agreed by Zion.

7.6 Chargebacks and payment disputes

If you initiate a chargeback or payment dispute, Zion may temporarily suspend the affected account, API keys, payment-related functions, refunds, credit transfers, or account changes while the dispute is investigated.

Where a chargeback or payment dispute is fraudulent, abusive, made in bad faith, or inconsistent with verified payment records, Zion may terminate the account, recover losses, and take other measures to the extent permitted by applicable law.

Nothing in this Section prevents you from exercising mandatory rights available under applicable law.

8. Account Deletion, Suspension, and Termination

8.1 User-initiated deletion

You may request account deletion through Settings → Danger Zone or another method provided by Zion. User-initiated deletion includes a 30-day grace period unless Zion determines that immediate action is required for security, fraud, legal, or abuse reasons.

During the grace period:

your account may remain functional;
a dashboard notice may display the scheduled deletion date; and
you may cancel the deletion request before completion.

After the grace period ends:

personally identifying information is anonymized or deleted as described in the Privacy Policy;
API keys are revoked;
active sessions are deleted;
the account is not recoverable; and
transaction records, payment records, credit ledger entries, security logs, and other records may be retained where necessary for legal, tax, fraud-prevention, accounting, dispute, and audit purposes.

8.2 Anonymization scope

At deletion completion, Zion may:

replace email with a hash for duplicate-signup and anti-abuse detection;
replace account name with “Deleted User”;
remove or null OAuth identifiers, Telegram ID, phone number, and session records;
null API-key names while retaining hashed key values for audit continuity; and
anonymize or detach usage logs where technically and legally feasible.

8.3 Remaining credit on deletion

Remaining credit may be forfeited after deletion completion, except where refund is required by applicable law or expressly approved under Section 7.

The dashboard should warn you of any remaining balance before deletion completion. If you wish to request a refund of remaining balance, you should submit the refund request before deletion completes. Zion may pause deletion while a refund request is under review.

8.4 Zion-initiated suspension or termination

Zion may suspend or terminate your account, API keys, access, payment functions, or specific features, with or without prior notice, if:

you materially breach these Terms;
Zion reasonably suspects fraud, abuse, unauthorized access, compromised credentials, payment reversal, or security risk;
an Upstream Provider requires or requests restriction;
a payment provider, hosting provider, or infrastructure provider requires restriction;
a competent authority, court, or applicable law requires it; or
Zion reasonably determines that continued access creates legal, security, operational, or reputational risk.

In fraud, abuse, or severe violation cases, Zion may immediately revoke access without a grace period and may forfeit remaining credit to the extent permitted by applicable law.

If you believe a suspension or termination was made in error, you may contact support to request review. Reinstatement is at Zion's discretion unless otherwise required by applicable law.

9. Service Availability and Upstream Dependencies

9.1 No formal SLA during Phase 1

During Phase 1, Zion does not provide a formal service-level agreement unless a separate written agreement states otherwise. The Service is provided on a best-effort basis. Zion makes no representation or warranty as to uptime, latency, throughput, model availability, or uninterrupted operation.

9.2 Maintenance

Zion may perform scheduled or emergency maintenance at any time, with or without advance notice. Zion will use commercially reasonable efforts to reduce unnecessary disruption where practicable.

9.3 Dependency on Upstream Providers

The Service depends on Upstream Providers. Upstream Provider outages, degraded performance, policy changes, pricing changes, model deprecations, safety restrictions, geographic restrictions, account restrictions, or service terminations may directly affect Zion.

Zion is not liable for:

Upstream Provider outages or degraded performance;
Upstream Provider price changes;
Upstream Provider decisions to restrict, block, suspend, or geo-fence users, regions, accounts, models, or requests;
model retirement, renaming, or output-behavior changes;
safety filters, moderation decisions, or refusals by Upstream Providers; or
delays or errors outside Zion's reasonable control.

9.4 Model changes and substitutions

Models may be added, removed, renamed, rate-limited, substituted, or repriced at any time due to upstream availability, pricing, policy, legal, or technical constraints.

9.5 Geographic restrictions

Zion may not actively geo-block all restricted countries or regions. Upstream Providers may enforce their own geographic, sanctions, compliance, or access restrictions independently. If an Upstream Provider blocks a request because of location, policy, or compliance restrictions, that is not a Zion-controlled failure.

10. Intellectual Property

10.1 User inputs and outputs

As between you and Zion, you retain ownership of the prompts, inputs, files, code, and data you submit through the Service (Inputs) and, subject to Upstream Provider terms, the outputs generated in response to your Inputs (Outputs).

Because Zion does not intend to store Inputs or Outputs except as described in the Privacy Policy, you are responsible for retaining your own copies if needed.

10.2 Upstream Provider terms on outputs

Rights in Outputs, including commercial-use rights, may be governed by the applicable Upstream Provider's terms, not solely by Zion. You are responsible for reviewing the applicable Upstream Provider's terms before relying on Outputs for commercial, regulated, or high-stakes purposes.

10.3 Zion intellectual property

The Service, including the Zion Router platform, routing and billing logic, dashboard UI, documentation, trademarks, trade names, branding, and zr- key-prefix convention, is and remains the property of Zion or its licensors. These Terms grant you only a limited, revocable, non-exclusive, non-transferable right to use the Service as intended and in compliance with these Terms.

10.4 Feedback

If you voluntarily provide feedback, suggestions, bug reports, or ideas, you grant Zion a worldwide, perpetual, irrevocable, royalty-free license to use them for any purpose without obligation to you, to the extent permitted by applicable law.

11. Data Protection and Privacy

11.1 Privacy Policy

Zion processes personal data as described in the Privacy Policy. The Privacy Policy forms part of the user-facing legal documentation and should be read together with these Terms.

11.2 Categories of data

Depending on your use of the Service, Zion may process account information, email address, OAuth identifiers, Telegram identifiers, payment records, invoice and receipt records, credit ledger entries, usage metadata, API-key metadata, security logs, support communications, and other information necessary to operate, secure, bill, and support the Service.

11.3 Transient routing of request data

Zion may process API request and response data transiently to route requests, receive responses, enforce technical limits, calculate usage, prevent abuse, and maintain service integrity. Zion's intended policy is not to persistently store prompt or response content except where necessary for security, debugging, abuse investigation, legal compliance, or as otherwise described in the Privacy Policy.

11.4 Consent and legal basis

Where required by applicable law, Zion will collect consent before processing personal data for purposes that require consent. Zion may also process data where necessary for contract performance, legal compliance, fraud prevention, cybersecurity, dispute handling, accounting, or legitimate service operation, to the extent permitted by applicable law.

11.5 Upstream Provider processing

Requests routed through Zion may be processed by Upstream Providers under their own terms and privacy policies. Zion does not control all processing performed by Upstream Providers. You are responsible for ensuring that your use of the Service and your submission of Inputs comply with applicable law and Upstream Provider terms.

12. Disclaimers

To the maximum extent permitted by applicable law, the Service is provided on an “as is” and “as available” basis.

Zion does not warrant that:

the Service will be uninterrupted, error-free, secure, or available at any particular time or location;
defects will be corrected;
any model, endpoint, feature, or Upstream Provider will remain available;
Outputs will be accurate, lawful, safe, non-infringing, or suitable for your purpose; or
the Service will meet your business, technical, legal, or compliance requirements.

Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under Vietnamese law, including liability for fraud, intentional misconduct, or mandatory consumer-protection obligations.

13. Limitation of Liability

To the maximum extent permitted by applicable law, Zion shall not be liable for any indirect, incidental, special, consequential, punitive, or exemplary damages, including loss of profits, loss of revenue, loss of data, loss of goodwill, business interruption, or cost of substitute services, whether based on contract, tort, negligence, strict liability, or any other theory.

Zion shall not be liable for damages arising from:

acts, omissions, outages, pricing changes, restrictions, or policy changes of Upstream Providers;
content of Inputs or Outputs;
your reliance on Outputs without appropriate review;
unauthorized access caused by your credential loss, leaked keys, unsafe client implementation, or failure to secure your systems;
payment errors caused by your incorrect payment details, wrong crypto network, wrong token, or missing reference;
events outside Zion's reasonable control; or
your breach of these Terms or applicable law.

To the maximum extent permitted by applicable law, Zion's total cumulative liability for any claim arising out of or relating to the Service shall not exceed the total amount you paid to Zion during the six months preceding the event giving rise to the claim.

This limitation does not apply to liability arising from fraud, intentional misconduct, or any liability that cannot be limited under applicable law.

14. Indemnification

You agree to defend, indemnify, and hold harmless Zion, its operator, employees, agents, contractors, successors, and assigns from and against any claim, demand, loss, liability, damage, cost, or expense, including reasonable legal fees, arising out of or related to:

your breach of these Terms;
your Inputs, Outputs, or use of the Service;
your violation of applicable law, Upstream Provider terms, or third-party rights;
your tax obligations;
your payment dispute, fraud, abuse, or misuse of the Service; or
your failure to safeguard credentials, accounts, systems, or API keys.

This indemnity applies to the extent permitted by applicable law and does not limit mandatory rights that cannot be waived.

15. Force Majeure

Zion is not liable for failure or delay in performance due to causes beyond its reasonable control, including natural disasters, war, terrorism, civil unrest, labor disputes, power outages, internet outages, government actions, legal restrictions, Upstream Provider actions, payment-network disruptions, blockchain-network congestion, DNS failure, CDN failure, TLS certificate authority issues, hosting-provider incidents, or third-party infrastructure failures.

16. Governing Law and Disputes

16.1 Governing law

These Terms are governed by and construed in accordance with the laws of the Socialist Republic of Vietnam, without regard to conflict-of-law principles.

16.2 Informal resolution first

Before initiating formal proceedings, you agree to contact Zion through the support contact in Section 17 and attempt to resolve the matter informally for at least 30 days, unless urgent injunctive relief, fraud prevention, legal compliance, or mandatory law requires otherwise.

16.3 Venue

Unless otherwise required by applicable law, disputes shall be resolved by the competent court of Vietnam. Where the law permits party-agreed venue, the parties agree to submit disputes to the competent court in Ho Chi Minh City, Vietnam.

16.4 Individual claims

To the extent permitted by applicable law, disputes must be brought in each party's individual capacity and not as a class, collective, or representative action.

17. Contact

Operator: Truong Quoc Tuan — Individual business operator / Cá nhân kinh doanh
Registered location: Ho Chi Minh City, Vietnam
Support email: support@zionrouter.com
Privacy contact: privacy@zionrouter.com
Telegram support channel: https://t.me/zion_router_support
Website: https://zionrouter.com

18. Changes to these Terms

Zion may modify these Terms from time to time.

For material changes, Zion will provide notice by email, dashboard notice, website notice, Telegram notice, or another reasonable method at least 14 days before the changes take effect, unless urgent security, legal, operational, Upstream Provider, or abuse-prevention reasons require faster action.

Your continued use of the Service after the effective date of updated Terms constitutes acceptance of the updated Terms. If you do not agree to updated Terms, your remedy is to stop using the Service and, if desired, request account deletion under Section 8.

19. Miscellaneous

19.1 Entire agreement

These Terms, together with the Privacy Policy, Cookie Policy and any documents incorporated by reference, constitute the entire agreement between you and Zion relating to the Service and supersede prior or contemporaneous communications on the same subject.

19.2 Severability

If any provision is found invalid or unenforceable, the remaining provisions remain in full force and effect. The invalid or unenforceable provision shall be interpreted or replaced to the extent necessary to achieve the original commercial intent in a lawful and enforceable manner.

19.3 No waiver

Zion's failure to enforce any right or provision is not a waiver of that right or provision.

19.4 Assignment

You may not assign or transfer these Terms without Zion's prior written consent. Zion may assign these Terms in connection with a merger, acquisition, reorganization, sale of assets, change of control, or transfer of Service operations, provided such assignment complies with applicable law.

19.5 Relationship

These Terms do not create a partnership, joint venture, agency, franchise, fiduciary, or employment relationship between you and Zion.

19.6 Language

For Users located in Vietnam or transactions governed by Vietnamese law, the Vietnamese version shall prevail to the extent required by applicable law. The English version is provided for convenience unless expressly agreed otherwise in a valid separate written agreement.

19.7 Survival

Sections relating to payment obligations, refund limitations, account deletion consequences, intellectual property, data retention, disclaimers, limitation of liability, indemnification, dispute resolution, and miscellaneous provisions survive termination to the extent necessary to give effect to their purpose.

Glossary

Virtual API key means a credential prefixed zr- that you generate in the dashboard and use to authenticate requests to Zion's /v1/* endpoints.

Upstream Provider means a third-party AI company or API provider whose models, APIs, or services Zion routes to through the Service.

Daily allowance means the token, USD, request, or other usage quota included in a subscription plan and refreshed on the applicable schedule.

Top-up credit means prepaid USD-denominated balance purchased through supported payment methods.

Grace period means the limited period after subscription expiry during which account rules may differ as described in Section 6.

Operator means the individual or legal entity operating Zion Router, as identified in Section 17.

Appendix A: Policy Change Log

2026-04-23: Initial draft prepared.
2026-04-26: Final publication draft prepared for Phase 1 launch under individual-business operation.
2026-04-26: Updated to position Zion Router as a multi-model AI API routing platform with third-party provider routing, provider-policy disclosures, and provider-routing controls.
2026-04-26 (v5, P0–P2 review): Restricted Phase 1 upstream scope to OpenAI only (§2.4); restructured payment terms with explicit Vietnam crypto stance (§5.4), user local-compliance representation (§5.5), and OFAC/UN/EU/UK/VN sanctions exclusions covering Cuba, Iran, North Korea, Syria, Crimea, Donetsk, and Luhansk (§5.6); clarified that prompt/response content is processed transiently only and review is limited (§4.4); replaced hard-coded pricing table with reference to dashboard/pricing page (§6.1).