This Uniform Rapid Suspension System ("URS") Policy explains how the URS applies to domain names sponsored by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") where the relevant top-level domain is subject to the URS.

1. Purpose and Scope

The URS is an ICANN rights-protection mechanism intended for clear cases of trademark abuse involving domain names in top-level domains to which the URS applies.

The URS complements, but does not replace, the Uniform Domain Name Dispute Resolution Policy ("UDRP"), court proceedings, or any other dispute-resolution procedure that may apply to a domain name.

NiceNIC does not determine the merits of a URS complaint. URS complaints are decided by an ICANN-approved URS Provider in accordance with the then-current URS Procedure, URS Rules, provider supplemental rules, and applicable ICANN requirements.

2. Official ICANN URS Procedure Incorporated

For each domain name subject to the URS, the then-current ICANN URS Procedure, URS Rules, and applicable technical requirements are incorporated into the relevant registration agreement by reference.

Official ICANN URS information:

https://www.icann.org/en/contracted-parties/registry-operators/services/rights-protection-mechanisms-and-dispute-resolution-procedures/urs

If this NiceNIC Policy conflicts with a mandatory provision of the then-current ICANN URS Procedure, URS Rules, applicable registry agreement, or other binding ICANN requirement, the mandatory provision controls.

3. When the URS Applies

The URS applies only where the relevant registry agreement, ICANN requirement, or other applicable rule makes the URS available for the domain name concerned.

The URS does not automatically apply to every country-code top-level domain ("ccTLD"). A ccTLD may instead use its own dispute-resolution policy.

Customers should review the applicable registry rules for the relevant TLD.

4. Filing a URS Complaint

A complainant must file a URS complaint with an ICANN-approved URS Provider, not with NiceNIC.

The complainant is responsible for:

• selecting an approved URS Provider;
• complying with the provider's filing requirements;
• paying applicable provider fees;
• establishing the elements required by the URS; and
• providing the evidence required by the applicable URS Procedure and Rules.

NiceNIC customer support and abuse channels are not substitutes for filing a URS complaint.

A trademark complaint submitted to NiceNIC does not automatically become a URS proceeding.

5. URS Providers

The list of ICANN-approved URS Providers may change.

Customers and complainants should rely on ICANN's current URS page for the official list of approved providers:

https://www.icann.org/en/contracted-parties/registry-operators/services/rights-protection-mechanisms-and-dispute-resolution-procedures/urs

6. Registration Data

Where Registration Data is redacted from public RDDS output, NiceNIC will provide Registration Data to the URS Provider only to the extent and through the mechanism required or permitted by the then-current URS Procedure, ICANN Registration Data Policy, applicable registry requirements, and applicable law.

Submission of non-public Registration Data in a URS proceeding does not create a general right for a complainant or other third party to receive NiceNIC customer information outside the URS process.

Requests outside the URS process are handled under NiceNIC's Request for Disclosure of Nonpublic Registration Data policy.

7. Notice and Domain Lock

When NiceNIC receives valid notice of a URS proceeding, NiceNIC will perform the registrar obligations assigned to it by the then-current URS Procedure and Rules.

The applicable Registry Operator is responsible for registry-level locking and other registry actions specified by the URS Procedure.

During a URS lock, changes to the registration may be restricted as required by the URS.

NiceNIC will not knowingly permit a registrant, reseller, account holder, or other person to use NiceNIC systems to evade a valid URS lock or mandatory URS restriction.

8. Registrant Response

The registrant is responsible for responding directly through the URS Provider and within the period specified by the then-current URS Procedure and Rules.

NiceNIC does not prepare a registrant's defense, decide whether a response is sufficient, or provide legal representation.

Failure to respond may result in a default proceeding, but a URS Provider must still apply the URS requirements and examination standards.

9. Burden and Determination

The URS is intended for clear cases meeting the evidentiary standard specified in the URS Procedure.

The URS Examiner, not NiceNIC, determines whether the complainant has established the required elements.

NiceNIC does not make findings concerning trademark ownership, legitimate interests, bad-faith registration, or bad-faith use merely because a URS complaint has been filed.

10. Effect of a Successful URS Complaint

If a final URS Determination requires suspension, the applicable Registry Operator will implement the suspension in accordance with the URS Procedure.

A successful URS proceeding generally results in suspension of the domain name for the applicable period rather than transfer of the domain name to the complainant.

The domain may be prevented from being transferred, deleted, or modified for the period required by the URS.

Any extension, restoration, or other post-determination action is subject to the then-current URS Procedure and Registry Operator requirements.

11. Determination in Favor of the Registrant

If the URS proceeding is determined in favor of the registrant, the applicable Registry Operator and URS Provider are responsible for the actions specified by the URS Procedure to restore or maintain the registrant's control as applicable.

12. Appeal and Other Remedies

Any right of appeal, de novo review, late response after default, or other URS remedy is governed by the then-current URS Procedure and Rules.

The URS does not eliminate rights that may otherwise exist to pursue a UDRP proceeding or a proceeding in a court of competent jurisdiction.

13. UDRP Distinguished

The URS and UDRP are separate dispute mechanisms.

A URS remedy is principally suspension. A UDRP proceeding may provide different remedies where the UDRP applies.

A party seeking legal relief should determine which mechanism is appropriate for its circumstances.

14. Abuse Reports Distinguished

A URS complaint is not the same as an abuse report.

Phishing, malware, botnets, pharming, compromised domains, or other operational abuse should be reported through NiceNIC's abuse-reporting channel:

https://nicenic.com/reportabuse.php

Trademark disputes that do not involve qualifying DNS Abuse are generally handled through the applicable rights-protection mechanism, including URS, UDRP, an applicable ccTLD dispute policy, or a court where appropriate.

15. Court Orders and Other Binding Process

NiceNIC will comply with valid court orders, mandatory registry instructions, ICANN requirements, and other binding legal process applicable to a domain name.

Such obligations may operate independently from a URS proceeding.

16. No Legal Advice

Information provided by NiceNIC concerning the URS is for administrative and service purposes only and is not legal advice.

A party that requires advice concerning trademark rights, defenses, jurisdiction, or litigation should consult qualified legal counsel.

17. Language and Priority

NiceNIC may provide translations or summaries for convenience.

The official English-language ICANN URS documents, as updated from time to time, control to the extent required by ICANN.

For a domain subject to mandatory registry-specific terms, those mandatory terms also apply.

Abuse Reporting & Handling Policy

This Abuse Reporting & Handling Policy describes how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") receives, investigates, tracks, and responds to reports of abuse involving domain names sponsored by NiceNIC or other NiceNIC services.

1. Purpose

NiceNIC is an ICANN-accredited registrar and maintains abuse-reporting and abuse-handling procedures to meet applicable contractual, registry, legal, security, and service obligations.

An abuse report is an allegation or signal requiring review. Submission of a report does not, by itself, establish that a customer or domain has violated NiceNIC policy, ICANN requirements, registry rules, or applicable law.

