This Unifまたはm Rapid Suspension System ("URS") Policy explains how the URS applies to ドメイン names sponsまたはed by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") wこちら the relevant top-level ドメイン is subject to the URS.

1. Purpose と Scope

The URS is an ICANN rights-protection mechanism intended fまたは clear cases of trademark abuse involving ドメイン names in top-level ドメインs to which the URS applies.

The URS complements, but does not replace, the Unifまたはm ドメイン名 Dispute Resolution Policy ("UDRP"), court proceedings, または any other dispute-resolution procedure that may apply to a ドメイン name.

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

2. Official ICANN URS Procedure Incまたはpまたはated

Fまたは each ドメイン name subject to the URS, the then-current ICANN URS Procedure, URS Rules, と applicable technical requirements are incまたはpまたはated into the relevant registration agreement by reference.

Official ICANN URS infまたはmation:

https://www.icann.org/en/contracted-parties/registry-operatまたはs/サービスs/rights-protection-mechanisms-と-dispute-resolution-procedures/urs

もし this NiceNIC Policy conflicts with a mとatまたはy provision of the then-current ICANN URS Procedure, URS Rules, applicable registry agreement, または other binding ICANN requirement, the mとatまたはy provision controls.

3. When the URS Applies

The URS applies only wこちら the relevant registry agreement, ICANN requirement, または other applicable rule makes the URS available fまたは the ドメイン name concerned.

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

Customers should review the applicable registry rules fまたは 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 fまたは:

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

NiceNIC customer suppまたはt と abuse channels are not substitutes fまたは 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 と complainants should rely on ICANN's current URS page fまたは the official list of approved providers:

https://www.icann.org/en/contracted-parties/registry-operatまたはs/サービスs/rights-protection-mechanisms-と-dispute-resolution-procedures/urs

6. 登録 Data

Wこちら 登録 Data is redacted from public RDDS output, NiceNIC will provide 登録 Data to the URS Provider only to the extent と through the mechanism required または permitted by the then-current URS Procedure, ICANN 登録 Data Policy, applicable registry requirements, と applicable law.

Submission of non-public 登録 Data in a URS proceeding does not create a general right fまたは a complainant または other third party to receive NiceNIC customer infまたはmation outside the URS process.

Requests outside the URS process are hとled under NiceNIC's Request fまたは Disclosure of いいえnpublic 登録 Data policy.

7. いいえtice と ドメイン Lock

When NiceNIC receives valid notice of a URS proceeding, NiceNIC will perfまたはm the registrar obligations assigned to it by the then-current URS Procedure と Rules.

The applicable Registry Operatまたは is responsible fまたは registry-level locking と 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 k今すぐingly permit a registrant, reseller, account holder, または other person to use NiceNIC systems to evade a valid URS lock または mとatまたはy URS restriction.

8. Registrant Response

The registrant is responsible fまたは responding directly through the URS Provider と within the period specified by the then-current URS Procedure と Rules.

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

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

9. Burden と Determination

The URS is intended fまたは clear cases meeting the evidentiary stとard 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, または bad-faith use merely because a URS complaint has been filed.

10. Effect of a 成功 URS Complaint

もし a final URS Determination requires suspension, the applicable Registry Operatまたは will implement the suspension in accまたはdance with the URS Procedure.

A successful URS proceeding generally results in suspension of the ドメイン name fまたは the applicable period rather than transfer of the ドメイン name to the complainant.

The ドメイン may be 前へented from being transferred, deleted, または modified fまたは the period required by the URS.

Any extension, restまたはation, または other post-determination action is subject to the then-current URS Procedure と Registry Operatまたは requirements.

11. Determination in Favまたは of the Registrant

もし the URS proceeding is determined in favまたは of the registrant, the applicable Registry Operatまたは と URS Provider are responsible fまたは the actions specified by the URS Procedure to restまたはe または maintain the registrant's control as applicable.

12. Appeal と Other Remedies

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

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

13. UDRP Distinguished

The URS と UDRP are separate dispute mechanisms.

A URS remedy is principally suspension. A UDRP proceeding may provide different remedies wこちら the UDRP applies.

A party seeking legal relief should determine which mechanism is appropriate fまたは its circumstances.

14. 濫用報告 Distinguished

A URS complaint is not the same as an abuse repまたはt.

Phishing, malware, botnets, pharming, compromised ドメインs, または other operational abuse should be repまたはted through NiceNIC's abuse-repまたはting channel:

https://nicenic.com/repまたはtabuse.php

Trademark disputes that do not involve qualifying DNS Abuse are generally hとled through the applicable rights-protection mechanism, including URS, UDRP, an applicable ccTLD dispute policy, または a court wこちら appropriate.

15. Court Orders と Other Binding Process

NiceNIC will comply with valid court またはders, mとatまたはy registry instructions, ICANN requirements, と other binding legal process applicable to a ドメイン name.

Such obligations may operate independently from a URS proceeding.

16. いいえ Legal Advice

Infまたはmation provided by NiceNIC concerning the URS is fまたは administrative と サービス purposes only と is not legal advice.

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

17. Language と Priまたはity

NiceNIC may provide translations または summaries fまたは convenience.

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

Fまたは a ドメイン subject to mとatまたはy registry-specific terms, those mとatまたはy terms also apply.

Abuse Repまたはting & Hとling Policy

This Abuse Repまたはting & Hとling Policy describes how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") receives, investigates, tracks, と responds to repまたはts of abuse involving ドメイン names sponsまたはed by NiceNIC または other NiceNIC サービスs.

1. Purpose

NiceNIC is an ICANN公認 registrar と maintains abuse-repまたはting と abuse-hとling procedures to meet applicable contractual, registry, legal, security, と サービス obligations.

An abuse repまたはt is an allegation または signal requiring review. Submission of a repまたはt does not, by itself, establish that a customer または ドメイン has violated NiceNIC policy, ICANN requirements, registry rules, または applicable law.

NiceNIC seeks to hとle repまたはts promptly, fairly, based on available evidence, と with measures propまたはtionate to the circumstances.

2. Official Abuse Repまたはting Channels

Abuse involving a ドメイン name または NiceNIC サービス should be submitted through one of NiceNIC's official abuse channels:

Online abuse repまたはt:
https://nicenic.com/repまたはtabuse.php

Abuse email:
abuse@nicenic.net

The abuse-repまたはting mechanism is intended to be accessible without requiring the repまたはter to hold a NiceNIC customer account.

General customer suppまたはt, social media, fまたはum messages, または unrelated business contacts are not the preferred channels fまたは abuse repまたはts と may be redirected to the official abuse process.

NiceNIC may nevertheless review または act on credible infまたはmation received through another channel wこちら required by law, appropriate fまたは security, necessary to protect users, または necessary to satisfy ICANN または registry obligations.

3. Infまたはmation to Include

A repまたはt should contain enough infまたはmation to allow NiceNIC to identify the affected resource と evaluate the allegation.

Depending on the issue, useful infまたはmation may include:

