By using the Custom Search API (referred to as the “CS API”), you (“Customer”) agree that such use is subject to these terms and conditions (the “Google CS API terms and conditions”) and also agree to be bound by the Google CS TOS (as defined below).
“API Documentation” means the documentation available at http://code.google.com/apis/customsearch/.
“Client User” means a third party that is accessing the CS Implementation so that such third party may offer the CS Implementation to end users.
“Deprecated Version” means the version of the CS API that will be discontinued, either because Google chooses to discontinue the CS API, or because Google upgrades the CS API to a newer version.
“Deprecation Period” means the three year period following an announcement by Google that the current version of the CS API will be deprecated.
“Google” means Google Inc. and its affiliates
“Google CS TOS” means the terms of service set forth at http://www.google.com/cse/docs/tos.html, or other such URL as Google may provide from time to time.
“CS API” means the application program interface that enables you to implement certain features of Google Custom Search on your website, your blog, or a collection of websites, and which is described in the API Documentation.
“CS Data” means data that is transmitted between the CS Implementation and CS Servers in connection with the CS API.
“CS Implementation” means a more customized version of Google Custom Search, based on the CS API, developed by Customer pursuant to the CS API Terms and the API Documentation, and which is used to communicate with CS Servers.
“CS Servers” means the servers used to provide the Google Custom Search services.
“Intellectual Property Rights” means current and future worldwide rights under patent law, copyright law, trade secret law, trademark law, moral rights law, and other similar rights.
“Software Principles” means the principles set forth at http://www.google.com/corporate/software_principles.html, or other such URL as Google may provide from time to time.
2.1 Handling of Data. The CS Implementation must be designed to store, handle, and transmit CS Data securely and in a manner at least as secure as any protocols described in the API Documentation.
2.2 Interaction with CS Servers. The CS Implementation must not interfere with the normal functioning of the CS Servers, and Customer acknowledges that Google may monitor CS API activity in order to prevent such interference. Except as expressly permitted by the API Documentation, Customer will not use any automated means (such as the use of scraping, robots or load testing) to access, query or otherwise collect CS related information. Google may set usage limits on features of the CS API.
2.3 Updates and Deprecation.
2.4 Fees.
This Section 3 only applies to Customer if Customer develops or distributes a CS Implementation for use by one or more third parties.
3.1 Treatment of CS Data. Customer will not sell, redistribute, sublicense or otherwise disclose or transfer to any third party all or any portion of the CS Data with one exception: Customer may disclose CS Data from a particular Client User to that Client User. If Customer terminates access to the CS Implementation for one of its Client Users, Customer must permit that Client User to copy and port any data related to that Client User which was previously collected through the CS Implementation. The CS Implementation must not, through its design or standard implementation, cause a Client User to breach the Google CS TOS.
3.2 Personally Identifiable Information. A CS Implementation will not collect personally identifiable information of any party unless it first: (a) informs the affected party about the types of information being collected and how that information may be used; and then (b) obtains the affected party’s express permission to do so.
3.3 Software Principles. Customer’s development and distribution of any software that uses the CS API, including the CS Implementation, must comply with the Software Principles. Customer’s development and distribution of any non web-based software, such as a software application that can reside at a location other than the web, that uses the CS API, including the CS Implementation, must be approved by Google’s prior to distribution.
4.1 Ownership. Except as expressly set forth herein, these terms do not grant either party any rights, implied or otherwise, to the other’s content or any of the other’s Intellectual Property Rights. Intellectual Property Rights in and to the content accessed through the services are the property of the applicable content owner and may be protected by applicable laws.
4.2 Indemnification. Customer agrees to indemnify, defend and hold harmless Google from and against any third party claims (and related liabilities, loss and expense) arising from or related to your breach of the Google CS API terms and conditions, your use of the CS API, or the development, distribution, or use of a CS Implementation.
4.3 Termination. Google may terminate these Google CS API terms and conditions or suspend or terminate your access to the CS API and any Deprecated Version of the CS API, or set limits on your usage in the following situations:
4.4 Effects of Termination. Upon a termination or notice of discontinuance, Customer must immediately stop using the CS API or Deprecated Version of the CS API, as applicable, and distributing or developing CS Implementations. Sections 2.4, 4.4, 4.6, and 4.7 will survive any termination of these Google CS API terms and conditions.
4.5 Modification. Google may modify these Google CS API terms and conditions from time to time in its sole discretion. If a modification is unacceptable to Customer, Customer may terminate these Google CS API terms and conditions by ceasing its use of the CS API. If Customer continues to use the CS API, then Customer will be deemed to have accepted the modifications.
4.6 Disclaimer and Limitation of Liability. The CS API is provided “as is” without any warranties. to the maximum extent permitted by applicable law, GOOGLE DOES NOT MAKE ANY OTHER WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR USE AND NONINFRINGEMENT. Google does not warrant that USE OF THE CS API will be error-free or uninterrupted. to the fullest extent permitted by law, GOOGLE WILL NOT HAVE ANY DIRECT, CONSEQUENTIAL, SPECIAL, INDIRECT, EXEMPLARY, PUNITIVE, OR OTHER LIABILITY WHETHER IN CONTRACT, TORT OR ANY OTHER LEGAL THEORY, RELATED TO THE CS API.
4.7 Miscellaneous. Customer is responsible for complying with all applicable laws in connection with Customer’s use of the CS API. The Google CS API terms and conditions are governed by California law except for its conflicts of laws principles. Any disputes will be adjudicated exclusively in the federal or state courts in Santa Clara County, California, and the parties consent to personal jurisdiction in these courts. The parties specifically exclude from application to these API Terms and Conditions the United Nations Convention on Contracts for the International Sale of Goods and the Uniform Computer Information Transactions Act. The Google CS API terms and conditions constitute the entire agreement between the parties with respect to the subject matter, and supersede and replace all prior or contemporaneous understandings or agreements, written or oral, regarding the subject matter. Google’s failure to exercise or enforce any right or provision hereunder will not constitute a waiver of the right or provision. If for any reason a court of competent jurisdiction finds any provision herein to be unenforceable, the remainder of these terms and conditions will continue in full force and effect. The Google CS API terms and conditions are not intended to benefit, nor will they be deemed to give rise to, any rights in any third party except for Google and its affiliates. Customer may not assign any rights hereunder and any attempt to do so is void. The Google CS API terms and conditions do not create any agency or partnership relationship.
April 15, 2011