NiceNIC seeks to handle reports promptly, fairly, based on available evidence, and with measures proportionate to the circumstances.

2. Official Abuse Reporting Channels

Abuse involving a domain name or NiceNIC service should be submitted through one of NiceNIC's official abuse channels:

Online abuse report:
https://nicenic.com/reportabuse.php

Abuse email:
abuse@nicenic.net

The abuse-reporting mechanism is intended to be accessible without requiring the reporter to hold a NiceNIC customer account.

General customer support, social media, forum messages, or unrelated business contacts are not the preferred channels for abuse reports and may be redirected to the official abuse process.

NiceNIC may nevertheless review or act on credible information received through another channel where required by law, appropriate for security, necessary to protect users, or necessary to satisfy ICANN or registry obligations.

3. Information to Include

A report should contain enough information to allow NiceNIC to identify the affected resource and evaluate the allegation.

Depending on the issue, useful information may include:

• the affected domain name;
• the complete abusive URL where applicable;
• the category of alleged abuse;
• a clear description of the activity;
• screenshots;
• full email headers and message content for email-related abuse;
• timestamps and time zone;
• relevant IP addresses;
• security or firewall logs;
• malware, phishing, or threat-intelligence evidence;
• payment receipts or transaction evidence for fraud reports;
• the legitimate brand or service being impersonated where relevant;
• legal documents or rights evidence where relevant; and
• the reporter's contact details for follow-up.

Reporters should avoid submitting unnecessary personal data, passwords, authentication codes, private keys, or unrelated confidential information.

4. Confirmation of Receipt

For reports submitted through the official abuse mechanism, NiceNIC will provide a confirmation of receipt sufficient to identify the submission in accordance with applicable ICANN requirements.

Where required by the applicable Registrar Accreditation Agreement, the confirmation will identify at least:

• NiceNIC as the registrar;
• the reported Registered Name or Registered Names; and
• the date the report was submitted.

A confirmation of receipt is not a determination that the allegation is valid.

5. Initial Review and Classification

NiceNIC may review:

• whether NiceNIC is the sponsoring registrar or relevant service provider;
• whether the reported activity remains active;
• the nature of the allegation;
• the quality and relevance of the evidence;
• whether the issue constitutes DNS Abuse for purposes of NiceNIC's ICANN registrar obligations;
• whether the domain appears to have been maliciously registered or instead appears to be a legitimate domain that has been compromised;
• whether the issue is principally associated with hosting, email, a subdomain, a third-party platform, or another provider;
• whether the report concerns trademark/copyright rights rather than DNS Abuse;
• applicable registry rules;
• applicable law, legal process, or court orders; and
• any other reasonably available information relevant to the investigation.
• 
  

6. DNS Abuse

For gTLDs subject to NiceNIC's ICANN registrar obligations, "DNS Abuse" has the meaning specified by the then-current ICANN Registrar Accreditation Agreement and related ICANN requirements.

As of the Effective Date of this Policy, the contractual DNS Abuse categories are:

• malware;
• botnets;
• phishing;
• pharming; and
• spam when spam serves as a delivery mechanism for one or more of the other specified forms of DNS Abuse.

Other harmful or illegal conduct may still violate NiceNIC policy or applicable law even if it does not fall within the ICANN contractual definition of DNS Abuse.

7. Actionable Evidence and Investigation

NiceNIC will take reasonable and prompt steps to investigate abuse reports as required by applicable registrar obligations.

Evidence is considered in context. A report does not need to use any particular commercial threat feed or reporting format to be considered.

Where information submitted by a reporter is incomplete, NiceNIC may:

• review information reasonably available to NiceNIC;
• request additional relevant evidence;
• inspect the reported URL or other relevant public resource where safe and appropriate;
• review account, nameserver, DNS, registration, or service information available to NiceNIC; or
• contact another relevant service provider or registry where appropriate.

NiceNIC will not require irrelevant evidence merely to delay handling of an otherwise actionable report.

8. Required Mitigation for DNS Abuse

When NiceNIC has actionable evidence that a gTLD Registered Name sponsored by NiceNIC is being used for DNS Abuse, NiceNIC will promptly take mitigation action that is reasonably necessary to stop or otherwise disrupt the Registered Name from being used for that DNS Abuse, as required by the applicable ICANN Registrar Accreditation Agreement.

The appropriate action depends on the circumstances, including:

• the type of DNS Abuse;
• the cause and severity of the harm;
• whether the activity is active;
• whether the domain appears maliciously registered or compromised;
• the technical role of the domain;
• the likely effectiveness of registrar-level action; and
• the risk of collateral damage to legitimate users or services.
• 
  

9. Proportionate Mitigation

Possible actions may include, where appropriate and permitted:

• requesting remediation;
• requiring the customer or reseller to remove or disable the abusive activity;
• applying a registrar lock;
• applying clientHold or another registrar status;
• restricting DNS or other NiceNIC-provided functionality;
• restricting email, hosting, API, or account access;
• referring the matter to the relevant hosting provider, registry, or other infrastructure provider;
• preserving relevant records;
• suspending an affected service;
• terminating a service or account for serious or repeated violations; or
• taking another measure reasonably necessary to address the abuse.

NiceNIC is not required to apply the same mitigation measure in every case.

10. Compromised Domains and Collateral Damage

A legitimate domain may be abused without the registrant's knowledge because of compromised hosting, credentials, content-management software, DNS settings, or another security failure.

Where reasonably practicable, NiceNIC will consider the risk of collateral damage before applying domain-level suspension.

For a compromised legitimate domain, requesting rapid remediation or applying a narrower mitigation may be more appropriate than immediate suspension if the narrower action is sufficient to stop or disrupt the abuse.

This does not prevent immediate suspension or another stronger measure where the circumstances, severity, continuing harm, legal requirements, or security risk justify it.

11. Maliciously Registered Domains

Where available evidence indicates that a domain was registered or is controlled primarily for phishing, malware, credential theft, botnet activity, pharming, or another serious abusive purpose, faster domain-level mitigation may be appropriate.

NiceNIC is not required to provide advance notice where doing so would materially increase the risk of harm, enable evasion, frustrate a mandatory requirement, or undermine effective mitigation.

12. Non-DNS Illegal Activity

Illegal Activity and DNS Abuse are not identical concepts.

Reports concerning fraud, unlawful goods or services, threats, impersonation, illegal content, sanctions, or other conduct may be handled under applicable law, NiceNIC's Terms of Service & Acceptable Use Policy, registry rules, court orders, or other relevant requirements even where the conduct does not meet the ICANN contractual definition of DNS Abuse.

The legal and technical role of NiceNIC will be considered when determining what action, if any, is appropriate.

13. Trademark and Domain-Name Rights Complaints

Trademark infringement or a dispute over rights in a domain name is not automatically DNS Abuse.

