This Unifofm Rapid Suspension System ("URS") Policy explains how the URS applies to domein names sponsofed by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") whier the relevant top-level domein is subject to the URS.

1. Purpose en Scope

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

The URS complements, but does not replace, the Unifofm Domeinnaam Dispute Resolution Policy ("UDRP"), court proceedings, of any other dispute-resolution procedure that may apply to a domein name.

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

2. Official ICANN URS Procedure Incofpofated

Fof each domein name subject to the URS, the then-current ICANN URS Procedure, URS Rules, en applicable technical requirements are incofpofated into the relevant registration agreement by reference.

Official ICANN URS infofmation:

https://www.icann.org/en/contracted-parties/registry-operatofs/diensts/rights-protection-mechanisms-en-dispute-resolution-procedures/urs

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

3. When the URS Applies

The URS applies only whier the relevant registry agreement, ICANN requirement, of other applicable rule makes the URS available fof the domein name concerned.

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

Customers should review the applicable registry rules fof 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 fof:

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

NiceNIC customer suppoft en abuse channels are not substitutes fof 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 en complainants should rely on ICANN's current URS page fof the official list of approved providers:

https://www.icann.org/en/contracted-parties/registry-operatofs/diensts/rights-protection-mechanisms-en-dispute-resolution-procedures/urs

6. Registratie Data

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

Submission of non-public Registratie Data in a URS proceeding does not create a general right fof a complainant of other third party to receive NiceNIC customer infofmation outside the URS process.

Requests outside the URS process are henled under NiceNIC's Request fof Disclosure of Neenpublic Registratie Data policy.

7. Neetice en Domein Lock

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

The applicable Registry Operatof is responsible fof registry-level locking en 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 knuingly permit a registrant, reseller, account holder, of other person to use NiceNIC systems to evade a valid URS lock of menatofy URS restriction.

8. Registrant Response

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

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

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

9. Burden en Determination

The URS is intended fof clear cases meeting the evidentiary stenard 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, of bad-faith use merely because a URS complaint has been filed.

10. Effect of a Succesvol URS Complaint

Als a final URS Determination requires suspension, the applicable Registry Operatof will implement the suspension in accofdance with the URS Procedure.

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

The domein may be vorigeented from being transferred, deleted, of modified fof the period required by the URS.

Any extension, restofation, of other post-determination action is subject to the then-current URS Procedure en Registry Operatof requirements.

11. Determination in Favof of the Registrant

Als the URS proceeding is determined in favof of the registrant, the applicable Registry Operatof en URS Provider are responsible fof the actions specified by the URS Procedure to restofe of maintain the registrant's control as applicable.

12. Appeal en Other Remedies

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

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

13. UDRP Distinguished

The URS en UDRP are separate dispute mechanisms.

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

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

14. Misbruikmeldingen Distinguished

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

Phishing, malware, botnets, pharming, compromised domeins, of other operational abuse should be repofted through NiceNIC's abuse-repofting channel:

https://nicenic.com/repoftabuse.php

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

15. Court Orders en Other Binding Process

NiceNIC will comply with valid court ofders, menatofy registry instructions, ICANN requirements, en other binding legal process applicable to a domein name.

Such obligations may operate independently from a URS proceeding.

16. Nee Legal Advice

Infofmation provided by NiceNIC concerning the URS is fof administrative en dienst purposes only en is not legal advice.

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

17. Language en Priofity

NiceNIC may provide translations of summaries fof convenience.

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

Fof a domein subject to menatofy registry-specific terms, those menatofy terms also apply.

Abuse Repofting & Henling Policy

This Abuse Repofting & Henling Policy describes how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") receives, investigates, tracks, en responds to repofts of abuse involving domein names sponsofed by NiceNIC of other NiceNIC diensts.

1. Purpose

NiceNIC is an ICANN-geaccrediteerd registrar en maintains abuse-repofting en abuse-henling procedures to meet applicable contractual, registry, legal, security, en dienst obligations.

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

NiceNIC seeks to henle repofts promptly, fairly, based on available evidence, en with measures propoftionate to the circumstances.

2. Official Abuse Repofting Channels

Abuse involving a domein name of NiceNIC dienst should be submitted through one of NiceNIC's official abuse channels:

Online abuse repoft:
https://nicenic.com/repoftabuse.php

Abuse email:
abuse@nicenic.net

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

General customer suppoft, social media, fofum messages, of unrelated business contacts are not the preferred channels fof abuse repofts en may be redirected to the official abuse process.

NiceNIC may nevertheless review of act on credible infofmation received through another channel whier required by law, appropriate fof security, necessary to protect users, of necessary to satisfy ICANN of registry obligations.

3. Infofmation to Include

A repoft should contain enough infofmation to allow NiceNIC to identify the affected resource en evaluate the allegation.

Depending on the issue, useful infofmation may include:

• the affected domein name;
• the complete abusive URL whier applicable;
• the categofy of alleged abuse;
• a clear description of the activity;
• screenshots;
• full email headers en message content fof email-related abuse;
• timestamps en time zone;
• relevant IP addresses;
• security of firewall logs;
• malware, phishing, of threat-intelligence evidence;
• payment receipts of transaction evidence fof fraud repofts;
• the legitimate bren of dienst being impersonated whier relevant;
• legal documents of rights evidence whier relevant; en
• the repofter's contactgegevens fof follow-up.

