Provider terms get skipped because they look like legal boilerplate. Two sections of them are operationally important, short, and written in plain language — and both change what you can safely build.
The acceptable use policy
This is the document that defines what the platform may be used for. It is normally a few pages and it decides, among other things, whether your workload is permitted at all.
Worth checking specifically:
- Outbound email. Many providers block SMTP ports by default and require a request, and some prohibit bulk sending entirely.
- Network scanning and security testing, including against your own systems — most providers require prior notice.
- Cryptocurrency mining, which is prohibited outright on a number of platforms.
- Content hosting rules, which vary considerably between providers and jurisdictions.
- Resale or sublicensing of the service to third parties, which is restricted on some platforms and permitted on others.
Operating outside the acceptable use policy is grounds for suspension irrespective of payment history, so it is worth confirming compliance before the workload exists rather than after.
Suspension and notice
Find the clause that says what happens when the provider believes something is wrong. Specifically: whether you get notice before suspension, how long you have to respond, and whether data is retained during the suspension or after termination. Retention windows vary from generous to a matter of days.
This clause is the strongest argument in the entire terms document for keeping backups somewhere other than the provider you are backing up.
Data location and processing
If personal data is involved, two things matter: which regions the data will physically sit in, and whether the provider’s data processing addendum covers the arrangement you need. Region selection is the operational half of this and is genuinely hard to reverse later — see cloud regions and IP location explained.
Also check whether backups, logs and support tooling stay in the same region as the primary data. They frequently do not by default.
Service limits and support
- Default quotas and the documented process for raising them — see account age, verification and service limits.
- Support tier. On several platforms, technical support is a paid add-on and the free tier covers billing questions only. That matters at 2am.
- Change and deprecation policy. How much notice you get before a service or an instance family is retired.
A ten-minute version
- Search the acceptable use policy for your workload category.
- Read the suspension clause and the data retention period.
- Confirm the region list covers where your data must live.
- Check whether technical support is included or paid.
- Note the quota process for anything you will need at scale.
That is genuinely enough to avoid the expensive surprises, and it takes less time than provisioning the first server.
Where to go next
- Account age, verification and service limits
- Handing over a cloud account
- BuyCloudBulk terms of service
Questions
Frequently asked
Can a cloud provider suspend an account without warning?
Terms usually permit immediate suspension for suspected abuse or non-payment, with notice periods varying by provider and by cause. The retention window for your data after suspension is the clause worth reading closely.
Is sending marketing email allowed on a cloud server?
Frequently restricted. Many providers block SMTP ports by default and some prohibit bulk sending outright, expecting you to use a dedicated email service instead.
Does choosing a region guarantee my data stays there?
For the primary data, generally yes. Backups, logs and support tooling may default elsewhere, so check those separately if data residency is a requirement.