Traffic Data Sample Clauses

Traffic Data. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non-existent domain names for purposes such as, without limitation, the determination of the availability and Security and Stability of the Internet, pinpointing specific points of failure, characterizing attacks and misconfigurations, identifying compromised networks and hosts and promoting the sale of domain names, provided however, that such use does not permit Registry Operator to disclose domain name registrant or end-user information or other Personal Data as defined in Section 3.1(c)(ii) that it collects through providing domain name registration services for any purpose not otherwise authorized by this agreement. In this regard, in the event the TLD registry is a "thick" registry model, the traffic data that may be accessible to and used by Registry Operator shall be limited to the data that would be accessible to a registry operated under a "thin" registry model. The process for the introduction of new Registry Services shall not apply to such traffic data. Nothing contained in this Section 3.1(f) shall be deemed to constitute consent or acquiescence by ICANN to an introduction by Registry Operator of a service employing a universal wildcard function, except that this sentence shall not prohibit the provision of nameservice or any other non-registry service for a domain or zone used for other than registration services to unaffiliated third parties by a single entity (including its affiliates) for domain names registered through an ICANN-accredited registrar. To the extent that traffic data subject to this provision is made available, access shall be on terms that are nondiscriminatory.
AutoNDA by SimpleDocs
Traffic Data. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non-existent domain names for purposes such as, without limitation, the determination of the availability and Security and Stability of the Internet, pinpointing specific points of failure, characterizing attacks and misconfigurations, identifying compromised networks and hosts, and promoting the sale of domain names; provided, however, that such use does not disclose domain name registrant, end user information or other Personal Data as defined in Section 3.1(c)(ii) for any purpose not otherwise authorized by this agreement. In this regard, in the event the TLD registry is a "thick" registry model, the traffic data that may be accessible to and used by Registry Operator shall be limited to the data that would be accessible to a registry operated under a "thin" registry model. The process for the introduction of new Registry Services shall not apply to such traffic data. Nothing contained in this Section 3.1(f) shall be deemed to constitute consent or acquiescence by ICANN to a re-introduction by Registry Operator of the SiteFinder service previously introduced by the Registry Operator on or about September 15, 2003, or the introduction of any other service employing a universal wildcard function, except that this sentence shall not prohibit the provision of nameservice or any other non-registry service for a domain or zone used for other than registration services to unaffiliated third parties by a single entity (including its affiliates) for domain names registered through an ICANN- accredited registrar. To the extent that traffic data subject to this provision is made available, access shall be on terms that are non-discriminatory.
Traffic Data. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non- existent domain names for purposes such as, without limitation, the determination of the availability and health of the Internet, pinpointing specific points of failure, characterizing attacks and misconfigurations, identifying compromised networks and hosts and promoting the sale of domain names, provided however, that such use does not permit Registry Operator to disclose domain name registrant or end- user information or other Personal Data as defined in Section 3.1(c)(ii) that it collects through providing domain name registration services for any purpose not otherwise authorized by this agreement. In this regard, in the event the TLD registry is a “thick” registry model, the traffic data that may be accessible to and used by Registry Operator shall be limited to the data that would be accessible to a registry operated under a “thin” registry model. The process for the introduction of new Registry Services shall not apply to such traffic data. Nothing contained in this section 3.1(f) shall be deemed to constitute consent or acquiescence by ICANN to an introduction by Registry Operator of a service employing a universal wildcard function. To the extent that traffic data subject to this provision is made available, access shall be on terms that are nondiscriminatory.
Traffic Data. State County X Consultant The County will supply information on existing counts if this information is currently on file. The Consultant shall determine if adjustments to these counts are warranted or if additional counts are required. The Consultant will be responsible for the adjustments or for the additional counts. The Traffic Department must approve all traffic data prior to use in design.
Traffic Data. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non­existent domain names for purposes such as, without limitation, the determination of the availability and health of the Internet, pinpointing specific points of failure, characterizing attacks and misconfigurations, identifying compromised networks and hosts and promoting the sale of domain names, provided however, that such use does not disclose domain name registrant or end­user information or other Personal Data as defined in Section 3.1(c)(ii) for any purpose not otherwise authorized by this agreement. The process for the introduction of new Registry Services shall not apply to such traffic data. Nothing contained in this section 3.1(f) shall be deemed to constitute consent or acquiescence by ICANN to an introduction by Registry Operator of a service employing a universal wildcard function. To the extent that traffic data subject to this provision is made available, access shall be on terms that are nondiscriminatory.
Traffic Data. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non-existent domain names for purposes such as, without limitation, the determination of the availability and health of the Internet, pinpointing specific points of failure, characterizing attacks and misconfigurations, identifying compromised networks and hosts, and promoting the sale of domain names; provided, however, that such use does not disclose domain name registrant, end user information or other Personal Data as defined in Section 3.1(c)(ii) for any purpose not otherwise authorized by this agreement. The process for the introduction of new Registry Services shall not apply to such traffic data. Nothing contained in this section 3.1(f) shall be deemed to constitute consent or acquiescence by ICANN to a re-introduction by Registry Operator of the SiteFinder service previously introduced by the Registry Operator on or about September 15, 2003, or the introduction of any substantially similar service employing a universal wildcard function intended to achieve the same or substantially similar effect as the SiteFinder service. To the extent that traffic data subject to this provision is made available, access shall be on terms that are non-discriminatory.
Traffic Data. 7.1 On a monthly basis, GeoCities will provide CDnow with a report in a form and via a distribution method mutually agreeable to the Parties concerning search and browsing behavior on the GeoCities Site, to the extent such behavior reasonably could relate to the online promotion or sale of Music or Video Products, or other products that CDnow may sell from time to time. CDnow will hold such data in confidence and will use it only in accordance with reasonable guidelines to be mutually agreed upon by the Parties. Notwithstanding anything to the contrary contained in this Section 7.1, GeoCities will not be required to deliver to CDnow any user data in violation of its then-existing policies regarding the protection of user information.
AutoNDA by SimpleDocs
Traffic Data. On a quarterly basis, iVillage will use its best efforts to provide Xxxxxx.xxx with mutually agreed data concerning search and browsing behavior on the Network, to the extent such behavior reasonably could relate to the online promotion or sale of books or other products that Xxxxxx.xxx i-nay sell from time to time. Xxxxxx.xxx shall treat such data as Confidential Information and will not use it iii except in accordance with reasonable guidelines to be agreed by the Parties. Notwithstanding anything contained in this Section, iVillage will not be required to deliver to Xxxxxx.xxx any user data in violation of its then-existing policies regarding the protection of user information.
Traffic Data. Traffic data is processed for the purpose of transmitting communication on an electronic communications network or for the billing in respect of that communication. This may include Customer Personal Data about the routing, duration or timing of a communication such as voice call, SMS or email, whether it relates to an individual or a company.
Traffic Data. You acknowledge that we will process or store data relating to the transmission of a communication through the Telco Services, including data relating to the time or duration of a communication and, where relevant, location data (“Traffic Data”), to manage billing or traffic, handle customer enquiries, or to prevent or detect fraud. You hereby consent to us processing the Traffic Data in accordance with this Section 3, and to us retaining such Traffic Data for so long as we require it in connection with the provision of Telco Services, up to a maximum of twenty-four (24) months or such other period as may be required by applicable laws and regulations. The processing of Traffic Data involves the collection of location data of terminal equipment from which the connection is made.‌
Time is Money Join Law Insider Premium to draft better contracts faster.