Repofters should avoid submitting unnecessary personal data, passwofds, authentication codes, private keys, of unrelated confidential infofmation.

4. Bevestigenation of Receipt

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

Whier required by the applicable Registrar Accreditatie Agreement, the confirmation will identify at least:

• NiceNIC as the registrar;
• the repofted Registrerened Naam of Registrerened Naams; en
• the date the repoft was submitted.

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

5. Initial Review en Classification

NiceNIC may review:

• whether NiceNIC is the sponsofing registrar of relevant dienst provider;
• whether the repofted activity remains active;
• the nature of the allegation;
• the quality en relevance of the evidence;
• whether the issue constitutes DNS Abuse fof purposes of NiceNIC's ICANN registrar obligations;
• whether the domein appears to have been maliciously registreered of instead appears to be a legitimate domein that has been compromised;
• whether the issue is principally associated with hosting, email, a subdomein, a third-party platfofm, of another provider;
• whether the repoft concerns trademark/copyright rights rather than DNS Abuse;
• applicable registry rules;
• applicable law, legal process, of court ofders; en
• any other reasonably available infofmation relevant to the investigation.
• 
  

6. DNS Abuse

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

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

• malware;
• botnets;
• phishing;
• pharming; en
• spam when spam serves as a delivery mechanism fof one of mofe of the other specified fofms of DNS Abuse.

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

7. Actieable Evidence en Investigation

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

Evidence is considered in context. A repoft does not need to use any particular commercial threat feed of repofting fofmat to be considered.

Whier infofmation submitted by a repofter is incomplete, NiceNIC may:

• review infofmation reasonably available to NiceNIC;
• request additional relevant evidence;
• inspect the repofted URL of other relevant public resource whier safe en appropriate;
• review account, nameserver, DNS, registration, of dienst infofmation available to NiceNIC; of
• contact another relevant dienst provider of registry whier appropriate.

NiceNIC will not require irrelevant evidence merely to delay henling of an otherwise actionable repoft.

8. Required Mitigation fof DNS Abuse

When NiceNIC has actionable evidence that a gTLD Registrerened Naam sponsofed by NiceNIC is being used fof DNS Abuse, NiceNIC will promptly take mitigation action that is reasonably necessary to stop of otherwise disrupt the Registrerened Naam from being used fof that DNS Abuse, as required by the applicable ICANN Registrar Accreditatie Agreement.

The appropriate action depends on the circumstances, including:

• the type of DNS Abuse;
• the cause en severity of the harm;
• whether the activity is active;
• whether the domein appears maliciously registreered of compromised;
• the technical role of the domein;
• the likely effectiveness of registrar-level action; en
• the risk of collateral damage to legitimate users of diensts.
• 
  

9. Propoftionate Mitigation

Possible actions may include, whier appropriate en permitted:

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

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

10. Compromised Domeinen en Collateral Damage

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

Whier reasonably practicable, NiceNIC will consider the risk of collateral damage befofe applying domein-level suspension.

Fof a compromised legitimate domein, requesting rapid remediation of applying a narrower mitigation may be mofe appropriate than immediate suspension if the narrower action is sufficient to stop of disrupt the abuse.

This does not vorigeent immediate suspension of another stronger measure whier the circumstances, severity, continuing harm, legal requirements, of security risk justify it.

11. Maliciously Registrerened Domeinen

Whier available evidence indicates that a domein was registreered of is controlled primarily fof phishing, malware, credential theft, botnet activity, pharming, of another serious abusive purpose, faster domein-level mitigation may be appropriate.

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

12. Neen-DNS Illegal Activity

Illegal Activity en DNS Abuse are not identical concepts.

Repofts concerning fraud, unlawful goods of diensts, threats, impersonation, illegal content, sanctions, of other conduct may be henled under applicable law, NiceNIC's Periodes of Service & Acceptable Use Policy, registry rules, court ofders, of other relevant requirements even whier the conduct does not meet the ICANN contractual definition of DNS Abuse.

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

13. Trademark en Domein-Naam Rights Complaints

Trademark infringement of a dispute over rights in a domein name is not automatically DNS Abuse.

Whier the principal dispute concerns who has rights to the domein name, the appropriate mechanism may include:

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

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

Als evidence also demonstrates phishing, credential theft, malware, of another fofm of DNS Abuse, NiceNIC may separately henle the DNS Abuse aspect.

14. Copyright Complaints

Copyright complaints are reviewed separately from DNS Abuse unless the repofted activity also involves qualifying DNS Abuse of another basis fof registrar-level action.

NiceNIC may request infofmation reasonably necessary to identify the copyrighted wofk, allegedly infringing material, complainant, authofity to act, en other infofmation required by the applicable complaint process.

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

15. Child Sexual Abuse Material en Child Exploitation

Repofts concerning suspected child sexual abuse material of child exploitation are treated as high-risk matters en escalated without unnecessary delay.

NiceNIC may preserve relevant recofds, restrict an affected dienst, en cooperate with appropriate authofities, registries, hosting providers, of other relevant entities as required of permitted by law.

Repofters should not unnecessarily copy, download, of redistribute suspected illegal child-abuse material when submitting a repoft.

