Sure, as a provider, you want to have absolutely no binding obligation to the person you are providing service to.
Of course, conversely, as the person receiving service, you absolutely want the provider to have binding obligations -- and "we can cancel this at any time for any reason or no reason with no obligation to give you anything, including your data, afterwards" isn't what you want from a service you are relying on in any kind of business use.
> As a separate matter: if these clauses discomfit you, speak to enterprise sales.
Or just don't use the service that offers them. The reason services use boilerplate like this isn't that its essential, its that the perceived cost/benefit ratio warrants it because most people don't read TOS and don't change behavior based on them.
Of course, conversely, as the person receiving service, you absolutely want the provider to have binding obligations -- and "we can cancel this at any time for any reason or no reason with no obligation to give you anything, including your data, afterwards" isn't what you want from a service you are relying on in any kind of business use.
> As a separate matter: if these clauses discomfit you, speak to enterprise sales.
Or just don't use the service that offers them. The reason services use boilerplate like this isn't that its essential, its that the perceived cost/benefit ratio warrants it because most people don't read TOS and don't change behavior based on them.