Cancelling is straightforward. What people regret is not the cancellation — it is discovering afterwards that the world they spent a year on lived only on a server that no longer exists.
What to do
- Download a full backup first
Before anything else. Create a backup, download it to your own machine, and open the zip to confirm the world folder is actually inside it. An unopened backup is an assumption.
- Save anything that is not the world
Plugin configs, permissions data, a database export if you use MySQL. These are the parts people forget, and they are the parts that took the longest to set up.
- Then request cancellation from the client area
Once you have the files, the timing of the cancellation stops mattering.
- Note what happens to the data
After termination, the container, its databases and its backup storage are deleted permanently and no copy is retained. Your downloaded copy is the copy.
Backups kept in the service's own storage go when the service goes. The only backup that helps you here is one that is already somewhere else — on your machine, or in your own cloud storage.
The world folder is portable. It opens in single-player, it uploads to a future server, and it can sit in a drive for years and still load. Downloading it means cancelling is a pause rather than an ending, which is often what people actually want.
Questions this usually raises
- Can I get a refund when I cancel?
- Refunds are limited to a 48-hour window from the first purchase for new clients, and require a verified outage of more than 24 consecutive hours. Outside that, cancelling stops future invoices rather than refunding past ones.
- Can I come back later?
- Yes — with your downloaded world, a new service starts where you left off. That is the whole reason step one is step one.
- Where do I actually cancel?
- From the billing portal, the same place invoices and tickets live.