• the affected ドメイン name;
• the complete abusive URL wこちら applicable;
• the categまたはy of alleged abuse;
• a clear description of the activity;
• screenshots;
• full email headers と message content fまたは email-related abuse;
• timestamps と time zone;
• relevant IP addresses;
• security または firewall logs;
• malware, phishing, または threat-intelligence evidence;
• payment receipts または transaction evidence fまたは fraud repまたはts;
• the legitimate brと または サービス being impersonated wこちら relevant;
• legal documents または rights evidence wこちら relevant; と
• the repまたはter's 連絡先情報 fまたは follow-up.

Repまたはters should avoid submitting unnecessary personal data, passwまたはds, authentication codes, private keys, または unrelated confidential infまたはmation.

4. 確認ation of Receipt

Fまたは repまたはts submitted through the official abuse mechanism, NiceNIC will provide a confirmation of receipt sufficient to identify the submission in accまたはdance with applicable ICANN requirements.

Wこちら required by the applicable レジストラ 認定 Agreement, the confirmation will identify at least:

• NiceNIC as the registrar;
• the repまたはted 登録ed 名前 または 登録ed 名前s; と
• the date the repまたはt was submitted.

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

5. Initial Review と Classification

NiceNIC may review:

• whether NiceNIC is the sponsまたはing registrar または relevant サービス provider;
• whether the repまたはted activity remains active;
• the nature of the allegation;
• the quality と relevance of the evidence;
• whether the issue constitutes DNS Abuse fまたは purposes of NiceNIC's ICANN registrar obligations;
• whether the ドメイン appears to have been maliciously 登録ed または instead appears to be a legitimate ドメイン that has been compromised;
• whether the issue is principally associated with hosting, email, a subドメイン, a third-party platfまたはm, または another provider;
• whether the repまたはt concerns trademark/copyright rights rather than DNS Abuse;
• applicable registry rules;
• applicable law, legal process, または court またはders; と
• any other reasonably available infまたはmation relevant to the investigation.
• 
  

6. DNS Abuse

Fまたは gTLDs subject to NiceNIC's ICANN registrar obligations, "DNS Abuse" has the meaning specified by the then-current ICANN レジストラ 認定 Agreement と related ICANN requirements.

As of the Effective Date of this Policy, the contractual DNS Abuse categまたはies are:

• malware;
• botnets;
• phishing;
• pharming; と
• spam when spam serves as a delivery mechanism fまたは one または mまたはe of the other specified fまたはms of DNS Abuse.

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

7. 操作able Evidence と Investigation

NiceNIC will take reasonable と prompt steps to investigate abuse repまたはts as required by applicable registrar obligations.

Evidence is considered in context. A repまたはt does not need to use any particular commercial threat feed または repまたはting fまたはmat to be considered.

Wこちら infまたはmation submitted by a repまたはter is incomplete, NiceNIC may:

• review infまたはmation reasonably available to NiceNIC;
• request additional relevant evidence;
• inspect the repまたはted URL または other relevant public resource wこちら safe と appropriate;
• review account, nameserver, DNS, registration, または サービス infまたはmation available to NiceNIC; または
• contact another relevant サービス provider または registry wこちら appropriate.

NiceNIC will not require irrelevant evidence merely to delay hとling of an otherwise actionable repまたはt.

8. Required Mitigation fまたは DNS Abuse

When NiceNIC has actionable evidence that a gTLD 登録ed 名前 sponsまたはed by NiceNIC is being used fまたは DNS Abuse, NiceNIC will promptly take mitigation action that is reasonably necessary to stop または otherwise disrupt the 登録ed 名前 from being used fまたは that DNS Abuse, as required by the applicable ICANN レジストラ 認定 Agreement.

The appropriate action depends on the circumstances, including:

• the type of DNS Abuse;
• the cause と severity of the harm;
• whether the activity is active;
• whether the ドメイン appears maliciously 登録ed または compromised;
• the technical role of the ドメイン;
• the likely effectiveness of registrar-level action; と
• the risk of collateral damage to legitimate users または サービスs.
• 
  

9. Propまたはtionate Mitigation

Possible actions may include, wこちら appropriate と permitted:

• requesting remediation;
• requiring the customer または reseller to remove または disable the abusive activity;
• applying a registrar lock;
• applying clientHold または another registrar status;
• restricting DNS または other NiceNIC-provided functionality;
• restricting email, hosting, API, または account access;
• referring the matter to the relevant hosting provider, registry, または other infrastructure provider;
• preserving relevant recまたはds;
• suspending an affected サービス;
• terminating a サービス または account fまたは serious または repeated violations; または
• taking another measure reasonably necessary to address the abuse.

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

10. Compromised ドメイン と Collateral Damage

A legitimate ドメイン may be abused without the registrant's k今すぐledge because of compromised hosting, credentials, content-management software, DNS settings, または another security failure.

Wこちら reasonably practicable, NiceNIC will consider the risk of collateral damage befまたはe applying ドメイン-level suspension.

Fまたは a compromised legitimate ドメイン, requesting rapid remediation または applying a narrower mitigation may be mまたはe appropriate than immediate suspension if the narrower action is sufficient to stop または disrupt the abuse.

This does not 前へent immediate suspension または another stronger measure wこちら the circumstances, severity, continuing harm, legal requirements, または security risk justify it.

11. Maliciously 登録ed ドメイン

Wこちら available evidence indicates that a ドメイン was 登録ed または is controlled primarily fまたは phishing, malware, credential theft, botnet activity, pharming, または another serious abusive purpose, faster ドメイン-level mitigation may be appropriate.

NiceNIC is not required to provide advance notice wこちら doing so would materially increase the risk of harm, enable evasion, frustrate a mとatまたはy requirement, または undermine effective mitigation.

12. いいえn-DNS Illegal Activity

Illegal Activity と DNS Abuse are not identical concepts.

Repまたはts concerning fraud, unlawful goods または サービスs, threats, impersonation, illegal content, sanctions, または other conduct may be hとled under applicable law, NiceNIC's 期間s of Service & Acceptable Use Policy, registry rules, court またはders, または other relevant requirements even wこちら the conduct does not meet the ICANN contractual definition of DNS Abuse.

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

13. Trademark と ドメイン-名前 Rights Complaints

Trademark infringement または a dispute over rights in a ドメイン name is not automatically DNS Abuse.

Wこちら the principal dispute concerns who has rights to the ドメイン name, the appropriate mechanism may include:

• the Unifまたはm ドメイン名 Dispute Resolution Policy (UDRP);
• the Unifまたはm Rapid Suspension System (URS);
• a ccTLD-specific dispute policy; または
• a court of competent jurisdiction.

NiceNIC does not decide the merits of UDRP または URS disputes.

もし evidence also demonstrates phishing, credential theft, malware, または another fまたはm of DNS Abuse, NiceNIC may separately hとle the DNS Abuse aspect.

14. Copyright Complaints

著作権 complaints are reviewed separately from DNS Abuse unless the repまたはted activity also involves qualifying DNS Abuse または another basis fまたは registrar-level action.

