First, the only thing that is actually urgent
Almost nothing in that email needs answering in the next hour. One thing does: getting a copy of your data. Suspension usually means the service is switched off but intact. Termination means the disk is scheduled for deletion, and the gap between the two is often days and sometimes hours.
So before you argue, before you draft anything, before you post about it: open a ticket asking for a data export or temporary read access, in writing, and say you are asking under whatever retention window their terms give you. Do that first even if you are certain you are in the right, because being right and having your database are unrelated.
What a suspension actually is
Suspension is a commercial act, not a legal one. Your contract with a host almost always lets them suspend for a list of reasons, and the list usually ends with a clause broad enough to cover anything. That clause is the one that matters, and it is worth reading in your own terms of service now rather than during an argument.
There are four common triggers and they are worth telling apart, because the right response differs completely:
| Trigger | What it usually means | What actually helps |
|---|---|---|
| Abuse report | Somebody complained about your content | Ask what was reported, and by whom |
| Copyright notice | A rights holder sent a takedown | Read the notice; consider a counter-notice |
| Billing | A card failed or a chargeback landed | Pay by a method that cannot be reversed |
| Resource use | You exceeded a limit nobody quantified | Ask for the figure and the threshold |
The reason this matters: three of those four are negotiable and the fourth is a jurisdiction problem wearing a policy costume. If the trigger was a complaint rather than a court order, somebody made a decision, and decisions can be questioned.
The five things to ask for, in writing
- The specific clause. Not "our terms of service" — the numbered clause they say you breached.
- The report itself. If a complaint triggered it, ask for a copy, including who sent it. Many hosts will send it; some will not, and a refusal is itself informative.
- The retention window. How long until the data is deleted, as a date and a time, not "shortly".
- A route to the data. Read-only access, an export, or a window to run a backup. Offer to pay for it.
- What would restore the service. If the answer is "nothing", you are not in a dispute, you are in an eviction, and you should stop negotiating and start moving.
Keep all of it in one thread and keep it civil. Not for their benefit — because a calm written record is the thing you will need if this ends up in front of anybody else, and because the person reading your ticket did not make the decision and can sometimes be persuaded to escalate it.
What not to do in the first day
- Do not issue a chargeback. It converts a content argument into a payment fraud file, and it is the fastest way to turn a suspension into a permanent termination with the data gone.
- Do not sign up again under a different name at the same host. Evasion clauses are the one part of a terms of service that gets enforced enthusiastically.
- Do not post the ticket publicly yet. It sometimes works and it more often hardens the position of the person who has to answer you.
- Do not accept "resource abuse" without a number. If nobody can tell you which limit and by how much, the reason is not the reason.
Then work out which problem you actually have
Once the data is safe, there is one question worth answering honestly: was this about your content, or about you? A host that suspended you over a miscounted resource limit is a supplier problem and you can shop for another supplier. A host that suspended you because somebody complained about what you publish is a structural problem, and moving to a similar company in a similar country buys you the same outcome with a different logo on it.
That is the point at which the jurisdiction question becomes the whole question, and it is what the jurisdictions guide is for. The short version: what protects you is not a policy promising to ignore complaints, it is a company that is not obliged to obey them, in a country whose courts a complainant would have to actually visit.
How this estate handles the same situation
Every notice that arrives here is read, answered, and forwarded to the customer in full with the complainant named. Content is removed on an order from a court with jurisdiction over the company that hosts it, and on nothing else. The count of notices received and the count acted on is published every quarter, including the quarters where the answer is zero.
There are two things that will get a service terminated here without notice, they are on the acceptable use policy, and the list does not grow. Everything else gets a letter and fourteen days.
Questions people actually ask
Can a host really delete my data?
Yes, and the terms you agreed to almost certainly say so. What varies is the window. Ask for it as a date, in writing, on the first day.
Should I send a counter-notice?
Only if the trigger was a copyright notice, only if you have a genuine basis, and only after reading what it commits you to — it includes consenting to a court's jurisdiction. There is a whole article on that, including when it is a bad idea.
Is a suspension the same as a takedown?
No, and conflating them is what makes people answer the wrong question. A takedown targets specific content. A suspension switches off the whole service, and hosts reach for it because it is cheaper than reading.
Will moving hosts fix it?
If the trigger was billing or resource limits, usually. If it was a complaint about content, only if the new host is in a country where the complaint carries no weight and is a company the complainant would have to sue there.
Written by the people who answer the notices, and corrected when it is wrong. Last revised 30 July 2026.
Every price on this estate is published in full, in one place. See the whole catalogue