| 172 | 178 | - The actions or performance of Registrars, over whom Registry has no direct control. |
| 173 | 179 | |
| 174 | 180 | Users assume all risks associated with their use of Registry's services, including reliance on third-party systems or Internet connectivity. |
| 175 | 181 | |
| 176 | 182 | ### 4.4 Limitation of Liability |
| 177 | 183 | |
| 178 | | To the fullest extent permitted by law, Registry, its affiliates, officers, directors, employees, agents, and contractors shall not be liable to Users for any indirect, incidental, consequential, special, or punitive damages arising from or related to the use of Registry's services, including but not limited to loss of profits, data, business opportunities, or goodwill. Registry's total liability to a User for any claim, whether in contract, tort, or otherwise, shall not exceed the fees earned and received by Registry for the specific Registration at issue, if any. This limitation applies even if Registry has been advised of the possibility of such damages. |
| 184 | 4.4.1 To the fullest extent permitted by applicable law, Registry, its affiliates, officers, directors, employees, agents, and contractors shall not be liable to Users for any indirect, incidental, consequential, special, exemplary, or punitive damages arising from or related to the use of Registry's services, including but not limited to loss of profits, revenue, data, business opportunities, or goodwill, regardless of the legal or equitable theory on which such damages are sought and even if Registry has been advised of the possibility of such damages. |
| 179 | 185 | |
| 186 | 4.4.2 Registry's total cumulative liability to a User for any and all claims arising out of or related to these Policies or Registry's services, whether in contract, tort (including negligence), statute, or otherwise, shall not exceed the greater of (a) the aggregate fees earned and received by Registry (whether directly or through a Registrar) attributable to the Registrations of the User giving rise to the claim during the twelve (12) months preceding the event giving rise to liability, or (b) one hundred U.S. dollars (US$100). |
| 187 | |
| 188 | 4.4.3 Some jurisdictions do not allow the exclusion or limitation of certain damages or liability, and in such jurisdictions the foregoing exclusions and limitations shall apply to the maximum extent permitted by applicable law. |
| 189 | |
| 190 | 4.4.4 This Section 4.4 does not limit or exclude (i) Registry's obligation to pay arbitration filing, administrative, or arbitrator fees as required by Section 4.7 or by applicable law or arbitration provider rules; (ii) liability for fraud, fraudulent misrepresentation, or willful misconduct; (iii) liability that cannot be excluded or limited under applicable law; or (iv) the parties' respective obligations under Section 4.5 (Indemnification). |
| 191 | |
| 180 | 192 | ### 4.5 Indemnification |
| 181 | 193 | |
| 182 | 194 | Users agree to indemnify, defend, and hold harmless Registry, its affiliates, officers, directors, employees, agents, and contractors from and against any claims, losses, damages, liabilities, costs, or expenses (including reasonable attorneys' fees) arising out of or related to: |
| 183 | 195 | |
| 184 | 196 | - Their use or misuse of a Name or Registry's services; |
| 185 | 197 | - Any breach of these Policies, including representations and warranties under Section 2.5; |
| 186 | 198 | - Any violation of applicable laws or third-party rights (e.g., intellectual property or privacy rights); |
| 187 | | - Disputes involving a Name, including those resolved under ICANN policies such as UDRP or URS. |
| 199 | - Disputes involving a Name, including those resolved under ICANN policies such as UDRP or URS (if applicable). |
| 188 | 200 | |
| 189 | 201 | This indemnification obligation: (a) shall not apply to the extent the obligation arose from the gross negligence or willful misconduct of Registry and (b) survives the termination or expiration of a Registration or the User's relationship with Registry. |
| 190 | 202 | |
| 191 | 203 | ### 4.6 Governing Law and Disputes |
| 192 | 204 | |
| 193 | 205 | These Terms and the Policies shall be governed by and construed in accordance with the laws of the State of Nevada, United States, without regard to its conflict of law principles. Except to the extent covered under the Arbitration Agreement contained in Section 4.7, any legal action or proceeding arising out of or related to these Terms shall be brought exclusively in the state or federal courts located in Clark County, Nevada. Users irrevocably submit to the jurisdiction and venue of such courts. |
| 194 | 206 | |
| 195 | 207 | ### 4.7 ARBITRATION & CLASS ACTION WAIVER |
| 196 | 208 | |
| 197 | | 4.7.1 As used in this section, **"Agreement to Arbitrate"** means the terms and conditions of this section of these Terms. |
| 209 | 4.7.1 **Definitions and Scope.** As used in this Section 4.7 (this "**Agreement to Arbitrate**"): "**User**" or "**you**" means the registrant or other person bound by these Terms; "**Registry**" or "**we**" means 8 Inc. and its affiliates, officers, directors, employees, agents, predecessors, successors, and assigns; and "**Dispute**" means any and all disputes, claims, or controversies, whether based in contract, tort, statute, regulation, fraud, misrepresentation, or any other legal or equitable theory, that have arisen or may arise between you and us, whether or not such Dispute involves a third party, relating in any way to any aspect of our relationship or any contact between us, direct or indirect, or arising out of or relating to this or any prior or subsequent version of these Terms, the registration, use, transfer, suspension, or deletion of any domain name, your use of or access to our registry services or any related services, or any data we collect or maintain about you or your domains. "Dispute" shall be construed as broadly as permitted by law; provided, however, that "Dispute" does not include (a) disputes subject to mandatory administrative proceedings under ICANN consensus policies (including the UDRP and URS) or any equivalent policies adopted by the Registry, which shall be resolved exclusively through such proceedings, or (b) either party's right to seek temporary or preliminary injunctive relief in a court of competent jurisdiction to prevent the actual or threatened infringement, misappropriation, or violation of intellectual property rights or to enforce confidentiality obligations. |
| 198 | 210 | |
| 199 | | 4.7.2 User (also referred to herein as "you") and Registry (also referred to herein as "we") each agree to resolve exclusively through final and binding arbitration any and all disputes or claims that have arisen or may arise between you and us (including any affiliates, officers, directors, employees, and agents), whether or not such dispute or claim involves a third party, relating in any way to any aspect of our relationship or any contact between us, direct or indirect, or arising out of this or previous versions of these Terms, or your use of or access to our registry services or other services (**"Dispute"**). |
| 211 | 4.7.2 **Agreement to Arbitrate; Bilateral Arbitration Required.** You and we each agree that, except as expressly set forth in Section 4.7.1, any Dispute shall be resolved exclusively through final and binding individual arbitration. Each Dispute shall proceed as a bilateral arbitration between a single User and Registry, conducted on an individualized basis. Nothing in this Agreement to Arbitrate authorizes class arbitration, mass arbitration as a unitary proceeding, representative arbitration, private attorney general arbitration, or the consolidation of claims of separate Users into a single proceeding except as expressly provided in Section 4.7.6 (Coordinated Filings). |
| 200 | 212 | |
| 201 | | 4.7.3 You and we agree as follows: |
| 213 | 4.7.3 **Mandatory Pre-Arbitration Notice and Informal Dispute Resolution.** |
| 202 | 214 | |
| 203 | | - (a) To submit the Dispute to a single arbitrator under the then-current Commercial Arbitration Rules of the American Arbitration Association (AAA), including when applicable the Optional Rules for Emergency Measures of Protection and the Consumer Arbitration Rules, or, by separate mutual agreement, at another arbitration institution. The AAA's rules, information regarding initiating a claim, and a description of the arbitration process are available at www.adr.org. The location of the arbitration and the allocation of fees and costs for such arbitration shall be determined in accordance with the AAA rules. As an alternative, you or we may bring a claim in your local "small claims" court, if permitted by that small claims court's rules. |
| 204 | | - (b) The Federal Arbitration Act governs the interpretation and enforcement of this Agreement to Arbitrate, and the arbitrability of the Dispute. The arbitrator will decide whether the Dispute can be arbitrated. |
| 205 | | - (c) You and we agree that each of us may bring a Dispute against the other only on our own behalf, and not on behalf of a government official or other person or entity, or a class of persons or entities. You and we agree, if we are a party to the proceeding, not to participate in a class action, a class-wide arbitration, a claim brought in a private attorney general or representative capacity, or a consolidated claim involving another person's use of the site or our services. You and we agree not to combine a claim that is subject to arbitration under these Terms with a claim that is not eligible for arbitration under these Terms. You and we agree to waive the right to a trial by jury for all disputes. |
| 206 | | - (d) If the prohibition against class actions and other claims brought on behalf of third parties contained in this provision is found to be unenforceable, then all of this provision will be null and void as to that Dispute. |
| 207 | | - (e) This Agreement to Arbitrate will survive the termination of your relationship with us. |
| 215 | (a) Condition Precedent. As a condition precedent to initiating arbitration or any other proceeding against Registry, you must first comply with the informal dispute resolution procedures set forth in this Section 4.7.3. Compliance with these procedures is essential so that you and Registry have a meaningful opportunity to resolve Disputes informally without incurring the costs of arbitration. |
| 208 | 216 | |
| 209 | | 4.7.4 To the extent permitted under applicable law, all aspects of the arbitration proceeding, and any ruling, decision, or award by the arbitrator, will be strictly confidential for the benefit of all parties. |
| 217 | (b) Individualized Notice of Dispute. You must deliver to Registry a written Notice of Dispute that contains, at a minimum: (i) your full legal name, current mailing address, telephone number, and the email address associated with your registrant account; (ii) the specific domain name(s) at issue; (iii) a clear description of the nature and factual basis of the Dispute, written in your own words and specific to your individual circumstances; (iv) the specific relief you seek, including any monetary amount; (v) your personal signature (electronic signatures acceptable); and (vi) if you are represented by counsel, the name and contact information of your counsel and counsel's signature. The Notice of Dispute must be delivered by email to legal\[at\]gen.xyz, with the subject line "Notice of Dispute," or by certified mail to Registry's registered agent on file with the Secretary of State of the State of Nevada. Form notices, mass-generated notices, and notices that do not contain individualized facts specific to your Dispute do not satisfy this requirement. |
| 210 | 218 | |
| 211 | | 4.7.5 Unless you and we agree otherwise, if the Agreement to Arbitrate is found by a court to be unenforceable, if your claim is not covered by the Agreement to Arbitrate, or if you neither are a resident of nor have a principal place of business in the US, you agree that any Dispute that has arisen, or may arise, between you and us must be resolved exclusively by a state or federal court located in Clark County, Nevada. You and we agree to submit to personal jurisdiction in such court. |
| 219 | (c) Sixty-Day Negotiation Period. For sixty (60) calendar days following Registry's receipt of a complete Notice of Dispute, you and Registry shall engage in good-faith negotiations to resolve the Dispute. During this period, either party may request, and the other party shall participate in good faith in, a single telephonic or video informal settlement conference of reasonable duration, at which each party shall be represented by a person with authority to settle the Dispute. |
| 212 | 220 | |
| 213 | | 4.7.6 Notwithstanding any provision in these Terms to the contrary, you and we agree that if we make a change to this Agreement to Arbitrate (other than a change to the notice address or the site link provided herein) in the future, that change shall not apply to a claim that was filed in a legal proceeding between you and us prior to the effective date of the change. The change shall apply to all other disputes or claims governed by the Agreement to Arbitrate that have arisen, or may arise, between you and us. We will notify you of a change to this Agreement to Arbitrate by posting the amended terms on the Site at least 30 days before the effective date of the change. |
| 221 | (d) Tolling. All applicable statutes of limitation and contractual limitation periods shall be tolled from the date Registry receives a complete Notice of Dispute through the conclusion of the informal dispute resolution period. |
| 214 | 222 | |
| 215 | | 4.7.7 You may opt out of this Agreement to Arbitrate. If you do so, neither you nor we can require the other to participate in an arbitration proceeding. To opt out, you must notify us in writing within 30 days of the date that you first became subject to this arbitration provision. Notice must be provided through the contact form maintained on the website for the relevant SLD (as provided for above hereto) with the subject line "Arbitration Opt-Out." |
| 223 | (e) Enforcement. Compliance with this Section 4.7.3 is a condition precedent to the filing of any arbitration demand. The party initiating arbitration must include with the demand a written certification, signed personally by the User and by counsel (if any), confirming compliance with each requirement of this Section 4.7.3. If a court or arbitrator determines that an arbitration was filed without compliance with this Section 4.7.3, the court or arbitrator may, in addition to any other available remedy, enjoin the prosecution of the arbitration and stay any obligation of Registry to pay arbitration fees with respect to that demand pending compliance. A failure to comply with this Section 4.7.3 may be raised as a defense in any subsequent proceeding. The right to enforce this Section 4.7.3 is essential to the bargain reflected in these Terms and is not subject to waiver by the arbitrator. |
| 216 | 224 | |
| 225 | 4.7.4 **Arbitration Provider and Rules.** |
| 226 | |
| 227 | (a) Primary Provider. Arbitrations under this Agreement to Arbitrate shall be administered by JAMS in accordance with the JAMS Comprehensive Arbitration Rules and Procedures (or, where applicable based on the amount in controversy, the JAMS Streamlined Arbitration Rules and Procedures), and, where the threshold in Section 4.7.6 is met, the JAMS Mass Arbitration Procedures and Guidelines, each as in effect at the time the arbitration is commenced. The parties expressly adopt and incorporate the JAMS Mass Arbitration Procedures and Guidelines for purposes of any Coordinated Filing. The JAMS rules and a description of the arbitration process are available at [www.jamsadr.com](https://www.jamsadr.com/). |
| 228 | |
| 229 | (b) Fallback Providers. If JAMS declines to administer the arbitration, is unavailable, or ceases to exist at the time arbitration is commenced, the parties shall instead arbitrate before the American Arbitration Association ("**AAA**") under its then-current Consumer Arbitration Rules and, where applicable, its Mass Arbitration Supplementary Rules. The AAA's rules are available at [www.adr.org](https://www.adr.org/). If neither JAMS nor AAA is available to administer the arbitration, the parties shall instead arbitrate before National Arbitration and Mediation ("**NAM**") under its then-current Comprehensive Dispute Resolution Rules and Procedures and, where applicable, its Mass Filing Supplemental Dispute Resolution Rules and Procedures. NAM's rules are available at [www.namadr.com](https://www.namadr.com/). If none of JAMS, AAA, or NAM is available, the parties shall mutually select a comparable, neutral arbitration provider; if they cannot agree within thirty (30) days, either party may petition a court of competent jurisdiction to appoint a substitute provider, and the unavailability of any particular provider shall not render this Agreement to Arbitrate unenforceable. |
| 230 | |
| 231 | (c) Single Arbitrator. Each arbitration shall be heard by a single neutral arbitrator selected in accordance with the applicable provider's rules, which afford each party meaningful participation in arbitrator selection. |
| 232 | |
| 233 | (d) Location, Format, and Fees. Hearings shall be conducted by videoconference unless the User and Registry agree otherwise or the arbitrator orders an in-person hearing for good cause, in which case the location shall be determined under the applicable provider's rules. Allocation of filing, administrative, and arbitrator fees shall be governed by the applicable provider's rules and any applicable consumer due-process protocols; provided that in no event shall fees exceed what would be required to render this Agreement to Arbitrate enforceable under applicable law. |
| 234 | |
| 235 | (e) Small Claims Alternative. As an alternative to arbitration, either party may bring an individual claim within the jurisdictional limits of, and in accordance with the rules of, a small claims court of competent jurisdiction. |
| 236 | |
| 237 | 4.7.5 **Claimant Verification Requirements.** Each demand for arbitration filed with the applicable provider must include, in addition to any requirements of the provider's rules: (a) the User's full legal name and the registered email address and account identifier associated with each domain registration giving rise to the claim; (b) a description of the specific domain registration(s) and transactions on which the claim is based, with sufficient particularity to permit Registry to identify the User in its records; (c) documentary evidence reasonably establishing that the User is a party to these Terms (such as a registration confirmation, account screenshot, or registrar confirmation); (d) a sworn declaration, signed by the User personally under penalty of perjury, attesting that the User has read the demand, the factual allegations are true and correct to the best of the User's knowledge, the User personally authorized the filing of the demand, and the User has complied with Section 4.7.3; and (e) if the User is represented by counsel, a written certification by counsel, subject to standards equivalent to Federal Rule of Civil Procedure 11, that counsel has personally communicated with the User, verified the User's identity and the existence of an agreement to these Terms, and confirmed the factual basis for each claim asserted. Demands that do not satisfy this Section 4.7.5 are not properly filed, and Registry shall have no obligation to pay any filing, administrative, or arbitrator fee with respect to such demands until the deficiencies are cured. |
| 238 | |
| 239 | 4.7.6 **Coordinated Filings (Batching Procedure).** |
| 240 | |
| 241 | (a) Trigger. This Section 4.7.6 applies whenever twenty-five (25) or more demands for arbitration that raise substantially similar claims against Registry are filed by, on behalf of, or with the assistance, coordination, or cooperation of the same counsel, group of counsel, or coordinated group of counsel within any sixty (60)-day period (a **"Coordinated Filing"**). Whether claims are "substantially similar" and whether counsel are "coordinated" shall be determined by the Process Administrator (or equivalent neutral) appointed under the applicable provider's rules. |
| 242 | |
| 243 | (b) Batching Into Tranches. All demands within a Coordinated Filing shall be organized into sequential batches of no more than fifty (50) demands each (each a "**Batch**"). Batches shall be selected by random draw, with each side entitled to designate a small, equal number of demands within each Batch. Each Batch shall be administered separately, with claims within a Batch heard by a single arbitrator assigned to that Batch (different arbitrators may preside over different Batches). The arbitrator for each Batch shall decide each demand on its individual merits. |
| 244 | |
| 245 | (c) No Precedential Effect. No award, ruling, or finding in any Batch shall have any preclusive, precedential, or binding effect on any User who is not a party to that Batch. Each User retains the full right to present their own evidence, arguments, and theories in their own proceeding. |
| 246 | |
| 247 | (d) Tolling and Sequencing. Statutes of limitation shall be tolled for all Users in queued Batches from the date the Coordinated Filing trigger is met until thirty (30) days after the User's Batch concludes. Batches shall proceed in reasonable sequence, with subsequent Batches commencing not later than ninety (90) days after the prior Batch is fully concluded, subject to provider scheduling. |
| 248 | |
| 249 | (e) Mediation After First Batches. Following the conclusion of the first two Batches, the parties shall participate in a global mediation administered by the applicable provider, lasting at least one full day, in a good-faith effort to resolve all remaining demands. If mediation does not resolve all remaining demands, Batches shall continue to proceed under this Section 4.7.6. |
| 250 | |
| 251 | (f) Delay Opt-Out. If a User's demand has not been assigned to a Batch and commenced on the merits within twenty-four (24) months after the date the Coordinated Filing trigger is met, the User may, at the User's sole option exercised by written notice, (i) withdraw the arbitration demand and pursue the claim in a court of competent jurisdiction in accordance with Section 4.7.9 (with the statute of limitations remaining tolled until thirty (30) days after such withdrawal), or (ii) require that the User's individual demand proceed to arbitration without further batching delay. |
| 252 | |
| 253 | (g) Mass-Arbitration Opt-Out. Within thirty (30) days after the Process Administrator determines that a Coordinated Filing exists and the User receives notice of that determination, the User may opt out of arbitration of the User's individual claim and instead pursue that claim in a court of competent jurisdiction in accordance with Section 4.7.9. To opt out, the User must provide written notice by email to legal\[at\]gen.xyz with the subject line "Coordinated Filing Opt-Out." |
| 254 | |
| 255 | (h) Mutuality. The procedures in this Section 4.7.6 apply equally to claims by Registry against multiple Users, to the extent such circumstances arise. |
| 256 | |
| 257 | 4.7.7 **Class, Representative, and Coordinated Action Waiver.** You and we each agree that any Dispute may be brought only in the party's individual capacity, and not as a plaintiff or class member in any purported class action, collective action, mass action, mass arbitration as a unitary proceeding, consolidated action, or representative proceeding (including any proceeding brought in a private attorney general capacity or on behalf of a government official, agency, or other person). The arbitrator shall have no authority to consolidate the claims of more than one User, to preside over any form of class, collective, mass, or representative arbitration, or to award class, collective, mass, or representative relief, except solely as expressly provided in Section 4.7.6. The arbitrator may award declaratory or injunctive relief only in favor of the individual party seeking relief and only to the extent necessary to provide relief warranted by that party's individual claim. You and we each waive the right to a trial by jury and the right to participate in a class action with respect to all Disputes. |
| 258 | |
| 259 | 4.7.8 **Severability of Mass-Arbitration Provisions.** If Section 4.7.6 (Coordinated Filings) is found by a court or arbitrator of competent jurisdiction to be unenforceable in whole or in part, that finding shall not invalidate the remainder of this Agreement to Arbitrate, including without limitation Section 4.7.2 (bilateral arbitration), Section 4.7.3 (informal dispute resolution), Section 4.7.4 (provider and rules), Section 4.7.5 (verification), and Section 4.7.7 (class waiver), each of which shall remain in full force and effect to the maximum extent permitted by law. If the prohibition on class actions in Section 4.7.7 is found to be unenforceable as to a particular Dispute, then that Dispute (and only that Dispute) shall be severed from this Agreement to Arbitrate and resolved in accordance with Section 4.7.9; the remainder of this Agreement to Arbitrate shall remain in full force and effect as to all other Disputes. |
| 260 | |
| 261 | 4.7.9 **Court Proceedings; Governing Law.** The Federal Arbitration Act, 9 U.S.C. § 1 et seq., governs the interpretation and enforcement of this Agreement to Arbitrate. Subject to the FAA, these Terms and any non-arbitrable Dispute shall be governed by the laws of the State of Nevada, without regard to its conflict-of-laws principles. The arbitrator shall decide all questions of arbitrability and the scope, applicability, formation, validity, and enforceability of this Agreement to Arbitrate, except that a court (and not an arbitrator) shall decide (i) whether a particular Dispute is subject to Section 4.7.1's exceptions and (ii) the enforceability of Section 4.7.7 (class waiver). If this Agreement to Arbitrate is found unenforceable as to a particular Dispute, if the Dispute is excluded from arbitration, if a User has timely opted out under Section 4.7.6(g) or 4.7.10, or if the User neither resides nor has a principal place of business in the United States and arbitration is not available, the Dispute shall be resolved exclusively by a state or federal court located in Clark County, Nevada, and you and we each consent to the personal jurisdiction of such courts and waive any objection based on inconvenient forum. |
| 262 | |
| 263 | 4.7.10 **Right to Opt Out of Arbitration.** You may opt out of this Agreement to Arbitrate. To opt out, you must provide written notice within thirty (30) days of the date you first became subject to this Agreement to Arbitrate (or, in the case of a material amendment to this Agreement to Arbitrate, within thirty (30) days of the effective date of that amendment, but only as to amended terms). Notice must be provided via email to legal\[at\]gen.xyz with the subject line "Arbitration Opt-Out" and must include your full legal name, registered email address, and, if applicable, the domain name(s) registered. A timely and valid opt-out is effective only with respect to the User submitting it and does not affect any other person. |
| 264 | |
| 265 | 4.7.11 **Confidentiality.** To the extent permitted by applicable law, the parties shall maintain the confidentiality of the existence and content of any arbitration proceeding under this Agreement to Arbitrate, including any award; provided, however, that nothing in this Section 4.7.11 shall prevent a party from (a) communicating with their counsel, accountants, insurers, or immediate family members; (b) participating in or responding to a government investigation or regulatory inquiry; (c) communicating with potential witnesses as reasonably necessary to prepare or present a claim or defense; (d) seeking judicial enforcement, vacatur, or confirmation of an arbitration award; or (e) making any disclosure required by law. |
| 266 | |
| 267 | 4.7.12 **Survival; Amendments.** This Agreement to Arbitrate shall survive the termination, expiration, or rescission of any domain registration or other relationship between you and Registry. Registry may amend this Agreement to Arbitrate from time to time by posting the amended terms on the Site for the relevant SLD. No amendment shall apply (i) to any Dispute as to which an arbitration demand or court proceeding has already been filed, or (ii) retroactively to any Dispute that has already accrued, unless you affirmatively assent to its retroactive application. Continued use of the registry services or maintenance of any domain registration following the effective date of an amendment of which you have received notice shall constitute acceptance of the amended terms as to Disputes accruing thereafter, subject to your right to opt out under Section 4.7.10. |
| 268 | |
| 217 | 269 | ### 4.8 Amendments |
| 218 | 270 | |
| 219 | 271 | Registry may amend these Terms as part of broader Policy updates, as described in Section 1. Changes will be posted on the applicable SLD website with at least thirty (30) days' notice before taking effect, unless immediate action is required for legal or security reasons. Continued submission of Applications or maintenance of Registrations after the effective date of amendments constitutes acceptance of the updated Terms. |
| 220 | 272 | |
| 221 | 273 | ### 4.9 Severability |
| 222 | 274 | |
| 223 | | If any provision of these Terms is found to be invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall remain in full force and effect, and the invalid provision shall be reformed to the extent necessary to make it enforceable while preserving its original intent. |
| 275 | If any provision of these Terms is found to be invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall remain in full force and effect, and the invalid provision shall be reformed to the extent necessary to make it enforceable while preserving its original intent. Notwithstanding the foregoing, severability of provisions in Section 4.7 shall be governed exclusively by Section 4.7.8. |
| 224 | 276 | |
| 225 | 277 | ### 4.10 No Waiver |
| 226 | 278 | |
| 227 | 279 | Registry's failure to enforce any provision of these Terms shall not constitute a waiver of such provision or any other right. Any waiver must be in writing and signed by an authorized representative of Registry to be effective. |
| 228 | 280 | |
| 229 | 281 | ### 4.11 Contact Information |
| 230 | 282 | |
| 231 | 283 | Users may contact Registry with questions or concerns about these Terms via the contact details provided on the applicable SLD website (listed above hereto). |
| 232 | 284 | |
| 233 | 285 | ## Section 5 - Privacy Policy |
| 234 | 286 | |
| 235 | | Last Updated: February 1, 2025 |
| 287 | Last Updated: As of the version date in the footer of the cover page to these Polices. |
| 236 | 288 | |
| 237 | | Registry values the privacy of Registrants and Applicants (collectively, "Users") who engage with our registry services for the SLDs. This Privacy Policy explains how and why we collect, use, and disclose personal information provided to Registry in connection with Applications and Registrations. Personal information includes data such as names, addresses, telephone numbers, email addresses, and other details that could directly or indirectly identify an individual ("Personal Information"). |
| 289 | Registry values the privacy of Registrants and Applicants (collectively, "**Users**") who engage with our registry services for the SLDs. This Privacy Policy explains how and why we collect, use, and disclose personal information provided to Registry in connection with Applications and Registrations. Personal information includes data such as names, addresses, telephone numbers, email addresses, and other details that could directly or indirectly identify an individual ("Personal Information"). |
| 238 | 290 | |
| 239 | 291 | Users are encouraged to review this Privacy Policy carefully. For questions or to exercise your rights as described herein, please contact us through any method indicated in the "Contact Us" page for the relevant SLD website. |
| 240 | 292 | |
| 241 | 293 | ### 5.1 Collection of Personal Information |
| 242 | 294 | |
| 243 | 295 | #### User-Provided Information |
| 244 | 296 | |
| 245 | 297 | Registry collects Personal Information from Users via Registrars when they submit Applications or maintain Registrations for Names in the SLDs. This includes information Users voluntarily provide, such as contact details required for registration. |
| 246 | 298 | |
| 247 | 299 | #### Website Interaction |
| 248 | 300 | |
| 249 | | We may collection information when Users visit an SLD website (listed above hereto). Such use is covered by the Privacy Policy included on such website. |
| 301 | We may collect information when Users visit an SLD website (listed in the cover page hereto). Such use is covered by the Privacy Policy included on such website. |
| 250 | 302 | |
| 251 | 303 | ### 5.2 Domain Name Registration Data |
| 252 | 304 | |
| 253 | 305 | #### Registration Data We Collect |
| 254 | 306 | |
| 255 | 307 | Registry collects data from Registrars necessary to register and manage Names in the SLDs ("Registration Data"), as required by our agreements with ICANN. This data, which Registrars provide on behalf of Users, includes: |
| 304 | 356 | |
| 305 | 357 | ### 5.5 Exceptions to Disclosure Limitations |
| 306 | 358 | |
| 307 | 359 | Registry limits disclosure of Personal Information to the terms of this Privacy Policy, but may disclose it: |
| 308 | 360 | |
| 309 | 361 | - To fulfill a registration-related transaction or provide requested information; |
| 310 | | - In emergencies affecting a User's or another's vital interests; |
| 311 | | - As required by ICANN or applicable law (e.g., court orders, subpoenas); |
| 312 | | - To enforce Section 3 (Acceptable Use and Anti-Abuse Policy) or protect DNS integrity; |
| 313 | | - To defend Registry's rights, property, or safety, or that of Users and the public; |
| 314 | | - To comply with lawful requests from public authorities, including for national security or law enforcement. |
| 362 | - To protect the vital interests of a User or another natural person, including in emergencies; |
| 363 | - If applicable, as required by ICANN consensus policies or applicable law (including court orders, subpoenas, or other legally binding requests); |
| 364 | - To enforce Section 3 (Acceptable Use and Anti-Abuse Policy), to protect the security, integrity, or stability of the SLDs or the Domain Name System, or to investigate suspected abuse; |
| 365 | - To establish, exercise, or defend legal claims, including in litigation, arbitration, or regulatory proceedings involving Registry, its affiliates, or any User; |
| 366 | - To comply with lawful requests from public authorities, including for purposes of national security or law enforcement, where Registry has a good-faith basis to believe disclosure is legally required. |
| 315 | 367 | |
| 316 | 368 | ### 5.6 Information Security and Retention |
| 317 | 369 | |
| 318 | 370 | #### Security Measures |
| 319 | 371 | |
| 320 | 372 | Registry employs physical, electronic, and procedural safeguards to protect Personal Information from unauthorized access, loss, or misuse. While we use industry-standard measures, no system is entirely secure, and we cannot guarantee absolute protection. |
| 321 | 373 | |
| 322 | 374 | #### Retention Periods |
| 323 | 375 | |
| 324 | | - **Registration Data:** Retained for the life of the Registration, plus up to six (6) years post-expiration if needed for legal defense, unless erased earlier per User request (see the Data Subject Rights subsection below). |
| 325 | | - **Orphaned Contact Data:** Data not tied to active Registrations is purged within ninety (90) days. |
| 326 | | - **Abuse-Related Data:** Retained up to six (6) years. |
| 376 | - **Registration Data:** Registration Data: Retained for the duration of the Registration and for up to six (6) years following expiration, transfer, or cancellation. This retention period reflects the applicable statutes of limitation for contract and tort claims under Nevada law and the survival period for indemnification obligations under Section 4.5, and is necessary to permit Registry to establish, exercise, or defend legal claims, comply with ICANN consensus policy obligations, and respond to law enforcement and regulatory inquiries. Registration Data may be erased earlier upon a verified User request under Section 5.7 (Data Subject Rights), subject to the exceptions stated therein. |
| 377 | - **Orphaned Contact Data:** Personal Information not associated with an active or recently expired Registration is purged within ninety (90) days of becoming orphaned. |
| 378 | - **Abuse-Related Data:** Data relating to suspected or confirmed violations of Section 3 (Acceptable Use and Anti-Abuse Policy) is retained for up to six (6) years following the conclusion of the relevant investigation or enforcement action. This retention period reflects the applicable statutes of limitation for fraud, computer-misuse, and intellectual property claims under U.S. and applicable foreign law, and is necessary to support cooperation with law enforcement, regulatory authorities, and affected third parties. |
| 379 | - **Operational Logs and Security Data:** Access logs, authentication records, and security event data are retained for up to twenty-four (24) months for the purposes of security monitoring, incident response, and investigation of suspected abuse. |
| 380 | - **Legal Hold:** Notwithstanding the foregoing, Registry may retain Personal Information for longer periods where required to comply with a legal obligation, court order, regulatory requirement, or pending or anticipated legal proceeding. |
| 327 | 381 | |
| 328 | 382 | ### 5.7 Data Subject Rights |
| 329 | 383 | |
| 384 | The following data subject rights apply to the extent required under applicable law for the respective data subject. |
| 385 | |
| 330 | 386 | #### Access and Rectification |
| 331 | 387 | |
| 332 | 388 | Users may request confirmation of whether Registry processes their Personal Information and, if so, access details such as categories of data, recipients, and retention periods. To correct inaccurate data, Users should first contact their Registrar to update Registration Data, which will sync with Registry's systems. If unable to do so, Users may contact Registry directly through the contact methods provided in the Contact Us page for the relevant SLD website, and we will rectify verified inaccuracies. |
| 333 | 389 | |
| 334 | 390 | #### Erasure |
| 335 | 391 | |
| 336 | 392 | Users may request erasure of their Personal Information if: |
| 337 | 393 | |
| 338 | 394 | - It is no longer needed for its original purpose; |
| 339 | | - They withdraw consent (where applicable); |
| 395 | - They withdraw consent (where consent was the lawful basis for processing); |
| 340 | 396 | - They object to processing without overriding legitimate grounds; |
| 341 | 397 | - It was unlawfully processed; or |
| 342 | 398 | - Erasure is legally required. |
| 343 | 399 | |
| 344 | | Registry will comply unless an exception applies (e.g., legal obligations). |
| 400 | Registry will respond to verified erasure requests without undue delay and in any event within thirty (30) days of receipt, except that Registry may extend this period by up to sixty (60) additional days where necessary due to the complexity or volume of requests, in which case Registry will inform the User of the extension and the reasons within the initial thirty (30)-day period. Registry will not honor erasure requests until the User's identity has been reasonably verified through the contact methods provided in the Contact Us page for the relevant SLD website. Registry may decline to erase Personal Information where retention is necessary (a) to comply with a legal obligation; (b) to establish, exercise, or defend legal claims; (c) for archiving purposes in the public interest; (d) to maintain the integrity, security, or stability of the SLDs or the Domain Name System; or (e) where the data relates to a Name involved in a pending or recently concluded abuse investigation, dispute, or enforcement action. |
| 345 | 401 | |
| 402 | #### Restriction of Processing |
| 403 | |
| 404 | Users may request that Registry restrict the processing of their Personal Information where (a) the User contests the accuracy of the data, for a period enabling Registry to verify accuracy; (b) the processing is unlawful and the User opposes erasure; (c) Registry no longer needs the data but the User requires it for legal claims; or (d) the User has objected to processing pending verification of overriding legitimate grounds. Where processing is restricted, Registry will continue to store the data but will not otherwise process it except with the User's consent or for the establishment, exercise, or defense of legal claims. |
| 405 | |
| 406 | #### Right to Object |
| 407 | |
| 408 | Users may object at any time to Registry's processing of their Personal Information based on legitimate interests. Registry will cease such processing unless it demonstrates compelling legitimate grounds that override the User's interests, rights, and freedoms, or unless the processing is necessary for the establishment, exercise, or defense of legal claims. Users may also object to processing for direct marketing purposes at any time, in which case Registry will cease such processing. |
| 409 | |
| 410 | #### Non-Discrimination |
| 411 | |
| 412 | Registry will not deny services, charge different prices, or provide a different level or quality of service to a User solely because the User has exercised any right described in this Section 5.7, except where the difference is reasonably related to the value provided by the User's data or as otherwise permitted by applicable law. |
| 413 | |
| 414 | #### Authorized Agents |
| 415 | |
| 416 | A User may designate an authorized agent to submit requests under this Section 5.7 on the User's behalf. Registry may require (a) written authorization from the User; (b) verification of the agent's identity; and (c) direct verification of the User's identity and confirmation of the User's authorization, before acting on any request submitted by an authorized agent. |
| 417 | |
| 418 | #### How to Exercise Rights |
| 419 | |
| 420 | To exercise any right described in this Section 5.7, contact Registry through the contact methods provided in the Contact Us page for the relevant SLD website. Registry will not discriminate against Users for exercising any right under this Section 5.7. There is no fee for submitting a request, except that Registry may charge a reasonable fee or refuse to act on requests that are manifestly unfounded, excessive, or repetitive, in which case Registry will explain the basis for the fee or refusal. |
| 421 | |
| 346 | 422 | #### Portability |
| 347 | 423 | |
| 348 | 424 | If Registry ceases to operate an SLD, this data may be transferred to another registry operator to ensure DNS continuity. |
| 349 | 425 | |
| 350 | 426 | #### EEA, Swiss, and UK Residents |
| 351 | 427 | |
| 352 | | For Users in these regions, Registry transfers data to the U.S. in compliance with the EU-U.S. Data Privacy Framework (DPF), UK Extension to the EU-U.S. DPF, and Swiss-U.S. DPF, certified by the U.S. Department of Commerce. See https://www.dataprivacyframework.gov/ for details. Users may contact Registry directly through the contact methods provided in the Contact Us page for the relevant SLD website for complaints, with unresolved issues referred to BBB DPF Services (https://bbbprograms.org/programs/all-programs/dpf-consumers/). |
| 428 | For Users in the European Economic Area, Switzerland, and the United Kingdom, Registry transfers Personal Information to the United States in reliance on the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and the Swiss-U.S. Data Privacy Framework (collectively, the "DPF"), as administered by the U.S. Department of Commerce. Registry's certification status and additional information are available at [https://www.dataprivacyframework.gov/](https://www.dataprivacyframework.gov/). |
| 353 | 429 | |
| 430 | In the event that the DPF or any component thereof is invalidated, suspended, or otherwise becomes unavailable as a lawful basis for transfer, Registry will transfer Personal Information on the basis of (a) Standard Contractual Clauses approved by the European Commission, the UK Information Commissioner's Office, or the Swiss Federal Data Protection and Information Commissioner, as applicable; (b) binding corporate rules; (c) any other transfer mechanism recognized as adequate under applicable law; or (d) a derogation expressly permitted under Article 49 of the GDPR or its UK or Swiss equivalents. Registry will implement supplementary measures where necessary to ensure that transferred data receives an essentially equivalent level of protection to that provided in the originating jurisdiction. |
| 431 | |
| 432 | Users may direct complaints relating to Registry's handling of Personal Information to Registry through the contact methods provided in the Contact Us page for the relevant SLD website. |
| 433 | |
| 354 | 434 | ### 5.8 Changes to This Privacy Policy |
| 355 | 435 | |
| 356 | 436 | Registry may update this Privacy Policy periodically. Updates will be posted on SLD websites (listed above hereto) with at least thirty (30) days' notice, unless immediate changes are required. Continued use of Registry's services after the effective date constitutes acceptance of the revised Privacy Policy. |
| 357 | 437 | |
| 358 | 438 | ### 5.9 Contact Us |
| 359 | 439 | |