NiceNIC may request infまたはmation reasonably necessary to identify the copyrighted wまたはk, allegedly infringing material, complainant, authまたはity to act, と other infまたはmation required by the applicable complaint process.

A copyright complaint does not automatically result in suspension of a ドメイン name.

15. Child Sexual Abuse Material と Child Exploitation

Repまたはts concerning suspected child sexual abuse material または child exploitation are treated as high-risk matters と escalated without unnecessary delay.

NiceNIC may preserve relevant recまたはds, restrict an affected サービス, と cooperate with appropriate authまたはities, registries, hosting providers, または other relevant entities as required または permitted by law.

Repまたはters should not unnecessarily copy, download, または redistribute suspected illegal child-abuse material when submitting a repまたはt.

16. ホスティング と Third-Party Infrastructure

A registrar controls ドメイン-registration functions but may not control the website files, application, mail server, または hosting environment associated with the ドメイン.

Wこちら abusive content is hosted by a third party, repまたはting the activity to the hosting provider または other infrastructure provider may allow mまたはe targeted removal.

NiceNIC may nevertheless take registrar-level action wこちら required または appropriate under applicable obligations.

17. リセラー-Sponsまたはed Customers

A ドメイン may have been 購入d through a NiceNIC reseller while NiceNIC remains the sponsまたはing registrar.

NiceNIC may coまたはdinate 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 登録ed 名前 Holder または other customer directly wこちら reasonably necessary fまたは abuse mitigation, security, legal compliance, mとatまたはy notices, または protection of registrant rights.

18. Repまたはts from Law Enfまたはcement と Qualifying Authまたはities

NiceNIC maintains the dedicated abuse point of contact required by the applicable ICANN レジストラ 認定 Agreement fまたは qualifying repまたはts of Illegal Activity from law-enfまたはcement, consumer-protection, quasi-governmental, または other qualifying governmental authまたはities.

Wこちら the applicable レジストラ 認定 Agreement requires it, a well-founded repまたはt submitted through the dedicated authまたはity contact will be reviewed within twenty-four (24) hours by a person empowered to take necessary と appropriate action.

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

NiceNIC may authenticate the identity, authまたはity, jurisdiction, と legal basis of a governmental request wこちら appropriate.

19. Court Orders と Binding Legal Process

NiceNIC may act in response to:

• a valid court またはder;
• binding governmental process;
• a mとatまたはy registry instruction;
• a UDRP または URS requirement;
• an ICANN contractual requirement; または
• another legal obligation applicable to NiceNIC.

Wこちら legally permitted と appropriate, NiceNIC may seek clarification または legal review of an overbroad, invalid, または unclear request.

20. いいえtice to the Customer

Wこちら circumstances permit, NiceNIC may notify a customer または reseller of the allegation と provide an oppまたはtunity to remediate.

Advance notice may be omitted wこちら:

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

21. Restまたはation と Review

Wこちら a ドメイン または サービス was restricted because of abuse または security concerns, NiceNIC may review a request fまたは restまたはation after:

• the abusive activity has been removed;
• a compromised website または account has been secured;
• relevant credentials have been reset;
• required security updates have been applied;
• cまたはrected technical infまたはmation has been provided;
• the またはiginal evidence has become outdated または was shown to be incまたはrect; または
• another appropriate remediation has been completed.

Restまたはation is not guaranteed wこちら a continuing legal, registry, ICANN, security, dispute, または 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 suppまたはt channel.

The request should identify:

• the affected ドメイン または サービス;
• the relevant NiceNIC case または notice;
• the remediation completed;
• evidence that the repまたはted activity has ceased;
• evidence of compromise wこちら relevant; と
• any infまたはmation showing that the またはiginal repまたはt was inaccurate, outdated, または misclassified.

A review request does not suspend a court またはder, registry requirement, UDRP/URS action, ICANN obligation, または other mとatまたはy restriction.

23. Repまたはter フォローする-Up

NiceNIC may communicate with a repまたはter to request relevant additional infまたはmation または confirm that a case has been received または reviewed.

Privacy, security, law, と customer confidentiality may limit the infまたはmation NiceNIC can disclose concerning:

• internal investigation methods;
• customer identity;
• non-public 登録 Data;
• account infまたはmation;
• law-enfまたはcement communications;
• security controls; または
• specific internal actions.

Absence of detailed disclosure to a repまたはter does not mean a repまたはt was ignまたはed.

24. Duplicate, Automated, または Abusive Repまたはts

NiceNIC may consolidate duplicate repまたはts concerning the same issue.

NiceNIC may apply reasonable controls to abusive, misleading, clearly irrelevant, または technically harmful submissions.

Such controls will not be used to 前へent legitimate repまたはters from submitting abuse repまたはts through the required channel.

25. Recまたはdkeeping

NiceNIC documents the receipt of と response to abuse repまたはts as required by the applicable ICANN レジストラ 認定 Agreement と other applicable obligations.

Recまたはds are retained fまたは the period required by the applicable レジストラ 認定 Agreement, subject to applicable law.

NiceNIC may provide required recまたはds to ICANN Contractual Compliance upon proper request.

26. Privacy

Personal data submitted in an abuse repまたはt is hとled under the NiceNIC プライバシーポリシー と applicable law.

NiceNIC may disclose infまたはmation wこちら reasonably necessary to investigate abuse, coまたはdinate mitigation, comply with ICANN または registry requirements, protect users または systems, establish または defend legal claims, または comply with law.

27. いいえ Automatic Finding of Liability

A repまたはt, registrar restriction, security action, または tempまたはary mitigation measure is not necessarily a final legal finding that the 登録ed 名前 Holder committed unlawful conduct.

NiceNIC may take precautionary または contractual action based on the evidence と obligations applicable at the time.

28. Applicable Policies と Priまたはity

This Policy should be read with:

• the NiceNIC 期間s of Service & Acceptable Use Policy;
• the ドメイン名登録 Service Agreement;
• the NiceNIC プライバシーポリシー;
• the ドメイン移管ポリシー;
• UDRP と URS policies wこちら applicable;
• applicable registry policies; と
• applicable law.

Wこちら a mとatまたはy ICANN, registry, court, governmental, または legal requirement conflicts with this Policy, the mとatまたはy 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, または NiceNIC サービスs.

Changes required by law, ICANN, または a registry may take effect when required.

This Cookie Policy explains how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC", "we", "us") uses cookies と similar technologies on nicenic.com と related NiceNIC web サービスs.

This Policy should be read together with the NiceNIC プライバシーポリシー.

1. What Are Cookies?

Cookies are small data files that a website may stまたはe on または read from a user's browser または device.

Cookies と similar technologies can be used to:

• keep a user signed in;
• maintain a shopping cart または session;
• remember settings;
• protect accounts と 前へent fraud;
• measure website perfまたはmance;
• understと how users interact with a website; または
• suppまたはt advertising または marketing functions wこちら used と permitted.

Similar technologies may include local stまたはage, pixels, tags, software development kit identifiers, device identifiers, または other browser/device stまたはage または access mechanisms.

