Original guide

Cloud hosting deals print a 30-day money-back guarantee. The provider's own rules give a domain 96 hours and a renewal nothing

Answer first: Short answer: the plan is refundable for 30 days, but the guarantee is a plan-level clock rather than a deal-level one, and most of what a discounted purchase bundles in falls outside it. On the two deal pages this site tracks the phrase 30-day money-back guarantee appears twice on the pricing page and four times on the cloud page, the pricing page adds a cancel-anytime line, and neither page prints a single exclusion: non-refundable, chargeback, dispute and proration all appear zero times on both. The provider's own refund policy, last revised 2026-10-02, sets the real edges. A new domain registration is refundable only if the request is initiated within 96 hours and more than 24 hours after any previous domain refund; Brazilian registrations get 168 hours instead. Domain renewals and completed transfers are never refundable, purchases made with crypto are never refundable, and the policy prints a separate list of products excluded from refunds under any circumstance that includes the paid boost for cloud hosting and credits of any type. VPS plans carry a 180-day cooldown between refunds, which is six times the 30-day window. A free domain bundled into a 12, 24 or 48-month deal is non-refundable and its standard price may be deducted from the refund. The refund is also the cancellation: submitting it stops the service and permanently deletes files, databases and email, and the money takes up to 48 hours of processing followed by 5-15 business days on a card.

Published: 2026-10-12 08:30

What this guide adds

Every fact in this article comes from pages the provider publishes and this site read: the two deal pages, the refund policy, and the knowledge-base articles linked below. The occurrence counts on the deal pages are this site's own count of terms on those two pages. The percentages and comparisons are this site's arithmetic on numbers the provider prints, and they are derived rather than sourced: 96 hours against the 720 hours in 30 days, the 30-day window against the printed 48-month term, the 180-day cooldown against the 30-day window, and the 48-hour processing window added to the published 5-15 business-day card timeframe. The two disagreements between the policy and the knowledge base are this site's own reading of two provider pages; no provider page states which one governs in either case, so the disagreement is reported as observed and not resolved. Where the policy is silent the article says so instead of filling the gap. No price, discount, traffic figure, ranking, click count, index count or performance number is invented here.

What the deal pages actually print about the guarantee

The pricing page prints the phrase 30-day money-back guarantee twice, once as a badge near the top of the page and once again in the list of things every plan includes, and it prints a companion line promising cancel anytime twice. The cloud page prints the same phrase four times, including one sentence that reads our 30-day money-back guarantee means it is risk-free, and a closing line that calls the product risk-free for 30 days.

That is the whole of it. Counting terms on the flattened text of the two pages, the pricing page prints non-refundable zero times, chargeback zero times, dispute zero times and proration zero times, and the cloud page prints the same four terms zero times each. The word refund appears exactly once on each page and in both cases it is the footer link to the policy document itself. The word cancel appears twice on the pricing page - the two cancel-anytime lines - and zero times on the cloud page, so the page that sells the longer, more expensive managed plans never says the word cancel at all.

The two deal pages therefore make a promise, give it a number, and then hand every edge case to a document they do not link from the body of the offer. That document is public, and the rest of this article is what it says.

The 30 days is a plan clock, not a deal clock

The refund policy, last revised 2026-10-02, opens its standard terms with the sentence that products may be refunded only if canceled within 30 days of the date of the transaction. It then defines date of the transaction in a way that matters for anyone who let a plan auto-renew: the phrase means the date of purchase of any product or service, which includes the date any renewal is processed. A renewal is therefore inside the 30-day clock on the day it is charged and outside it 30 days later, exactly like a first purchase.

The standard window covers hosting plans, SSL certificates, daily backups, the provider's CDN product, its own email product and the third-party Titan email product, priority support, a VPN bundle sold in 6 and 12-month terms, a game panel, and VPS plans other than upgrades. Two carve-outs sit inside that list. Hosting is covered for all plans except the first payment after a free trial and all VPS hosting plans, yet VPS and KVM VPS are then listed separately as refundable except for upgrades. Read literally, the standard-terms list excludes VPS plans and then re-includes them, which is the first of several places where the policy has to be read twice.

The second carve-out is the one a deal buyer feels: a discounted term is where the guarantee is advertised hardest, and a discounted term is where a free domain is bundled, and a bundled domain is governed by a different clock entirely.

The domains exception: 96 hours, not 30 days

A new domain registration is refundable only if two conditions are met at the moment the refund is initiated. The first is that the request lands within 96 hours of the registration. The second is that more than 24 hours have passed since the last refund of any other domain registration on the account. The second condition is a spacing rule rather than a deadline, and it is easy to trip: refund one domain, buy and refund another inside the same day, and the second request is refused.

Brazilian registrations get a longer window. For .br, .com.br and .net.br the policy sets the registration window at 168 hours instead of 96, which is seven days. That is the only extension printed.

