Proposed launch terms, not yet effective. Company details and service-specific commitments must be confirmed before live orders. The sections below describe the proposed policy in full.
On this page
1. Scope and related policies
These terms describe the relationship between Starcloud and the person or organisation using its customer account and cloud server services. References to you include anyone you authorise to manage your account. You must have the legal capacity to enter an agreement and the authority to act for any organisation you represent.
Your accepted order identifies the service, resources, billing period and price. Read these terms together with the Acceptable Use Policy, Privacy Policy, Refund Policy and any service-level schedule expressly included with your order. Mandatory rights under applicable law take priority over conflicting contractual wording.
2. Your account and account security
Provide accurate contact and billing information and keep it current. Use a unique password, enable additional authentication where available and restrict access to trusted people. You are responsible for instructions submitted through your account by people you have authorised.
Contact support promptly if you suspect unauthorised access, an incorrect order or compromised credentials. Never send passwords, private SSH keys, complete payment-card numbers or recovery codes in a support ticket. Ownership checks may be needed before account access or sensitive information can be changed.
3. Orders and service activation
Review your server size, operating system, region, storage, backup selection and access rules before ordering. An order acknowledgement or invoice is not confirmation that a server has been provisioned. Activation follows order acceptance, any required checks and confirmation that the selected resources are available.
Starcloud may decline an order that cannot be fulfilled, contains a material pricing error or presents a substantiated security or abuse risk. A material substitution requires your agreement. Payments for an order that is declined or cannot be supplied are handled under the Refund Policy.
Preview plans, simulated services and demonstration invoices are for evaluation. They do not provide a running server or establish a production service commitment.
4. Prices, invoices and payment
The accepted checkout total and order confirmation identify the currency, recurring charges, selected extras and applicable taxes. Marketing prices are a summary; review the complete order before payment. Optional storage or backup features are chargeable only when included in your selected configuration or subsequently authorised.
Pay invoices using an available method by the due date shown. Automatic collection requires the relevant payment authorisation. Report suspected duplicate charges or billing mistakes with the invoice reference and enough information to identify the issue. An unpaid or disputed amount does not justify charging a different payment method without authorisation.
5. Renewal, changes and cancellation
The order and account billing information must identify whether a service renews, its billing period and the method of payment. Any change to the recurring price must be communicated before it applies to a future period, with an opportunity to cancel before that period begins.
Submit cancellation through the available account controls or a support ticket that identifies the service and requested cancellation date. Keep the confirmation. Switching off a virtual machine, ceasing to use it or deleting files inside it is not a cancellation request and may leave reserved resources billable.
Upgrades and other changes take effect only after the revised price and configuration have been accepted. Cancellation stops future service as confirmed; it does not by itself determine whether an earlier payment is refundable.
6. Server management and access
Unless a separate managed-service agreement says otherwise, you administer your operating system, applications, patches, licences, accounts and data. Root or administrator access allows changes that can interrupt or damage your service. Check compatibility and keep a recovery plan before making significant changes.
Restrict SSH and Remote Desktop access to addresses you trust. Protect your private keys on your own device, rotate compromised credentials and remove access that is no longer needed. You must hold the permissions and software licences required for the workloads you install.
7. Your content and backups
You retain your rights in the content you place on a server. You authorise the processing needed to store, transmit and support that content as part of the service. You are responsible for having the necessary rights and lawful basis to upload or process it.
Backups are optional unless your accepted order states otherwise. A backup option is not a guarantee that every file, application or recovery point can be restored. Keep independent copies of important data and test recovery. Export the data you need before cancellation or termination; do not rely on continued access or recoverability after deletion.
8. Availability and support
Service interruptions may arise from maintenance, incidents, software faults or network conditions. Any contractual availability target and credit entitlement must be expressly included in the applicable service-level schedule. A marketing illustration or an estimate of activation time is not an availability guarantee.
Use the customer portal for account and service questions. Support scope, hours and response commitments are those expressly included with your service. Application development, operating-system administration and recovery of customer-caused data loss are not included unless separately agreed.
9. Restrictions, suspension and termination
Starcloud may restrict or suspend an affected service where reasonably necessary to address non-payment, a material breach, a legal requirement or an immediate threat to people, systems or network integrity. Where practical and lawful, notice should explain the reason and the action needed to resolve it.
Urgent protective action may precede notice. Restrictions should be proportionate to the issue. Reinstatement may require payment of valid overdue charges, removal of prohibited activity or evidence that a compromise has been resolved. A material or repeated breach that remains unresolved may result in termination.
Suspension is not a substitute for cancellation and does not promise a data-retention period. Ask support about access and export options before relying on a suspended service for recovery.
10. Responsibility and legal remedies
Each party is responsible for its own obligations and for loss attributable to its breach, subject to applicable law and the accepted agreement. You should assess whether the service is appropriate for your workload, especially where interruption could affect safety or essential operations.
Nothing in these terms excludes liability or a remedy that cannot lawfully be excluded, including applicable consumer protections. This draft does not set a monetary liability cap or require you to waive statutory rights. Any additional limitation must appear clearly in the final agreement before an order is accepted.
11. Questions and disputes
Raise a concern through support with the relevant service, invoice and a description of the outcome you are seeking. Both parties should make a reasonable effort to resolve the issue using the available records. Reporting a dispute does not remove your rights to contact a payment provider, regulator or competent court.
The final contracting entity and any agreed governing law must be identified before live orders are accepted. No jurisdiction, arbitration requirement or foreign court is selected by this draft. Mandatory protections in your place of residence continue to apply where required by law.
12. Changes to these terms
Revisions should carry an effective date and be available before they govern a new order or renewal. Material changes affecting an existing service should be communicated in advance, except where immediate changes are necessary for law or security. A later version does not retroactively remove rights or remedies that have already arisen.
If part of the agreement is unenforceable, the remaining provisions continue to the extent permitted by law. A delay in enforcing a right is not, by itself, a waiver of that right.
Questions about this policy?
If you have an account, open a support ticket with the relevant service or invoice reference. Otherwise, check the contact page for available ways to reach us.