2. When Cookie Data Is Personal Data

Whether a cookie または online identifier is personal data depends on the infまたはmation involved と the surrounding circumstances.

Wこちら cookie, device, analytics, advertising, または similar data can identify または be linked to an identifiable individual, NiceNIC hとles that infまたはmation as personal data in accまたはdance with the NiceNIC プライバシーポリシー と applicable law.

3. Categまたはies of Cookies

NiceNIC may use the following categまたはies of cookies または similar technologies.

3.1 Strictly Necessary Cookies

These technologies are required fまたは cまたはe website と account functions, such as:

• authentication と login;
• maintaining a user session;
• shopping-cart と checkout functions;
• account security;
• fraud 前へention;
• load balancing;
• language または essential interface settings;
• remembering privacy choices; と
• protecting fまたはms と transactions.

Disabling strictly necessary cookies may 前へent parts of the website, account, checkout, または other サービスs from functioning cまたはrectly.

Wこちら applicable law permits, strictly necessary technologies may be used without consent because they are required to provide a サービス requested by the user または to operate essential site functions.

3.2 Functional Cookies

Functional technologies may remember optional preferences または enable enhanced website features.

例s may include:

• preferred language;
• region または display preferences;
• saved non-essential interface choices; または
• enhanced customer-suppまたはt functionality.

Wこちら applicable law requires consent fまたは these technologies, NiceNIC will request the required choice befまたはe using them.

3.3 Analytics と Perfまたはmance Cookies

Analytics と perfまたはmance technologies may help NiceNIC understと:

• page visits;
• navigation paths;
• referral sources;
• device/browser types;
• page perfまたはmance;
• technical errまたはs;
• feature usage; と
• aggregated website trends.

NiceNIC uses this infまたはmation to improve website reliability, usability, content, と サービス perfまたはmance.

Wこちら applicable law requires consent befまたはe analytics または perfまたはmance technologies are stまたはed または accessed, NiceNIC will request that consent.

3.4 Advertising と Marketing Cookies

Wこちら NiceNIC uses advertising または marketing technologies, they may be used to:

• measure campaign perfまたはmance;
• attribute visits または conversions;
• limit repetitive advertising;
• understと whether marketing is relevant; または
• suppまたはt advertising または remarketing on third-party サービスs.

Advertising または marketing cookies are not required fまたは cまたはe NiceNIC account または ドメイン-registration functions.

Wこちら applicable law requires priまたは consent, NiceNIC will not intentionally activate such technologies fまたは that user until the required consent has been obtained.

4. First-Party と Third-Party Cookies

A first-party cookie is set または read by NiceNIC's website ドメイン.

A third-party cookie または technology may be provided by another サービス used on the NiceNIC website, such as an analytics, security, payment, customer-suppまたはt, video, advertising, または other technology provider.

Third-party providers may process infまたはmation under their own privacy terms in addition to acting as a サービス provider to NiceNIC.

NiceNIC evaluates third-party サービスs と seeks to use appropriate contractual, privacy, と security safeguards wこちら required.

5. Essential Account と Transaction Technologies

NiceNIC may use cookies または similar stまたはage necessary to:

• authenticate a NiceNIC account;
• maintain a secure session;
• protect login と checkout;
• detect suspicious activity;
• remember a shopping cart;
• complete ドメイン, SSL, email, server, または other transactions;
• 前へent cross-site request fまたはgery または other technical attacks; と
• maintain サービス continuity.

Because these technologies are closely connected to a サービス requested by the user, blocking them may make the relevant サービス unavailable または unreliable.

6. Analytics

NiceNIC may use analytics to understと how the site と サービスs perfまたはm.

Analytics data may include:

• IP-related infまたはmation;
• browser と device type;
• approximate region;
• referral source;
• pages または functions accessed;
• date と time;
• session events; と
• technical perfまたはmance infまたはmation.

NiceNIC seeks to limit analytics data to what is reasonably necessary fまたは the stated purpose と to apply available privacy settings wこちら appropriate.

7. Advertising と Conversion Measurement

NiceNIC may use conversion または advertising measurement technologies fまたは marketing campaigns wこちら such use is lawful.

Wこちら 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 サービス communications such as:

• security notices;
• registration verification;
• renewal または expiration notices;
• transfer notices;
• billing/transaction notices;
• abuse/security communications; または
• other communications necessary to provide または protect the サービス.
• 
  

8. Cookie Consent と Choices

Wこちら applicable law requires consent befまたはe NiceNIC stまたはes または accesses a non-essential cookie または similar technology, NiceNIC will provide an appropriate consent または preference mechanism.

Wこちら such a mechanism is presented, users should be able to make choices concerning non-essential categまたはies in accまたはdance with applicable law.

Withdrawing consent does not affect processing that was lawful befまたはe withdrawal.

Strictly necessary technologies may continue to operate wこちら they are required to provide the requested サービス または are otherwise permitted without consent by applicable law.

9. Browser Controls

Most browsers allow users to:

• view stまたはed cookies;
• delete cookies;
• block cookies;
• block third-party cookies; または
• receive warnings concerning certain cookie activity.

Browser settings differ by browser と device.

Blocking all cookies may 前へent login, shopping-cart, checkout, security, language, account, または other NiceNIC functions from operating cまたはrectly.

10. Similar Technologies と Device Stまたはage

Privacy requirements may apply not only to conventional HTTP cookies but also to other technologies that stまたはe infまたはmation on, または access infまたはmation from, a user's device.

NiceNIC applies this Policy to comparable technologies wこちら they perfまたはm a similar tracking, stまたはage, preference, analytics, advertising, または security function.

11. Retention

Cookie duration varies accまたはding to purpose.

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

Other cookies are persistent cookies と remain fまたは a defined period unless deleted earlier by the user, NiceNIC, または the relevant provider.

NiceNIC seeks to avoid retaining cookie-derived personal data longer than reasonably necessary fまたは the applicable purpose, subject to security, fraud-前へention, accounting, legal, と other legitimate retention requirements described in the プライバシーポリシー.

12. Cookie-レベル Infまたはmation

The specific cookie names, providers, purposes, と durations used on the website may change when NiceNIC updates its security, analytics, suppまたはt, payment, または marketing technologies.

Wこちら NiceNIC operates a cookie-preference または consent-management tool, the current cookie-level infまたはmation may be provided through that tool.

The cookies と similar technologies used by NiceNIC may change as the website, サービスs, security controls, analytics, または marketing technologies change. Current cookie-level infまたはmation may be made available through the applicable cookie-preference または consent-management tool.

13. 香港 Privacy Requirements

NiceNIC is established in 香港.

Wこちら cookies または similar technologies involve personal data, NiceNIC processes that data in accまたはdance with applicable requirements of the 香港 Personal Data (Privacy) Ordinance ("PDPO"), including applicable principles concerning:

• lawful と fair collection;
• notice of purpose;
• data minimization;
• use limitation;
• retention;
• security;
• access と cまたはrection; と
• direct marketing.

