AFS Queries Sample Clauses

AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing, Customer understands and agrees that: (a) queries sent to Google for processing under its AFS Service may be initiated only by Subscribers entering text into WebSearch Boxes on the AFS Site and approved Customer Desktop Applications as provided herein; and (b) Customer shall send any and all queries generated on the AFS Sites and approved Customer Desktop Applications as provided in subsection (a) above to Google for processing under its AFS Services in accordance with the requirements provided by Google, without editing, filtering, truncating, appending terms to or otherwise modifying such AFS Queries, either individually or in the aggregate. Notwithstanding anything to the contrary, Google shall have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement.
Sample 1Sample 2Sample 3See All (7)
AutoNDA by SimpleDocs
AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing, Customer understands and agrees that: (a) queries sent to Google for processing under its AFS Service may be initiated only by End Users (i) entering text into web search boxes on the AFS Site(s) or on any AFD Results Page as provided herein, and (ii) clicking on text links included on the AFS Site or any AFD Results Page that are identified as search queries (e.g., labeled as “Related Searches”) and that generate a search results page; and (b) Customer shall send any and all queries generated on the AFS Sites as provided in subsection (a) above to Google for processing under its AFS Services in accordance with the requirements provided by Google, without editing, filtering, truncating, appending terms to or otherwise modifying such AFS Queries, either individually or in the aggregate. Notwithstanding anything to the contrary, Google will have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement.
Sample 1Sample 2
AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing, Customer understands and agrees that: (a) Queries sent to Google for processing under its AFS Service may be initiated only by End Users [*]; and (v) as otherwise approved by Google in writing; and (b) except as otherwise permitted [*], Customer shall send [*] Queries [*] to Google for processing under its AFS Services in accordance with the requirements provided by Google, without [*]. Notwithstanding anything to the contrary, Google will have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement.
Sample 1
AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing: (a) AFS Queries sent to Google for processing under the AFS Service may be initiated only by (i) End Users entering text into search boxes on the Properties and AFS Client Applications as provided herein, or (ii) [*]; and (b) AFS Queries that are generated on the Properties and AFS Client Applications and sent by Yahoo! to Google for processing under the AFS Service in accordance with Google’s technical requirements, will be sent by Yahoo! to Google without editing, truncating, appending terms to or otherwise modifying the AFS Queries either individually or in the aggregate. Notwithstanding anything to the contrary in the Agreement, Google will have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement. (b) Client IDs. Yahoo! must assign a separate Client ID to each category of [*]. (c) [*].
Sample 1
AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing, IAC understands and agrees and the IAC Site Affiliates shall ensure that: (a) queries sent to Google for processing under its AFS Service [***], and (b) the IAC Site Affiliates shall send such AFS Queries to Google for processing under its AFS Services [***]. Notwithstanding anything to the contrary, Google will have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement. [***]
Sample 1
AFS Queries. Unless (and then only to the extent) otherwise approved by Google in writing, Customer understands and agrees that: (a) queries sent to Google for processing under its AFS Service may be initiated only by End Users (i) entering text into WebSearch Boxes on the AFS Site and AFS Client Application as provided herein, (ii) clicking on text links included on the AFS Site that are identified as search queries (i.e., labeled as “Related Searches”) and that generate a search results page, and (iii) clicking on text links that comprise directory listings included on the AFS Site and that resolve to a page that displays directory search results; and (b) Customer shall send any and all queries generated on the AFS Sites and AFS Client Application as provided in subsection (a) above to Google for processing under its AFS Services in accordance with the requirements provided by Google, without editing, filtering, truncating, appending terms to or otherwise modifying such AFS Queries, either individually or in the aggregate. Notwithstanding anything to the contrary, Google will have no obligation to process AFS Queries that are not sent in compliance with the requirements of this Agreement.
Sample 1

Related to AFS Queries

  • RDDS query RTT Refers to the collective of “WHOIS query RTT” and “Web-­‐based-­‐ WHOIS query RTT”.

  • WHOIS query RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the WHOIS response. If the RTT is 5-­‐times or more the corresponding SLR, the RTT will be considered undefined.

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • Web Site Information on registration for and use of the E-Verify program can be obtained via the Internet at the Department of Homeland Security Web site: xxxx://xxx.xxx.xxx/E-Verify.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Links If The Services are made available through the Internet, the Financial Institution’s website may provide links to other websites, including those of Third Parties who may also provide services to You. You acknowledge that all those other websites and Third Party services are independent from the Financial Institution’s and may be subject to separate agreements that govern their use. The Financial Institution and Central 1 have no liability for those other websites or their contents or the use of Third Party services. Links are provided for convenience only, and You assume all risk resulting from accessing or using such other websites or Third Party services.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

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