[grabeh]

I think there's a few points:

a) at what point is content uploaded to Grammarly. Is it uploaded automatically as you input (if you have the Chrome extension), or is it uploaded only where a user activates the extension. Clearly if the latter, then no one is going to be using Grammarly to check their code so no issue. Even if the former, it's still debatable whether or not the terms of use would even grant rights. It's still limited to content 'in connection with the use of the services or software' - content uploaded passively without any user action (aside from the initial act of installing the extension) doesn't fall neatly into that bracket.

b) The likelihood of Grammarly taking a decision to incorporate third party code into their service or to improve their service on the basis of the license granted in the terms of use is extremely slim. The reputational hit if it were to come out, and the lack of legal certainty over the status of the third party code would both act as a strong disincentive to do this.

[godelski]

> or is it uploaded only where a user activates the extension.

What if the extension is always running? Looking in every text field it finds? Because that would be convenient, but clearly we aren't "using the service" in all instances (as in ignoring what it suggests because it is easier than turning it off).

[grabeh]

For sure - that was my thinking on the alternative scenario. If that happens then that certainly changes the picture somewhat although my other points remain true around what Grammarly would decide to do with that content I would say!