Where the principal dispute concerns who has rights to the domain name, the appropriate mechanism may include:

• the Uniform Domain Name Dispute Resolution Policy (UDRP);
• the Uniform Rapid Suspension System (URS);
• a ccTLD-specific dispute policy; or
• a court of competent jurisdiction.

NiceNIC does not decide the merits of UDRP or URS disputes.

If evidence also demonstrates phishing, credential theft, malware, or another form of DNS Abuse, NiceNIC may separately handle the DNS Abuse aspect.

14. Copyright Complaints

Copyright complaints are reviewed separately from DNS Abuse unless the reported activity also involves qualifying DNS Abuse or another basis for registrar-level action.

NiceNIC may request information reasonably necessary to identify the copyrighted work, allegedly infringing material, complainant, authority to act, and other information required by the applicable complaint process.

A copyright complaint does not automatically result in suspension of a domain name.

15. Child Sexual Abuse Material and Child Exploitation

Reports concerning suspected child sexual abuse material or child exploitation are treated as high-risk matters and escalated without unnecessary delay.

NiceNIC may preserve relevant records, restrict an affected service, and cooperate with appropriate authorities, registries, hosting providers, or other relevant entities as required or permitted by law.

Reporters should not unnecessarily copy, download, or redistribute suspected illegal child-abuse material when submitting a report.

16. Hosting and Third-Party Infrastructure

A registrar controls domain-registration functions but may not control the website files, application, mail server, or hosting environment associated with the domain.

Where abusive content is hosted by a third party, reporting the activity to the hosting provider or other infrastructure provider may allow more targeted removal.

NiceNIC may nevertheless take registrar-level action where required or appropriate under applicable obligations.

17. Reseller-Sponsored Customers

A domain may have been purchased through a NiceNIC reseller while NiceNIC remains the sponsoring registrar.

NiceNIC may coordinate with the reseller during an abuse investigation, but delegation to a reseller does not eliminate NiceNIC's applicable ICANN registrar obligations.

NiceNIC may contact the Registered Name Holder or other customer directly where reasonably necessary for abuse mitigation, security, legal compliance, mandatory notices, or protection of registrant rights.

18. Reports from Law Enforcement and Qualifying Authorities

NiceNIC maintains the dedicated abuse point of contact required by the applicable ICANN Registrar Accreditation Agreement for qualifying reports of Illegal Activity from law-enforcement, consumer-protection, quasi-governmental, or other qualifying governmental authorities.

Where the applicable Registrar Accreditation Agreement requires it, a well-founded report submitted through the dedicated authority contact will be reviewed within twenty-four (24) hours by a person empowered to take necessary and appropriate action.

NiceNIC is not required to take action that would contravene applicable law.

NiceNIC may authenticate the identity, authority, jurisdiction, and legal basis of a governmental request where appropriate.

19. Court Orders and Binding Legal Process

NiceNIC may act in response to:

• a valid court order;
• binding governmental process;
• a mandatory registry instruction;
• a UDRP or URS requirement;
• an ICANN contractual requirement; or
• another legal obligation applicable to NiceNIC.

Where legally permitted and appropriate, NiceNIC may seek clarification or legal review of an overbroad, invalid, or unclear request.

20. Notice to the Customer

Where circumstances permit, NiceNIC may notify a customer or reseller of the allegation and provide an opportunity to remediate.

Advance notice may be omitted where:

• immediate mitigation is reasonably necessary;
• evidence indicates an intentionally malicious registration;
• notice could enable evasion or destruction of evidence;
• a court, authority, registry, ICANN requirement, or law restricts notice;
• a serious security or child-safety risk exists; or
• delay would materially increase harm.
• 
  

21. Restoration and Review

Where a domain or service was restricted because of abuse or security concerns, NiceNIC may review a request for restoration after:

• the abusive activity has been removed;
• a compromised website or account has been secured;
• relevant credentials have been reset;
• required security updates have been applied;
• corrected technical information has been provided;
• the original evidence has become outdated or was shown to be incorrect; or
• another appropriate remediation has been completed.

Restoration is not guaranteed where a continuing legal, registry, ICANN, security, dispute, or abuse basis requires the restriction to remain.

22. Customer Review / Appeal

A customer affected by a discretionary NiceNIC abuse action may request review through NiceNIC's support channel.

The request should identify:

• the affected domain or service;
• the relevant NiceNIC case or notice;
• the remediation completed;
• evidence that the reported activity has ceased;
• evidence of compromise where relevant; and
• any information showing that the original report was inaccurate, outdated, or misclassified.

A review request does not suspend a court order, registry requirement, UDRP/URS action, ICANN obligation, or other mandatory restriction.

23. Reporter Follow-Up

NiceNIC may communicate with a reporter to request relevant additional information or confirm that a case has been received or reviewed.

Privacy, security, law, and customer confidentiality may limit the information NiceNIC can disclose concerning:

• internal investigation methods;
• customer identity;
• non-public Registration Data;
• account information;
• law-enforcement communications;
• security controls; or
• specific internal actions.

Absence of detailed disclosure to a reporter does not mean a report was ignored.

24. Duplicate, Automated, or Abusive Reports

NiceNIC may consolidate duplicate reports concerning the same issue.

NiceNIC may apply reasonable controls to abusive, misleading, clearly irrelevant, or technically harmful submissions.

Such controls will not be used to prevent legitimate reporters from submitting abuse reports through the required channel.

25. Recordkeeping

NiceNIC documents the receipt of and response to abuse reports as required by the applicable ICANN Registrar Accreditation Agreement and other applicable obligations.

Records are retained for the period required by the applicable Registrar Accreditation Agreement, subject to applicable law.

NiceNIC may provide required records to ICANN Contractual Compliance upon proper request.

26. Privacy

Personal data submitted in an abuse report is handled under the NiceNIC Privacy Policy and applicable law.

NiceNIC may disclose information where reasonably necessary to investigate abuse, coordinate mitigation, comply with ICANN or registry requirements, protect users or systems, establish or defend legal claims, or comply with law.

27. No Automatic Finding of Liability

A report, registrar restriction, security action, or temporary mitigation measure is not necessarily a final legal finding that the Registered Name Holder committed unlawful conduct.

NiceNIC may take precautionary or contractual action based on the evidence and obligations applicable at the time.

28. Applicable Policies and Priority

This Policy should be read with:

• the NiceNIC Terms of Service & Acceptable Use Policy;
• the Domain Name Registration Service Agreement;
• the NiceNIC Privacy Policy;
• the Domain Transfer Policy;
• UDRP and URS policies where applicable;
• applicable registry policies; and
• applicable law.

Where a mandatory ICANN, registry, court, governmental, or legal requirement conflicts with this Policy, the mandatory requirement controls to the extent of the conflict.

29. Changes

NiceNIC may update this Policy to reflect changes in law, ICANN requirements, registry rules, abuse patterns, security practices, or NiceNIC services.