Against the headline promise the arithmetic is stark and it is this site's arithmetic on the provider's own numbers: 30 days is 720 hours, so the 96-hour domain window is 13.3% of the window the badge advertises. A buyer who reads 30-day money-back guarantee, buys hosting with a domain, and comes back in two weeks still has a refundable plan and a non-refundable domain.

The policy also publishes the other direction - a list of country-code registries that do not permit a refund on cancellation at all. It runs to well over 50 entries, and it includes the extensions a small business is most likely to want: .uk and .co.uk, .in and .co.in, .de and .com.de, .ca, .us, .fr, .eu, .it, .nl, .se, .es, .pl, .au and .com.au, .jp, .ch, .cz, .dk, .be, .at, .gr, .pt, .fi, .tr and .com.tr, .mx and .com.mx, .ae, .cl, .pe, .pk, .si and more. Register one of those and the domain is outside the guarantee from the moment it exists.

A domain that was bought but never activated is treated differently again: it is refundable only if it has not been activated and the cancellation is requested inside the standard 30-day period from payment.

What is never refundable at all

The policy keeps a separate list of products and services that are not available for refunds under any circumstance. It is the list that answers most of the arguments a buyer would otherwise have with support, and it is printed in full. It contains redemption fees, domain name renewals, domain name transfers where the transfer succeeded, privacy protection, an SEO toolkit, an SEO marketing panel, Google Workspace email, VPS control-panel licences, website cleanup, upgrades for the game panel, VPS upgrades for KVM VPS, an email storage add-on, a paid boost for cloud hosting, AI Builder credits, credits for two named third-party AI platforms, all paid support services, GPU hosting, and the provider's own account credits.

Three of those deserve to be read twice against the deal pages. Domain name renewals are never refundable - and because the policy defines date of the transaction to include the renewal date, a renewal is the one payment that is inside the 30-day clock and excluded from the refund list at the same time. The paid boost for cloud hosting is never refundable, so the upsell attached to a cloud plan does not inherit the plan's guarantee. And credits of any type are never refundable, which covers the promotional credits the deal pages describe as a one-time gift.

The policy also states that services suspended, canceled or terminated for abusive usage or any other breach of the terms are not eligible for a refund, and that the provider reserves the right to decline a request unilaterally where it sees signs of refund abuse, defined as refunding the same services multiple times or repeatedly buying in bulk and asking for a refund.

The VPS cooldown: one refund every 180 days

VPS hosting gets its own paragraph rather than a line in the standard list. A VPS plan is refundable only if the request is initiated within 30 days of the transaction for that specific plan and more than 180 days have passed since the last refund for any other VPS plan on the account. The knowledge base restates it as a cooldown: after a successful VPS refund you are not eligible for another until 180 days have passed from the completion date of the last one.

The comparison is this site's arithmetic on two printed numbers: 180 days is six times the 30-day window that the guarantee badge advertises. For a buyer who tries one VPS tier, refunds it, and wants to try another, the guarantee is effectively a once-per-half-year entitlement, not a 30-day one.

Two other products carry conditions of the same shape. The provider's reach plan is refundable only inside 30 days, only if at least 180 days have passed since the last refund of another reach plan, and only if the buyer did not previously use the free version - in that case only the first renewal of the paid plan after upgrading from the free plan is eligible. The horizons plan is refundable inside 30 days only if fewer than 30 messages or prompts have been used, which puts a usage ceiling on top of the time ceiling.

Paid internal website migrations - between two accounts or two hosting plans at the same provider - are refundable only if the migration could not be completed because of technical errors.

A free domain is not a free refund

The policy has a section for special deals, and it names the exact offer the deal pages lead with: a free domain when buying a 12, 24 or 48-month hosting plan. A domain given away in that offer is non-refundable, cannot be exchanged for a different domain, and cannot be exchanged for another product. The three Brazilian extensions are carved out of that rule.

There is a second sentence that decides what actually lands in the buyer's account. Where a refund is granted, the provider reserves the right to refund the difference between the amount paid and the price of the domain that was received for free. The knowledge base states the same mechanic more plainly: if the refunded hosting plan included a free domain, the standard price of the domain may be deducted from the total refund amount. In both versions the buyer keeps the domain for the remainder of its billing period.

So the bundled domain behaves like a purchase the buyer did not choose to make. It is priced at the standard rate rather than at any promotional rate, it is deducted from whatever comes back, and it cannot be handed back to make the refund whole.

This is the point where the term a buyer selected changes the value of the guarantee. The special-deals rule is written around the 12, 24 and 48-month terms specifically, so the longer and cheaper the term the buyer chose, the wider the gap between what the badge promises and what a refund actually returns. The deduction is taken at the domain's standard price rather than at any promotional rate, and the policy publishes no formula for arriving at that figure.

Where the money goes, and how long it takes

The refund flow offers a choice of destination. Money can go back to the original payment method, or to the provider's own account balance, which arrives instantly and can be spent on any purchase except one funded through the crypto gateway. The balance option is a one-way door: the policy says that once a refund to balance is initiated for an invoice it becomes irrevocable and cannot be refunded to a different source, and the knowledge base repeats it - a refund to balance can only be issued once every 12 months per invoice.

