AICloudGate / YungeRace Limited
Service terms draft
Confirm deliverables, then confirm the order. This is a framework for reviewing commercial terms, not a contract automatically accepted by browsing or making an inquiry.
01 Contracting entity and confirmation
AICloudGate is the website brand, operated by YungeRace Limited. This site provides information and inquiries, not online payment. A final order should identify the contracting entity and be confirmed in writing by both parties; this draft does not replace a signed order or contract.
Pending review: registration details, final contracting and acceptance procedures. Browsing or submitting a form does not create a paid order.
02 Services and access routes
Services may include commercial coordination for AI API access, usage and payment options, and AWS, GCP or Alibaba Cloud International billing. Official account/API routes and managed/intermediary platform routes are different products: account ownership, key permissions, request routing, billing and support boundaries should each be stated. Prepaid credit is usage credit for the agreed service, not a bank deposit.
03 Independent supplier and upstream rules
Cloud and model brand names identify products and do not imply certification or endorsement by every provider. Accounts, products and usage must follow the terms of the providers involved in the actual route. Models, regions, quotas and prices may change upstream and should be checked at quotation and activation.
04 Displayed pricing and quotations
The catalog is for inquiries, not a guarantee of access for every account or region. Potential AWS savings of approximately 30% apply only to eligible, reviewed bills, not a universal 30% discount on all services. Final models, regions, pricing units, tiers and conditions are governed by the written quote before payment.
Confirm per order: quotation validity, price-change notice and treatment of orders already paid.
05 Customer eligibility and use review
Inquiries require review of region, intended use, spend and payment route. The actual provider may impose account, identity or eligibility requirements. Initial inquiries do not require passwords, API keys or identity documents; any later verification should first specify its requirements and secure channel.
Pending review: customer eligibility criteria, necessary documents and procedures when service cannot be provided.
06 Accounts, permissions and keys
The quote should specify account ownership, control of billing and resources, key custody, and transfer or revocation of permissions at termination. Do not send root-account passwords or production keys through this form. If a key is exposed, contact the relevant account administrator and revoke or rotate it through the actual platform’s process.
Confirm per order: permission scope, credential delivery, responsibility for unauthorised usage and handover procedures.
07 Permitted use and compliance
Usage must comply with applicable law and actual provider policies. We do not offer stolen credits, exposed keys, malware, fraud, spam or circumvention of verification or regional restrictions. Account sharing, resale and redistribution require review of provider rules and the specific order; access is not permission for any use.
08 Usage, quotas and balances
Model IDs, regions, request rates, token quotas, resource capacity and prepaid amounts should be confirmed in the order. An upstream quota or prepaid balance is not automatically a hard spending cap; metering delays may cause overages. This website has no balance lookup, automatic top-up or inference-limit control facility.
Confirm per order: enforcement of limits, balance alerts, suspension conditions and handling overages.
09 Pricing, payment and settlement
Before payment, confirm currency, pricing method, taxes, exchange rates, payment channel, invoices or receipts, settlement cycle and bill reconciliation. Products and routes may carry different costs; a single website discount cannot establish the entire cost.
Agree in writing per order; this draft sets no default currency, tax treatment or settlement cycle.
10 Prepaid credit and refunds
Company practice is written agreement per order: pre- or post-activation refund conditions, unused balances, fees, refund timeframes and credit validity must be confirmed before payment. This website establishes neither unconditional refunds nor default non-refundability or automatic forfeiture at expiry. See the balance and refund draft.
11 Support scope and interruptions
Support is defined by the actual order. Round-the-clock coverage, custom development, managed operations, fixed response times and an uptime SLA are not included by default. Upstream outages, model changes or network issues may affect service. Model outputs are not guaranteed to be accurate or suitable for every use; important results should be verified.
Confirm per order: support hours, response targets, incident communication, remedies and upstream responsibility boundaries.
12 Responsibility and liability limits
This draft sets no liability cap and does not blanket-exclude all upstream failures, indirect losses or data issues. Responsibilities, excludable losses and non-excludable statutory liabilities require legal review for the order, jurisdiction and transaction type.
Legal review pending: limitations, exceptions, loss assessment and any liability cap. Unfinished provisions are not in force.
13 Claims and allocation of costs
Allocation of third-party claims, unauthorised-use losses and response costs requires consideration of facts, responsibility, law and the order. This draft does not automatically shift all losses to customers or impose unreviewed unlimited indemnities.
Legal review pending: claim notices, cooperation in defence, reasonable costs and indemnity scope.
14 Confidentiality and data processing
Provide redacted bills for an initial review, not passwords, keys or unrelated personal data. Inquiry-site processing is described in the privacy draft. Actual AI requests, responses, logs and account-data routes require separate disclosure for the order; the marketing server location does not establish the model processing location.
Per-order confirmation and legal review: confidentiality scope, access, processor arrangements and deletion or handover requirements.
15 Suspension and termination
Non-payment, suspected abuse, security issues, upstream restrictions or legal requirements may affect service. Triggers, notice, opportunities to remedy, data/account handover and remaining balances should be defined in the final order. This page does not establish default permanent suspension or balance forfeiture.
Review and agree per order: notice periods, termination procedures, incurred costs and remaining balances.
16 Force majeure and major events
Major events may affect delivery, but whether they constitute force majeure, notice and mitigation duties, and performance or refund arrangements after delay depend on law and the final order. An “upstream cause” does not by itself waive every responsibility.
Legal review pending: covered events, notice, mitigation, prolonged disruption and costs.
17 Governing law and disputes
For order or billing questions, first contact sales@aicloudgate.ai for reconciliation. A Hong Kong contact address alone does not determine governing law, courts or an arbitration seat. This draft selects no dispute forum and does not limit rights that cannot legally be excluded.
Legal review and contract confirmation pending: governing law, courts or arbitration mechanism and procedures.
18 Document priority, updates and contact
This is a review draft; its update date is not an effective date. Priority between final orders, supplements, provider rules and final terms, and handling differences between Chinese and English, should be established when contracting. Company contact address: UNIT A7, 12/F ASTORIA BLDG 34 ASHLEY RD TSIM SHA TSUI HONG KONG. Commercial contact: sales@aicloudgate.ai.