terms-of-service
What is the Google &quot;Company&quot; TOS for, compared to the Google Chrome TOS?
<p>So I see <a href="https://policies.google.com/terms?hl=en-US" rel="nofollow noreferrer">Google's TOS</a>, and <a href="https://www.google.com/intl/en_pk/chrome/privacy/eula_text.html" rel="nofollow noreferrer">Google Chrome's TOS</a>. First off, does the "Google's TOS" actually mean it's for the Google company as a whole, or is this just for the search engine? They mention user accounts, which is part of their core to the ecosystem of Google Apps and such (Gmail, etc.), so what exactly is this TOS for? When do you agree to this?</p>

<p>Second, if the "Google's TOS" is all you need, why do you have the Chrome TOS? Do you need a TOS for every product you create? Or can one general one suffice?</p>

<p>Basically, should a downloadable mobile/desktop app have a TOS called "My Company TOS", or "My App TOS"? Or should the "My App TOS" include a link to the "My Company TOS" as a prereq? Or does just having the "My App TOS" suffice?</p>

<p><em>I understand that Chrome is the browser we use for the web, a specific Google product. What I don't understand is (a) why they have a generic Company-wide TOS, and (b) how that relates to product-specific TOSes.</em></p>

<p>The "company TOS" specifically says that it applies to all of Google's Services.  It also says:</p>

<blockquote>
  <p>Our Services are very diverse, so sometimes additional terms or
  product requirements (including age requirements) may apply.
  Additional terms will be available with the relevant Services, and
  those additional terms become part of your agreement with us if you
  use those Services.</p>
</blockquote>

<p>So the terms in the "company" TOS apply to <em>all</em> their services, including Chrome, and the Chrome TOS adds <em>additional</em> terms that only apply to Chrome.  If you use Chrome, you have to comply with all the terms in both documents, except where the Chrome TOS specifically overrides the company TOS.</p>

<p>Presumably they found it inconvenient to have separate documents for all their many services, so they wrote a generic document that would be appropriate for most of them, and then they supplement this with specific documents when individual services need something special.</p>

<p>For your own apps, you'd have to decide, based on your business needs and in consultation with your lawyers, which of these two models makes the most sense for you.  It might depend on whether you had many apps that needed very different terms, or if they were all pretty similar.</p>