Changes required by law, ICANN, or a registry may take effect when required.

This Cookie Policy explains how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC", "we", "us") uses cookies and similar technologies on nicenic.com and related NiceNIC web services.

This Policy should be read together with the NiceNIC Privacy Policy.

1. What Are Cookies?

Cookies are small data files that a website may store on or read from a user's browser or device.

Cookies and similar technologies can be used to:

• keep a user signed in;
• maintain a shopping cart or session;
• remember settings;
• protect accounts and prevent fraud;
• measure website performance;
• understand how users interact with a website; or
• support advertising or marketing functions where used and permitted.

Similar technologies may include local storage, pixels, tags, software development kit identifiers, device identifiers, or other browser/device storage or access mechanisms.

2. When Cookie Data Is Personal Data

Whether a cookie or online identifier is personal data depends on the information involved and the surrounding circumstances.

Where cookie, device, analytics, advertising, or similar data can identify or be linked to an identifiable individual, NiceNIC handles that information as personal data in accordance with the NiceNIC Privacy Policy and applicable law.

3. Categories of Cookies

NiceNIC may use the following categories of cookies or similar technologies.

3.1 Strictly Necessary Cookies

These technologies are required for core website and account functions, such as:

• authentication and login;
• maintaining a user session;
• shopping-cart and checkout functions;
• account security;
• fraud prevention;
• load balancing;
• language or essential interface settings;
• remembering privacy choices; and
• protecting forms and transactions.

Disabling strictly necessary cookies may prevent parts of the website, account, checkout, or other services from functioning correctly.

Where applicable law permits, strictly necessary technologies may be used without consent because they are required to provide a service requested by the user or to operate essential site functions.

3.2 Functional Cookies

Functional technologies may remember optional preferences or enable enhanced website features.

Examples may include:

• preferred language;
• region or display preferences;
• saved non-essential interface choices; or
• enhanced customer-support functionality.

Where applicable law requires consent for these technologies, NiceNIC will request the required choice before using them.

3.3 Analytics and Performance Cookies

Analytics and performance technologies may help NiceNIC understand:

• page visits;
• navigation paths;
• referral sources;
• device/browser types;
• page performance;
• technical errors;
• feature usage; and
• aggregated website trends.

NiceNIC uses this information to improve website reliability, usability, content, and service performance.

Where applicable law requires consent before analytics or performance technologies are stored or accessed, NiceNIC will request that consent.

3.4 Advertising and Marketing Cookies

Where NiceNIC uses advertising or marketing technologies, they may be used to:

• measure campaign performance;
• attribute visits or conversions;
• limit repetitive advertising;
• understand whether marketing is relevant; or
• support advertising or remarketing on third-party services.

Advertising or marketing cookies are not required for core NiceNIC account or domain-registration functions.

Where applicable law requires prior consent, NiceNIC will not intentionally activate such technologies for that user until the required consent has been obtained.

4. First-Party and Third-Party Cookies

A first-party cookie is set or read by NiceNIC's website domain.

A third-party cookie or technology may be provided by another service used on the NiceNIC website, such as an analytics, security, payment, customer-support, video, advertising, or other technology provider.

Third-party providers may process information under their own privacy terms in addition to acting as a service provider to NiceNIC.

NiceNIC evaluates third-party services and seeks to use appropriate contractual, privacy, and security safeguards where required.

5. Essential Account and Transaction Technologies

NiceNIC may use cookies or similar storage necessary to:

• authenticate a NiceNIC account;
• maintain a secure session;
• protect login and checkout;
• detect suspicious activity;
• remember a shopping cart;
• complete domain, SSL, email, server, or other transactions;
• prevent cross-site request forgery or other technical attacks; and
• maintain service continuity.

Because these technologies are closely connected to a service requested by the user, blocking them may make the relevant service unavailable or unreliable.

6. Analytics

NiceNIC may use analytics to understand how the site and services perform.

Analytics data may include:

• IP-related information;
• browser and device type;
• approximate region;
• referral source;
• pages or functions accessed;
• date and time;
• session events; and
• technical performance information.

NiceNIC seeks to limit analytics data to what is reasonably necessary for the stated purpose and to apply available privacy settings where appropriate.

7. Advertising and Conversion Measurement

NiceNIC may use conversion or advertising measurement technologies for marketing campaigns where such use is lawful.

Where required by applicable law, these technologies are subject to the user's consent choices.

NiceNIC does not treat refusal of optional advertising cookies as refusal of strictly necessary service communications such as:

• security notices;
• registration verification;
• renewal or expiration notices;
• transfer notices;
• billing/transaction notices;
• abuse/security communications; or
• other communications necessary to provide or protect the service.
• 
  

8. Cookie Consent and Choices

Where applicable law requires consent before NiceNIC stores or accesses a non-essential cookie or similar technology, NiceNIC will provide an appropriate consent or preference mechanism.

Where such a mechanism is presented, users should be able to make choices concerning non-essential categories in accordance with applicable law.

Withdrawing consent does not affect processing that was lawful before withdrawal.

Strictly necessary technologies may continue to operate where they are required to provide the requested service or are otherwise permitted without consent by applicable law.

9. Browser Controls

Most browsers allow users to:

• view stored cookies;
• delete cookies;
• block cookies;
• block third-party cookies; or
• receive warnings concerning certain cookie activity.

Browser settings differ by browser and device.

Blocking all cookies may prevent login, shopping-cart, checkout, security, language, account, or other NiceNIC functions from operating correctly.

10. Similar Technologies and Device Storage

Privacy requirements may apply not only to conventional HTTP cookies but also to other technologies that store information on, or access information from, a user's device.

NiceNIC applies this Policy to comparable technologies where they perform a similar tracking, storage, preference, analytics, advertising, or security function.

11. Retention

Cookie duration varies according to purpose.

Some cookies are session cookies and expire when the browser session ends.

Other cookies are persistent cookies and remain for a defined period unless deleted earlier by the user, NiceNIC, or the relevant provider.

NiceNIC seeks to avoid retaining cookie-derived personal data longer than reasonably necessary for the applicable purpose, subject to security, fraud-prevention, accounting, legal, and other legitimate retention requirements described in the Privacy Policy.

12. Cookie-Level Information

The specific cookie names, providers, purposes, and durations used on the website may change when NiceNIC updates its security, analytics, support, payment, or marketing technologies.

Where NiceNIC operates a cookie-preference or consent-management tool, the current cookie-level information may be provided through that tool.

The cookies and similar technologies used by NiceNIC may change as the website, services, security controls, analytics, or marketing technologies change. Current cookie-level information may be made available through the applicable cookie-preference or consent-management tool.

13. Hong Kong Privacy Requirements

NiceNIC is established in Hong Kong.

Where cookies or similar technologies involve personal data, NiceNIC processes that data in accordance with applicable requirements of the Hong Kong Personal Data (Privacy) Ordinance ("PDPO"), including applicable principles concerning:

