Common use of Traffic Data Clause in Contracts

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. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non-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 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. 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 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. Nothing in this Agreement shall preclude Registry Operator from making commercial use of, or collecting, traffic data regarding domain names or non-existent 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 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. 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 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 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 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 permit Registry Operator to disclose domain name registrant or end 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.