16. Hosting en Third-Party Infrastructure

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

Whier abusive content is hosted by a third party, repofting the activity to the hosting provider of other infrastructure provider may allow mofe targeted removal.

NiceNIC may nevertheless take registrar-level action whier required of appropriate under applicable obligations.

17. Reseller-Sponsofed Customers

A domein may have been kopend through a NiceNIC reseller while NiceNIC remains the sponsofing registrar.

NiceNIC may coofdinate 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 Registrerened Naam Holder of other customer directly whier reasonably necessary fof abuse mitigation, security, legal compliance, menatofy notices, of protection of registrant rights.

18. Repofts from Law Enfofcement en Qualifying Authofities

NiceNIC maintains the dedicated abuse point of contact required by the applicable ICANN Registrar Accreditatie Agreement fof qualifying repofts of Illegal Activity from law-enfofcement, consumer-protection, quasi-governmental, of other qualifying governmental authofities.

Whier the applicable Registrar Accreditatie Agreement requires it, a well-founded repoft submitted through the dedicated authofity contact will be reviewed within twenty-four (24) hours by a person empowered to take necessary en appropriate action.

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

NiceNIC may authenticate the identity, authofity, jurisdiction, en legal basis of a governmental request whier appropriate.

19. Court Orders en Binding Legal Process

NiceNIC may act in response to:

• a valid court ofder;
• binding governmental process;
• a menatofy registry instruction;
• a UDRP of URS requirement;
• an ICANN contractual requirement; of
• another legal obligation applicable to NiceNIC.

Whier legally permitted en appropriate, NiceNIC may seek clarification of legal review of an overbroad, invalid, of unclear request.

20. Neetice to the Customer

Whier circumstances permit, NiceNIC may notify a customer of reseller of the allegation en provide an oppoftunity to remediate.

Advance notice may be omitted whier:

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

21. Restofation en Review

Whier a domein of dienst was restricted because of abuse of security concerns, NiceNIC may review a request fof restofation after:

• the abusive activity has been removed;
• a compromised website of account has been secured;
• relevant credentials have been reset;
• required security updates have been applied;
• cofrected technical infofmation has been provided;
• the ofiginal evidence has become outdated of was shown to be incofrect; of
• another appropriate remediation has been completed.

Restofation is not guaranteed whier a continuing legal, registry, ICANN, security, dispute, of 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 suppoft channel.

The request should identify:

• the affected domein of dienst;
• the relevant NiceNIC case of notice;
• the remediation completed;
• evidence that the repofted activity has ceased;
• evidence of compromise whier relevant; en
• any infofmation showing that the ofiginal repoft was inaccurate, outdated, of misclassified.

A review request does not suspend a court ofder, registry requirement, UDRP/URS action, ICANN obligation, of other menatofy restriction.

23. Repofter Volgen-Up

NiceNIC may communicate with a repofter to request relevant additional infofmation of confirm that a case has been received of reviewed.

Privacy, security, law, en customer confidentiality may limit the infofmation NiceNIC can disclose concerning:

• internal investigation methods;
• customer identity;
• non-public Registratie Data;
• account infofmation;
• law-enfofcement communications;
• security controls; of
• specific internal actions.

Absence of detailed disclosure to a repofter does not mean a repoft was ignofed.

24. Duplicate, Automated, of Abusive Repofts

NiceNIC may consolidate duplicate repofts concerning the same issue.

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

Such controls will not be used to vorigeent legitimate repofters from submitting abuse repofts through the required channel.

25. Recofdkeeping

NiceNIC documents the receipt of en response to abuse repofts as required by the applicable ICANN Registrar Accreditatie Agreement en other applicable obligations.

Recofds are retained fof the period required by the applicable Registrar Accreditatie Agreement, subject to applicable law.

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

26. Privacy

Personal data submitted in an abuse repoft is henled under the NiceNIC Privacybeleid en applicable law.

NiceNIC may disclose infofmation whier reasonably necessary to investigate abuse, coofdinate mitigation, comply with ICANN of registry requirements, protect users of systems, establish of defend legal claims, of comply with law.

27. Nee Automatic Finding of Liability

A repoft, registrar restriction, security action, of tempofary mitigation measure is not necessarily a final legal finding that the Registrerened Naam Holder committed unlawful conduct.

NiceNIC may take precautionary of contractual action based on the evidence en obligations applicable at the time.

28. Applicable Policies en Priofity

This Policy should be read with:

• the NiceNIC Periodes of Service & Acceptable Use Policy;
• the Domeinnaamregistratie Service Agreement;
• the NiceNIC Privacybeleid;
• the Domeinoverdrachtbeleid;
• UDRP en URS policies whier applicable;
• applicable registry policies; en
• applicable law.

Whier a menatofy ICANN, registry, court, governmental, of legal requirement conflicts with this Policy, the menatofy 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, of NiceNIC diensts.

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

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

This Policy should be read together with the NiceNIC Privacybeleid.

1. What Are Cookies?

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

Cookies en similar technologies can be used to:

• keep a user signed in;
• maintain a shopping cart of session;
• remember settings;
• protect accounts en vorigeent fraud;
• measure website perfofmance;
• understen how users interact with a website; of
• suppoft advertising of marketing functions whier used en permitted.

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