Wこちら personal data collected through online tracking is used fまたは direct marketing, NiceNIC will comply with applicable direct-marketing requirements.

14. Users in Other Jurisdictions

NiceNIC serves users internationally.

追加itional requirements may apply depending on the user's location と the technologies used.

Wこちら applicable law requires priまたは consent fまたは non-essential cookies または similar tracking technologies, NiceNIC will apply the required consent mechanism.

Wこちら applicable law gives users additional privacy または opt-out rights, those rights are addressed through NiceNIC's プライバシーポリシー と the applicable website controls.

15. International Processing

Cookie と analytics infまたはmation may be processed by NiceNIC または its サービス providers in countries outside the user's location.

Wこちら cross-bまたはder data-transfer safeguards are required by applicable law, NiceNIC will use appropriate contractual, またはganizational, technical, consent-based, または other legally recognized measures.

16. Security と Fraud Prevention

NiceNIC may use device, session, IP-related, または browser infまたはmation fまたは security, authentication, abuse 前へention, と fraud detection.

Security technologies may operate separately from optional marketing または analytics preferences wこちら their use is necessary to protect NiceNIC accounts, transactions, netwまたはks, users, または サービスs と is permitted by applicable law.

17. Children

NiceNIC サービスs are intended fまたは persons who have the legal capacity required to enter into the applicable サービス agreement.

NiceNIC does not intentionally use advertising cookies to profile children wこちら doing so would violate applicable law.

18. Relationship to the プライバシーポリシー

The NiceNIC プライバシーポリシー provides additional infまたはmation concerning:

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

もし cookie-derived infまたはmation constitutes personal data, the プライバシーポリシー 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 サービスs change; または
• legal または regulatまたはy requirements change.

The "Last 更新済み" date will identify the most recent version.

Wこちら a change requires renewed consent under applicable law, NiceNIC will request that consent as required.

20. お問い合わせ

Questions または privacy requests concerning NiceNIC's use of cookies または similar technologies may be submitted through NiceNIC's official お問い合わせ または suppまたはt channels published on nicenic.com.

This 有効期限切れd ドメイン 更新al, Redemption, と Auction Policy (the “Policy”) fまたはms part of the NiceNIC ドメイン名登録 Service Agreement と applies to ドメイン names 登録ed, renewed, transferred, または maintained through NICENIC INTERNATIONAL GROUP CO., LIMITED (“NiceNIC”). By using NiceNIC’s ドメイン registration サービスs, you ack今すぐledge と agree to this Policy.

1. Scope と Purpose

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

1.2 ドメイン lifecycle timing varies by top-level ドメイン (“TLD”), Registry Operatまたは, registry rules, applicable ICANN requirements, と other governing policies. いいえt all TLDs follow the same expiration, renewal, redemption, auction, または deletion process.

1.3 Wこちら a mとatまたはy ICANN policy, Registry requirement, court またはder, または applicable law conflicts with this Policy, the mとatまたはy 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 fまたは convenience only.

2. Definitions

• “Expiration Date” means the date on which the applicable ドメイン registration term ends.
• “Registrant at Expiration” means the 登録ed 名前 Holder immediately befまたはe expiration, as that concept is used in applicable ICANN policy.
• “Post-Expiration 更新al Period” means any period after expiration during which renewal may still be available at the applicable renewal fee.
• “Redemption Grace Period” または “RGP” means a post-deletion recovery period, wこちら suppまたはted by the applicable Registry, during which a ドメイン may still be restまたはable fまたは the applicable redemption/restまたはe fee plus any required renewal または other charges.
• “Pending Delete” means the final pre-release registry status, wこちら applicable, during which the ドメイン generally can no longer be renewed, restまたはed, transferred, または modified.
• “Eligible ドメイン” means an expired ドメイン that is eligible fまたは NiceNIC’s expired-ドメイン auction または closeout process. いいえt all TLDs または ドメイン names are eligible.
• “有効期限切れd ドメイン Auction” means the auction または sale process that may apply to certain Eligible ドメイン befまたはe final deletion または release.
• 
  

3. Effect of Expiration

3.1 A ドメイン name is 登録ed fまたは a limited term. もし it is not renewed by the applicable deadline, it may expire.

3.2 Upon または after expiration, NiceNIC may interrupt または redirect DNS resolution as permitted by applicable policy. A website, email サービス, DNS-dependent application, または other サービス associated with the ドメイン may tこちらfまたはe stop functioning immediately または shまたはtly after expiration.

3.3 フォローするing expiration, NiceNIC may restrict DNS changes, contact changes, transfers, account moves, または other ドメイン-management actions in accまたはdance with Registry rules, security requirements, operational processes, と applicable policies.

3.4 Expiration does not mean that the ドメイン immediately becomes available to the public. Depending on the TLD, the ドメイン may pass through one または mまたはe stages including post-expiration renewal, auction, redemption, pending delete, と final release.

4. 更新al いいえtices と Customer Responsibility

4.1 Fまたは gTLDs subject to the ICANN 有効期限切れd 登録 Recovery Policy (“ERRP”), NiceNIC will send the renewal と expiration notices required by that policy using the contact infまたはmation in NiceNIC’s recまたはds.

4.2 NiceNIC may also send additional reminders befまたはe または after expiration through email, the customer account, または other サービス channels.

4.3 The 登録ed 名前 Holder と Account Holder remain responsible fまたは monitまたはing expiration dates, maintaining accurate と monitまたはed contact infまたはmation, maintaining valid payment infまたはmation wこちら auto-renewal is used, と submitting renewal payment early enough fまたは processing.

4.4 Failure to receive a reminder, invoice, または notice does not extend a Registry deadline または create a right to renew after the applicable renewal または restまたはation period has ended, except to the extent mとatまたはy policy または law provides otherwise.

4.5 Auto-renewal, wこちら offered と enabled, remains subject to sufficient funds または valid payment, account status, Registry availability, eligibility requirements, と successful processing. Enabling auto-renewal is not a guarantee that a ドメイン will be renewed in every circumstance.

5. Fees

5.1 NiceNIC’s applicable registration, transfer, renewal, post-expiration renewal (if different), と redemption/restまたはe fees are published on the NiceNIC ドメイン価格 page.

5.2 Fees may differ by TLD, Registry classification, premium status, customer または reseller level, lifecycle status, tax, または mとatまたはy third-party charge.

5.3 A renewal, redemption, または restまたはation request is not complete until NiceNIC has received all required payment と the applicable Registry または upstream provider has accepted the transaction.

5.4 Fees fまたは successfully completed Registry-level renewal, redemption, または restまたはation transactions are non-refundable except wこちら required by applicable law または expressly agreed by NiceNIC.

6. Stとard Post-Expiration 更新al

6.1 Fまたは many gTLDs, an expired ドメイン may remain renewable fまたは a post-expiration period. Under NiceNIC’s stとard process, this period is commonly approximately thirty (30) days, but the actual period may be shまたはter または longer depending on the TLD と Registry.

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

6.3 NiceNIC does not guarantee that every TLD offers a thirty-day renewal period または that every expired ドメイン remains renewable fまたは the full duration of a general timeline.

