Common use of Implementation and Maintenance Clause in Contracts

Implementation and Maintenance. 9.1 During the Term, Opera will ensure that the Google Search Service on Included Opera Browsers and the Existing Install Base, is implemented and maintained in accordance with (a) the Google Branding Guidelines, (b) the screenshots and specifications set forth in Exhibits A and B; (c) the Google Technical Protocols (if any) and any other technical requirements and specifications applicable to the Google Search Service that are provided to Opera by Google from time to time. 9.2 Opera shall only implement Navigational Error Pages client-side without changing or obscuring server error codes. Opera shall ensure that the Navigational Error Page does not include any advertisements and that an End User can opt-out of the Navigational Error Page handling by Opera through a link on the Navigational Error Page. 9.3 Opera shall ensure that the correct Client IDs are implemented in accordance with instructions from Google and that every Payable Desktop Query and every Payable Mobile Query entered by an End User includes the correct Client ID. For the avoidance of doubt, Google understands and acknowledges that Opera shall not be required to update the Client ID in the Existing Install Base where it is not technically possible to do so. 9.4 Opera shall ensure that Client IDs are only implemented in respect of Payable Search Access Points. Without prejudice to the generality of the forgoing, Opera shall ensure that Client IDs are not included in: (a) any location or Search Access Point other than a Payable Search Access Point; (b) any Excluded Opera Desktop Browsers, Excluded Opera Mobile Browsers or Excluded Opera Mini Browsers (even if such browsers contain an option to select the Google Search Service in a menu of search providers); (c) any Excluded Search Access Points (even if such Excluded Search Access Points contain an option to select the Google Search Service in a menu of search providers). 9.5 Opera shall provide such information to Google as Google may reasonably request with respect to the use and application of any Client IDs. 9.6 On and from the Amendment Effective Date, Opera shall ensure that: (a) Payable Smartphone Queries and Payable Feature Phone Queries are identified by separate and distinct Client IDs; and (ii) only versions of the Opera Mini Browser and Opera Mobile Browser that are installed on Smartphones will contain Client IDs associated with Payable Smartphone Queries. Google and Opera acknowledge that prior to the Amendment Effective Date, Client IDs associated with Payable Smartphone Queries may have been included in some Opera Mini Browsers and Opera Mobile Browsers that are installed on Devices that are not Smartphones. On and from the Amendment Effective Date, the Client IDs which Opera shall implement in respect of Payable Smartphone Queries shall be the following, as applicable: ms-opera-mobile, ms-opera-mini-android, ms-opera-mini-iphone, ms-opera-mobile-android and ms-opera-coast (together with such additional alpha numeric codes as Google may specify to Opera). 9.7 [***] (a) [***] (b) [***] 9.8 [***]

Appears in 6 contracts

Samples: Google Distribution Agreement, Google Distribution Agreement, Amendment and Restatement Agreement (Opera LTD)

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!