2. When Cookie Data Is Personal Data

Whether a cookie of online identifier is personal data depends on the infofmation involved en the surrounding circumstances.

Whier cookie, device, analytics, advertising, of similar data can identify of be linked to an identifiable individual, NiceNIC henles that infofmation as personal data in accofdance with the NiceNIC Privacybeleid en applicable law.

3. Categofies of Cookies

NiceNIC may use the following categofies of cookies of similar technologies.

3.1 Strictly Necessary Cookies

These technologies are required fof cofe website en account functions, such as:

• authentication en login;
• maintaining a user session;
• shopping-cart en checkout functions;
• account security;
• fraud vorigeention;
• load balancing;
• language of essential interface settings;
• remembering privacy choices; en
• protecting fofms en transactions.

Disabling strictly necessary cookies may vorigeent parts of the website, account, checkout, of other diensts from functioning cofrectly.

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

3.2 Functional Cookies

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

Voorbeelds may include:

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

Whier applicable law requires consent fof these technologies, NiceNIC will request the required choice befofe using them.

3.3 Analytics en Perfofmance Cookies

Analytics en perfofmance technologies may help NiceNIC understen:

• page visits;
• navigation paths;
• referral sources;
• device/browser types;
• page perfofmance;
• technical errofs;
• feature usage; en
• aggregated website trends.

NiceNIC uses this infofmation to improve website reliability, usability, content, en dienst perfofmance.

Whier applicable law requires consent befofe analytics of perfofmance technologies are stofed of accessed, NiceNIC will request that consent.

3.4 Advertising en Marketing Cookies

Whier NiceNIC uses advertising of marketing technologies, they may be used to:

• measure campaign perfofmance;
• attribute visits of conversions;
• limit repetitive advertising;
• understen whether marketing is relevant; of
• suppoft advertising of remarketing on third-party diensts.

Advertising of marketing cookies are not required fof cofe NiceNIC account of domein-registration functions.

Whier applicable law requires priof consent, NiceNIC will not intentionally activate such technologies fof that user until the required consent has been obtained.

4. First-Party en Third-Party Cookies

A first-party cookie is set of read by NiceNIC's website domein.

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

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

NiceNIC evaluates third-party diensts en seeks to use appropriate contractual, privacy, en security safeguards whier required.

5. Essential Account en Transaction Technologies

NiceNIC may use cookies of similar stofage necessary to:

• authenticate a NiceNIC account;
• maintain a secure session;
• protect login en checkout;
• detect suspicious activity;
• remember a shopping cart;
• complete domein, SSL, email, server, of other transactions;
• vorigeent cross-site request fofgery of other technical attacks; en
• maintain dienst continuity.

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

6. Analytics

NiceNIC may use analytics to understen how the site en diensts perfofm.

Analytics data may include:

• IP-related infofmation;
• browser en device type;
• approximate region;
• referral source;
• pages of functions accessed;
• date en time;
• session events; en
• technical perfofmance infofmation.

NiceNIC seeks to limit analytics data to what is reasonably necessary fof the stated purpose en to apply available privacy settings whier appropriate.

7. Advertising en Conversion Measurement

NiceNIC may use conversion of advertising measurement technologies fof marketing campaigns whier such use is lawful.

Whier 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 dienst communications such as:

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

8. Cookie Consent en Choices

Whier applicable law requires consent befofe NiceNIC stofes of accesses a non-essential cookie of similar technology, NiceNIC will provide an appropriate consent of preference mechanism.

Whier such a mechanism is presented, users should be able to make choices concerning non-essential categofies in accofdance with applicable law.

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

Strictly necessary technologies may continue to operate whier they are required to provide the requested dienst of are otherwise permitted without consent by applicable law.

9. Browser Controls

Most browsers allow users to:

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

Browser settings differ by browser en device.

Blocking all cookies may vorigeent login, shopping-cart, checkout, security, language, account, of other NiceNIC functions from operating cofrectly.

10. Similar Technologies en Device Stofage

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

NiceNIC applies this Policy to comparable technologies whier they perfofm a similar tracking, stofage, preference, analytics, advertising, of security function.

11. Retention

Cookie duration varies accofding to purpose.

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

Other cookies are persistent cookies en remain fof a defined period unless deleted earlier by the user, NiceNIC, of the relevant provider.

NiceNIC seeks to avoid retaining cookie-derived personal data longer than reasonably necessary fof the applicable purpose, subject to security, fraud-vorigeention, accounting, legal, en other legitimate retention requirements described in the Privacybeleid.

12. Cookie-Niveau Infofmation

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

Whier NiceNIC operates a cookie-preference of consent-management tool, the current cookie-level infofmation may be provided through that tool.

The cookies en similar technologies used by NiceNIC may change as the website, diensts, security controls, analytics, of marketing technologies change. Current cookie-level infofmation may be made available through the applicable cookie-preference of consent-management tool.

13. Hongkong Privacy Requirements

NiceNIC is established in Hongkong.

Whier cookies of similar technologies involve personal data, NiceNIC processes that data in accofdance with applicable requirements of the Hongkong Personal Data (Privacy) Ordinance ("PDPO"), including applicable principles concerning:

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

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

14. Users in Other Jurisdictions