• lawful and fair collection;
• notice of purpose;
• data minimization;
• use limitation;
• retention;
• security;
• access and correction; and
• direct marketing.

Where personal data collected through online tracking is used for direct marketing, NiceNIC will comply with applicable direct-marketing requirements.

14. Users in Other Jurisdictions

NiceNIC serves users internationally.

Additional requirements may apply depending on the user's location and the technologies used.

Where applicable law requires prior consent for non-essential cookies or similar tracking technologies, NiceNIC will apply the required consent mechanism.

Where applicable law gives users additional privacy or opt-out rights, those rights are addressed through NiceNIC's Privacy Policy and the applicable website controls.

15. International Processing

Cookie and analytics information may be processed by NiceNIC or its service providers in countries outside the user's location.

Where cross-border data-transfer safeguards are required by applicable law, NiceNIC will use appropriate contractual, organizational, technical, consent-based, or other legally recognized measures.

16. Security and Fraud Prevention

NiceNIC may use device, session, IP-related, or browser information for security, authentication, abuse prevention, and fraud detection.

Security technologies may operate separately from optional marketing or analytics preferences where their use is necessary to protect NiceNIC accounts, transactions, networks, users, or services and is permitted by applicable law.

17. Children

NiceNIC services are intended for persons who have the legal capacity required to enter into the applicable service agreement.

NiceNIC does not intentionally use advertising cookies to profile children where doing so would violate applicable law.

18. Relationship to the Privacy Policy

The NiceNIC Privacy Policy provides additional information concerning:

• personal data collected by NiceNIC;
• purposes of processing;
• recipients;
• international transfers;
• security;
• retention; and
• privacy rights.

If cookie-derived information constitutes personal data, the Privacy Policy applies in addition to this Cookie Policy.

19. Changes to this Cookie Policy

NiceNIC may update this Cookie Policy when:

• technologies change;
• new providers are used;
• cookie purposes change;
• NiceNIC services change; or
• legal or regulatory requirements change.

The "Last Updated" date will identify the most recent version.

Where a change requires renewed consent under applicable law, NiceNIC will request that consent as required.

20. Contact

Questions or privacy requests concerning NiceNIC's use of cookies or similar technologies may be submitted through NiceNIC's official Contact Us or support channels published on nicenic.com.

This Expired Domain Renewal, Redemption, and Auction Policy (the “Policy”) forms part of the NiceNIC Domain Name Registration Service Agreement and applies to domain names registered, renewed, transferred, or maintained through NICENIC INTERNATIONAL GROUP CO., LIMITED (“NiceNIC”). By using NiceNIC’s domain registration services, you acknowledge and agree to this Policy.

1. Scope and Purpose

1.1 This Policy explains the general post-expiration process that may apply to domain names managed through NiceNIC, including expiration, renewal, redemption, expired domain auction, pending delete status, and release of a domain name back to the public registration pool.

1.2 Domain lifecycle timing varies by top-level domain (“TLD”), Registry Operator, registry rules, applicable ICANN requirements, and other governing policies. Not all TLDs follow the same expiration, renewal, redemption, auction, or deletion process.

1.3 Where a mandatory ICANN policy, Registry requirement, court order, or applicable law conflicts with this Policy, the mandatory requirement controls to the extent of the conflict.

1.4 The English-language version of this Policy controls to the extent permitted by applicable law. Any translation is provided for convenience only.

2. Definitions

• “Expiration Date” means the date on which the applicable domain registration term ends.
• “Registrant at Expiration” means the Registered Name Holder immediately before expiration, as that concept is used in applicable ICANN policy.
• “Post-Expiration Renewal Period” means any period after expiration during which renewal may still be available at the applicable renewal fee.
• “Redemption Grace Period” or “RGP” means a post-deletion recovery period, where supported by the applicable Registry, during which a domain may still be restorable for the applicable redemption/restore fee plus any required renewal or other charges.
• “Pending Delete” means the final pre-release registry status, where applicable, during which the domain generally can no longer be renewed, restored, transferred, or modified.
• “Eligible Domain” means an expired domain that is eligible for NiceNIC’s expired-domain auction or closeout process. Not all TLDs or domain names are eligible.
• “Expired Domain Auction” means the auction or sale process that may apply to certain Eligible Domains before final deletion or release.
• 
  

3. Effect of Expiration

3.1 A domain name is registered for a limited term. If it is not renewed by the applicable deadline, it may expire.

3.2 Upon or after expiration, NiceNIC may interrupt or redirect DNS resolution as permitted by applicable policy. A website, email service, DNS-dependent application, or other service associated with the domain may therefore stop functioning immediately or shortly after expiration.

3.3 Following expiration, NiceNIC may restrict DNS changes, contact changes, transfers, account moves, or other domain-management actions in accordance with Registry rules, security requirements, operational processes, and applicable policies.

3.4 Expiration does not mean that the domain immediately becomes available to the public. Depending on the TLD, the domain may pass through one or more stages including post-expiration renewal, auction, redemption, pending delete, and final release.

4. Renewal Notices and Customer Responsibility

4.1 For gTLDs subject to the ICANN Expired Registration Recovery Policy (“ERRP”), NiceNIC will send the renewal and expiration notices required by that policy using the contact information in NiceNIC’s records.

4.2 NiceNIC may also send additional reminders before or after expiration through email, the customer account, or other service channels.

4.3 The Registered Name Holder and Account Holder remain responsible for monitoring expiration dates, maintaining accurate and monitored contact information, maintaining valid payment information where auto-renewal is used, and submitting renewal payment early enough for processing.

4.4 Failure to receive a reminder, invoice, or notice does not extend a Registry deadline or create a right to renew after the applicable renewal or restoration period has ended, except to the extent mandatory policy or law provides otherwise.

4.5 Auto-renewal, where offered and enabled, remains subject to sufficient funds or valid payment, account status, Registry availability, eligibility requirements, and successful processing. Enabling auto-renewal is not a guarantee that a domain will be renewed in every circumstance.

5. Fees

5.1 NiceNIC’s applicable registration, transfer, renewal, post-expiration renewal (if different), and redemption/restore fees are published on the NiceNIC Domain Prices page.

5.2 Fees may differ by TLD, Registry classification, premium status, customer or reseller level, lifecycle status, tax, or mandatory third-party charge.

5.3 A renewal, redemption, or restoration request is not complete until NiceNIC has received all required payment and the applicable Registry or upstream provider has accepted the transaction.

5.4 Fees for successfully completed Registry-level renewal, redemption, or restoration transactions are non-refundable except where required by applicable law or expressly agreed by NiceNIC.

6. Standard Post-Expiration Renewal

6.1 For many gTLDs, an expired domain may remain renewable for a post-expiration period. Under NiceNIC’s standard process, this period is commonly approximately thirty (30) days, but the actual period may be shorter or longer depending on the TLD and Registry.