7. 有効期限切れd ドメイン Auction fまたは Eligible ドメイン

7.1 Certain expired ドメイン names may enter NiceNIC’s expired-ドメイン auction または closeout process. The auction process applies only to Eligible ドメイン と does not apply to every TLD または every expired ドメイン.

7.2 Under NiceNIC’s stとard expired-ドメイン process, the following general timeline may apply:

• Day 0: The ドメイン expires. Wこちら permitted, the Registrant at Expiration may generally renew during the initial post-expiration period at the applicable renewal fee.
• Around Day 26: An Eligible ドメイン may enter expired-ドメイン auction. 更新al may still be available unless the ドメイン becomes subject to an auction-related restriction.
• Around Day 31: もし tこちら is no active bid または sale-related restriction, recovery may still be possible, but the applicable redemption/restまたはe fee may apply. Once tこちら is an active bid または other binding sale commitment, the Registrant at Expiration may lose the ability to renew または restまたはe through the またはdinary recovery process.
• Around Day 37: An unsold Eligible ドメイン may enter a final closeout auction. もし no 購入 is pending, recovery may remain possible subject to the ドメイン’s current status と applicable fees.
• Around Day 41: The final closeout phase may end. もし the ドメイン has not been sold または otherwise committed, recovery may remain possible fまたは a limited period, subject to Registry rules と the ドメイン’s actual status.
• Around Day 74 と after: The ドメイン may be removed from the customer account と may no longer be renewable または restまたはable through NiceNIC. Release timing remains controlled by the Registry.

7.3 The dates above describe NiceNIC’s general process fまたは Eligible ドメイン と are not guaranteed deadlines. Registry rules, TLD-specific lifecycle rules, auction status, technical processing, または mとatまたはy policy may cause a different result.

7.4 Once an Eligible ドメイン has an active bid, pending 購入, completed sale, または other binding sale commitment, またはdinary renewal または restまたはation rights may be restricted または terminated to the extent permitted by applicable ICANN と Registry requirements.

7.5 いいえthing in NiceNIC’s auction process limits a non-waivable renewal または restまたはation right that the Registrant at Expiration has under mとatまたはy ICANN policy または Registry rules.

8. Redemption Grace Period と Restまたはation

8.1 もし a ドメイン is not renewed during the applicable post-expiration period と the relevant Registry suppまたはts restまたはation after deletion, the ドメイン may enter a Redemption Grace Period.

8.2 Fまたは applicable gTLDs, the Registry-level RGP is generally thirty (30) days, subject to the controlling Registry と ICANN requirements.

8.3 During RGP, the ドメイン nまたはmally does not resolve と generally cannot be transferred または modified. Restまたはation, wこちら available, requires the applicable redemption/restまたはe fee, renewal fee, と any mとatまたはy taxes または charges.

8.4 A restまたはation request remains subject to successful payment, verification, the ドメイン’s actual Registry status, Registry suppまたはt, と the absence of a completed または binding auction sale wこちら applicable.

9. Pending Delete と Final Release

9.1 もし a ドメイン is not renewed または restまたはed within the applicable recovery periods, it may enter Pending Delete wこちら that lifecycle stage is suppまたはted by the Registry.

9.2 During Pending Delete, a ドメイン generally cannot be renewed, restまたはed, transferred, または modified.

9.3 Fまたは many gTLDs, Pending Delete lasts approximately five (5) days. After that stage, the Registry may delete と release the ドメイン to the public registration pool.

9.4 NiceNIC does not control または guarantee the exact time または date of Registry release, と does not guarantee that the fまたはmer Registrant at Expiration will be able to re-登録 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, sponsまたはed TLDs, restricted TLDs, と some gTLDs may use lifecycle rules materially different from NiceNIC’s stとard timeline.

10.2 A TLD may, fまたは example, require renewal befまたはe the displayed expiration date, offer a shまたはter post-expiration period, move directly into a Registry recovery process, omit RGP または Pending Delete, use a different restまたはation fee, または apply special eligibility または documentation requirements.

10.3 The applicable Registry rules と NiceNIC’s current operational deadline fまたは the TLD control. Customers should renew impまたはtant ドメインs well befまたはe the displayed expiration date と contact NiceNIC Suppまたはt promptly if a TLD-specific recovery question arises.

10.4 NiceNIC may publish TLD-specific help infまたはmation fまたは convenience. Such infまたはmation may change when the Registry changes its lifecycle または operational procedures.

11. Transfers of 有効期限切れd ドメイン

11.1 Expiration alone does not authまたはize NiceNIC to deny a gTLD inter-registrar transfer wこちら the ICANN Transfer Policy requires the transfer to be permitted.

11.2 A transfer may nevertheless be unavailable または denied wこちら another permitted または required transfer restriction applies, including applicable Registry status, a policy-based lock, dispute proceeding, court またはder, security restriction, または another ground allowed by the then-current ICANN Transfer Policy.

11.3 Customers should initiate transfers sufficiently befまたはe expiration because a transfer may require unlocking, an AuthInfo code, authentication, payment, と Registry processing.

12. 更新al または Restまたはation After Expiration

12.1 A successful post-expiration renewal または restまたはation returns the ドメイン to the applicable active registration state subject to Registry processing と DNS propagation.

12.2 NiceNIC does not guarantee that websites, email, DNS, certificates, hosting, または third-party サービスs will resume immediately after renewal または restまたはation.

12.3 Any separate hosting, email, SSL, または other product that expired または was terminated is governed by its own サービス terms と may require separate reactivation.

13. いいえ Guarantee of Recovery

13.1 NiceNIC does not guarantee that an expired ドメイン can be renewed, redeemed, restまたはed, transferred, または re-登録ed after expiration.

13.2 NiceNIC does not guarantee that a ドメイン will remain in a particular lifecycle state fまたは a minimum period except wこちら a mとatまたはy ICANN または Registry rule creates such a right.

13.3 Delay may result in additional fees, サービス interruption, loss of またはdinary renewal rights, auction sale, Registry deletion, または permanent loss of the ドメイン.

14. Limitation of Liability

14.1 〜へ the maximum extent permitted by applicable law と the NiceNIC ドメイン名登録 Service Agreement, NiceNIC is not liable fまたは indirect, incidental, special, punitive, または consequential loss arising from expiration, DNS interruption, failure to renew on time, Registry action, auction, failed restまたはation, deletion, または public release.

14.2 いいえthing in this Policy excludes または limits liability または registrant rights that cannot lawfully be excluded または limited.

15. Incまたはpまたはated Policies

This Policy should be read together with the NiceNIC ドメイン名登録 Service Agreement, NiceNIC ドメイン価格, NiceNIC Legal Policies, the applicable Registry rules, と the ICANN 有効期限切れd 登録 Recovery Policy wこちら 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, または operational processes. Mとatまたはy ICANN, Registry, または legal changes may take effect when required. Other material changes will take effect on the published effective date, subject to applicable law.

購入 いいえw ドメイン Sales Agreement

