Currently, to get an A at ToS;DR classifications, a service must have no bad (or blocker) cases.
Sometimes this may seem unfair, especially when a service only has bad cases that aren’t really affecting user’s rights.
As a result, I propose changing to neutral the following cases (further explanations are detailed below):
- In the topic Guarantee:
Case 160: No guarantee is given regarding quality
Case 290: This service does not guarantee that it or the products obtained through it meet your expectations or requirements
Case 286: The service is provided 'as is' and to be used at your sole risk
Case 288: The service does not guarantee accuracy or reliability of the information provided
These cases can be applied to any service, and anyway terms that don’t disclaim warranties are often incomplete and not enforceable (there’s no such thing as a Service that is able to guarantee that they’ll meet our requirements, for instance).
Regarding this case, the reason is similar too. It’s impossible to know if someday in the future they would need to stop providing some features or even terminate the service.
As raised in The problem of "You must create an account to use this service", this case is quite ambiguous. There are many services (like email providers, VPNs or Anti-Virus services) for which requiring users to register makes sense and creating an account doesn’t necessarily mean providing personally identifiable information (which is covered by case 409)
We could purge the points linked to it, and only keep those linked to services that shouldn’t require users to register, but that would make the case even more ambiguous and probably only few services would fit with the case.
What are your thoughts?