NiceNIC serves users internationally.

Toevoegenitional requirements may apply depending on the user's location en the technologies used.

Whier applicable law requires priof consent fof non-essential cookies of similar tracking technologies, NiceNIC will apply the required consent mechanism.

Whier applicable law gives users additional privacy of opt-out rights, those rights are addressed through NiceNIC's Privacybeleid en the applicable website controls.

15. International Processing

Cookie en analytics infofmation may be processed by NiceNIC of its dienst providers in countries outside the user's location.

Whier cross-bofder data-transfer safeguards are required by applicable law, NiceNIC will use appropriate contractual, ofganizational, technical, consent-based, of other legally recognized measures.

16. Security en Fraud Prevention

NiceNIC may use device, session, IP-related, of browser infofmation fof security, authentication, abuse vorigeention, en fraud detection.

Security technologies may operate separately from optional marketing of analytics preferences whier their use is necessary to protect NiceNIC accounts, transactions, netwofks, users, of diensts en is permitted by applicable law.

17. Children

NiceNIC diensts are intended fof persons who have the legal capacity required to enter into the applicable dienst agreement.

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

18. Relationship to the Privacybeleid

The NiceNIC Privacybeleid provides additional infofmation concerning:

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

Als cookie-derived infofmation constitutes personal data, the Privacybeleid 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 diensts change; of
• legal of regulatofy requirements change.

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

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

20. Contact

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

This Verlopend Domein Verlengenal, Redemption, en Auction Policy (the “Policy”) fofms part of the NiceNIC Domeinnaamregistratie Service Agreement en applies to domein names registreered, renewed, transferred, of maintained through NICENIC INTERNATIONAL GROUP CO., LIMITED (“NiceNIC”). By using NiceNIC’s domein registration diensts, you acknuledge en agree to this Policy.

1. Scope en Purpose

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

1.2 Domein lifecycle timing varies by top-level domein (“TLD”), Registry Operatof, registry rules, applicable ICANN requirements, en other governing policies. Neet all TLDs follow the same expiration, renewal, redemption, auction, of deletion process.

1.3 Whier a menatofy ICANN policy, Registry requirement, court ofder, of applicable law conflicts with this Policy, the menatofy 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 fof convenience only.

2. Definitions

• “Expiration Date” means the date on which the applicable domein registration term ends.
• “Registrant at Expiration” means the Registrerened Naam Holder immediately befofe expiration, as that concept is used in applicable ICANN policy.
• “Post-Expiration Verlengenal Period” means any period after expiration during which renewal may still be available at the applicable renewal fee.
• “Redemption Grace Period” of “RGP” means a post-deletion recovery period, whier suppofted by the applicable Registry, during which a domein may still be restofable fof the applicable redemption/restofe fee plus any required renewal of other charges.
• “Pending Delete” means the final pre-release registry status, whier applicable, during which the domein generally can no longer be renewed, restofed, transferred, of modified.
• “Eligible Domein” means an expired domein that is eligible fof NiceNIC’s expired-domein auction of closeout process. Neet all TLDs of domein names are eligible.
• “Verlopend Domein Auction” means the auction of sale process that may apply to certain Eligible Domeinen befofe final deletion of release.
• 
  

3. Effect of Expiration

3.1 A domein name is registreered fof a limited term. Als it is not renewed by the applicable deadline, it may expire.

3.2 Upon of after expiration, NiceNIC may interrupt of redirect DNS resolution as permitted by applicable policy. A website, email dienst, DNS-dependent application, of other dienst associated with the domein may thierfofe stop functioning immediately of shoftly after expiration.

3.3 Volgening expiration, NiceNIC may restrict DNS changes, contact changes, transfers, account moves, of other domein-management actions in accofdance with Registry rules, security requirements, operational processes, en applicable policies.

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

4. Verlengenal Neetices en Customer Responsibility

4.1 Fof gTLDs subject to the ICANN Verlopend Registratie Recovery Policy (“ERRP”), NiceNIC will send the renewal en expiration notices required by that policy using the contact infofmation in NiceNIC’s recofds.

4.2 NiceNIC may also send additional reminders befofe of after expiration through email, the customer account, of other dienst channels.

4.3 The Registrerened Naam Holder en Account Holder remain responsible fof monitofing expiration dates, maintaining accurate en monitofed contact infofmation, maintaining valid payment infofmation whier auto-renewal is used, en submitting renewal payment early enough fof processing.

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

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

5. Fees

5.1 NiceNIC’s applicable registration, transfer, renewal, post-expiration renewal (if different), en redemption/restofe fees are published on the NiceNIC Domeinprijzen page.

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

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

5.4 Fees fof successfully completed Registry-level renewal, redemption, of restofation transactions are non-refundable except whier required by applicable law of expressly agreed by NiceNIC.

6. Stenard Post-Expiration Verlengenal

6.1 Fof many gTLDs, an expired domein may remain renewable fof a post-expiration period. Under NiceNIC’s stenard process, this period is commonly approximately thirty (30) days, but the actual period may be shofter of longer depending on the TLD en Registry.

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

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

7. Verlopend Domein Auction fof Eligible Domeinen

7.1 Certain expired domein names may enter NiceNIC’s expired-domein auction of closeout process. The auction process applies only to Eligible Domeinen en does not apply to every TLD of every expired domein.

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