6.2 During an available post-expiration renewal period, the Registrant at Expiration may generally renew the domain subject to the applicable renewal fee, successful payment, verification, Registry availability, and any auction-related restriction described below.

6.3 NiceNIC does not guarantee that every TLD offers a thirty-day renewal period or that every expired domain remains renewable for the full duration of a general timeline.

7. Expired Domain Auction for Eligible Domains

7.1 Certain expired domain names may enter NiceNIC’s expired-domain auction or closeout process. The auction process applies only to Eligible Domains and does not apply to every TLD or every expired domain.

7.2 Under NiceNIC’s standard expired-domain process, the following general timeline may apply:

• Day 0: The domain expires. Where permitted, the Registrant at Expiration may generally renew during the initial post-expiration period at the applicable renewal fee.
• Around Day 26: An Eligible Domain may enter expired-domain auction. Renewal may still be available unless the domain becomes subject to an auction-related restriction.
• Around Day 31: If there is no active bid or sale-related restriction, recovery may still be possible, but the applicable redemption/restore fee may apply. Once there is an active bid or other binding sale commitment, the Registrant at Expiration may lose the ability to renew or restore through the ordinary recovery process.
• Around Day 37: An unsold Eligible Domain may enter a final closeout auction. If no purchase is pending, recovery may remain possible subject to the domain’s current status and applicable fees.
• Around Day 41: The final closeout phase may end. If the domain has not been sold or otherwise committed, recovery may remain possible for a limited period, subject to Registry rules and the domain’s actual status.
• Around Day 74 and after: The domain may be removed from the customer account and may no longer be renewable or restorable through NiceNIC. Release timing remains controlled by the Registry.

7.3 The dates above describe NiceNIC’s general process for Eligible Domains and are not guaranteed deadlines. Registry rules, TLD-specific lifecycle rules, auction status, technical processing, or mandatory policy may cause a different result.

7.4 Once an Eligible Domain has an active bid, pending purchase, completed sale, or other binding sale commitment, ordinary renewal or restoration rights may be restricted or terminated to the extent permitted by applicable ICANN and Registry requirements.

7.5 Nothing in NiceNIC’s auction process limits a non-waivable renewal or restoration right that the Registrant at Expiration has under mandatory ICANN policy or Registry rules.

8. Redemption Grace Period and Restoration

8.1 If a domain is not renewed during the applicable post-expiration period and the relevant Registry supports restoration after deletion, the domain may enter a Redemption Grace Period.

8.2 For applicable gTLDs, the Registry-level RGP is generally thirty (30) days, subject to the controlling Registry and ICANN requirements.

8.3 During RGP, the domain normally does not resolve and generally cannot be transferred or modified. Restoration, where available, requires the applicable redemption/restore fee, renewal fee, and any mandatory taxes or charges.

8.4 A restoration request remains subject to successful payment, verification, the domain’s actual Registry status, Registry support, and the absence of a completed or binding auction sale where applicable.

9. Pending Delete and Final Release

9.1 If a domain is not renewed or restored within the applicable recovery periods, it may enter Pending Delete where that lifecycle stage is supported by the Registry.

9.2 During Pending Delete, a domain generally cannot be renewed, restored, transferred, or modified.

9.3 For many gTLDs, Pending Delete lasts approximately five (5) days. After that stage, the Registry may delete and release the domain to the public registration pool.

9.4 NiceNIC does not control or guarantee the exact time or date of Registry release, and does not guarantee that the former Registrant at Expiration will be able to re-register the name. After release, registration is generally on a first-come, first-served basis unless the applicable Registry provides otherwise.

10. TLD-Specific Variations

10.1 ccTLDs, sponsored TLDs, restricted TLDs, and some gTLDs may use lifecycle rules materially different from NiceNIC’s standard timeline.

10.2 A TLD may, for example, require renewal before the displayed expiration date, offer a shorter post-expiration period, move directly into a Registry recovery process, omit RGP or Pending Delete, use a different restoration fee, or apply special eligibility or documentation requirements.

10.3 The applicable Registry rules and NiceNIC’s current operational deadline for the TLD control. Customers should renew important domains well before the displayed expiration date and contact NiceNIC Support promptly if a TLD-specific recovery question arises.

10.4 NiceNIC may publish TLD-specific help information for convenience. Such information may change when the Registry changes its lifecycle or operational procedures.

11. Transfers of Expired Domains

11.1 Expiration alone does not authorize NiceNIC to deny a gTLD inter-registrar transfer where the ICANN Transfer Policy requires the transfer to be permitted.

11.2 A transfer may nevertheless be unavailable or denied where another permitted or required transfer restriction applies, including applicable Registry status, a policy-based lock, dispute proceeding, court order, security restriction, or another ground allowed by the then-current ICANN Transfer Policy.

11.3 Customers should initiate transfers sufficiently before expiration because a transfer may require unlocking, an AuthInfo code, authentication, payment, and Registry processing.

12. Renewal or Restoration After Expiration

12.1 A successful post-expiration renewal or restoration returns the domain to the applicable active registration state subject to Registry processing and DNS propagation.

12.2 NiceNIC does not guarantee that websites, email, DNS, certificates, hosting, or third-party services will resume immediately after renewal or restoration.

12.3 Any separate hosting, email, SSL, or other product that expired or was terminated is governed by its own service terms and may require separate reactivation.

13. No Guarantee of Recovery

13.1 NiceNIC does not guarantee that an expired domain can be renewed, redeemed, restored, transferred, or re-registered after expiration.

13.2 NiceNIC does not guarantee that a domain will remain in a particular lifecycle state for a minimum period except where a mandatory ICANN or Registry rule creates such a right.

13.3 Delay may result in additional fees, service interruption, loss of ordinary renewal rights, auction sale, Registry deletion, or permanent loss of the domain.

14. Limitation of Liability

14.1 To the maximum extent permitted by applicable law and the NiceNIC Domain Name Registration Service Agreement, NiceNIC is not liable for indirect, incidental, special, punitive, or consequential loss arising from expiration, DNS interruption, failure to renew on time, Registry action, auction, failed restoration, deletion, or public release.

14.2 Nothing in this Policy excludes or limits liability or registrant rights that cannot lawfully be excluded or limited.

15. Incorporated Policies

This Policy should be read together with the NiceNIC Domain Name Registration Service Agreement, NiceNIC Domain Prices, NiceNIC Legal Policies, the applicable Registry rules, and the ICANN Expired Registration Recovery Policy where applicable.

16. Changes to this Policy

NiceNIC may update this Policy to reflect changes in ICANN requirements, Registry rules, TLD lifecycles, auction procedures, fees, security practices, or operational processes. Mandatory ICANN, Registry, or legal changes may take effect when required. Other material changes will take effect on the published effective date, subject to applicable law.

Buy Now Domain Sales Agreement

This Agreement governs fixed-price "Buy Now" domain transactions offered by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

1. Service