Three payment methods cannot go back to the source at all and are refundable to balance only: Multibanco in Portugal, GCash in the Philippines and Fawry in Egypt. One, VTC Pay in Vietnam, supports full refunds only and not partial ones. Payments made in cash through methods with no associated account, such as OXXO and SPEI on the Mexican storefront, require the buyer to hand over bank details - account holder name, a national identity number, bank name, branch number, account number, account type, and for Mexico the 18-digit interbank number or for Argentina the uniform banking code - before anything can be sent.

The clock is two-stage, and this is the part the badge compresses into nothing. The knowledge base states that a refund can take up to 48 hours to be issued by the billing team. Only then does the payment method's own timeframe start: PayPal 2-3 business days, PIX 2-3, credit or debit card 5-15, and any other method 5-15. Business days are Monday to Friday excluding bank holidays. Adding the two printed stages, the slowest published path is a 48-hour processing window followed by up to 15 business days on a card - 17 business days in total, which is about three and a half weeks before the money is back.

Two smaller rules complete the picture. An over-funded balance can be refunded within 30 days of the payment that caused the over-funding. And a refund requested after a request is already in flight is not a thing: the knowledge base states the request is not reversible.

Two provider pages disagree, and the provider says which one governs

The refund policy and the knowledge base article that summarises it are not identical, and the differences are worth naming because both pages are the provider's own.

On domain transfers the policy requires that the transfer was unsuccessful and that the refund is initiated within 30 days from payment for the transfer. The knowledge base article states the same condition with a 96-hour window instead of 30 days. On purchased LLM credits the policy lists credits for two named AI platforms among the products not available for refunds under any circumstance, while the knowledge base says those credits are deducted from the refund amount - a deduction assumes a refund exists to deduct from.

The knowledge base resolves the question of which page wins, in its own words: the refund policy is the authoritative source for refund eligibility, and the article describes itself as a summary of the policy. On the one question that is only answered in the knowledge base, the domain-transfer window, a buyer holding both pages has a 30-day and a 96-hour answer and no statement from the provider about which applies. This site reports the disagreement rather than resolving it, because resolving it would require inventing a rule the provider has not published.

The irreversible part: the refund is also the cancellation

Submitting a refund request is the same act as cancelling the service. The knowledge base states it twice: as soon as a refund is processed the associated services are canceled automatically and stop working, and the refund request itself is not reversible - all files, databases, emails and any configuration are permanently lost, and a buyer who changes their mind must purchase a new service and restore from backups.

The practical consequence is that a refund request is preceded by a download, and one product has no download. Websites built with the provider's AI builder in manual mode cannot have their backups downloaded, and the cancellation article repeats the restriction; the alternative the knowledge base offers is exporting the content to WordPress. For every other site the advice is to download files, databases and email before starting.

Cancelling without refunding is a different operation and it is not a delete. There is no delete button or menu option in the dashboard for services, and the cancellation article says so directly. What a buyer does instead is turn off auto-renewal under billing and subscriptions, after which the service stays active until its expiration date and is then cancelled and deleted automatically. A domain cannot be deleted at all - it stays in the account until it expires, because of registry rules - and the account itself cannot be deleted while any active service is attached to it.

One more consequence is printed in the chargeback section, and it is the reason a buyer should call support before calling the card issuer. The policy treats a chargeback, reversal or payment dispute as a breach of the payment obligation. The remedies it reserves include immediate termination without notice of the account and of any domain or service registered or renewed through it, disabling card checkout on the account, and in the case of criminal fraud or obvious payment fraud permanent termination with no option to recover. To restore an account after a chargeback the buyer must verify the payment method, either with proof of payment or a censored photo of the card showing the first six and last four digits, and pay the fees and processing charges incurred.

What the guarantee leaves unstated

Several things a buyer would want are not published anywhere in the ten pages read for this article. The policy does not say whether the 30-day window is counted from the moment the payment is taken or from the moment the service becomes active, so a buyer cannot tell which of the two dates the clock starts on. It does not state how the standard price of a free domain is determined when the buyer received it inside a special deal, so the deduction cannot be predicted before the refund is requested. It does not say whether a promotional rate can be recovered if the buyer refunds and later repurchases the same plan.

It also does not quantify refund abuse. The policy reserves the right to decline a request where it sees abuse and gives two examples - refunding the same service repeatedly and buying in bulk to refund - but publishes no threshold, so a buyer cannot know how many refunds in a period is one too many. The 24-hour spacing rule for domain registrations is the only numeric anti-abuse limit in the document.

Finally, the policy does not explain the inconsistency in its own standard-terms list, where hosting is covered for all plans except all VPS hosting plans and VPS plans are then listed as refundable separately. Reading the document as a whole, the special VPS paragraph with its 180-day cooldown is the operative rule, and the flat exclusion sentence reads as the older of the two. This site reports the text as printed and does not choose between them.