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, АПИ, Или 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 Перенос домена Policy;
• 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 ccTLDs, 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 ccTLDs 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. Prohiбитed 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 prohiбитed 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 prohiбитed 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 Телефонecommunications 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 arбитration 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."

Телефонnic:
"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.