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 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.
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, 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.
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. 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. 7.1 On a monthly basis, GeoCities will provide SDE with mutually agreed data, in a form acceptable to SDE, concerning search and browsing behavior on the GeoCities Site, to the extent such behavior reasonably could relate to the online promotion or sale of computer hardware and software, or other products that SDE may sell from time to time. SDE will hold such data in confidence and will use it only in accordance with reasonable guidelines to be agreed by the Parties.
7.2 SDE will use its best efforts to provide GeoCities with an online report, produced on a daily basis, of orders for SDE's products submitted by GeoCities' users. Such report is to be used by GeoCities to actively track performance of various promotional tools that it has in service. GeoCities will hold such data in confidence and will use it only in accordance with reasonable guidelines to be agreed by the Parties. Notwithstanding anything to the contrary contained in this Section, SDE will not be required to deliver to GeoCities any data in violation of its then-existing policies regarding the protection of actual sales information.
Traffic Data. 8.1 On a monthly basis, GeoCities will provide FCCSU-LLC with mutually agreed data concerning search and browsing behavior on the GeoCities Site, to the extent such behavior reasonably could relate to the online promotion or sale of Consumer Card Products, or other [***] Confidential treatment requested for redacted portion. products that FCCSU-LLC may sell from time to time. FCCSU-LLC will hold such data in confidence and will use it only in accordance with reasonable guidelines to be agreed by the Parties. Notwithstanding anything to the contrary contained in this Section 8, GeoCities will not be required to deliver to FCCSU-LLC any User data in violation of its then-existing policies regarding the protection of User information. Prior to the Commencement Date of this Agreement the Company shall deliver to both FUSA and FCCSU-LLC its then existing policies regarding the protection of User information, and to the extent practicable, provide FUSA and FCCSU-LLC with thirty (30) days notice of any changes to such policies.
8.2 FCCSU-LLC will use commercially reasonable efforts to provide GeoCities with an online report, produced on a daily basis, of inquiries and/or applications for FUSA's products submitted by Company Users. Such report is to be used by GeoCities to actively track performance of various promotional tools that it has in service. GeoCities will hold such data in confidence and will use it only in accordance with reasonable guidelines to be agreed by the Parties. Notwithstanding anything to the contrary contained in this Section, FCCSU-LLC will not be required to deliver to GeoCities any data in violation of its then- existing policies regarding the protection of information about consumers and sales. Prior to the Commencement Date of this Agreement, FCCSU-LLC shall deliver to the Company its then existing policies regarding the protection of such information, and to the extent practicable, provide the Company with thirty (30) days notice of any changes to such policies.
8.3 FCCSU-LLC may maintain separately all information which is submitted and/or obtained as a result of an application for an account relationship with Company Users. This information becomes a part of FCCSU-LLC's own files and shall not be subject to this Agreement; provided that, any use of such information, except for fulfilling obligations hereunder, will not imply or suggest an endorsement of such information by the Company.
8.4 FCCSU-LLC and the Company mutually agree th...