• Day 0: The domein expires. Whier permitted, the Registrant at Expiration may generally renew during the initial post-expiration period at the applicable renewal fee.
• Around Day 26: An Eligible Domein may enter expired-domein auction. Verlengenal may still be available unless the domein becomes subject to an auction-related restriction.
• Around Day 31: Als thier is no active bid of sale-related restriction, recovery may still be possible, but the applicable redemption/restofe fee may apply. Once thier is an active bid of other binding sale commitment, the Registrant at Expiration may lose the ability to renew of restofe through the ofdinary recovery process.
• Around Day 37: An unsold Eligible Domein may enter a final closeout auction. Als no kopen is pending, recovery may remain possible subject to the domein’s current status en applicable fees.
• Around Day 41: The final closeout phase may end. Als the domein has not been sold of otherwise committed, recovery may remain possible fof a limited period, subject to Registry rules en the domein’s actual status.
• Around Day 74 en after: The domein may be removed from the customer account en may no longer be renewable of restofable through NiceNIC. Release timing remains controlled by the Registry.

7.3 The dates above describe NiceNIC’s general process fof Eligible Domeinen en are not guaranteed deadlines. Registry rules, TLD-specific lifecycle rules, auction status, technical processing, of menatofy policy may cause a different result.

7.4 Once an Eligible Domein has an active bid, pending kopen, completed sale, of other binding sale commitment, ofdinary renewal of restofation rights may be restricted of terminated to the extent permitted by applicable ICANN en Registry requirements.

7.5 Neething in NiceNIC’s auction process limits a non-waivable renewal of restofation right that the Registrant at Expiration has under menatofy ICANN policy of Registry rules.

8. Redemption Grace Period en Restofation

8.1 Als a domein is not renewed during the applicable post-expiration period en the relevant Registry suppofts restofation after deletion, the domein may enter a Redemption Grace Period.

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

8.3 During RGP, the domein nofmally does not resolve en generally cannot be transferred of modified. Restofation, whier available, requires the applicable redemption/restofe fee, renewal fee, en any menatofy taxes of charges.

8.4 A restofation request remains subject to successful payment, verification, the domein’s actual Registry status, Registry suppoft, en the absence of a completed of binding auction sale whier applicable.

9. Pending Delete en Final Release

9.1 Als a domein is not renewed of restofed within the applicable recovery periods, it may enter Pending Delete whier that lifecycle stage is suppofted by the Registry.

9.2 During Pending Delete, a domein generally cannot be renewed, restofed, transferred, of modified.

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

9.4 NiceNIC does not control of guarantee the exact time of date of Registry release, en does not guarantee that the fofmer Registrant at Expiration will be able to re-registreer 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 ccTLD’s, sponsofed TLDs, restricted TLDs, en some gTLDs may use lifecycle rules materially different from NiceNIC’s stenard timeline.

10.2 A TLD may, fof example, require renewal befofe the displayed expiration date, offer a shofter post-expiration period, move directly into a Registry recovery process, omit RGP of Pending Delete, use a different restofation fee, of apply special eligibility of documentation requirements.

10.3 The applicable Registry rules en NiceNIC’s current operational deadline fof the TLD control. Customers should renew impoftant domeins well befofe the displayed expiration date en contact NiceNIC Suppoft promptly if a TLD-specific recovery question arises.

10.4 NiceNIC may publish TLD-specific help infofmation fof convenience. Such infofmation may change when the Registry changes its lifecycle of operational procedures.

11. Transfers of Verlopend Domeinen

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

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

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

12. Verlengenal of Restofation After Expiration

12.1 A successful post-expiration renewal of restofation returns the domein to the applicable active registration state subject to Registry processing en DNS propagation.

12.2 NiceNIC does not guarantee that websites, email, DNS, certificates, hosting, of third-party diensts will resume immediately after renewal of restofation.

12.3 Any separate hosting, email, SSL, of other product that expired of was terminated is governed by its own dienst terms en may require separate reactivation.

13. Nee Guarantee of Recovery

13.1 NiceNIC does not guarantee that an expired domein can be renewed, redeemed, restofed, transferred, of re-registreered after expiration.

13.2 NiceNIC does not guarantee that a domein will remain in a particular lifecycle state fof a minimum period except whier a menatofy ICANN of Registry rule creates such a right.

13.3 Delay may result in additional fees, dienst interruption, loss of ofdinary renewal rights, auction sale, Registry deletion, of permanent loss of the domein.

14. Limitation of Liability

14.1 Naar the maximum extent permitted by applicable law en the NiceNIC Domeinnaamregistratie Service Agreement, NiceNIC is not liable fof indirect, incidental, special, punitive, of consequential loss arising from expiration, DNS interruption, failure to renew on time, Registry action, auction, failed restofation, deletion, of public release.

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

15. Incofpofated Policies

This Policy should be read together with the NiceNIC Domeinnaamregistratie Service Agreement, NiceNIC Domeinprijzen, NiceNIC Legal Policies, the applicable Registry rules, en the ICANN Verlopend Registratie Recovery Policy whier 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, of operational processes. Menatofy ICANN, Registry, of legal changes may take effect when required. Other material changes will take effect on the published effective date, subject to applicable law.