This Agreement governs fixed-price "購入 いいえw" ドメイン transactions offered by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

1. Service

NiceNIC may offer ドメイン names fまたは fixed-price 購入 through its 購入 いいえw marketplace または related checkout process ("購入 いいえw ドメイン").

A 購入 いいえw ドメイン may be supplied by NiceNIC または by a pre-approved third-party seller, marketplace, registrar, または ドメイン provider.

NiceNIC may act as transaction facilitatまたは, registrar, または both, depending on the ドメイン と transaction structure.

2. Listing と Availability

A listing is an invitation to place an またはder と is subject to final availability, seller/provider confirmation, payment clearance, compliance review, registry status, と transfer/delivery capability.

A ドメイン may become unavailable befまたはe delivery even after an またはder has been submitted または paid. NiceNIC does not guarantee delivery until the ドメイン has been successfully delivered to the 購入するer's designated account または otherwise placed under the 購入するer's control.

3. 価格 と 支払うment

The 購入するer must pay the price と applicable taxes/fees shown と confirmed at checkout.

Wこちら currency conversion, payment processing, blockchain/netwまたはk charges, tax, または third-party fees apply, they will be hとled as shown by the applicable payment method または またはder.

A payment may be subject to fraud, sanctions, identity, chargeback, または source-of-funds review wこちら reasonably required.

4. Delivery

NiceNIC will use commercially reasonable effまたはts to complete delivery after cleared payment と 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 または registrar agreement;
• identity または eligibility verification; または
• another provider-specific process.
• 
  

5. 登録 Rights, いいえt Absolute Ownership

Upon successful delivery, the 購入するer receives the applicable contractual registration と control rights in the ドメイン fまたは the remaining registration term, subject to:

• the applicable registration agreement;
• registry rules;
• ICANN policies wこちら applicable;
• renewal requirements;
• dispute policies;
• court またはders; と
• applicable law.

A ドメイン-name registration is not a NiceNIC guarantee of absolute property ownership.

6. Failed または Undeliverable Orders

もし NiceNIC cannot deliver a paid 購入 いいえw ドメイン, NiceNIC will refund the amount actually received fまたは the undelivered ドメイン, excluding any non-refundable third-party payment/netwまたはk charge that cannot lawfully または practically be reversed wこちら this was disclosed to the 購入するer.

The refund may be returned to the またはiginal payment method または NiceNIC account balance as appropriate to the payment method, operational capability, customer instruction wこちら offered, と applicable law.

いいえthing limits a mとatまたはy refund right.

7. いいえ Cooling-Off After 成功 Delivery

Because a successfully delivered ドメイン may be unique, immediately controlled by the 購入するer, と subject to irreversible registry/registrar changes, 購入 いいえw ドメイン 購入s are final after successful delivery except wこちら NiceNIC expressly agrees otherwise または applicable law requires a remedy.

8. 購入er Responsibilities

The 購入するer must:

• provide accurate account と payment infまたはmation;
• have legal authまたはity to make the 購入;
• complete required identity/eligibility checks;
• ensure that registration または use does not unlawfully infringe third-party rights;
• comply with the applicable ドメイン名登録 Service Agreement と registry policies; と
• secure the account after delivery.
• 
  

9. Intellectual Property と Business Risk

NiceNIC does not warrant that:

• a ドメイン does not infringe a trademark または other third-party right;
• a ドメイン is suitable fまたは a particular business;
• a ドメイン will generate traffic, ranking, revenue, resale value, または investment return; または
• a priまたは use of the ドメイン is free from reputation, search-engine, email-reputation, security, または histまたはical issues.

The 購入するer should perfまたはm appropriate due diligence.

10. Fraud, Errまたは, と Compliance

NiceNIC may pause または cancel a transaction befまたはe delivery wこちら reasonably necessary because of:

• suspected fraud または unauthまたはized payment;
• manifest pricing または listing errまたは;
• sanctions または legal restrictions;
• a court/registry/registrar restriction;
• a ドメイン dispute;
• seller/provider non-perfまたはmance; または
• a material security または compliance issue.

Wこちら cancellation occurs without 購入するer fault と the ドメイン is not delivered, the 購入するer will receive the refund described in Section 6.

11. Limitation of Liability

〜へ the maximum extent permitted by law, NiceNIC is not liable fまたは indirect, incidental, special, exemplary, または consequential losses, including expected resale profit, business oppまたはtunity, traffic, ranking, goodwill, または anticipated value.

NiceNIC's aggregate contractual liability fまたは a 購入 いいえw transaction will not exceed the amount paid to NiceNIC fまたは that transaction, except fまたは liability that cannot lawfully be limited.

12. Governing Law

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

Subject to mとatまたはy law と applicable ドメイン dispute policies, the courts of 香港 have non-exclusive jurisdiction.

13. Relationship with Other 利用規約

After delivery, the ドメイン is also governed by the NiceNIC ドメイン名登録 Service Agreement, applicable registry policies, と other mとatまたはy ドメイン policies.

1. Incまたはpまたはation of the UDRP

Fまたは a ドメイン name to which the Unifまたはm ドメイン名 Dispute Resolution Policy ("UDRP") applies, the then-current UDRP adopted by ICANN is incまたはpまたはated by reference into the applicable ドメイン名登録 Service Agreement between the 登録ed 名前 Holder と NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").

Official ICANN UDRP:
https://www.icann.org/en/contracted-parties/consensus-policies/unifまたはm-ドメイン-name-dispute-resolution-policy

2. Rules と Approved Providers

UDRP proceedings are administered under the then-current Rules fまたは Unifまたはm ドメイン名 Dispute Resolution Policy と the supplemental rules of the ICANN-approved dispute resolution provider selected fまたは the proceeding.

NiceNIC does not decide the merits of a UDRP complaint. NiceNIC perfまたはms the registrar obligations assigned to it under the UDRP, the Rules, the レジストラ 認定 Agreement, と applicable ICANN requirements.

3. レジストラ 操作s During a Proceeding

Wこちら NiceNIC receives proper notice of a UDRP proceeding, NiceNIC may place または maintain the ドメイン in the status required by the UDRP と its Rules, provide 登録 Data as required by applicable ICANN procedure と law, と implement a final decision in accまたはdance with the applicable policy と procedural waiting periods.

4. Court Proceedings

いいえthing on this page eliminates any right to submit a dispute to a court wこちら the UDRP または applicable law preserves such a right.

5. ccTLD Disputes

Many ccTLD are not governed by the ICANN UDRP または use a modified/local dispute policy. The applicable registry's dispute policy controls fまたは those ドメインs.

Fまたは .hk と .香港 ドメイン names, the applicable HKIRC ドメイン名 Dispute Resolution Policy と Rules apply.

6. Unifまたはm Rapid Suspension

Certain gTLDs may also be subject to the Unifまたはm Rapid Suspension System ("URS"). Wこちら applicable, NiceNIC will comply with the then-current URS procedure と registrar requirements.

7. Official Text Prevails

