Clear terms for an upstream-dependent hosting model.

This document is a pre-launch working draft of terms RENANT LIMITED may use for Renant-branded services. It is not in force and does not bind a visitor, RENANT LIMITED, or any upstream provider.

A future contract should be formed only when an authorized customer accepts the then-effective terms and a specific order, and RENANT LIMITED confirms acceptance. A website page, calculator, recommendation, provider directory, stock indicator, application, or acknowledgment of an inquiry is not acceptance of an order.

RENANT LIMITED intends to operate Renant as a provider-neutral reseller, coordination, and support layer. Renant does not claim to own every datacenter, network, server, cloud platform, IP prefix, or facility shown in a planning experience.

A service may depend on one or more upstream infrastructure, reseller-channel, network, software, payment, monitoring, or support providers. The accepted order should identify the selected product, region, material upstream dependencies or disclosure model, responsibility split, and any provider terms passed through to the customer.

Provider APIs and published specifications can change. RENANT LIMITED should verify price, availability, quota, licensing, location, lifecycle operations, and resale authority before confirming an order.

• The person accepting an order must have legal capacity and authority to bind the named customer.
• Account information must be accurate, current, and used only by authorized people.
• The customer is responsible for protecting sign-in methods, API credentials, recovery channels, and invited-user access.
• RENANT LIMITED may require proportionate identity, organization, payment, sanctions, fraud, or intended-use checks before accepting or continuing a service.
• A downstream reseller must maintain authority to act for each linked customer and must not expose another tenant's information.

Account selection in a user interface does not itself create a role or permission. Production authorization must be enforced server-side.

Until connected to a contracted provider, sample machine profiles, locations, prices, capacities, performance descriptions, uptime figures, and provisioning states are planning examples only. They are not live inventory or an offer to sell.

A guided recommendation is intended to reduce technical guesswork. It does not guarantee fitness for a workload. The customer remains responsible for explaining material requirements, including audience location, operating system, licensing, data sensitivity, availability, recovery, bandwidth, IPv4, and regulatory needs.

Expert filters normalize common provider fields, but an absent value may mean “unknown” rather than “not supported.” The accepted order overrides general catalog copy for the purchased service.

A valid quote should state its expiry, settlement currency, billing interval, included usage, upstream cost assumptions, Renant charges, licenses, network or IPv4 charges, estimated taxes where applicable, and consequences of provider price or foreign-exchange changes.

A displayed currency is for comparison unless the quote identifies it as the settlement currency. RENANT LIMITED cannot accept a currency merely because a browser can format it.

Descriptions of a cost-first, low-margin, or near-zero-profit mission are business aims, not a contractual promise that a customer price equals a provider's wholesale cost. A sustainable price may account for payment processing, foreign exchange, refunds, taxes, support, compliance, abuse handling, and other disclosed operating costs.

The customer is responsible for taxes, duties, withholding, bank fees, and similar charges allocated to it in the accepted order. No payment-card details should be submitted through a general contact form.

1. A quote or application is reviewed for eligibility, current provider availability, intended use, and billing readiness.
2. If accepted, Renant may create or link an upstream customer, subscription, project, billing relationship, or entitlement.
3. The infrastructure adapter may request the selected VM, VPS, server, storage, or network resource.
4. The service becomes active only after the provider confirms creation and Renant records the resulting resource.

Provisioning is asynchronous and may fail because of quota, stock, capacity, validation, provider review, payment, region, image, license, or network constraints. An order should state whether payment is authorized, captured, reversed, credited, or refunded after such a failure.

RENANT LIMITED may use idempotent retries and reconciliation, but should not silently substitute a provider, country, material specification, billing term, or public IP without approval.

The customer must use services lawfully, follow the adopted Acceptable Use Policy, maintain reasonable access controls, install updates for customer-managed software, preserve independent backups where appropriate, and notify Renant of suspected compromise.

“Managed,” “assisted,” and “self-managed” are different service scopes. Monitoring, patching, backup verification, incident response, application administration, and recovery are included only when the accepted order says so.

Customer instructions must be accurate and authorized. RENANT LIMITED is not responsible for loss caused by executing a valid instruction where the agreed authentication and approval process was followed, subject to the final liability terms.

Upstream providers may retire products, change APIs or prices, alter regions, perform maintenance, or require migration. RENANT LIMITED should give reasonable notice when it receives adequate notice and should explain any material price, provider, location, or service change requiring customer approval.

Emergency security, abuse, legal, or provider actions may require faster intervention. Where safe and permitted, Renant should communicate the reason, affected scope, expected next step, and available review route.

No uptime, response, restoration, or support target applies unless it is stated in an accepted order or effective service schedule. Demonstration status and response figures are not SLAs.

A final policy may permit proportionate suspension for non-payment, material breach, security compromise, unlawful activity, serious abuse, risk to other users or networks, invalid authority, or a binding provider or legal requirement.

Except where urgent action is reasonably necessary, the customer should receive notice and a chance to remedy. Suspension should be limited to the affected service where practical. It does not automatically erase amounts already due or records that must be retained.

Termination, export windows, backups, data deletion, domain or IP return, prepaid amounts, refunds, and provider cancellation charges must be stated in the applicable order. Customers should retrieve data before the applicable deletion deadline.

An assigned IP address is a limited right to use the address with the authorized service and for the agreed period; it is not a transfer of ownership. Assignments may depend on an upstream provider or lessor and may change or be withdrawn under the order, the IPv4 Leasing Policy, registry requirements, routing security, or abuse controls.

The customer must not issue, alter, reuse, or rely on a letter of authorization outside its exact prefix, ASN, party, purpose, and validity period. Route announcements, IRR objects, ROAs, reverse DNS, geolocation, and reputation may require separate coordination and are not guaranteed by a generated document.

Personal data is intended to be handled under the adopted Privacy Notice and any required data-processing terms. Each party should protect the other's non-public business, security, customer, pricing, and technical information and use it only for the authorized relationship.

Provider disclosure and customer confidentiality are not opposites: RENANT LIMITED should identify material upstream dependencies where required while protecting credentials, wholesale terms, security details, and unrelated customer information.

Infrastructure carries risks including interruption, latency, data loss, cyberattack, provider failure, configuration error, and changing law. The final terms must state any legally permitted warranties, exclusions, remedies, indemnities, liability cap, excluded loss, force-majeure treatment, claim process, governing law, and dispute forum.

This draft intentionally does not invent those provisions. They affect risk allocation and must be aligned with RENANT LIMITED's insurance, upstream contracts, customer type, Hong Kong registration, and each launch market.

An adopted version should carry an effective date and revision history. Changes that materially reduce customer rights or alter an active service should follow the notice and consent process in the accepted contract and applicable law.

RENANT LIMITED
3906, 39/F, THE CENTER, 99
QUEEN'S ROAD, CENTRAL
HONG KONG