44 ms·

If I understand Google's ToS right, you are giving them a license to do pretty much anything with the data you upload to Drive. For instance, if you backup your

If I understand Google's ToS right, you are giving them a license to do pretty much anything with the data you upload to Drive. For instance, if you backup your git repo to Drive, Google's engineers have a license to take your source code and incorporate it into their own products. Now of course Google's not actually going to do that. So why not make the license say that? Google is using a generic ToS for all their products, but it's not appropriate to products that host valuable intellectual property.

tomkarlo 15y ago
Because it's impractical to create a TOS that defines all possible ways they might need to use that data in order to provide the service (from any court's viewpoint) but also explicitly carve out that usage. If re-using the code as you posit is indistinguishable (legally) from a valid use of the data they need in order to provide the service, they're not going to carve it out of the TOS. It's better to not attempt that, and let you (as the customer) pick if you're okay with that. If you find the risk unacceptable, don't use the service. To some degree that's a better outcome than exposing the host to a ton of legal risk.