NiceNIC may offer domain names for fixed-price purchase through its Buy Now marketplace or related checkout process ("Buy Now Domains").

A Buy Now Domain may be supplied by NiceNIC or by a pre-approved third-party seller, marketplace, registrar, or domain provider.

NiceNIC may act as transaction facilitator, registrar, or both, depending on the domain and transaction structure.

2. Listing and Availability

A listing is an invitation to place an order and is subject to final availability, seller/provider confirmation, payment clearance, compliance review, registry status, and transfer/delivery capability.

A domain may become unavailable before delivery even after an order has been submitted or paid. NiceNIC does not guarantee delivery until the domain has been successfully delivered to the buyer's designated account or otherwise placed under the buyer's control.

3. Price and Payment

The buyer must pay the price and applicable taxes/fees shown and confirmed at checkout.

Where currency conversion, payment processing, blockchain/network charges, tax, or third-party fees apply, they will be handled as shown by the applicable payment method or order.

A payment may be subject to fraud, sanctions, identity, chargeback, or source-of-funds review where reasonably required.

4. Delivery

NiceNIC will use commercially reasonable efforts to complete delivery after cleared payment and required verification.

The estimated delivery period shown on the site is an estimate rather than a guaranteed deadline unless NiceNIC expressly agrees otherwise in writing.

Delivery may require:

• an internal account push;
• an inter-registrar transfer;
• change of registrant;
• acceptance of a registry or registrar agreement;
• identity or eligibility verification; or
• another provider-specific process.
• 
  

5. Registration Rights, Not Absolute Ownership

Upon successful delivery, the buyer receives the applicable contractual registration and control rights in the domain for the remaining registration term, subject to:

• the applicable registration agreement;
• registry rules;
• ICANN policies where applicable;
• renewal requirements;
• dispute policies;
• court orders; and
• applicable law.

A domain-name registration is not a NiceNIC guarantee of absolute property ownership.

6. Failed or Undeliverable Orders

If NiceNIC cannot deliver a paid Buy Now Domain, NiceNIC will refund the amount actually received for the undelivered domain, excluding any non-refundable third-party payment/network charge that cannot lawfully or practically be reversed where this was disclosed to the buyer.

The refund may be returned to the original payment method or NiceNIC account balance as appropriate to the payment method, operational capability, customer instruction where offered, and applicable law.

Nothing limits a mandatory refund right.

7. No Cooling-Off After Successful Delivery

Because a successfully delivered domain may be unique, immediately controlled by the buyer, and subject to irreversible registry/registrar changes, Buy Now domain purchases are final after successful delivery except where NiceNIC expressly agrees otherwise or applicable law requires a remedy.

8. Buyer Responsibilities

The buyer must:

• provide accurate account and payment information;
• have legal authority to make the purchase;
• complete required identity/eligibility checks;
• ensure that registration or use does not unlawfully infringe third-party rights;
• comply with the applicable Domain Name Registration Service Agreement and registry policies; and
• secure the account after delivery.
• 
  

9. Intellectual Property and Business Risk

NiceNIC does not warrant that:

• a domain does not infringe a trademark or other third-party right;
• a domain is suitable for a particular business;
• a domain will generate traffic, ranking, revenue, resale value, or investment return; or
• a prior use of the domain is free from reputation, search-engine, email-reputation, security, or historical issues.

The buyer should perform appropriate due diligence.

10. Fraud, Error, and Compliance

NiceNIC may pause or cancel a transaction before delivery where reasonably necessary because of:

• suspected fraud or unauthorized payment;
• manifest pricing or listing error;
• sanctions or legal restrictions;
• a court/registry/registrar restriction;
• a domain dispute;
• seller/provider non-performance; or
• a material security or compliance issue.

Where cancellation occurs without buyer fault and the domain is not delivered, the buyer will receive the refund described in Section 6.

11. Limitation of Liability

To the maximum extent permitted by law, NiceNIC is not liable for indirect, incidental, special, exemplary, or consequential losses, including expected resale profit, business opportunity, traffic, ranking, goodwill, or anticipated value.

NiceNIC's aggregate contractual liability for a Buy Now transaction will not exceed the amount paid to NiceNIC for that transaction, except for liability that cannot lawfully be limited.

12. Governing Law

This Agreement is governed by the laws of the Hong Kong Special Administrative Region.

Subject to mandatory law and applicable domain dispute policies, the courts of Hong Kong have non-exclusive jurisdiction.

13. Relationship with Other Agreements

After delivery, the domain is also governed by the NiceNIC Domain Name Registration Service Agreement, applicable registry policies, and other mandatory domain policies.

1. Incorporation of the UDRP

For a domain name to which the Uniform Domain Name Dispute Resolution Policy ("UDRP") applies, the then-current UDRP adopted by ICANN is incorporated by reference into the applicable Domain Name Registration Service Agreement between the Registered Name Holder and NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

Official ICANN UDRP:
https://www.icann.org/en/contracted-parties/consensus-policies/uniform-domain-name-dispute-resolution-policy

2. Rules and Approved Providers

UDRP proceedings are administered under the then-current Rules for Uniform Domain Name Dispute Resolution Policy and the supplemental rules of the ICANN-approved dispute resolution provider selected for the proceeding.

NiceNIC does not decide the merits of a UDRP complaint. NiceNIC performs the registrar obligations assigned to it under the UDRP, the Rules, the Registrar Accreditation Agreement, and applicable ICANN requirements.

3. Registrar Actions During a Proceeding

Where NiceNIC receives proper notice of a UDRP proceeding, NiceNIC may place or maintain the domain in the status required by the UDRP and its Rules, provide Registration Data as required by applicable ICANN procedure and law, and implement a final decision in accordance with the applicable policy and procedural waiting periods.

4. Court Proceedings

Nothing on this page eliminates any right to submit a dispute to a court where the UDRP or applicable law preserves such a right.

5. ccTLD Disputes

Many ccTLDs are not governed by the ICANN UDRP or use a modified/local dispute policy. The applicable registry's dispute policy controls for those domains.

For .hk and .香港 domain names, the applicable HKIRC Domain Name Dispute Resolution Policy and Rules apply.

6. Uniform Rapid Suspension

Certain gTLDs may also be subject to the Uniform Rapid Suspension System ("URS"). Where applicable, NiceNIC will comply with the then-current URS procedure and registrar requirements.

7. Official Text Prevails

NiceNIC may provide summaries or translations for convenience. They do not replace the official policy. To the extent of any inconsistency, the then-current official policy and rules applicable to the domain name control.

These AI Terms govern AI-enabled features made available by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC"), including AI-assisted domain search, naming suggestions, text generation, analysis, or similar tools ("AI Services").

1. Relationship to Other Terms

These AI Terms supplement the NiceNIC Terms of Service and Privacy Policy.

Where an AI feature is used in connection with domain registration or another NiceNIC service, the applicable product agreement also applies.

2. Inputs and Outputs

