Thanks for following up, Michael, it is much appreciated. It does leave me (and judging my adjacent comments, also others) with questions, including:
* That wording seems very specific - is there a reason you did not just say "we will not use Customer Input or Customer Content to train our AI" given you have defined those terms? Are you leaving scope for something else (such as uploaded files or presentation content) to still be used?
* Can you also clarify exactly which (and whose) "consent" is applicable here? In meetings between multiple equal parties there may not be any one party with standing to consent for everyone involved. Your blog post seems to assume there can be, but the ToS don't appear to define "consent".
It's great that you are engaging and writing about this, many thanks.
While your blog is interesting, it doesn't change the impact of the Terms of Service as currently written. They seem to give you the freedom to train your current and future AI/ML capabilities using any Customer Content (10.4), and your terms apparently have your users warrant that doing so will not infringe any rights (10.6).
Perhaps your terms of use should reflect your current practices rather than leaving scope for those practices to vary without users realising? Will you be changing them following all this feedback?
Thanks for commenting. The issue is not with using AI features though - it is with the Terms granting you unrestricted and eternal use to our conversations to train your AI and potentially disclose our work to your other customers.
* That wording seems very specific - is there a reason you did not just say "we will not use Customer Input or Customer Content to train our AI" given you have defined those terms? Are you leaving scope for something else (such as uploaded files or presentation content) to still be used? * Can you also clarify exactly which (and whose) "consent" is applicable here? In meetings between multiple equal parties there may not be any one party with standing to consent for everyone involved. Your blog post seems to assume there can be, but the ToS don't appear to define "consent".