Cancellation timing, eligibility and refund exclusions.
Submit cancellation through the ShelbyHost client area or an authenticated support ticket. Requests from unauthorised addresses or informal channels may require account verification. Unless you request immediate cancellation, an accepted request normally takes effect at the end of the current paid term.
To avoid renewal, submit the request before the next invoice or renewal date shown in your client area. Domain renewals, third-party licences and some infrastructure commitments may be processed in advance and can become non-refundable once ordered.
First-time customers purchasing an eligible monthly shared or reseller hosting plan may request a refund within 30 calendar days of the initial activation date. Eligibility applies only to the hosting fee actually paid and only where the order or product page does not state different terms.
VPS, cloud and dedicated services incur upstream and provisioning costs and are refundable only when the applicable order page or a written quotation expressly states a refund right. Where no such statement is provided, those services are non-refundable after provisioning.
Approved refunds are returned to the original payment method where reasonably possible. Processing time depends on the payment provider and banking network. Any non-refundable taxes, gateway costs, currency-conversion differences or chargeback fees may be deducted where permitted.
You must download and verify your data before the cancellation becomes effective. Service data may be permanently deleted after termination and may not be recoverable. ShelbyHost does not guarantee retention of backups for cancelled or unpaid services.
Please contact support before initiating a payment dispute so we can review billing and service records. An unjustified chargeback may lead to suspension and recovery of associated fees.
Submit cancellation and refund requests through the client area or the ShelbyHost contact page. Include the service identifier and reason for the request; never send passwords in a ticket.