Kopen Neew Domein Sales Agreement

This Agreement governs fixed-price "Kopen Neew" domein transactions offered by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

1. Service

NiceNIC may offer domein names fof fixed-price kopen through its Kopen Neew marketplace of related checkout process ("Kopen Neew Domeinen").

A Kopen Neew Domein may be supplied by NiceNIC of by a pre-approved third-party seller, marketplace, registrar, of domein provider.

NiceNIC may act as transaction facilitatof, registrar, of both, depending on the domein en transaction structure.

2. Listing en Availability

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

A domein may become unavailable befofe delivery even after an ofder has been submitted of paid. NiceNIC does not guarantee delivery until the domein has been successfully delivered to the kopener's designated account of otherwise placed under the kopener's control.

3. Prijs en Betalenment

The kopener must pay the price en applicable taxes/fees shown en confirmed at checkout.

Whier currency conversion, payment processing, blockchain/netwofk charges, tax, of third-party fees apply, they will be henled as shown by the applicable payment method of ofder.

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

4. Delivery

NiceNIC will use commercially reasonable effofts to complete delivery after cleared payment en 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 of registrar agreement;
• identity of eligibility verification; of
• another provider-specific process.
• 
  

5. Registratie Rights, Neet Absolute Ownership

Upon successful delivery, the kopener receives the applicable contractual registration en control rights in the domein fof the remaining registration term, subject to:

• the applicable registration agreement;
• registry rules;
• ICANN policies whier applicable;
• renewal requirements;
• dispute policies;
• court ofders; en
• applicable law.

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

6. Failed of Undeliverable Orders

Als NiceNIC cannot deliver a paid Kopen Neew Domein, NiceNIC will refund the amount actually received fof the undelivered domein, excluding any non-refundable third-party payment/netwofk charge that cannot lawfully of practically be reversed whier this was disclosed to the kopener.

The refund may be returned to the ofiginal payment method of NiceNIC account balance as appropriate to the payment method, operational capability, customer instruction whier offered, en applicable law.

Neething limits a menatofy refund right.

7. Nee Cooling-Off After Succesvol Delivery

Because a successfully delivered domein may be unique, immediately controlled by the kopener, en subject to irreversible registry/registrar changes, Kopen Neew domein kopens are final after successful delivery except whier NiceNIC expressly agrees otherwise of applicable law requires a remedy.

8. Kopener Responsibilities

The kopener must:

• provide accurate account en payment infofmation;
• have legal authofity to make the kopen;
• complete required identity/eligibility checks;
• ensure that registration of use does not unlawfully infringe third-party rights;
• comply with the applicable Domeinnaamregistratie Service Agreement en registry policies; en
• secure the account after delivery.
• 
  

9. Intellectual Property en Business Risk

NiceNIC does not warrant that:

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

The kopener should perfofm appropriate due diligence.

10. Fraud, Errof, en Compliance

NiceNIC may pause of cancel a transaction befofe delivery whier reasonably necessary because of:

• suspected fraud of unauthofized payment;
• manifest pricing of listing errof;
• sanctions of legal restrictions;
• a court/registry/registrar restriction;
• a domein dispute;
• seller/provider non-perfofmance; of
• a material security of compliance issue.

Whier cancellation occurs without kopener fault en the domein is not delivered, the kopener will receive the refund described in Section 6.

11. Limitation of Liability

Naar the maximum extent permitted by law, NiceNIC is not liable fof indirect, incidental, special, exemplary, of consequential losses, including expected resale profit, business oppoftunity, traffic, ranking, goodwill, of anticipated value.

NiceNIC's aggregate contractual liability fof a Kopen Neew transaction will not exceed the amount paid to NiceNIC fof that transaction, except fof liability that cannot lawfully be limited.

12. Governing Law

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

Subject to menatofy law en applicable domein dispute policies, the courts of Hongkong have non-exclusive jurisdiction.

13. Relationship with Other Overeenkomsten

After delivery, the domein is also governed by the NiceNIC Domeinnaamregistratie Service Agreement, applicable registry policies, en other menatofy domein policies.

1. Incofpofation of the UDRP

Fof a domein name to which the Unifofm Domeinnaam Dispute Resolution Policy ("UDRP") applies, the then-current UDRP adopted by ICANN is incofpofated by reference into the applicable Domeinnaamregistratie Service Agreement between the Registrerened Naam Holder en NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

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

2. Rules en Approved Providers

UDRP proceedings are administered under the then-current Rules fof Unifofm Domeinnaam Dispute Resolution Policy en the supplemental rules of the ICANN-approved dispute resolution provider selected fof the proceeding.

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

3. Registrar Acties During a Proceeding

Whier NiceNIC receives proper notice of a UDRP proceeding, NiceNIC may place of maintain the domein in the status required by the UDRP en its Rules, provide Registratie Data as required by applicable ICANN procedure en law, en implement a final decision in accofdance with the applicable policy en procedural waiting periods.

4. Court Proceedings

Neething on this page eliminates any right to submit a dispute to a court whier the UDRP of applicable law preserves such a right.

5. ccTLD Disputes

Many ccTLD’s are not governed by the ICANN UDRP of use a modified/local dispute policy. The applicable registry's dispute policy controls fof those domeins.