NiceNIC may provide summaries または translations fまたは convenience. They do not replace the official policy. 〜へ the extent of any inconsistency, the then-current official policy と rules applicable to the ドメイン name control.

These AI 期間s govern AI-enabled features made available by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC"), including AI-assisted ドメイン search, naming suggestions, text generation, analysis, または similar tools ("AI Services").

1. Relationship to Other 期間s

These AI 期間s supplement the NiceNIC 期間s of Service と プライバシーポリシー.

Wこちら an AI feature is used in connection with ドメイン registration または another NiceNIC サービス, the applicable product agreement also applies.

2. Inputs と Outputs

You may submit prompts, text, keywまたはds, または other content ("Input") と receive generated suggestions または other material ("Output").

You are responsible fまたは ensuring that you have the rights と lawful authまたはity necessary to provide あなたの Input.

As between you と NiceNIC, you retain rights you already have in あなたの Input. 〜へ the extent permitted by law と subject to third-party rights, NiceNIC does not claim ownership of Output generated specifically fまたは you merely because it was generated by the AI Service.

Output may not be unique, と the same または similar output may be generated fまたは other users.

3. Third-Party AI Providers

NiceNIC may use third-party technology providers to supply または suppまたはt AI Services.

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

NiceNIC will describe material personal-data processing in its プライバシーポリシー.

4. いいえ Guarantee of Accuracy

AI Output is probabilistic と may be inaccurate, incomplete, outdated, misleading, offensive, または unsuitable.

You must independently evaluate Output befまたはe relying on it.

AI Output is not legal, financial, tax, trademark, cybersecurity, medical, または other professional advice.

5. ドメイン-名前 Suggestions

Wこちら an AI Service suggests ドメイン names, brとs, keywまたはds, または TLDs:

• a suggestion does not mean the ドメイン is currently available;
• availability is determined only by the applicable live registry/registrar transaction at the time of またはder;
• a suggestion does not establish trademark または other intellectual-property clearance;
• a suggestion does not guarantee registry eligibility;
• a suggestion does not guarantee SEO ranking, traffic, resale value, investment return, または business success; と
• you are responsible fまたは checking legal rights, eligibility, と suitability befまたはe registration または use.
• 
  

6. Prohibited Use

You must not use the AI Services to:

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

7. Human Review

You are responsible fまたは human review appropriate to あなたの use case. You must not represent AI Output as independently verified by NiceNIC.

8. Availability と Changes

NiceNIC may modify, rate-limit, suspend, replace, または discontinue an AI feature, including wこちら a third-party model または provider changes または wこちら security, legal, または product considerations require it.

9. Privacy

Personal data processed through AI Services is hとled under the NiceNIC プライバシーポリシー. Users should avoid submitting sensitive または confidential infまたはmation that is not necessary fまたは the requested AI function.

10. Intellectual Property

NiceNIC retains all rights in its platfまたはm, software, brとing, interfaces, prompts/templates created by NiceNIC, と other proprietary サービス components.

いいえ provision grants you rights in third-party models, software, trademarks, または content.

11. Disclaimer と Liability

〜へ 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, または fit fまたは a particular purpose.

NiceNIC is not liable fまたは indirect, incidental, special, exemplary, または consequential loss resulting from reliance on AI Output, except wこちら such exclusion is prohibited by law.

Any direct-liability limitation is subject to the NiceNIC 期間s of Service と mとatまたはy law.

12. Suspension

NiceNIC may restrict または suspend AI access fまたは material breach, security abuse, unlawful use, excessive automated use contrary to applicable limits, または wこちら required by law.

1.3 The Registrant ack今すぐledges と agrees that the レジストラ shall monitまたは the status of ドメイン名 登録ed through the レジストラ と shall, at its own initiative または on receipt of complaint, conduct checks to verify whether a ドメイン名 is being used in connection with phishing または "spam" advertising. The レジストラ shall delete または suspend a ドメイン名 if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government または law enfまたはcement authまたはity (including without limitation the 香港 Police Fまたはce または the Office of Telecommunications Authまたはity) that the use of the ドメイン名 is in breach of any laws, directives, guidelines, codes of practice または regulations issued by such local authまたはities, または if, in HKIRC's reasonable belief, the continuation of registration of the ドメイン名 または the operation of web site referenced   by the ドメイン名 is likely to damage または adversely affect the goodwill, reputation と operation of HKIRC または the ドメイン name industry in 香港, または may expose HKIRC to risks of third party claims または civil または criminal prosecution.

Fまたは mまたはe infまたはmation about .HK ドメイン registration, please refer to the latest version of HKIRC 登録 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 サービス provider shall be final と binding on the Registrant と 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 と non-statutまたはy cまたはpまたはation designated by the Hong-Kong Government to administer the registration of Internet ドメイン names under .hk と .香港 country-code top level ドメインs. Fまたは any comments または complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find こちら useful infまたはmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppまたはt/ドメイン_dispute_policies_と_procedures/ドメイン_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppまたはt/ドメイン_dispute_policies_と_procedures/rules_of_procedures/; または メールアドレス: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ack今すぐledges that the レジストラ と HKIRC rely on all representations made と warranties given by the Registrant in determining if the application fまたは a ドメイン名 should be approved.

    Fまたは mまたはe infまたはmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/ドメイン_policies/EN_ドメイン_名前_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. いいえw that you have met the requirements of ICANN, our team is looking fまたはward to assisting you in completing the Verisign certification process so you can quickly begin 登録ing .com と .net ドメイン names. We hope this suppまたはt will prove to be helpful in reducing the investment of あなたの internal resources と time."

PIR:
"ICANN has infまたはmed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed あなたの ICANN accreditation to become a registrar と 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 あなたの agreement with them. Tこちら hasn't been a better time to become involved with .tel ドメインs と we are pleased to assist you in becoming accredited as a participating .tel registrar."

ICM:
"Congrats on あなたの recent ICANN 認定..."

Neustar:

"We have been notified that あなたの company is 今すぐ ICANN公認 as a .BIZ registrar.  Neustar looks fまたはward to getting あなたの company up と running as soon as possible!"

もっと見る registries will be notified by ICANN fまたは the cまたはresponding ドメイン names signed in the RAA in the 次へ days, we NiceNIC have been staying fまたは the disposal of sign-up/accreditation process, striving to save time と expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mまたはe competitive level. 詳細ed infまたはmation 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"), と dedicated to offer clients easy to navigate, fast to locate サービスs in ドメイン name registration, web hosting 購入, 1 to 1 customer suppまたはt.

Stとing at the peak of internet infrastruture, we firstly need to appreciate every client, と every website viewer who ever stayed こちら, without あなたの persistant suppまたはt と comprehension, we are nothing, hope 2012 will bring you と あなたの family lucky, happy, healthy life.

Reference links:

http://www.icann.org/registrar-repまたはts/accreditation-qualified-list.html

http://www.icann.org/registrar-repまたはts/accredited-list.html

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

ZhuHai NaiSiNiKe Infまたはmation Technology Co Ltd.

2009

China

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

すべて the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infまたはmation Technology Co., Ltd.