You may submit prompts, text, keywords, or other content ("Input") and receive generated suggestions or other material ("Output").

You are responsible for ensuring that you have the rights and lawful authority necessary to provide your Input.

As between you and NiceNIC, you retain rights you already have in your Input. To the extent permitted by law and subject to third-party rights, NiceNIC does not claim ownership of Output generated specifically for you merely because it was generated by the AI Service.

Output may not be unique, and the same or similar output may be generated for other users.

3. Third-Party AI Providers

NiceNIC may use third-party technology providers to supply or support AI Services.

Input, Output, and related technical data may be transmitted to and processed by those providers to the extent necessary to provide, secure, monitor, troubleshoot, and improve the AI Service, subject to applicable contractual and privacy requirements.

NiceNIC will describe material personal-data processing in its Privacy Policy.

4. No Guarantee of Accuracy

AI Output is probabilistic and may be inaccurate, incomplete, outdated, misleading, offensive, or unsuitable.

You must independently evaluate Output before relying on it.

AI Output is not legal, financial, tax, trademark, cybersecurity, medical, or other professional advice.

5. Domain-Name Suggestions

Where an AI Service suggests domain names, brands, keywords, or TLDs:

• a suggestion does not mean the domain is currently available;
• availability is determined only by the applicable live registry/registrar transaction at the time of order;
• a suggestion does not establish trademark or other intellectual-property clearance;
• a suggestion does not guarantee registry eligibility;
• a suggestion does not guarantee SEO ranking, traffic, resale value, investment return, or business success; and
• you are responsible for checking legal rights, eligibility, and suitability before registration or use.
• 
  

6. Prohibited Use

You must not use the AI Services to:

• facilitate unlawful activity;
• generate or operationalize malware, phishing, credential theft, fraud, or attacks;
• evade NiceNIC security or abuse controls;
• infringe third-party intellectual-property, privacy, or other legal rights;
• impersonate another person unlawfully;
• make solely automated high-impact decisions about an individual where such use is prohibited by law; or
• submit content you are not permitted to disclose, including highly confidential credentials, authentication codes, or unlawful personal data.
• 
  

7. Human Review

You are responsible for human review appropriate to your use case. You must not represent AI Output as independently verified by NiceNIC.

8. Availability and Changes

NiceNIC may modify, rate-limit, suspend, replace, or discontinue an AI feature, including where a third-party model or provider changes or where security, legal, or product considerations require it.

9. Privacy

Personal data processed through AI Services is handled under the NiceNIC Privacy Policy. Users should avoid submitting sensitive or confidential information that is not necessary for the requested AI function.

10. Intellectual Property

NiceNIC retains all rights in its platform, software, branding, interfaces, prompts/templates created by NiceNIC, and other proprietary service components.

No provision grants you rights in third-party models, software, trademarks, or content.

11. Disclaimer and Liability

To the maximum extent permitted by law, AI Services are provided on an "as available" basis without a guarantee that Output is accurate, unique, non-infringing, or fit for a particular purpose.

NiceNIC is not liable for indirect, incidental, special, exemplary, or consequential loss resulting from reliance on AI Output, except where such exclusion is prohibited by law.

Any direct-liability limitation is subject to the NiceNIC Terms of Service and mandatory law.

12. Suspension

NiceNIC may restrict or suspend AI access for material breach, security abuse, unlawful use, excessive automated use contrary to applicable limits, or where required by law.

1.3 The Registrant acknowledges and agrees that the Registrar shall monitor the status of Domain Names registered through the Registrar and shall, at its own initiative or on receipt of complaint, conduct checks to verify whether a Domain Name is being used in connection with phishing or "spam" advertising. The Registrar shall delete or suspend a Domain Name if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government or law enforcement authority (including without limitation the Hong Kong Police Force or the Office of Telecommunications Authority) that the use of the Domain Name is in breach of any laws, directives, guidelines, codes of practice or regulations issued by such local authorities, or if, in HKIRC's reasonable belief, the continuation of registration of the Domain Name or the operation of web site referenced   by the Domain Name is likely to damage or adversely affect the goodwill, reputation and operation of HKIRC or the domain name industry in Hong Kong, or may expose HKIRC to risks of third party claims or civil or criminal prosecution.

For more information about .HK domain registration, please refer to the latest version of HKIRC Registration Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

5.2 Any decision made by an arbitration panel duly appointed by a dispute resolution service provider shall be final and binding on the Registrant and the Registrant shall abide by such decision.

5.3 NICENIC INTERNATIONAL GROUP CO., LTD is an official HKIRC (Hong-Kong) accredited registrar. HKIRC is a non-profit-making and non-statutory corporation designated by the Hong-Kong Government to administer the registration of Internet domain names under .hk and .香港 country-code top level domains. For any comments or complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find here useful information: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_support/domain_dispute_policies_and_procedures/domain_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_support/domain_dispute_policies_and_procedures/rules_of_procedures/; or Email address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant acknowledges that the Registrar and HKIRC rely on all representations made and warranties given by the Registrant in determining if the application for a Domain Name should be approved.

    For more information about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domain_policies/EN_Domain_Name_Acceptable_Use_Policy.pdf.

Below is the letter of congratulation from Verisign:
"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. Now that you have met the requirements of ICANN, our team is looking forward to assisting you in completing the Verisign certification process so you can quickly begin registering .com and .net domain names. We hope this support will prove to be helpful in reducing the investment of your internal resources and time."

PIR:
"ICANN has informed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed your ICANN accreditation to become a registrar and wish to partner with us by becoming an .ORG accredited registrar."

Telnic:
"We received notification from ICANN that you have added the .tel appendix to your agreement with them. There hasn't been a better time to become involved with .tel domains and we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on your recent ICANN Accreditation..."

Neustar:

"We have been notified that your company is now ICANN-accredited as a .BIZ registrar.  Neustar looks forward to getting your company up and running as soon as possible!"

More registries will be notified by ICANN for the corresponding domain names signed in the RAA in the next days, we NiceNIC have been staying for the disposal of sign-up/accreditation process, striving to save time and expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a more competitive level. Detailed information will come out when available. 

Flying with the strong momentum, our English version website NiceNIC.NETwas launched with her unique style of "Keep Internet Simple Stupid" (acronym "KISS"), and dedicated to offer clients easy to navigate, fast to locate services in domain name registration, web hosting purchase, 1 to 1 customer support.

Standing at the peak of internet infrastruture, we firstly need to appreciate every client, and every website viewer who ever stayed here, without your persistant support and comprehension, we are nothing, hope 2012 will bring you and your family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-reports/accreditation-qualified-list.html

http://www.icann.org/registrar-reports/accredited-list.html

http://www.internic.com/alpha.html

ZhuHai NaiSiNiKe Information Technology Co Ltd.

2009

China

.asia .biz .com .info .mobi .name .net .org .tel .xxx

All the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Information Technology Co., Ltd.