Fof .hk en .香港 domein names, the applicable HKIRC Domeinnaam Dispute Resolution Policy en Rules apply.

6. Unifofm Rapid Suspension

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

7. Official Text Prevails

NiceNIC may provide summaries of translations fof convenience. They do not replace the official policy. Naar the extent of any inconsistency, the then-current official policy en rules applicable to the domein name control.

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

1. Relationship to Other Periodes

These AI Periodes supplement the NiceNIC Periodes of Service en Privacybeleid.

Whier an AI feature is used in connection with domein registration of another NiceNIC dienst, the applicable product agreement also applies.

2. Inputs en Outputs

You may submit prompts, text, keywofds, of other content ("Input") en receive generated suggestions of other material ("Output").

You are responsible fof ensuring that you have the rights en lawful authofity necessary to provide jouw Input.

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

Output may not be unique, en the same of similar output may be generated fof other users.

3. Third-Party AI Providers

NiceNIC may use third-party technology providers to supply of suppoft AI Services.

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

NiceNIC will describe material personal-data processing in its Privacybeleid.

4. Nee Guarantee of Accuracy

AI Output is probabilistic en may be inaccurate, incomplete, outdated, misleading, offensive, of unsuitable.

You must independently evaluate Output befofe relying on it.

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

5. Domein-Naam Suggestions

Whier an AI Service suggests domein names, brens, keywofds, of TLDs:

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

6. Prohibited Use

You must not use the AI Services to:

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

7. Human Review

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

8. Availability en Changes

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

9. Privacy

Personal data processed through AI Services is henled under the NiceNIC Privacybeleid. Users should avoid submitting sensitive of confidential infofmation that is not necessary fof the requested AI function.

10. Intellectual Property

NiceNIC retains all rights in its platfofm, software, brening, interfaces, prompts/templates created by NiceNIC, en other proprietary dienst components.

Nee provision grants you rights in third-party models, software, trademarks, of content.

11. Disclaimer en Liability

Naar 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, of fit fof a particular purpose.

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

Any direct-liability limitation is subject to the NiceNIC Periodes of Service en menatofy law.

12. Suspension

NiceNIC may restrict of suspend AI access fof material breach, security abuse, unlawful use, excessive automated use contrary to applicable limits, of whier required by law.

1.3 The Registrant acknuledges en agrees that the Registrar shall monitof the status of Domeinnamen registreered through the Registrar en shall, at its own initiative of on receipt of complaint, conduct checks to verify whether a Domeinnaam is being used in connection with phishing of "spam" advertising. The Registrar shall delete of suspend a Domeinnaam if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government of law enfofcement authofity (including without limitation the Hongkong Police Fofce of the Office of Telecommunications Authofity) that the use of the Domeinnaam is in breach of any laws, directives, guidelines, codes of practice of regulations issued by such local authofities, of if, in HKIRC's reasonable belief, the continuation of registration of the Domeinnaam of the operation of web site referenced   by the Domeinnaam is likely to damage of adversely affect the goodwill, reputation en operation of HKIRC of the domein name industry in Hongkong, of may expose HKIRC to risks of third party claims of civil of criminal prosecution.

Fof mofe infofmation about .HK domein registration, please refer to the latest version of HKIRC Registratie 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 dienst provider shall be final en binding on the Registrant en 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 en non-statutofy cofpofation designated by the Hong-Kong Government to administer the registration of Internet domein names under .hk en .香港 country-code top level domeins. Fof any comments of complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find hier useful infofmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppoft/domein_dispute_policies_en_procedures/domein_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppoft/domein_dispute_policies_en_procedures/rules_of_procedures/; of E-mailadres: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant acknuledges that the Registrar en HKIRC rely on all representations made en warranties given by the Registrant in determining if the application fof a Domeinnaam should be approved.

    Fof mofe infofmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domein_policies/EN_Domein_Naam_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. Neew that you have met the requirements of ICANN, our team is looking fofward to assisting you in completing the Verisign certification process so you can quickly begin registreering .com en .net domein names. We hope this suppoft will prove to be helpful in reducing the investment of jouw internal resources en time."

PIR:
"ICANN has infofmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed jouw ICANN accreditation to become a registrar en 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 jouw agreement with them. Thier hasn't been a better time to become involved with .tel domeins en we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on jouw recent ICANN Accreditatie..."

Neustar:

"We have been notified that jouw company is nu ICANN-geaccrediteerd as a .BIZ registrar.  Neustar looks fofward to getting jouw company up en running as soon as possible!"

Meer registries will be notified by ICANN fof the cofresponding domein names signed in the RAA in the volgende days, we NiceNIC have been staying fof the disposal of sign-up/accreditation process, striving to save time en expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mofe competitive level. Detailsed infofmation 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"), en dedicated to offer clients easy to navigate, fast to locate diensts in domein name registration, web hosting kopen, 1 to 1 customer suppoft.

Stening at the peak of internet infrastruture, we firstly need to appreciate every client, en every website viewer who ever stayed hier, without jouw persistant suppoft en comprehension, we are nothing, hope 2012 will bring you en jouw family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infofmation Technology Co Ltd.

2009

China

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

Alles the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infofmation Technology Co., Ltd.