You sign online checking "I accept terms." Six months later, fifteen-day unpaid invoice: site cut, database inaccessible, support cites clause 12.3. "Included" backups? Best effort — last restorable copy is three weeks old. Nobody opened the PDF on signing day.
Hosting terms and conditions define what the provider must do — and especially what they do not must do. They override sales talk. Reading before signing means buying with open eyes; reading after incident means negotiating from weakness.
Clauses to scrutinize first
| Clause | Question to ask |
|---|---|
| Backups and restore | Frequency, retention, paid restore? Tested? |
| SLA and credits | Scope, exclusions, compensation cap |
| Suspension and termination | Unpaid delay, abuse, "excessive" CPU |
| Acceptable use | Mass mail, mining, prohibited content |
| Data and reversibility | Export, post-termination deadline, fees |
| Liability limitation | Damage cap — often monthly fee amount |
| Subprocessors and location | Where data is processed, country change |
| Support | Channels, response times, out-of-scope app |
Scenarios where terms bite
Unpaid invoice — fast suspension; not always grace period to recover database.
Abuse report — host may cut before your response; see handling abuse.
Resource overrun — "unlimited" CPU often under fair use; throttling or surprise billing.
Contract end — data erased after N days; export your responsibility if not automated. Plan an exit procedure before effective termination, not the day before.
Content liability — you remain publisher; host hosts. Boundary with host/client responsibility.
Negotiate or refuse — B2B and volume
SMBs and associations: request amendment on backup retention, suspension delay, GDPR DPA. Enterprise: custom SLA, tested reversibility. If clause unacceptable (IP assignment, unilateral access without cause), change host — compare via directory.
Terms are the real comparison. Monthly price is one line — and sometimes the least risky one.
The peak: contract describes worst day, not demo day
Here is what sales does not read aloud.
Decide and move forward without blind spots
Before paying first month, treat terms as audit:
- Download terms and DPA before payment — not just pricing page.
- Highlight backups, suspension, liability and data export.
- Align with your own client terms if you are reselling agency.
- Test restore on staging environment and document gaps vs marketing promise.
- Archive signed version with date — online terms sometimes change without explicit notice.
To compare providers and documented conditions, use the directory and comparison tool.
Frequently asked questions
Are included backups guaranteed?
Rarely. Most contracts limit to reasonable effort without restoration guarantee. Check frequency, retention, restore cost and exclusions — then test recovery yourself on a staging environment before you need it in production.
Can the host suspend without notice?
Possible for abuse, unpaid invoice or CPU overload — delays vary widely between contracts. Read the suspension and termination section before counting on a forty-eight hour notice the salesperson mentioned verbally.
Who owns hosted data?
You, in principle, with export and post-termination retention conditions defined in the contract. In a dispute the host may limit access — verify reversibility and data return deadline.
Does marketing SLA deliver what it promises?
Terms and exclusions always override the homepage. Compare scope, exclusions and credits with our guide on the 99.99% uptime myth before committing to a contractual service level.
Sign hosting like insurance: the day you read the contract should not be the day the site is already down.