Comment by wongarsu
1 year ago
A license grant like this is common in the context of review systems or forums or the like. For example if I go to addons.mozilla.org and post a review for an addon, Mozilla arguably needs a license grant like this to allow them to publish the review. And preferably they would want to word it in a way that then allows them to use the same review in print or a super bowl spot.
The weird thing is that a) I don't think this license grant covers any of that, since publishing a review doesn't improve my experience, it improves other's experiences, and b) Mozilla Websites like addons.mozilla.org have a completely different TOS [1], with a completely different license grant.
I have no idea what this license grant is supposed to accomplish, or what it would even allow that requires a license grant in the first place
Thinking about this a bit more: the most likely use for this specific license grant I can come up with is a 3rd party partnership similar to pre-acquisition Pocket.
Imagine if on first startup Firefox offers you to show website recommendations. Maybe a prechecked checkbox. If you don't say no, they send anything you type in the address bar to some third party, that third party throws that in a recommendation system and spits out websites you may want to visit, which Firefox then shows in the new-tab page. This license grant would cover that. They would be using a license on content I input (all my keystrokes in the address bar) to help me experience online content (recommendations for new content) as I indicate (they asked). In principle recommending me websites based on all images I upload with Firefox would also be covered, though that's a bit far fetched.
Of course in the EU you'd probably have pretty strict consent requirements because of the GDPR, same with other jurisdictions with strong privacy protections. But in places with weak privacy protections the grant in question should cover all bases to pull something like this