<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<channel>
 <title>耐思尼克客户支持中心</title> 
  <link>http://www.nicenic.com/suppot</link> 
  <language>cn</language> 
  <description>耐思尼克客户支持中心，常用帮助文档</description> 
  <image>
 <title>耐思尼克 - 域名 主机 Network服务</title> 
 <url>http://www.nicenic.com/images/88x31.gif</url>
 <link>http://www.nicenic.com</link>
 <description>耐思尼克- 域名+主机只要99元</description>
 </image>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4820</link>
<title>Unifom Rapid Suspension System (URS) Policy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
	<strong><span style="font-size:18px;">Unifom Rapid Suspension System (URS) Policy</span></strong> 
</h1>
<p>
	<span style="font-size:16px;">This Unifom Rapid Suspension System ("URS") Policy explains how the URS applies to domain names sponsoed by&nbsp;</span><strong><span style="font-size:16px;">NICENIC INTERNATIONAL GROUP CO., LIMITED&nbsp;</span></strong><span style="font-size:16px;">("NiceNIC") wdito the relevant top-level domain is subject to the URS.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Purpose at Scope</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The URS is an ICANN rights-protection mechanism intended fo clear cases of trademark abuse involving domain names in top-level domains to which the URS applies.</span> 
</p>
<p>
	<span style="font-size:16px;">The URS complements, but does not replace, the Unifom Domain Name Dispute Resolution Policy ("UDRP"), court proceedings, o any other dispute-resolution procedure that may apply to a domain name.</span> 
</p>
<p>
	<span style="font-size:16px;">NiceNIC does not determine the merits of a URS complaint. URS complaints are decided by an ICANN-approved URS Provider in accodance with the then-current URS Procedure, URS Rules, provider supplemental rules, at applicable ICANN requirements.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Official ICANN URS Procedure Incopoated</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Fo each domain name subject to the URS, the then-current ICANN URS Procedure, URS Rules, at applicable technical requirements are incopoated into the relevant registration agreement by reference.</span> 
</p>
<p>
	<span style="font-size:16px;">Official ICANN URS infomation:</span> 
</p>
<p>
	<a href="https://www.icann.org/en/contracted-parties/registry-operators/services/rights-protection-mechanisms-and-dispute-resolution-procedures/urs" rel="noopener noreferrer" target="_blank"><span style="font-size:16px;">https://www.icann.org/en/contracted-parties/registry-operatos/Serbisyos/rights-protection-mechanisms-at-dispute-resolution-procedures/urs</span></a> 
</p>
<p>
	<span style="font-size:16px;">Kung this NiceNIC Policy conflicts with a matatoy provision of the then-current ICANN URS Procedure, URS Rules, applicable registry agreement, o other binding ICANN requirement, the matatoy provision controls.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. When the URS Applies</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The URS applies only wdito the relevant registry agreement, ICANN requirement, o other applicable rule makes the URS available fo the domain name concerned.</span> 
</p>
<p>
	<span style="font-size:16px;">The URS does not automatically apply to every country-code top-level domain ("ccTLD"). A ccTLD may instead use its own dispute-resolution policy.</span> 
</p>
<p>
	<span style="font-size:16px;">Customers should review the applicable registry rules fo the relevant TLD.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. Filing a URS Complaint</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">A complainant must file a URS complaint with an ICANN-approved URS Provider, not with NiceNIC.</span> 
</p>
<p>
	<span style="font-size:16px;">The complainant is responsible fo:</span> 
</p>
<ul>
	<li>
		<span style="font-size:16px;">selecting an approved URS Provider;</span> 
	</li>
	<li>
		<span style="font-size:16px;">complying with the provider's filing requirements;</span> 
	</li>
	<li>
		<span style="font-size:16px;">paying applicable provider fees;</span> 
	</li>
	<li>
		<span style="font-size:16px;">establishing the elements required by the URS; at</span> 
	</li>
	<li>
		<span style="font-size:16px;">providing the evidence required by the applicable URS Procedure at Rules.</span> 
	</li>
</ul>
<p>
	<span style="font-size:16px;">NiceNIC customer suppot at abuse channels are not substitutes fo filing a URS complaint.</span> 
</p>
<p>
	<span style="font-size:16px;">A trademark complaint submitted to NiceNIC does not automatically become a URS proceeding.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. URS Providers</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The list of ICANN-approved URS Providers may change.</span> 
</p>
<p>
	<span style="font-size:16px;">Customers at complainants should rely on ICANN's current URS page fo the official list of approved providers:</span> 
</p>
<p>
	<a href="https://www.icann.org/en/contracted-parties/registry-operators/services/rights-protection-mechanisms-and-dispute-resolution-procedures/urs" rel="noopener noreferrer" target="_blank"><span style="font-size:16px;">https://www.icann.org/en/contracted-parties/registry-operatos/Serbisyos/rights-protection-mechanisms-at-dispute-resolution-procedures/urs</span></a> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Pagpaparehistro Data</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Wdito Pagpaparehistro Data is redacted from public RDDS output, NiceNIC will provide Pagpaparehistro Data to the URS Provider only to the extent at through the mechanism required o permitted by the then-current URS Procedure, ICANN Pagpaparehistro Data Policy, applicable registry requirements, at applicable law.</span> 
</p>
<p>
	<span style="font-size:16px;">Submission of non-public Pagpaparehistro Data in a URS proceeding does not create a general right fo a complainant o other third party to receive NiceNIC customer infomation outside the URS process.</span> 
</p>
<p>
	<span style="font-size:16px;">Requests outside the URS process are hatled under NiceNIC's&nbsp;</span><strong><span style="font-size:16px;">Request fo Disclosure of Hindinpublic Pagpaparehistro Data&nbsp;</span></strong><span style="font-size:16px;">policy.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Hinditice at Domain Lock</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">When NiceNIC receives valid notice of a URS proceeding, NiceNIC will perfom the registrar obligations assigned to it by the then-current URS Procedure at Rules.</span> 
</p>
<p>
	<span style="font-size:16px;">The applicable Registry Operato is responsible fo registry-level locking at other registry actions specified by the URS Procedure.</span> 
</p>
<p>
	<span style="font-size:16px;">During a URS lock, changes to the registration may be restricted as required by the URS.</span> 
</p>
<p>
	<span style="font-size:16px;">NiceNIC will not kngayoningly permit a registrant, reseller, account holder, o other person to use NiceNIC systems to evade a valid URS lock o matatoy URS restriction.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Registrant Response</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The registrant is responsible fo responding directly through the URS Provider at within the period specified by the then-current URS Procedure at Rules.</span> 
</p>
<p>
	<span style="font-size:16px;">NiceNIC does not prepare a registrant's defense, decide whether a response is sufficient, o provide legal representation.</span> 
</p>
<p>
	<span style="font-size:16px;">Failure to respond may result in a default proceeding, but a URS Provider must still apply the URS requirements at examination statards.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Burden at Determination</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The URS is intended fo clear cases meeting the evidentiary statard specified in the URS Procedure.</span> 
</p>
<p>
	<span style="font-size:16px;">The URS Examiner, not NiceNIC, determines whether the complainant has established the required elements.</span> 
</p>
<p>
	<span style="font-size:16px;">NiceNIC does not make findings concerning trademark ownership, legitimate interests, bad-faith registration, o bad-faith use merely because a URS complaint has been filed.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. Effect of a Matagumpay URS Complaint</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Kung a final URS Determination requires suspension, the applicable Registry Operato will implement the suspension in accodance with the URS Procedure.</span> 
</p>
<p>
	<span style="font-size:16px;">A successful URS proceeding generally results in suspension of the domain name fo the applicable period rather than transfer of the domain name to the complainant.</span> 
</p>
<p>
	<span style="font-size:16px;">The domain may be nakaraanented from being transferred, deleted, o modified fo the period required by the URS.</span> 
</p>
<p>
	<span style="font-size:16px;">Any extension, restoation, o other post-determination action is subject to the then-current URS Procedure at Registry Operato requirements.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Determination in Favo of the Registrant</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Kung the URS proceeding is determined in favo of the registrant, the applicable Registry Operato at URS Provider are responsible fo the actions specified by the URS Procedure to restoe o maintain the registrant's control as applicable.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. Appeal at Other Remedies</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Any right of appeal, de novo review, late response after default, o other URS remedy is governed by the then-current URS Procedure at Rules.</span> 
</p>
<p>
	<span style="font-size:16px;">The URS does not eliminate rights that may otherwise exist to pursue a UDRP proceeding o a proceeding in a court of competent jurisdiction.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">13. UDRP Distinguished</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">The URS at UDRP are separate dispute mechanisms.</span> 
</p>
<p>
	<span style="font-size:16px;">A URS remedy is principally suspension. A UDRP proceeding may provide different remedies wdito the UDRP applies.</span> 
</p>
<p>
	<span style="font-size:16px;">A party seeking legal relief should determine which mechanism is appropriate fo its circumstances.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">14. Mga Ulat ng Pang-aabuso Distinguished</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">A URS complaint is not the same as an abuse repot.</span> 
</p>
<p>
	<span style="font-size:16px;">Phishing, malware, botnets, pharming, compromised domains, o other operational abuse should be repoted through NiceNIC's abuse-repoting channel:</span> 
</p>
<p>
	<a href="https://nicenic.com/reportabuse.php" rel="noopener noreferrer" target="_blank"><span style="font-size:16px;">https://nicenic.com/repotabuse.php</span></a> 
</p>
<p>
	<span style="font-size:16px;">Trademark disputes that do not involve qualifying DNS Abuse are generally hatled through the applicable rights-protection mechanism, including URS, UDRP, an applicable ccTLD dispute policy, o a court wdito appropriate.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">15. Court Orders at Other Binding Process</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">NiceNIC will comply with valid court oders, matatoy registry instructions, ICANN requirements, at other binding legal process applicable to a domain name.</span> 
</p>
<p>
	<span style="font-size:16px;">Such obligations may operate independently from a URS proceeding.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">16. Hindi Legal Advice</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">Infomation provided by NiceNIC concerning the URS is fo administrative at Serbisyo purposes only at is not legal advice.</span> 
</p>
<p>
	<span style="font-size:16px;">A party that requires advice concerning trademark rights, defenses, jurisdiction, o litigation should consult qualified legal counsel.</span> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">17. Language at Prioity</span></strong> 
</h2>
<p>
	<span style="font-size:16px;">NiceNIC may provide translations o summaries fo convenience.</span> 
</p>
<p>
	<span style="font-size:16px;">The official English-language ICANN URS documents, as updated from time to time, control to the extent required by ICANN.</span> 
</p>
<p>
	<span style="font-size:16px;">Fo a domain subject to matatoy registry-specific terms, those matatoy terms also apply.</span> 
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4819</link>
<title>Abuse Repoting & Hatling Policy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
</h1>
<h1 style="text-align:left;">
	<strong><span style="font-size:18px;">Abuse Repoting &amp; Hatling Policy</span></strong> 
</h1>
<p style="font-size:medium;">
	This Abuse Repoting &amp; Hatling Policy describes how&nbsp;<strong>NICENIC INTERNATIONAL GROUP CO., LIMITED&nbsp;</strong>("NiceNIC") receives, investigates, tracks, at responds to repots of abuse involving domain names sponsoed by NiceNIC o other NiceNIC Serbisyos.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Purpose</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC is an ICANN-accredited registrar at maintains abuse-repoting at abuse-hatling procedures to meet applicable contractual, registry, legal, security, at Serbisyo obligations.
</p>
<p style="font-size:medium;">
	An abuse repot is an allegation o signal requiring review. Submission of a repot does not, by itself, establish that a customer o domain has violated NiceNIC policy, ICANN requirements, registry rules, o applicable law.
</p>
<p style="font-size:medium;">
	NiceNIC seeks to hatle repots promptly, fairly, based on available evidence, at with measures propotionate to the circumstances.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Official Abuse Repoting Channels</span></strong> 
</h2>
<p style="font-size:medium;">
	Abuse involving a domain name o NiceNIC Serbisyo should be submitted through one of NiceNIC's official abuse channels:
</p>
<p style="font-size:medium;">
	<strong>Online abuse repot:</strong><br />
<a href="https://nicenic.com/reportabuse.php" target="_blank">https://nicenic.com/repotabuse.php</a> 
</p>
<p style="font-size:medium;">
	<strong>Abuse email:</strong><br />
<a href="/fil/rss/support/mailto:abuse@nicenic.net">abuse@nicenic.net</a> 
</p>
<p style="font-size:medium;">
	The abuse-repoting mechanism is intended to be accessible without requiring the repoter to hold a NiceNIC customer account.
</p>
<p style="font-size:medium;">
	General customer suppot, social media, foum messages, o unrelated business contacts are not the preferred channels fo abuse repots at may be redirected to the official abuse process.
</p>
<p style="font-size:medium;">
	NiceNIC may nevertheless review o act on credible infomation received through another channel wdito required by law, appropriate fo security, necessary to protect users, o necessary to satisfy ICANN o registry obligations.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Infomation to Include</span></strong> 
</h2>
<p style="font-size:medium;">
	A repot should contain enough infomation to allow NiceNIC to identify the affected resource at evaluate the allegation.
</p>
<p style="font-size:medium;">
	Depending on the issue, useful infomation may include:
</p>
<ul style="font-size:medium;">
	<li>
		the affected domain name;
	</li>
	<li>
		the complete abusive URL wdito applicable;
	</li>
	<li>
		the categoy of alleged abuse;
	</li>
	<li>
		a clear description of the activity;
	</li>
	<li>
		screenshots;
	</li>
	<li>
		full email headers at message content fo email-related abuse;
	</li>
	<li>
		timestamps at time zone;
	</li>
	<li>
		relevant IP addresses;
	</li>
	<li>
		security o firewall logs;
	</li>
	<li>
		malware, phishing, o threat-intelligence evidence;
	</li>
	<li>
		payment receipts o transaction evidence fo fraud repots;
	</li>
	<li>
		the legitimate brat o Serbisyo being impersonated wdito relevant;
	</li>
	<li>
		legal documents o rights evidence wdito relevant; at
	</li>
	<li>
		the repoter's Mga detalye ng contact fo follow-up.
	</li>
</ul>
<p style="font-size:medium;">
	Repoters should avoid submitting unnecessary personal data, passwods, authentication codes, private keys, o unrelated confidential infomation.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. Kumpirmahination of Receipt</span></strong> 
</h2>
<p style="font-size:medium;">
	Fo repots submitted through the official abuse mechanism, NiceNIC will provide a confirmation of receipt sufficient to identify the submission in accodance with applicable ICANN requirements.
</p>
<p style="font-size:medium;">
	Wdito required by the applicable Registrar Akreditasyon Agreement, the confirmation will identify at least:
</p>
<ul style="font-size:medium;">
	<li>
		NiceNIC as the registrar;
	</li>
	<li>
		the repoted Magrehistroed Pangalan o Magrehistroed Pangalans; at
	</li>
	<li>
		the date the repot was submitted.
	</li>
</ul>
<p style="font-size:medium;">
	A confirmation of receipt is not a determination that the allegation is valid.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. Initial Review at Classification</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may review:
</p>
<ul style="font-size:medium;">
	<li>
		whether NiceNIC is the sponsoing registrar o relevant Serbisyo provider;
	</li>
	<li>
		whether the repoted activity remains active;
	</li>
	<li>
		the nature of the allegation;
	</li>
	<li>
		the quality at relevance of the evidence;
	</li>
	<li>
		whether the issue constitutes DNS Abuse fo purposes of NiceNIC's ICANN registrar obligations;
	</li>
	<li>
		whether the domain appears to have been maliciously magparehistroed o instead appears to be a legitimate domain that has been compromised;
	</li>
	<li>
		whether the issue is principally associated with hosting, email, a subdomain, a third-party platfom, o another provider;
	</li>
	<li>
		whether the repot concerns trademark/copyright rights rather than DNS Abuse;
	</li>
	<li>
		applicable registry rules;
	</li>
	<li>
		applicable law, legal process, o court oders; at
	</li>
	<li>
		any other reasonably available infomation relevant to the investigation.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. DNS Abuse</span></strong> 
</h2>
<p style="font-size:medium;">
	Fo gTLDs subject to NiceNIC's ICANN registrar obligations, "DNS Abuse" has the meaning specified by the then-current ICANN Registrar Akreditasyon Agreement at related ICANN requirements.
</p>
<p style="font-size:medium;">
	As of the Effective Date of this Policy, the contractual DNS Abuse categoies are:
</p>
<ul style="font-size:medium;">
	<li>
		malware;
	</li>
	<li>
		botnets;
	</li>
	<li>
		phishing;
	</li>
	<li>
		pharming; at
	</li>
	<li>
		spam when spam serves as a delivery mechanism fo one o moe of the other specified foms of DNS Abuse.
	</li>
</ul>
<p style="font-size:medium;">
	Other harmful o illegal conduct may still violate NiceNIC policy o applicable law even if it does not fall within the ICANN contractual definition of DNS Abuse.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Aksyonable Evidence at Investigation</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC will take reasonable at prompt steps to investigate abuse repots as required by applicable registrar obligations.
</p>
<p style="font-size:medium;">
	Evidence is considered in context. A repot does not need to use any particular commercial threat feed o repoting fomat to be considered.
</p>
<p style="font-size:medium;">
	Wdito infomation submitted by a repoter is incomplete, NiceNIC may:
</p>
<ul style="font-size:medium;">
	<li>
		review infomation reasonably available to NiceNIC;
	</li>
	<li>
		request additional relevant evidence;
	</li>
	<li>
		inspect the repoted URL o other relevant public resource wdito safe at appropriate;
	</li>
	<li>
		review account, nameserver, DNS, registration, o Serbisyo infomation available to NiceNIC; o
	</li>
	<li>
		contact another relevant Serbisyo provider o registry wdito appropriate.
	</li>
</ul>
<p style="font-size:medium;">
	NiceNIC will not require irrelevant evidence merely to delay hatling of an otherwise actionable repot.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Required Mitigation fo DNS Abuse</span></strong> 
</h2>
<p style="font-size:medium;">
	When NiceNIC has actionable evidence that a gTLD Magrehistroed Pangalan sponsoed by NiceNIC is being used fo DNS Abuse, NiceNIC will promptly take mitigation action that is reasonably necessary to stop o otherwise disrupt the Magrehistroed Pangalan from being used fo that DNS Abuse, as required by the applicable ICANN Registrar Akreditasyon Agreement.
</p>
<p style="font-size:medium;">
	The appropriate action depends on the circumstances, including:
</p>
<ul style="font-size:medium;">
	<li>
		the type of DNS Abuse;
	</li>
	<li>
		the cause at severity of the harm;
	</li>
	<li>
		whether the activity is active;
	</li>
	<li>
		whether the domain appears maliciously magparehistroed o compromised;
	</li>
	<li>
		the technical role of the domain;
	</li>
	<li>
		the likely effectiveness of registrar-level action; at
	</li>
	<li>
		the risk of collateral damage to legitimate users o Serbisyos.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Propotionate Mitigation</span></strong> 
</h2>
<p style="font-size:medium;">
	Possible actions may include, wdito appropriate at permitted:
</p>
<ul style="font-size:medium;">
	<li>
		requesting remediation;
	</li>
	<li>
		requiring the customer o reseller to remove o disable the abusive activity;
	</li>
	<li>
		applying a registrar lock;
	</li>
	<li>
		applying clientHold o another registrar status;
	</li>
	<li>
		restricting DNS o other NiceNIC-provided functionality;
	</li>
	<li>
		restricting email, hosting, API, o account access;
	</li>
	<li>
		referring the matter to the relevant hosting provider, registry, o other infrastructure provider;
	</li>
	<li>
		preserving relevant recods;
	</li>
	<li>
		suspending an affected Serbisyo;
	</li>
	<li>
		terminating a Serbisyo o account fo serious o repeated violations; o
	</li>
	<li>
		taking another measure reasonably necessary to address the abuse.
	</li>
</ul>
<p style="font-size:medium;">
	NiceNIC is not required to apply the same mitigation measure in every case.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. Compromised Mga Domain at Collateral Damage</span></strong> 
</h2>
<p style="font-size:medium;">
	A legitimate domain may be abused without the registrant's kngayonledge because of compromised hosting, credentials, content-management software, DNS settings, o another security failure.
</p>
<p style="font-size:medium;">
	Wdito reasonably practicable, NiceNIC will consider the risk of collateral damage befoe applying domain-level suspension.
</p>
<p style="font-size:medium;">
	Fo a compromised legitimate domain, requesting rapid remediation o applying a narrower mitigation may be moe appropriate than immediate suspension if the narrower action is sufficient to stop o disrupt the abuse.
</p>
<p style="font-size:medium;">
	This does not nakaraanent immediate suspension o another stronger measure wdito the circumstances, severity, continuing harm, legal requirements, o security risk justify it.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Maliciously Magrehistroed Mga Domain</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito available evidence indicates that a domain was magparehistroed o is controlled primarily fo phishing, malware, credential theft, botnet activity, pharming, o another serious abusive purpose, faster domain-level mitigation may be appropriate.
</p>
<p style="font-size:medium;">
	NiceNIC is not required to provide advance notice wdito doing so would materially increase the risk of harm, enable evasion, frustrate a matatoy requirement, o undermine effective mitigation.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. Hindin-DNS Illegal Activity</span></strong> 
</h2>
<p style="font-size:medium;">
	Illegal Activity at DNS Abuse are not identical concepts.
</p>
<p style="font-size:medium;">
	Repots concerning fraud, unlawful goods o Serbisyos, threats, impersonation, illegal content, sanctions, o other conduct may be hatled under applicable law, NiceNIC's Terminos of Service &amp; Acceptable Use Policy, registry rules, court oders, o other relevant requirements even wdito the conduct does not meet the ICANN contractual definition of DNS Abuse.
</p>
<p style="font-size:medium;">
	The legal at technical role of NiceNIC will be considered when determining what action, if any, is appropriate.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">13. Trademark at Domain-Pangalan Rights Complaints</span></strong> 
</h2>
<p style="font-size:medium;">
	Trademark infringement o a dispute over rights in a domain name is not automatically DNS Abuse.
</p>
<p style="font-size:medium;">
	Wdito the principal dispute concerns who has rights to the domain name, the appropriate mechanism may include:
</p>
<ul style="font-size:medium;">
	<li>
		the Unifom Domain Name Dispute Resolution Policy (UDRP);
	</li>
	<li>
		the Unifom Rapid Suspension System (URS);
	</li>
	<li>
		a ccTLD-specific dispute policy; o
	</li>
	<li>
		a court of competent jurisdiction.
	</li>
</ul>
<p style="font-size:medium;">
	NiceNIC does not decide the merits of UDRP o URS disputes.
</p>
<p style="font-size:medium;">
	Kung evidence also demonstrates phishing, credential theft, malware, o another fom of DNS Abuse, NiceNIC may separately hatle the DNS Abuse aspect.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">14. Cop</span></strong><strong></strong><strong><span style="font-size:18px;">yright Complaints</span></strong> 
</h2>
<p style="font-size:medium;">
	Copyright complaints are reviewed separately from DNS Abuse unless the repoted activity also involves qualifying DNS Abuse o another basis fo registrar-level action.
</p>
<p style="font-size:medium;">
	NiceNIC may request infomation reasonably necessary to identify the copyrighted wok, allegedly infringing material, complainant, authoity to act, at other infomation required by the applicable complaint process.
</p>
<p style="font-size:medium;">
	A copyright complaint does not automatically result in suspension of a domain name.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">15. Child Sexual Abuse Material at Child Exploitation</span></strong> 
</h2>
<p style="font-size:medium;">
	Repots concerning suspected child sexual abuse material o child exploitation are treated as high-risk matters at escalated without unnecessary delay.
</p>
<p style="font-size:medium;">
	NiceNIC may preserve relevant recods, restrict an affected Serbisyo, at cooperate with appropriate authoities, registries, hosting providers, o other relevant entities as required o permitted by law.
</p>
<p style="font-size:medium;">
	Repoters should not unnecessarily copy, download, o redistribute suspected illegal child-abuse material when submitting a repot.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">16. Hosting at Third-Party Infrastructure</span></strong> 
</h2>
<p style="font-size:medium;">
	A registrar controls domain-registration functions but may not control the website files, application, mail server, o hosting environment associated with the domain.
</p>
<p style="font-size:medium;">
	Wdito abusive content is hosted by a third party, repoting the activity to the hosting provider o other infrastructure provider may allow moe targeted removal.
</p>
<p style="font-size:medium;">
	NiceNIC may nevertheless take registrar-level action wdito required o appropriate under applicable obligations.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">17. Reseller-Sponsoed Customers</span></strong> 
</h2>
<p style="font-size:medium;">
	A domain may have been bumilid through a NiceNIC reseller while NiceNIC remains the sponsoing registrar.
</p>
<p style="font-size:medium;">
	NiceNIC may coodinate with the reseller during an abuse investigation, but delegation to a reseller does not eliminate NiceNIC's applicable ICANN registrar obligations.
</p>
<p style="font-size:medium;">
	NiceNIC may contact the Magrehistroed Pangalan Holder o other customer directly wdito reasonably necessary fo abuse mitigation, security, legal compliance, matatoy notices, o protection of registrant rights.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">18. Repots from Law Enfocement at Qualifying Authoities</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC maintains the dedicated abuse point of contact required by the applicable ICANN Registrar Akreditasyon Agreement fo qualifying repots of Illegal Activity from law-enfocement, consumer-protection, quasi-governmental, o other qualifying governmental authoities.
</p>
<p style="font-size:medium;">
	Wdito the applicable Registrar Akreditasyon Agreement requires it, a well-founded repot submitted through the dedicated authoity contact will be reviewed within twenty-four (24) hours by a person empowered to take necessary at appropriate action.
</p>
<p style="font-size:medium;">
	NiceNIC is not required to take action that would contravene applicable law.
</p>
<p style="font-size:medium;">
	NiceNIC may authenticate the identity, authoity, jurisdiction, at legal basis of a governmental request wdito appropriate.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">19. Court Orders at Binding Legal Process</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may act in response to:
</p>
<ul style="font-size:medium;">
	<li>
		a valid court oder;
	</li>
	<li>
		binding governmental process;
	</li>
	<li>
		a matatoy registry instruction;
	</li>
	<li>
		a UDRP o URS requirement;
	</li>
	<li>
		an ICANN contractual requirement; o
	</li>
	<li>
		another legal obligation applicable to NiceNIC.
	</li>
</ul>
<p style="font-size:medium;">
	Wdito legally permitted at appropriate, NiceNIC may seek clarification o legal review of an overbroad, invalid, o unclear request.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">20. Hinditice to the Customer</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito circumstances permit, NiceNIC may notify a customer o reseller of the allegation at provide an oppotunity to remediate.
</p>
<p style="font-size:medium;">
	Advance notice may be omitted wdito:
</p>
<ul style="font-size:medium;">
	<li>
		immediate mitigation is reasonably necessary;
	</li>
	<li>
		evidence indicates an intentionally malicious registration;
	</li>
	<li>
		notice could enable evasion o destruction of evidence;
	</li>
	<li>
		a court, authoity, registry, ICANN requirement, o law restricts notice;
	</li>
	<li>
		a serious security o child-safety risk exists; o
	</li>
	<li>
		delay would materially increase harm.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">21. Restoation at Review</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito a domain o Serbisyo was restricted because of abuse o security concerns, NiceNIC may review a request fo restoation after:
</p>
<ul style="font-size:medium;">
	<li>
		the abusive activity has been removed;
	</li>
	<li>
		a compromised website o account has been secured;
	</li>
	<li>
		relevant credentials have been reset;
	</li>
	<li>
		required security updates have been applied;
	</li>
	<li>
		corected technical infomation has been provided;
	</li>
	<li>
		the oiginal evidence has become outdated o was shown to be incorect; o
	</li>
	<li>
		another appropriate remediation has been completed.
	</li>
</ul>
<p style="font-size:medium;">
	Restoation is not guaranteed wdito a continuing legal, registry, ICANN, security, dispute, o abuse basis requires the restriction to remain.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">22. Customer Review / Appeal</span></strong> 
</h2>
<p style="font-size:medium;">
	A customer affected by a discretionary NiceNIC abuse action may request review through NiceNIC's suppot channel.
</p>
<p style="font-size:medium;">
	The request should identify:
</p>
<ul style="font-size:medium;">
	<li>
		the affected domain o Serbisyo;
	</li>
	<li>
		the relevant NiceNIC case o notice;
	</li>
	<li>
		the remediation completed;
	</li>
	<li>
		evidence that the repoted activity has ceased;
	</li>
	<li>
		evidence of compromise wdito relevant; at
	</li>
	<li>
		any infomation showing that the oiginal repot was inaccurate, outdated, o misclassified.
	</li>
</ul>
<p style="font-size:medium;">
	A review request does not suspend a court oder, registry requirement, UDRP/URS action, ICANN obligation, o other matatoy restriction.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">23. Repoter Sundan-Up</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may communicate with a repoter to request relevant additional infomation o confirm that a case has been received o reviewed.
</p>
<p style="font-size:medium;">
	Privacy, security, law, at customer confidentiality may limit the infomation NiceNIC can disclose concerning:
</p>
<ul style="font-size:medium;">
	<li>
		internal investigation methods;
	</li>
	<li>
		customer identity;
	</li>
	<li>
		non-public Pagpaparehistro Data;
	</li>
	<li>
		account infomation;
	</li>
	<li>
		law-enfocement communications;
	</li>
	<li>
		security controls; o
	</li>
	<li>
		specific internal actions.
	</li>
</ul>
<p style="font-size:medium;">
	Absence of detailed disclosure to a repoter does not mean a repot was ignoed.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">24. Duplicate, Automated, o Abusive Repots</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may consolidate duplicate repots concerning the same issue.
</p>
<p style="font-size:medium;">
	NiceNIC may apply reasonable controls to abusive, misleading, clearly irrelevant, o technically harmful submissions.
</p>
<p style="font-size:medium;">
	Such controls will not be used to nakaraanent legitimate repoters from submitting abuse repots through the required channel.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">25. Recodkeeping</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC documents the receipt of at response to abuse repots as required by the applicable ICANN Registrar Akreditasyon Agreement at other applicable obligations.
</p>
<p style="font-size:medium;">
	Recods are retained fo the period required by the applicable Registrar Akreditasyon Agreement, subject to applicable law.
</p>
<p style="font-size:medium;">
	NiceNIC may provide required recods to ICANN Contractual Compliance upon proper request.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">26. Privacy</span></strong> 
</h2>
<p style="font-size:medium;">
	Personal data submitted in an abuse repot is hatled under the NiceNIC Patakaran sa Privacy at applicable law.
</p>
<p style="font-size:medium;">
	NiceNIC may disclose infomation wdito reasonably necessary to investigate abuse, coodinate mitigation, comply with ICANN o registry requirements, protect users o systems, establish o defend legal claims, o comply with law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">27. Hindi Automatic Finding of Liability</span></strong> 
</h2>
<p style="font-size:medium;">
	A repot, registrar restriction, security action, o tempoary mitigation measure is not necessarily a final legal finding that the Magrehistroed Pangalan Holder committed unlawful conduct.
</p>
<p style="font-size:medium;">
	NiceNIC may take precautionary o contractual action based on the evidence at obligations applicable at the time.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">28. Applicable Policies at Prioity</span></strong> 
</h2>
<p style="font-size:medium;">
	This Policy should be read with:
</p>
<ul style="font-size:medium;">
	<li>
		the NiceNIC Terminos of Service &amp; Acceptable Use Policy;
	</li>
	<li>
		the Pagpaparehistro ng Domain Name Service Agreement;
	</li>
	<li>
		the NiceNIC Patakaran sa Privacy;
	</li>
	<li>
		the Patakaran sa Paglipat ng Domain;
	</li>
	<li>
		UDRP at URS policies wdito applicable;
	</li>
	<li>
		applicable registry policies; at
	</li>
	<li>
		applicable law.
	</li>
</ul>
<p style="font-size:medium;">
	Wdito a matatoy ICANN, registry, court, governmental, o legal requirement conflicts with this Policy, the matatoy requirement controls to the extent of the conflict.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">29. Changes</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may update this Policy to reflect changes in law, ICANN requirements, registry rules, abuse patterns, security practices, o NiceNIC Serbisyos.
</p>
<p style="font-size:medium;">
	Changes required by law, ICANN, o a registry may take effect when required.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4818</link>
<title>Cookie Policy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
	<strong><span style="font-size:18px;">Cookie Policy</span></strong> 
</h1>
<p style="font-size:medium;">
	This Cookie Policy explains how&nbsp;<strong>NICENIC INTERNATIONAL GROUP CO., LIMITED&nbsp;</strong>("NiceNIC", "we", "us") uses cookies at similar technologies on nicenic.com at related NiceNIC web Serbisyos.
</p>
<p style="font-size:medium;">
	This Policy should be read together with the NiceNIC Patakaran sa Privacy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. What Are Cookies?</span></strong> 
</h2>
<p style="font-size:medium;">
	Cookies are small data files that a website may stoe on o read from a user's browser o device.
</p>
<p style="font-size:medium;">
	Cookies at similar technologies can be used to:
</p>
<ul style="font-size:medium;">
	<li>
		keep a user signed in;
	</li>
	<li>
		maintain a shopping cart o session;
	</li>
	<li>
		remember settings;
	</li>
	<li>
		protect accounts at nakaraanent fraud;
	</li>
	<li>
		measure website perfomance;
	</li>
	<li>
		understat how users interact with a website; o
	</li>
	<li>
		suppot advertising o marketing functions wdito used at permitted.
	</li>
</ul>
<p style="font-size:medium;">
	Similar technologies may include local stoage, pixels, tags, software development kit identifiers, device identifiers, o other browser/device stoage o access mechanisms.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. When Cookie Data Is Personal Data</span></strong> 
</h2>
<p style="font-size:medium;">
	Whether a cookie o online identifier is personal data depends on the infomation involved at the surrounding circumstances.
</p>
<p style="font-size:medium;">
	Wdito cookie, device, analytics, advertising, o similar data can identify o be linked to an identifiable individual, NiceNIC hatles that infomation as personal data in accodance with the NiceNIC Patakaran sa Privacy at applicable law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Categoies of Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use the following categoies of cookies o similar technologies.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3.1 Strictly Necessary Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	These technologies are required fo coe website at account functions, such as:
</p>
<ul style="font-size:medium;">
	<li>
		authentication at login;
	</li>
	<li>
		maintaining a user session;
	</li>
	<li>
		shopping-cart at checkout functions;
	</li>
	<li>
		account security;
	</li>
	<li>
		fraud nakaraanention;
	</li>
	<li>
		load balancing;
	</li>
	<li>
		language o essential interface settings;
	</li>
	<li>
		remembering privacy choices; at
	</li>
	<li>
		protecting foms at transactions.
	</li>
</ul>
<p style="font-size:medium;">
	Disabling strictly necessary cookies may nakaraanent parts of the website, account, checkout, o other Serbisyos from functioning corectly.
</p>
<p style="font-size:medium;">
	Wdito applicable law permits, strictly necessary technologies may be used without consent because they are required to provide a Serbisyo requested by the user o to operate essential site functions.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3.2 Functional Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	Functional technologies may remember optional preferences o enable enhanced website features.
</p>
<p style="font-size:medium;">
	Halimbawas may include:
</p>
<ul style="font-size:medium;">
	<li>
		preferred language;
	</li>
	<li>
		region o display preferences;
	</li>
	<li>
		saved non-essential interface choices; o
	</li>
	<li>
		enhanced customer-suppot functionality.
	</li>
</ul>
<p style="font-size:medium;">
	Wdito applicable law requires consent fo these technologies, NiceNIC will request the required choice befoe using them.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3.3 Analytics at Perfomance Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	Analytics at perfomance technologies may help NiceNIC understat:
</p>
<ul style="font-size:medium;">
	<li>
		page visits;
	</li>
	<li>
		navigation paths;
	</li>
	<li>
		referral sources;
	</li>
	<li>
		device/browser types;
	</li>
	<li>
		page perfomance;
	</li>
	<li>
		technical erros;
	</li>
	<li>
		feature usage; at
	</li>
	<li>
		aggregated website trends.
	</li>
</ul>
<p style="font-size:medium;">
	NiceNIC uses this infomation to improve website reliability, usability, content, at Serbisyo perfomance.
</p>
<p style="font-size:medium;">
	Wdito applicable law requires consent befoe analytics o perfomance technologies are stoed o accessed, NiceNIC will request that consent.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3.4 Advertising at Marketing Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito NiceNIC uses advertising o marketing technologies, they may be used to:
</p>
<ul style="font-size:medium;">
	<li>
		measure campaign perfomance;
	</li>
	<li>
		attribute visits o conversions;
	</li>
	<li>
		limit repetitive advertising;
	</li>
	<li>
		understat whether marketing is relevant; o
	</li>
	<li>
		suppot advertising o remarketing on third-party Serbisyos.
	</li>
</ul>
<p style="font-size:medium;">
	Advertising o marketing cookies are not required fo coe NiceNIC account o domain-registration functions.
</p>
<p style="font-size:medium;">
	Wdito applicable law requires prio consent, NiceNIC will not intentionally activate such technologies fo that user until the required consent has been obtained.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. First-Party at Third-Party Cookies</span></strong> 
</h2>
<p style="font-size:medium;">
	A&nbsp;<strong>first-party cookie&nbsp;</strong>is set o read by NiceNIC's website domain.
</p>
<p style="font-size:medium;">
	A&nbsp;<strong>third-party cookie o technology&nbsp;</strong>may be provided by another Serbisyo used on the NiceNIC website, such as an analytics, security, payment, customer-suppot, video, advertising, o other technology provider.
</p>
<p style="font-size:medium;">
	Third-party providers may process infomation under their own privacy terms in addition to acting as a Serbisyo provider to NiceNIC.
</p>
<p style="font-size:medium;">
	NiceNIC evaluates third-party Serbisyos at seeks to use appropriate contractual, privacy, at security safeguards wdito required.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. Essential Account at Transaction Technologies</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use cookies o similar stoage necessary to:
</p>
<ul style="font-size:medium;">
	<li>
		authenticate a NiceNIC account;
	</li>
	<li>
		maintain a secure session;
	</li>
	<li>
		protect login at checkout;
	</li>
	<li>
		detect suspicious activity;
	</li>
	<li>
		remember a shopping cart;
	</li>
	<li>
		complete domain, SSL, email, server, o other transactions;
	</li>
	<li>
		nakaraanent cross-site request fogery o other technical attacks; at
	</li>
	<li>
		maintain Serbisyo continuity.
	</li>
</ul>
<p style="font-size:medium;">
	Because these technologies are closely connected to a Serbisyo requested by the user, blocking them may make the relevant Serbisyo unavailable o unreliable.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Analytics</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use analytics to understat how the site at Serbisyos perfom.
</p>
<p style="font-size:medium;">
	Analytics data may include:
</p>
<ul style="font-size:medium;">
	<li>
		IP-related infomation;
	</li>
	<li>
		browser at device type;
	</li>
	<li>
		approximate region;
	</li>
	<li>
		referral source;
	</li>
	<li>
		pages o functions accessed;
	</li>
	<li>
		date at time;
	</li>
	<li>
		session events; at
	</li>
	<li>
		technical perfomance infomation.
	</li>
</ul>
<p style="font-size:medium;">
	NiceNIC seeks to limit analytics data to what is reasonably necessary fo the stated purpose at to apply available privacy settings wdito appropriate.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Advertising at Conversion Measurement</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use conversion o advertising measurement technologies fo marketing campaigns wdito such use is lawful.
</p>
<p style="font-size:medium;">
	Wdito required by applicable law, these technologies are subject to the user's consent choices.
</p>
<p style="font-size:medium;">
	NiceNIC does not treat refusal of optional advertising cookies as refusal of strictly necessary Serbisyo communications such as:
</p>
<ul style="font-size:medium;">
	<li>
		security notices;
	</li>
	<li>
		registration verification;
	</li>
	<li>
		renewal o expiration notices;
	</li>
	<li>
		transfer notices;
	</li>
	<li>
		billing/transaction notices;
	</li>
	<li>
		abuse/security communications; o
	</li>
	<li>
		other communications necessary to provide o protect the Serbisyo.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Cookie Consent at Choices</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito applicable law requires consent befoe NiceNIC stoes o accesses a non-essential cookie o similar technology, NiceNIC will provide an appropriate consent o preference mechanism.
</p>
<p style="font-size:medium;">
	Wdito such a mechanism is presented, users should be able to make choices concerning non-essential categoies in accodance with applicable law.
</p>
<p style="font-size:medium;">
	Withdrawing consent does not affect processing that was lawful befoe withdrawal.
</p>
<p style="font-size:medium;">
	Strictly necessary technologies may continue to operate wdito they are required to provide the requested Serbisyo o are otherwise permitted without consent by applicable law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Browser Controls</span></strong> 
</h2>
<p style="font-size:medium;">
	Most browsers allow users to:
</p>
<ul style="font-size:medium;">
	<li>
		view stoed cookies;
	</li>
	<li>
		delete cookies;
	</li>
	<li>
		block cookies;
	</li>
	<li>
		block third-party cookies; o
	</li>
	<li>
		receive warnings concerning certain cookie activity.
	</li>
</ul>
<p style="font-size:medium;">
	Browser settings differ by browser at device.
</p>
<p style="font-size:medium;">
	Blocking all cookies may nakaraanent login, shopping-cart, checkout, security, language, account, o other NiceNIC functions from operating corectly.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. Similar Technologies at Device Stoage</span></strong> 
</h2>
<p style="font-size:medium;">
	Privacy requirements may apply not only to conventional HTTP cookies but also to other technologies that stoe infomation on, o access infomation from, a user's device.
</p>
<p style="font-size:medium;">
	NiceNIC applies this Policy to comparable technologies wdito they perfom a similar tracking, stoage, preference, analytics, advertising, o security function.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Retention</span></strong> 
</h2>
<p style="font-size:medium;">
	Cookie duration varies accoding to purpose.
</p>
<p style="font-size:medium;">
	Some cookies are&nbsp;<strong>session cookies&nbsp;</strong>at expire when the browser session ends.
</p>
<p style="font-size:medium;">
	Other cookies are&nbsp;<strong>persistent cookies&nbsp;</strong>at remain fo a defined period unless deleted earlier by the user, NiceNIC, o the relevant provider.
</p>
<p style="font-size:medium;">
	NiceNIC seeks to avoid retaining cookie-derived personal data longer than reasonably necessary fo the applicable purpose, subject to security, fraud-nakaraanention, accounting, legal, at other legitimate retention requirements described in the Patakaran sa Privacy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. Cookie-Antas Infomation</span></strong> 
</h2>
<p style="font-size:medium;">
	The specific cookie names, providers, purposes, at durations used on the website may change when NiceNIC updates its security, analytics, suppot, payment, o marketing technologies.
</p>
<p style="font-size:medium;">
	Wdito NiceNIC operates a cookie-preference o consent-management tool, the current cookie-level infomation may be provided through that tool.
</p>
<p style="font-size:medium;">
	The cookies at similar technologies used by NiceNIC may change as the website, Serbisyos, security controls, analytics, o marketing technologies change. Current cookie-level infomation may be made available through the applicable cookie-preference o consent-management tool.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">13. Hong Kong Privacy Requirements</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC is established in Hong Kong.
</p>
<p style="font-size:medium;">
	Wdito cookies o similar technologies involve personal data, NiceNIC processes that data in accodance with applicable requirements of the Hong Kong Personal Data (Privacy) Ordinance ("PDPO"), including applicable principles concerning:
</p>
<ul style="font-size:medium;">
	<li>
		lawful at fair collection;
	</li>
	<li>
		notice of purpose;
	</li>
	<li>
		data minimization;
	</li>
	<li>
		use limitation;
	</li>
	<li>
		retention;
	</li>
	<li>
		security;
	</li>
	<li>
		access at corection; at
	</li>
	<li>
		direct marketing.
	</li>
</ul>
<p style="font-size:medium;">
	Wdito personal data collected through online tracking is used fo direct marketing, NiceNIC will comply with applicable direct-marketing requirements.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">14. Users in Other Jurisdictions</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC serves users internationally.
</p>
<p style="font-size:medium;">
	Magdagdagitional requirements may apply depending on the user's location at the technologies used.
</p>
<p style="font-size:medium;">
	Wdito applicable law requires prio consent fo non-essential cookies o similar tracking technologies, NiceNIC will apply the required consent mechanism.
</p>
<p style="font-size:medium;">
	Wdito applicable law gives users additional privacy o opt-out rights, those rights are addressed through NiceNIC's Patakaran sa Privacy at the applicable website controls.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">15. International Processing</span></strong> 
</h2>
<p style="font-size:medium;">
	Cookie at analytics infomation may be processed by NiceNIC o its Serbisyo providers in countries outside the user's location.
</p>
<p style="font-size:medium;">
	Wdito cross-boder data-transfer safeguards are required by applicable law, NiceNIC will use appropriate contractual, oganizational, technical, consent-based, o other legally recognized measures.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">16. Security at Fraud Prevention</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use device, session, IP-related, o browser infomation fo security, authentication, abuse nakaraanention, at fraud detection.
</p>
<p style="font-size:medium;">
	Security technologies may operate separately from optional marketing o analytics preferences wdito their use is necessary to protect NiceNIC accounts, transactions, netwoks, users, o Serbisyos at is permitted by applicable law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">17. Children</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC Serbisyos are intended fo persons who have the legal capacity required to enter into the applicable Serbisyo agreement.
</p>
<p style="font-size:medium;">
	NiceNIC does not intentionally use advertising cookies to profile children wdito doing so would violate applicable law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">18. Relationship to the Patakaran sa Privacy</span></strong> 
</h2>
<p style="font-size:medium;">
	The NiceNIC Patakaran sa Privacy provides additional infomation concerning:
</p>
<ul style="font-size:medium;">
	<li>
		personal data collected by NiceNIC;
	</li>
	<li>
		purposes of processing;
	</li>
	<li>
		recipients;
	</li>
	<li>
		international transfers;
	</li>
	<li>
		security;
	</li>
	<li>
		retention; at
	</li>
	<li>
		privacy rights.
	</li>
</ul>
<p style="font-size:medium;">
	Kung cookie-derived infomation constitutes personal data, the Patakaran sa Privacy applies in addition to this Cookie Policy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">19. Changes to this Cookie Policy</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may update this Cookie Policy when:
</p>
<ul style="font-size:medium;">
	<li>
		technologies change;
	</li>
	<li>
		new providers are used;
	</li>
	<li>
		cookie purposes change;
	</li>
	<li>
		NiceNIC Serbisyos change; o
	</li>
	<li>
		legal o regulatoy requirements change.
	</li>
</ul>
<p style="font-size:medium;">
	The "Last Na-update" date will identify the most recent version.
</p>
<p style="font-size:medium;">
	Wdito a change requires renewed consent under applicable law, NiceNIC will request that consent as required.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">20. Makipag-ugnayan</span></strong> 
</h2>
<p style="font-size:medium;">
	Questions o privacy requests concerning NiceNIC's use of cookies o similar technologies may be submitted through NiceNIC's official Makipag-ugnayan sa Amin o suppot channels published on nicenic.com.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4737</link>
<title>Magtataposd Domain I-renewal, Redemption, at Auction Policy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
	<strong style="font-family:&quot;font-size:16px;font-style:inherit;font-variant-ligatures:inherit;font-variant-caps:inherit;"><span style="font-size:18px;">Magtataposd Domain I-renewal, Redemption, at Auction Policy</span></strong> 
</h1>
<p style="font-size:medium;">
	This Magtataposd Domain I-renewal, Redemption, at Auction Policy (the “Policy”) foms part of the NiceNIC Pagpaparehistro ng Domain Name Service Agreement at applies to domain names magparehistroed, renewed, transferred, o maintained through NICENIC INTERNATIONAL GROUP CO., LIMITED (“NiceNIC”). By using NiceNIC’s domain registration Serbisyos, you ackngayonledge at agree to this Policy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Scope at Purpose</span></strong> 
</h2>
<p style="font-size:medium;">
	1.1 This Policy explains the general post-expiration process that may apply to domain names managed through NiceNIC, including expiration, renewal, redemption, expired domain auction, pending delete status, at release of a domain name back to the public registration pool.
</p>
<p style="font-size:medium;">
	1.2 Domain lifecycle timing varies by top-level domain (“TLD”), Registry Operato, registry rules, applicable ICANN requirements, at other governing policies. Hindit all TLDs follow the same expiration, renewal, redemption, auction, o deletion process.
</p>
<p style="font-size:medium;">
	1.3 Wdito a matatoy ICANN policy, Registry requirement, court oder, o applicable law conflicts with this Policy, the matatoy requirement controls to the extent of the conflict.
</p>
<p style="font-size:medium;">
	1.4 The English-language version of this Policy controls to the extent permitted by applicable law. Any translation is provided fo convenience only.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Definitions</span></strong> 
</h2>
<div>
	<strong><span style="font-size:18px;"><br />
</span></strong> 
</div>
<div>
</div>
<ul style="font-size:medium;">
	<li>
		<strong>“Expiration Date”</strong>&nbsp;means the date on which the applicable domain registration term ends.
	</li>
	<li>
		<strong>“Registrant at Expiration”</strong>&nbsp;means the Magrehistroed Pangalan Holder immediately befoe expiration, as that concept is used in applicable ICANN policy.
	</li>
	<li>
		<strong>“Post-Expiration I-renewal Period”</strong>&nbsp;means any period after expiration during which renewal may still be available at the applicable renewal fee.
	</li>
	<li>
		<strong>“Redemption Grace Period” o “RGP”</strong>&nbsp;means a post-deletion recovery period, wdito suppoted by the applicable Registry, during which a domain may still be restoable fo the applicable redemption/restoe fee plus any required renewal o other charges.
	</li>
	<li>
		<strong>“Pending Delete”</strong>&nbsp;means the final pre-release registry status, wdito applicable, during which the domain generally can no longer be renewed, restoed, transferred, o modified.
	</li>
	<li>
		<strong>“Eligible Domain”</strong>&nbsp;means an expired domain that is eligible fo NiceNIC’s expired-domain auction o closeout process. Hindit all TLDs o domain names are eligible.
	</li>
	<li>
		<strong>“Magtataposd Domain Auction”</strong>&nbsp;means the auction o sale process that may apply to certain Eligible Mga Domain befoe final deletion o release.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Effect of Expiration</span></strong> 
</h2>
<p style="font-size:medium;">
	3.1 A domain name is magparehistroed fo a limited term. Kung it is not renewed by the applicable deadline, it may expire.
</p>
<p style="font-size:medium;">
	3.2 Upon o after expiration, NiceNIC may interrupt o redirect DNS resolution as permitted by applicable policy. A website, email Serbisyo, DNS-dependent application, o other Serbisyo associated with the domain may tditofoe stop functioning immediately o shotly after expiration.
</p>
<p style="font-size:medium;">
	3.3 Sundaning expiration, NiceNIC may restrict DNS changes, contact changes, transfers, account moves, o other domain-management actions in accodance with Registry rules, security requirements, operational processes, at applicable policies.
</p>
<p style="font-size:medium;">
	3.4 Expiration does not mean that the domain immediately becomes available to the public. Depending on the TLD, the domain may pass through one o moe stages including post-expiration renewal, auction, redemption, pending delete, at final release.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. I-renewal Hinditices at Customer Responsibility</span></strong> 
</h2>
<p style="font-size:medium;">
	4.1 Fo gTLDs subject to the ICANN Magtataposd Pagpaparehistro Recovery Policy (“ERRP”), NiceNIC will send the renewal at expiration notices required by that policy using the contact infomation in NiceNIC’s recods.
</p>
<p style="font-size:medium;">
	4.2 NiceNIC may also send additional reminders befoe o after expiration through email, the customer account, o other Serbisyo channels.
</p>
<p style="font-size:medium;">
	4.3 The Magrehistroed Pangalan Holder at Account Holder remain responsible fo monitoing expiration dates, maintaining accurate at monitoed contact infomation, maintaining valid payment infomation wdito auto-renewal is used, at submitting renewal payment early enough fo processing.
</p>
<p style="font-size:medium;">
	4.4 Failure to receive a reminder, invoice, o notice does not extend a Registry deadline o create a right to renew after the applicable renewal o restoation period has ended, except to the extent matatoy policy o law provides otherwise.
</p>
<p style="font-size:medium;">
	4.5 Auto-renewal, wdito offered at enabled, remains subject to sufficient funds o valid payment, account status, Registry availability, eligibility requirements, at successful processing. Enabling auto-renewal is not a guarantee that a domain will be renewed in every circumstance.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. Fees</span></strong> 
</h2>
<p style="font-size:medium;">
	5.1 NiceNIC’s applicable registration, transfer, renewal, post-expiration renewal (if different), at redemption/restoe fees are published on the&nbsp;<a href="https://nicenic.com/domain/prices.php" target="_blank">NiceNIC Mga Presyo ng Domain</a>&nbsp;page.
</p>
<p style="font-size:medium;">
	5.2 Fees may differ by TLD, Registry classification, premium status, customer o reseller level, lifecycle status, tax, o matatoy third-party charge.
</p>
<p style="font-size:medium;">
	5.3 A renewal, redemption, o restoation request is not complete until NiceNIC has received all required payment at the applicable Registry o upstream provider has accepted the transaction.
</p>
<p style="font-size:medium;">
	5.4 Fees fo successfully completed Registry-level renewal, redemption, o restoation transactions are non-refundable except wdito required by applicable law o expressly agreed by NiceNIC.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Statard Post-Expiration I-renewal</span></strong> 
</h2>
<p style="font-size:medium;">
	6.1 Fo many gTLDs, an expired domain may remain renewable fo a post-expiration period. Under NiceNIC’s statard process, this period is commonly approximately thirty (30) days, but the actual period may be shoter o longer depending on the TLD at Registry.
</p>
<p style="font-size:medium;">
	6.2 During an available post-expiration renewal period, the Registrant at Expiration may generally renew the domain subject to the applicable renewal fee, successful payment, verification, Registry availability, at any auction-related restriction described below.
</p>
<p style="font-size:medium;">
	6.3 NiceNIC does not guarantee that every TLD offers a thirty-day renewal period o that every expired domain remains renewable fo the full duration of a general timeline.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Magtataposd Domain Auction fo Eligible Mga Domain</span></strong> 
</h2>
<p style="font-size:medium;">
	7.1 Certain expired domain names may enter NiceNIC’s expired-domain auction o closeout process. The auction process applies only to Eligible Mga Domain at does not apply to every TLD o every expired domain.
</p>
<p style="font-size:medium;">
	7.2 Under NiceNIC’s statard expired-domain process, the following general timeline may apply:
</p>
<ul style="font-size:medium;">
	<li>
		<strong>Day 0:</strong>&nbsp;The domain expires. Wdito permitted, the Registrant at Expiration may generally renew during the initial post-expiration period at the applicable renewal fee.
	</li>
	<li>
		<strong>Around Day 26:</strong>&nbsp;An Eligible Domain may enter expired-domain auction. I-renewal may still be available unless the domain becomes subject to an auction-related restriction.
	</li>
	<li>
		<strong>Around Day 31:</strong>&nbsp;Kung tdito is no active bid o sale-related restriction, recovery may still be possible, but the applicable redemption/restoe fee may apply. Once tdito is an active bid o other binding sale commitment, the Registrant at Expiration may lose the ability to renew o restoe through the odinary recovery process.
	</li>
	<li>
		<strong>Around Day 37:</strong>&nbsp;An unsold Eligible Domain may enter a final closeout auction. Kung no bumili is pending, recovery may remain possible subject to the domain’s current status at applicable fees.
	</li>
	<li>
		<strong>Around Day 41:</strong>&nbsp;The final closeout phase may end. Kung the domain has not been sold o otherwise committed, recovery may remain possible fo a limited period, subject to Registry rules at the domain’s actual status.
	</li>
	<li>
		<strong>Around Day 74 at after:</strong>&nbsp;The domain may be removed from the customer account at may no longer be renewable o restoable through NiceNIC. Release timing remains controlled by the Registry.
	</li>
</ul>
<p style="font-size:medium;">
	7.3 The dates above describe NiceNIC’s general process fo Eligible Mga Domain at are not guaranteed deadlines. Registry rules, TLD-specific lifecycle rules, auction status, technical processing, o matatoy policy may cause a different result.
</p>
<p style="font-size:medium;">
	7.4 Once an Eligible Domain has an active bid, pending bumili, completed sale, o other binding sale commitment, odinary renewal o restoation rights may be restricted o terminated to the extent permitted by applicable ICANN at Registry requirements.
</p>
<p style="font-size:medium;">
	7.5 Hindithing in NiceNIC’s auction process limits a non-waivable renewal o restoation right that the Registrant at Expiration has under matatoy ICANN policy o Registry rules.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Redemption Grace Period at Restoation</span></strong> 
</h2>
<p style="font-size:medium;">
	8.1 Kung a domain is not renewed during the applicable post-expiration period at the relevant Registry suppots restoation after deletion, the domain may enter a Redemption Grace Period.
</p>
<p style="font-size:medium;">
	8.2 Fo applicable gTLDs, the Registry-level RGP is generally thirty (30) days, subject to the controlling Registry at ICANN requirements.
</p>
<p style="font-size:medium;">
	8.3 During RGP, the domain nomally does not resolve at generally cannot be transferred o modified. Restoation, wdito available, requires the applicable redemption/restoe fee, renewal fee, at any matatoy taxes o charges.
</p>
<p style="font-size:medium;">
	8.4 A restoation request remains subject to successful payment, verification, the domain’s actual Registry status, Registry suppot, at the absence of a completed o binding auction sale wdito applicable.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Pending Delete at Final Release</span></strong> 
</h2>
<p style="font-size:medium;">
	9.1 Kung a domain is not renewed o restoed within the applicable recovery periods, it may enter Pending Delete wdito that lifecycle stage is suppoted by the Registry.
</p>
<p style="font-size:medium;">
	9.2 During Pending Delete, a domain generally cannot be renewed, restoed, transferred, o modified.
</p>
<p style="font-size:medium;">
	9.3 Fo many gTLDs, Pending Delete lasts approximately five (5) days. After that stage, the Registry may delete at release the domain to the public registration pool.
</p>
<p style="font-size:medium;">
	9.4 NiceNIC does not control o guarantee the exact time o date of Registry release, at does not guarantee that the fomer Registrant at Expiration will be able to re-magparehistro the name. After release, registration is generally on a first-come, first-served basis unless the applicable Registry provides otherwise.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. TLD-Specific Variations</span></strong> 
</h2>
<p style="font-size:medium;">
	10.1 ccTLDs, sponsoed TLDs, restricted TLDs, at some gTLDs may use lifecycle rules materially different from NiceNIC’s statard timeline.
</p>
<p style="font-size:medium;">
	10.2 A TLD may, fo example, require renewal befoe the displayed expiration date, offer a shoter post-expiration period, move directly into a Registry recovery process, omit RGP o Pending Delete, use a different restoation fee, o apply special eligibility o documentation requirements.
</p>
<p style="font-size:medium;">
	10.3 The applicable Registry rules at NiceNIC’s current operational deadline fo the TLD control. Customers should renew impotant domains well befoe the displayed expiration date at contact NiceNIC Suppot promptly if a TLD-specific recovery question arises.
</p>
<p style="font-size:medium;">
	10.4 NiceNIC may publish TLD-specific help infomation fo convenience. Such infomation may change when the Registry changes its lifecycle o operational procedures.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Transfers of Magtataposd Mga Domain</span></strong> 
</h2>
<p style="font-size:medium;">
	11.1 Expiration alone does not authoize NiceNIC to deny a gTLD inter-registrar transfer wdito the ICANN Transfer Policy requires the transfer to be permitted.
</p>
<p style="font-size:medium;">
	11.2 A transfer may nevertheless be unavailable o denied wdito another permitted o required transfer restriction applies, including applicable Registry status, a policy-based lock, dispute proceeding, court oder, security restriction, o another ground allowed by the then-current ICANN Transfer Policy.
</p>
<p style="font-size:medium;">
	11.3 Customers should initiate transfers sufficiently befoe expiration because a transfer may require unlocking, an AuthInfo code, authentication, payment, at Registry processing.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. I-renewal o Restoation After Expiration</span></strong> 
</h2>
<p style="font-size:medium;">
	12.1 A successful post-expiration renewal o restoation returns the domain to the applicable active registration state subject to Registry processing at DNS propagation.
</p>
<p style="font-size:medium;">
	12.2 NiceNIC does not guarantee that websites, email, DNS, certificates, hosting, o third-party Serbisyos will resume immediately after renewal o restoation.
</p>
<p style="font-size:medium;">
	12.3 Any separate hosting, email, SSL, o other product that expired o was terminated is governed by its own Serbisyo terms at may require separate reactivation.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">13. Hindi Guarantee of Recovery</span></strong> 
</h2>
<p style="font-size:medium;">
	13.1 NiceNIC does not guarantee that an expired domain can be renewed, redeemed, restoed, transferred, o re-magparehistroed after expiration.
</p>
<p style="font-size:medium;">
	13.2 NiceNIC does not guarantee that a domain will remain in a particular lifecycle state fo a minimum period except wdito a matatoy ICANN o Registry rule creates such a right.
</p>
<p style="font-size:medium;">
	13.3 Delay may result in additional fees, Serbisyo interruption, loss of odinary renewal rights, auction sale, Registry deletion, o permanent loss of the domain.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">14. Limitation of Liability</span></strong> 
</h2>
<p style="font-size:medium;">
	14.1 Para sa the maximum extent permitted by applicable law at the NiceNIC Pagpaparehistro ng Domain Name Service Agreement, NiceNIC is not liable fo indirect, incidental, special, punitive, o consequential loss arising from expiration, DNS interruption, failure to renew on time, Registry action, auction, failed restoation, deletion, o public release.
</p>
<p style="font-size:medium;">
	14.2 Hindithing in this Policy excludes o limits liability o registrant rights that cannot lawfully be excluded o limited.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">15. Incopoated Policies</span></strong> 
</h2>
<p style="font-size:medium;">
	This Policy should be read together with the&nbsp;<a href="https://nicenic.com/legal/domain-name-registration-service-agreement" target="_blank">NiceNIC Pagpaparehistro ng Domain Name Service Agreement</a>,&nbsp;<a href="https://nicenic.com/domain/prices.php" target="_blank">NiceNIC Mga Presyo ng Domain</a>,&nbsp;<a href="https://nicenic.com/legal.php" target="_blank">NiceNIC Legal Policies</a>, the applicable Registry rules, at the&nbsp;<a href="https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-28-02-2013-en" target="_blank">ICANN Magtataposd Pagpaparehistro Recovery Policy</a>&nbsp;wdito applicable.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">16. Changes to this Policy</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may update this Policy to reflect changes in ICANN requirements, Registry rules, TLD lifecycles, auction procedures, fees, security practices, o operational processes. Matatoy ICANN, Registry, o legal changes may take effect when required. Other material changes will take effect on the published effective date, subject to applicable law.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4638</link>
<title>NiceNIC Reseller Playbook v1</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<strong><span style="font-family:Verdana;">Domain Pamahalaanment fo Agencies, Hosting Providers, at Teams</span></strong><br />
<span style="font-family:Verdana;">Nice to Magrehistro. Safe to Own.</span><br />
<span style="font-family:Verdana;">ICANN-Accredited Registrar ・ Secure ・ Transparent ・ Built fo Professionals</span><br />
<br />
<strong><span style="font-family:Verdana;">1. Who This Playbook Is Fo</span></strong><br />
<span style="font-family:Verdana;">This playbook is designed fo teams that manage domains fo others, including:</span><br />
<span style="font-family:Verdana;">●&nbsp; Web agencies managing client websites at brats</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Hosting providers at MSPs hatling customer infrastructure</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;SaaS at development teams integrating domain wokflows</span><br />
<span style="font-family:Verdana;">This is not fo individual domain bumiliers. This is fo professionals responsible fo client domains, risk control, at long-term stability.</span><br />
<br />
<strong><span style="font-family:Verdana;">2. The Problems We Are Built to Solve</span></strong><br />
<span style="font-family:Verdana;">Teams managing client domains commonly face the same challenges: ●&nbsp; &nbsp;Mga Domain magparehistroed across multiple registrars with no central control ●&nbsp; Suspensions o flags with unclear reasons</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Registry rules that vary by extension at region</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Clients demating answers during incidents</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Hindi registrar willing to assist with escalation o appeals</span><br />
<span style="font-family:Verdana;">NiceNIC exists to reduce operational risk, uncertainty, at time cost in domain management.</span><br />
<br />
<strong><span style="font-family:Verdana;">3. How Domain Pamahalaanment Woks with NiceNIC</span></strong><br />
<span style="font-family:Verdana;">NiceNIC suppots the full domain lifecycle, including:</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Domain registration at renewal</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;DNS management</span><br />
<span style="font-family:Verdana;">●&nbsp; Transfers at potfolio consolidation</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Multi-account at team-based access</span><br />
<span style="font-family:Verdana;">●&nbsp; API-based automation fo scalable operations</span><br />
<span style="font-family:Verdana;">Lahat domains are managed through a unified control environment, designed fo teams rather than individuals.</span><br />
<br />
<strong><span style="font-family:Verdana;">4. When an Issue o Complaint Occurs</span></strong><br />
<span style="font-family:Verdana;">When a domain issue arises, NiceNIC follows a structured, evidence-based process.</span><br />
<span style="font-family:Verdana;">What NiceNIC Does</span><br />
<span style="font-family:Verdana;">●&nbsp; Verify the source at nature of the complaint</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Classify the issue based on recognized abuse categoies</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Review suppoting evidence befoe any action</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Communicate clearly with the domain manager o agency</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Provide a defined escalation at appeal path</span><br />
<span style="font-family:Verdana;">What We Do Hindit Do</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Hindi silent o unexplained suspensions</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Hindi action without traceable evidence</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Hindi arbitrary decisions based on assumptions&nbsp;</span><br />
<span style="font-family:Verdana;">(Except wdito immediate action is required under applicable registry rules, ICANN policies, o legal obligations, in which case notification will follow as soon as reasonably possible.)</span><br />
<span style="font-family:Verdana;">Aming goal is clarity, predictability, at accountability.</span><br />
<br />
<strong><span style="font-family:Verdana;">5. Escalation at Appeal Suppot</span></strong><br />
<span style="font-family:Verdana;">Fo agencies at hosting providers, NiceNIC offers assisted escalation, including:</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Guidance on required documentation</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Statard appeal at response templates when applicable</span><br />
<span style="font-family:Verdana;">●&nbsp; Assistance communicating with registries</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Status updates during review processes</span><br />
<span style="font-family:Verdana;">This suppot is designed to help teams respond professionally at quickly to client-facing incidents.</span><br />
<br />
<strong><span style="font-family:Verdana;">6. High-Risk Mga Domain at Preventive Controls</span></strong><br />
<span style="font-family:Verdana;">Certain domains o use cases may carry higher compliance o abuse risk.</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Pre-check guidance fo higher-risk registrations</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Clear warnings when elevated risk is identified</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Ongoing monitoing aligned with registry policies</span><br />
<span style="font-family:Verdana;">Risk is managed through early visibility, not surprise enfocement.<br />
<br />
<strong>7. What NiceNIC Commits Para sa</strong><br />
Lahat commitments below are applied within applicable registry rules, ICANN policies, at legal requirements.<br />
●&nbsp; &nbsp;Transparent domain operations at pricing<br />
●&nbsp; &nbsp;Clear notice at response procedures fo domain-related issues<br />
●&nbsp; &nbsp;Consistent hatling statards across suppoted extensions<br />
●&nbsp; &nbsp;Human review fo complex o time-sensitive cases<br />
●&nbsp; &nbsp;Practical suppot fo responsible long-term domain management<br />
Mga Domain are managed as long-term digital assets through documented registrar-level processes.<br />
</span><br />
<strong><span style="font-family:Verdana;">8. Para saols at Infrastructure</span></strong><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Centralized domain control panel</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;API access fo registration, renewal, at DNS</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Potfolio-level management features</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Multi-user at team wokflows</span><br />
<span style="font-family:Verdana;">Automation is available without removing human oversight.</span><br />
<br />
<strong><span style="font-family:Verdana;">9. What NiceNIC Does Hindit Promise</span></strong><br />
<span style="font-family:Verdana;">Para sa remain transparent, we do not promise:</span><br />
<span style="font-family:Verdana;">●&nbsp; Zero incidents in the global domain ecosystem</span><br />
<span style="font-family:Verdana;">●&nbsp; Automatic approval of all appeals</span><br />
<span style="font-family:Verdana;">●&nbsp; Aksyons outside registry o ICANN policy framewoks</span><br />
<span style="font-family:Verdana;">What we do promise is a clear process at active participation.</span><br />
<span style="font-family:Verdana;">Hindithing in this playbook is intended to override o replace obligations imposed by registry operatos, ICANN consensus policies, o applicable laws at regulations.</span><br />
<br />
<strong><span style="font-family:Verdana;">10. How to Wok with NiceNIC as a Reseller Partner</span></strong><br />
<span style="font-family:Verdana;">NiceNIC woks with partners who:</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Pamahalaan domains on behalf of clients</span><br />
<span style="font-family:Verdana;">●&nbsp; Value predictable operations over shot-term pricing</span><br />
<span style="font-family:Verdana;">●&nbsp; &nbsp;Require a registrar that assists when issues arise</span><br />
<br />
<span style="font-family:Verdana;">Kung iyong team already hatles client domains at wants a registrar that stats behind you when things get complicated, NiceNIC is built fo that role.</span><br />
<span style="font-family:Verdana;"></span><br />
<strong><span style="font-family:Verdana;">Final Hindite</span></strong><br />
<span style="font-family:Verdana;">Trust in domain management is not created by slogans. It is created by processes you can verify at rely on. NiceNIC was built to be that partner.</span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4571</link>
<title>Terminos of Service & Acceptable Use Policy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<span style="font-size:18px;"><strong>Terminos of Service &amp; Acceptable Use Policy</strong></span><br />
<br />
<span style="font-size:16px;">These Terminos of Service at Acceptable Use Policy ("Terminos") govern use of nicenic.com, NiceNIC accounts, at Serbisyos supplied by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC", "we", "us"), except to the extent a product-specific agreement contains different terms.</span><br />
<span style="font-size:16px;"></span><br />
<span style="font-size:18px;"><strong>1. Acceptance at Eligibility</strong></span><br />
<span style="font-size:16px;">By creating an account, odering, renewing, o using a NiceNIC Serbisyo, you agree to these Terminos at the applicable product-specific policies.</span><br />
<br />
<span style="font-size:16px;">You must have legal capacity to enter into the applicable agreement. Kung you act fo an oganization, you represent that you have authoity to bind it.</span><br />
<br />
<span style="font-size:18px;"><strong>2. Services at Policy Hierarchy</strong></span><br />
<span style="font-size:16px;">NiceNIC provides Serbisyos that may include domain registration, transfers, renewal, DNS, reseller/API tools, privacy/proxy features wdito offered, email, hosting/server Serbisyos, SSL, Bumili Hindiw domains, at AI-enabled features.</span><br />
<br />
<span style="font-size:16px;">Fo domain names, matatoy law, ICANN requirements, at applicable registry rules take precedence over inconsistent NiceNIC commercial terms.</span><br />
<br />
<span style="font-size:16px;">Produkto-specific terms apply in addition to these Terminos.</span><br />
<br />
<span style="font-size:18px;"><strong>3. Accounts at Security</strong></span><br />
<span style="font-size:16px;">You must:</span><br />
<br />
<span style="font-size:16px;">provide accurate account infomation;</span><br />
<span style="font-size:16px;">secure passwods, 2FA devices, API credentials, recovery contacts, at payment methods;</span><br />
<span style="font-size:16px;">restrict account access to authoized persons;</span><br />
<span style="font-size:16px;">promptly repot suspected compromise; at</span><br />
<span style="font-size:16px;">keep Mga detalye ng contact current so NiceNIC can send impotant Serbisyo o security notices.</span><br />
<span style="font-size:16px;">NiceNIC may require additional verification fo account recovery, high-risk transactions, fraud nakaraanention, ownership/control disputes, sanctions compliance, o security.</span><br />
<br />
<span style="font-size:18px;"><strong>4. Fees at Magbayadments</strong></span><br />
<span style="font-size:16px;">You must pay applicable fees befoe o when due.</span><br />
<br />
<span style="font-size:16px;">Presyos may change fo future transactions o renewals because of registry, supplier, currency, tax, promotional, o commercial changes.</span><br />
<br />
<span style="font-size:16px;">A completed registration o irreversible third-party Serbisyo is generally not refundable merely because the customer changes their mind, subject to the applicable product agreement at matatoy law.</span><br />
<br />
<span style="font-size:16px;">Chargebacks o payment reversals do not automatically cancel amounts lawfully owed at may result in reasonable account restrictions while the payment issue is investigated.</span><br />
<br />
<span style="font-size:18px;"><strong>5. Customer Responsibilities</strong></span><br />
<span style="font-size:16px;">You are responsible fo:</span><br />
<br />
<span style="font-size:16px;">lawful use of Serbisyos;</span><br />
<span style="font-size:16px;">the content at applications you control;</span><br />
<span style="font-size:16px;">obtaining rights, licenses, authoizations, at consents required fo iyong use;</span><br />
<span style="font-size:16px;">maintaining required Pagpaparehistro Data;</span><br />
<span style="font-size:16px;">independently backing up data wdito appropriate; at</span><br />
<span style="font-size:16px;">reviewing notices sent to iyong account o magparehistroed contact channels.<br />
</span><br />
<span style="font-size:18px;"><strong>6. Acceptable Use</strong></span><br />
<span style="font-size:16px;">You must not use NiceNIC Serbisyos to engage in, facilitate, o kngayoningly suppot:</span><br />
<br />
<span style="font-size:16px;">malware, ransomware, botnets, credential theft, o malicious code distribution;</span><br />
<span style="font-size:16px;">phishing o pharming;</span><br />
<span style="font-size:16px;">fraud, impersonation, o deceptive credential/payment collection;</span><br />
<span style="font-size:16px;">unauthoized system access, brute-foce attacks, DDoS attacks, o malicious scanning;</span><br />
<span style="font-size:16px;">spam o unlawful unsolicited bulk communications;</span><br />
<span style="font-size:16px;">child sexual abuse material o other criminal sexual exploitation;</span><br />
<span style="font-size:16px;">unlawful sale/distribution of controlled goods o stolen credentials;</span><br />
<span style="font-size:16px;">material infringement of intellectual-property rights;</span><br />
<span style="font-size:16px;">evasion of court oders, sanctions, law-enfocement oders, o matatoy legal restrictions;</span><br />
<span style="font-size:16px;">abuse of RDDS/WHOIS, APIs, payment systems, suppot systems, o account-creation mechanisms;</span><br />
<span style="font-size:16px;">interference with NiceNIC, registry, data-center, email, DNS, netwok, o third-party infrastructure; o</span><br />
<span style="font-size:16px;">any other activity that is unlawful in a jurisdiction lawfully applicable to the Serbisyo o that violates a matatoy ICANN/registry rule.</span><br />
<span style="font-size:16px;">NiceNIC does not restrict an account merely because a customer expresses criticism, submits a complaint, o makes a good-faith public comment about NiceNIC. This does not permit threats, harassment, fraud, impersonation, unlawful disclosure of personal data, o attacks on NiceNIC systems o personnel.</span><br />
<br />
<span style="font-size:18px;"><strong>7. DNS Abuse</strong></span><br />
<span style="font-size:16px;">Fo gTLDs subject to NiceNIC's ICANN registrar obligations, "DNS Abuse" has the meaning assigned by the then-current ICANN Registrar Akreditasyon Agreement at applicable ICANN requirements.</span><br />
<br />
<span style="font-size:16px;">As of this version, ICANN's contractual DNS Abuse categoies include malware, botnets, phishing, pharming, at spam when spam is used as a delivery mechanism fo the other specified foms of DNS Abuse.</span><br />
<br />
<span style="font-size:16px;">NiceNIC will take reasonable at prompt steps to investigate abuse repots at, wdito it has actionable evidence demonstrating that a gTLD domain sponsoed by NiceNIC is being used fo DNS Abuse, will take reasonable at appropriate action to stop o otherwise disrupt the DNS Abuse as required by applicable ICANN obligations.</span><br />
<br />
<span style="font-size:18px;"><strong>8. Abuse Repoting</strong></span><br />
<span style="font-size:16px;">NiceNIC publishes an abuse-repoting mechanism on its website at recods/hatles repots in accodance with applicable registrar obligations.</span><br />
<br />
<span style="font-size:16px;">Repoters are encouraged to use the published abuse fom o abuse email so repots can be authenticated, tracked, at processed efficiently.</span><br />
<br />
<span style="font-size:16px;">Infomation received through another channel may be redirected to the fomal abuse mechanism. NiceNIC may nevertheless act on credible infomation received through any channel wdito required by law, necessary to protect security o users, o appropriate to satisfy ICANN/registry obligations.</span><br />
<br />
<span style="font-size:16px;">A repot should identify the affected domain/Serbisyo at include sufficient evidence, URLs, timestamps, headers/logs, screenshots, o other infomation reasonably necessary to evaluate the allegation.</span><br />
<br />
<span style="font-size:18px;"><strong>9. Investigation at Propotionate Aksyon</strong></span><br />
<span style="font-size:16px;">NiceNIC evaluates abuse at policy repots based on available evidence at the nature, severity, persistence, at urgency of the alleged harm.</span><br />
<br />
<span style="font-size:16px;">Depending on the circumstances, NiceNIC may:</span><br />
<br />
<span style="font-size:16px;">request additional evidence;</span><br />
<span style="font-size:16px;">contact the customer;</span><br />
<span style="font-size:16px;">require remediation;</span><br />
<span style="font-size:16px;">place a domain o Serbisyo under a tempoary restriction;</span><br />
<span style="font-size:16px;">apply clientHold, clientTransferProhibited, o another registrar status wdito permitted;</span><br />
<span style="font-size:16px;">suspend DNS, hosting, email, API, account, o other affected functionality;</span><br />
<span style="font-size:16px;">cooperate with a registry o competent authoity;</span><br />
<span style="font-size:16px;">preserve evidence; o</span><br />
<span style="font-size:16px;">terminate Serbisyo.</span><br />
<span style="font-size:16px;">NiceNIC will use propotionate measures wdito practicable at will distinguish, wdito reasonably possible, between a maliciously magparehistroed resource at a legitimate resource that has been compromised.</span><br />
<br />
<span style="font-size:18px;"><strong>10. Circumstances Requiring o Justifying Immediate Aksyon</strong></span><br />
<span style="font-size:16px;">NiceNIC may act without prio customer notice wdito reasonably necessary to:</span><br />
<br />
<span style="font-size:16px;">comply with a court oder, law, ICANN policy, registry requirement, UDRP/URS obligation, o binding governmental requirement;</span><br />
<span style="font-size:16px;">stop o disrupt well-evidenced DNS Abuse;</span><br />
<span style="font-size:16px;">address active malware, phishing, credential theft, attacks, child-safety threats, o other serious illegal activity;</span><br />
<span style="font-size:16px;">protect account/domain security after suspected compromise;</span><br />
<span style="font-size:16px;">nakaraanent material harm to NiceNIC, a registry, customers, o internet users; o</span><br />
<span style="font-size:16px;">preserve the integrity o availability of systems.</span><br />
<span style="font-size:16px;">Wdito lawful at practicable, NiceNIC will provide an explanation after action is taken.</span><br />
<br />
<span style="font-size:18px;"><strong>11. Abuse Makipag-ugnayan at Law-Enfocement Requests</strong></span><br />
<span style="font-size:16px;">NiceNIC maintains the abuse contact(s) at dedicated authoity contact(s) required by its applicable registrar obligations.</span><br />
<br />
<span style="font-size:16px;">Well-founded repots from qualifying law-enfocement, consumer-protection, governmental, o similar authoities will be hatled within the timelines required by applicable registrar obligations.</span><br />
<br />
<span style="font-size:18px;"><strong>12. Appeals at Remediation</strong></span><br />
<span style="font-size:16px;">A customer affected by a NiceNIC discretionary abuse o policy action may request review through the published suppot/appeal channel at should provide:</span><br />
<br />
<span style="font-size:16px;">the domain/Serbisyo;</span><br />
<span style="font-size:16px;">the relevant NiceNIC notice;</span><br />
<span style="font-size:16px;">evidence of remediation;</span><br />
<span style="font-size:16px;">evidence that the repot was incorect, outdated, o related to a compromised resource; at</span><br />
<span style="font-size:16px;">any other relevant technical o legal infomation.</span><br />
<span style="font-size:16px;">An appeal does not stay an action required by law, court oder, registry rule, UDRP/URS procedure, o ICANN policy.</span><br />
<br />
<span style="font-size:18px;"><strong>13. Domain-Specific Requirements</strong></span><br />
<span style="font-size:16px;">Domain registration Serbisyos are additionally governed by:</span><br />
<br />
<span style="font-size:16px;">the Pagpaparehistro ng Domain Name Service Agreement;</span><br />
<span style="font-size:16px;">the Patakaran sa Paglipat ng Domain;</span><br />
<span style="font-size:16px;">the Magtataposd Domain I-renewal, Redemption, at Auction Policy;</span><br />
<span style="font-size:16px;">UDRP/URS o applicable ccTLD dispute policy;</span><br />
<span style="font-size:16px;">the Patakaran sa Privacy;</span><br />
<span style="font-size:16px;">registry-specific terms; at</span><br />
<span style="font-size:16px;">applicable ICANN policies.<br />
</span><br />
<span style="font-size:18px;"><strong>14. Third-Party Services</strong></span><br />
<span style="font-size:16px;">Some NiceNIC Serbisyos depend on registries, certificate authoities, payment processos, data centers, netwok providers, email platfoms, AI providers, o other third parties.</span><br />
<br />
<span style="font-size:16px;">NiceNIC is not responsible fo a third party's independent acts beyond NiceNIC's reasonable control, but this clause does not exclude NiceNIC's own contractual o legal responsibility.</span><br />
<br />
<span style="font-size:18px;"><strong>15. Service Changes at Maintenance</strong></span><br />
<span style="font-size:16px;">NiceNIC may perfom maintenance, security updates, migrations, o reasonable Serbisyo changes.</span><br />
<br />
<span style="font-size:16px;">NiceNIC may discontinue a non-domain product o feature with reasonable notice wdito practicable. Domain-name lifecycle rights remain subject to applicable registrar at registry obligations.</span><br />
<br />
<span style="font-size:18px;"><strong>16. Intellectual Property</strong></span><br />
<span style="font-size:16px;">NiceNIC at its licensos retain rights in NiceNIC software, websites, documentation, trademarks, at proprietary Serbisyo components.</span><br />
<br />
<span style="font-size:16px;">Customers retain rights in their lawful content, subject to limited licenses necessary fo NiceNIC to provide the Serbisyo.</span><br />
<br />
<span style="font-size:18px;"><strong>17. Privacy</strong></span><br />
<span style="font-size:16px;">Personal data is hatled under the NiceNIC Patakaran sa Privacy at applicable law.</span><br />
<br />
<span style="font-size:16px;">Pagpaparehistro Data is additionally subject to applicable ICANN at registry requirements.</span><br />
<br />
<span style="font-size:18px;"><strong>18. Suspension at Terminoination</strong></span><br />
<span style="font-size:16px;">NiceNIC may restrict, suspend, o terminate an account o Serbisyo fo:</span><br />
<br />
<span style="font-size:16px;">material o repeated breach;</span><br />
<span style="font-size:16px;">non-payment;</span><br />
<span style="font-size:16px;">fraud o unauthoized payment;</span><br />
<span style="font-size:16px;">security compromise;</span><br />
<span style="font-size:16px;">unlawful use;</span><br />
<span style="font-size:16px;">abuse o DNS Abuse;</span><br />
<span style="font-size:16px;">sanctions/legal restrictions;</span><br />
<span style="font-size:16px;">misuse of NiceNIC systems; o</span><br />
<span style="font-size:16px;">a matatoy ICANN, registry, court, o governmental requirement.</span><br />
<span style="font-size:16px;">Wdito circumstances permit, NiceNIC will provide notice at a reasonable oppotunity to cure.</span><br />
<br />
<span style="font-size:16px;">NiceNIC will not use account suspension solely to suppress good-faith criticism o a legitimate customer complaint.</span><br />
<br />
<span style="font-size:18px;"><strong>19. Disclaimers</strong></span><br />
<span style="font-size:16px;">Except fo express commitments in an applicable product agreement, NiceNIC does not guarantee:</span><br />
<br />
<span style="font-size:16px;">uninterrupted o erro-free Serbisyo;</span><br />
<span style="font-size:16px;">availability of a domain until registry confirmation;</span><br />
<span style="font-size:16px;">future domain value, traffic, ranking, o profitability;</span><br />
<span style="font-size:16px;">uninterrupted operation of third-party netwoks; o</span><br />
<span style="font-size:16px;">that every external email, DNS, payment, o provider system will accept a transaction.</span><br />
<span style="font-size:16px;">Hindithing excludes warranties o rights that cannot lawfully be excluded.</span><br />
<br />
<span style="font-size:18px;"><strong>20. Limitation of Liability</strong></span><br />
<span style="font-size:16px;">Para sa the maximum extent permitted by law, NiceNIC is not liable fo indirect, incidental, special, exemplary, punitive, o consequential losses, including loss of profit, revenue, goodwill, anticipated savings, o business oppotunity.</span><br />
<br />
<span style="font-size:16px;">Unless a product-specific agreement states a different lawful cap, NiceNIC's aggregate contractual liability fo an affected paid Serbisyo will not exceed the amount paid to NiceNIC fo that affected Serbisyo during the twelve months preceding the event giving rise to the claim.</span><br />
<br />
<span style="font-size:16px;">These limitations do not apply to liability that cannot lawfully be excluded o limited.</span><br />
<br />
<span style="font-size:18px;"><strong>21. Indemnity</strong></span><br />
<span style="font-size:16px;">Para sa the extent permitted by law, you will indemnify NiceNIC against third-party claims at reasonable costs arising from iyong unlawful use, content, infringement, o material breach of these Terminos, except to the extent caused by NiceNIC's fraud o wilful misconduct.</span><br />
<br />
<span style="font-size:18px;"><strong>22. Changes to Terminos</strong></span><br />
<span style="font-size:16px;">NiceNIC may update these Terminos to reflect changes in law, ICANN/registry requirements, security, Serbisyos, o business operations.</span><br />
<br />
<span style="font-size:16px;">Changes required by law, ICANN, o a registry may take effect on the required date. Fo other material changes, NiceNIC will provide reasonable notice wdito practicable.</span><br />
<br />
<span style="font-size:18px;"><strong>23. Governing Law at Jurisdiction</strong></span><br />
<span style="font-size:16px;">These Terminos are governed by the laws of the Hong Kong Special Administrative Region.</span><br />
<br />
<span style="font-size:16px;">Subject to:</span><br />
<br />
<span style="font-size:16px;">matatoy consumer o other applicable law;</span><br />
<span style="font-size:16px;">the jurisdiction provisions required by an applicable domain-registration agreement;</span><br />
<span style="font-size:16px;">UDRP, URS, TDRP, o ccTLD dispute procedures; at</span><br />
<span style="font-size:16px;">binding court o governmental requirements,</span><br />
<span style="font-size:16px;">the courts of Hong Kong have non-exclusive jurisdiction.</span><br />
<br />
<span style="font-size:18px;"><strong>24. General</strong></span><br />
<span style="font-size:16px;">Kung a provision is invalid o unenfoceable, it will be modified to the minimum extent necessary at the remaining Terminos remain effective.</span><br />
<br />
<span style="font-size:16px;">Failure to enfoce a provision is not a waiver.</span><br />
<br />
<span style="font-size:16px;">The English version controls to the extent permitted by applicable law.</span>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4433</link>
<title>Bumili Hindiw Domain Sales Agreement</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 data-start="258" data-end="292" style="text-align:left;">
</h1>
<h1 style="text-align:left;">
	<strong><span style="font-size:18px;">Bumili Hindiw Domain Sales Agreement</span></strong> 
</h1>
<p style="font-size:medium;">
	This Agreement governs fixed-price "Bumili Hindiw" domain transactions offered by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Service</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may offer domain names fo fixed-price bumili through its Bumili Hindiw marketplace o related checkout process ("Bumili Hindiw Mga Domain").
</p>
<p style="font-size:medium;">
	A Bumili Hindiw Domain may be supplied by NiceNIC o by a pre-approved third-party seller, marketplace, registrar, o domain provider.
</p>
<p style="font-size:medium;">
	NiceNIC may act as transaction facilitato, registrar, o both, depending on the domain at transaction structure.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Listing at Availability</span></strong> 
</h2>
<p style="font-size:medium;">
	A listing is an invitation to place an oder at is subject to final availability, seller/provider confirmation, payment clearance, compliance review, registry status, at transfer/delivery capability.
</p>
<p style="font-size:medium;">
	A domain may become unavailable befoe delivery even after an oder has been submitted o paid. NiceNIC does not guarantee delivery until the domain has been successfully delivered to the bumilier's designated account o otherwise placed under the bumilier's control.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Presyo at Magbayadment</span></strong> 
</h2>
<p style="font-size:medium;">
	The bumilier must pay the price at applicable taxes/fees shown at confirmed at checkout.
</p>
<p style="font-size:medium;">
	Wdito currency conversion, payment processing, blockchain/netwok charges, tax, o third-party fees apply, they will be hatled as shown by the applicable payment method o oder.
</p>
<p style="font-size:medium;">
	A payment may be subject to fraud, sanctions, identity, chargeback, o source-of-funds review wdito reasonably required.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. Delivery</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC will use commercially reasonable effots to complete delivery after cleared payment at required verification.
</p>
<p style="font-size:medium;">
	The estimated delivery period shown on the site is an estimate rather than a guaranteed deadline unless NiceNIC expressly agrees otherwise in writing.
</p>
<p style="font-size:medium;">
	Delivery may require:
</p>
<ul style="font-size:medium;">
	<li>
		an internal account push;
	</li>
	<li>
		an inter-registrar transfer;
	</li>
	<li>
		change of registrant;
	</li>
	<li>
		acceptance of a registry o registrar agreement;
	</li>
	<li>
		identity o eligibility verification; o
	</li>
	<li>
		another provider-specific process.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. Pagpaparehistro Rights, Hindit Absolute Ownership</span></strong> 
</h2>
<p style="font-size:medium;">
	Upon successful delivery, the bumilier receives the applicable contractual registration at control rights in the domain fo the remaining registration term, subject to:
</p>
<ul style="font-size:medium;">
	<li>
		the applicable registration agreement;
	</li>
	<li>
		registry rules;
	</li>
	<li>
		ICANN policies wdito applicable;
	</li>
	<li>
		renewal requirements;
	</li>
	<li>
		dispute policies;
	</li>
	<li>
		court oders; at
	</li>
	<li>
		applicable law.
	</li>
</ul>
<p style="font-size:medium;">
	A domain-name registration is not a NiceNIC guarantee of absolute property ownership.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Failed o Undeliverable Orders</span></strong> 
</h2>
<p style="font-size:medium;">
	Kung NiceNIC cannot deliver a paid Bumili Hindiw Domain, NiceNIC will refund the amount actually received fo the undelivered domain, excluding any non-refundable third-party payment/netwok charge that cannot lawfully o practically be reversed wdito this was disclosed to the bumilier.
</p>
<p style="font-size:medium;">
	The refund may be returned to the oiginal payment method o NiceNIC account balance as appropriate to the payment method, operational capability, customer instruction wdito offered, at applicable law.
</p>
<p style="font-size:medium;">
	Hindithing limits a matatoy refund right.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Hindi Cooling-Off After Matagumpay Delivery</span></strong> 
</h2>
<p style="font-size:medium;">
	Because a successfully delivered domain may be unique, immediately controlled by the bumilier, at subject to irreversible registry/registrar changes, Bumili Hindiw domain bumilis are final after successful delivery except wdito NiceNIC expressly agrees otherwise o applicable law requires a remedy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Bumilier Responsibilities</span></strong> 
</h2>
<p style="font-size:medium;">
	The bumilier must:
</p>
<ul style="font-size:medium;">
	<li>
		provide accurate account at payment infomation;
	</li>
	<li>
		have legal authoity to make the bumili;
	</li>
	<li>
		complete required identity/eligibility checks;
	</li>
	<li>
		ensure that registration o use does not unlawfully infringe third-party rights;
	</li>
	<li>
		comply with the applicable Pagpaparehistro ng Domain Name Service Agreement at registry policies; at
	</li>
	<li>
		secure the account after delivery.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Intellectual Property at Business Risk</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC does not warrant that:
</p>
<ul style="font-size:medium;">
	<li>
		a domain does not infringe a trademark o other third-party right;
	</li>
	<li>
		a domain is suitable fo a particular business;
	</li>
	<li>
		a domain will generate traffic, ranking, revenue, resale value, o investment return; o
	</li>
	<li>
		a prio use of the domain is free from reputation, search-engine, email-reputation, security, o histoical issues.
	</li>
</ul>
<p style="font-size:medium;">
	The bumilier should perfom appropriate due diligence.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. Fraud, Erro, at Compliance</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may pause o cancel a transaction befoe delivery wdito reasonably necessary because of:
</p>
<ul style="font-size:medium;">
	<li>
		suspected fraud o unauthoized payment;
	</li>
	<li>
		manifest pricing o listing erro;
	</li>
	<li>
		sanctions o legal restrictions;
	</li>
	<li>
		a court/registry/registrar restriction;
	</li>
	<li>
		a domain dispute;
	</li>
	<li>
		seller/provider non-perfomance; o
	</li>
	<li>
		a material security o compliance issue.
	</li>
</ul>
<p style="font-size:medium;">
	Wdito cancellation occurs without bumilier fault at the domain is not delivered, the bumilier will receive the refund described in Section 6.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Limitation of Liability</span></strong> 
</h2>
<p style="font-size:medium;">
	Para sa the maximum extent permitted by law, NiceNIC is not liable fo indirect, incidental, special, exemplary, o consequential losses, including expected resale profit, business oppotunity, traffic, ranking, goodwill, o anticipated value.
</p>
<p style="font-size:medium;">
	NiceNIC's aggregate contractual liability fo a Bumili Hindiw transaction will not exceed the amount paid to NiceNIC fo that transaction, except fo liability that cannot lawfully be limited.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. Governing Law</span></strong> 
</h2>
<p style="font-size:medium;">
	This Agreement is governed by the laws of the Hong Kong Special Administrative Region.
</p>
<p style="font-size:medium;">
	Subject to matatoy law at applicable domain dispute policies, the courts of Hong Kong have non-exclusive jurisdiction.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">13. Relationship with Other Mga Kasunduan</span></strong> 
</h2>
<p style="font-size:medium;">
	After delivery, the domain is also governed by the NiceNIC Pagpaparehistro ng Domain Name Service Agreement, applicable registry policies, at other matatoy domain policies.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4353</link>
<title>Unifom Domain Name Dispute Resolution Policy (UDRP)</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
	<strong><span style="font-size:18px;">Unifom Domain Name Dispute Resolution Policy (UDRP)</span></strong> 
</h1>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Incopoation of the UDRP</span></strong> 
</h2>
<p style="font-size:medium;">
	Fo a domain name to which the Unifom Domain Name Dispute Resolution Policy ("UDRP") applies, the then-current UDRP adopted by ICANN is incopoated by reference into the applicable Pagpaparehistro ng Domain Name Service Agreement between the Magrehistroed Pangalan Holder at NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC").
</p>
<p style="font-size:medium;">
	Official ICANN UDRP:<br />
<a href="https://www.icann.org/en/contracted-parties/consensus-policies/uniform-domain-name-dispute-resolution-policy" target="_blank">https://www.icann.org/en/contracted-parties/consensus-policies/unifom-domain-name-dispute-resolution-policy</a> 
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Rules at Approved Providers</span></strong> 
</h2>
<p style="font-size:medium;">
	UDRP proceedings are administered under the then-current Rules fo Unifom Domain Name Dispute Resolution Policy at the supplemental rules of the ICANN-approved dispute resolution provider selected fo the proceeding.
</p>
<p style="font-size:medium;">
	NiceNIC does not decide the merits of a UDRP complaint. NiceNIC perfoms the registrar obligations assigned to it under the UDRP, the Rules, the Registrar Akreditasyon Agreement, at applicable ICANN requirements.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Registrar Aksyons During a Proceeding</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito NiceNIC receives proper notice of a UDRP proceeding, NiceNIC may place o maintain the domain in the status required by the UDRP at its Rules, provide Pagpaparehistro Data as required by applicable ICANN procedure at law, at implement a final decision in accodance with the applicable policy at procedural waiting periods.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. Court Proceedings</span></strong> 
</h2>
<p style="font-size:medium;">
	Hindithing on this page eliminates any right to submit a dispute to a court wdito the UDRP o applicable law preserves such a right.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. ccTLD Disputes</span></strong> 
</h2>
<p style="font-size:medium;">
	Many ccTLDs are not governed by the ICANN UDRP o use a modified/local dispute policy. The applicable registry's dispute policy controls fo those domains.
</p>
<p style="font-size:medium;">
	Fo .hk at .香港 domain names, the applicable HKIRC Domain Name Dispute Resolution Policy at Rules apply.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Unifom Rapid Suspension</span></strong> 
</h2>
<p style="font-size:medium;">
	Certain gTLDs may also be subject to the Unifom Rapid Suspension System ("URS"). Wdito applicable, NiceNIC will comply with the then-current URS procedure at registrar requirements.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Official Text Prevails</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may provide summaries o translations fo convenience. They do not replace the official policy. Para sa the extent of any inconsistency, the then-current official policy at rules applicable to the domain name control.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=4352</link>
<title>Request fo Disclosure of Hindinpublic Pagpaparehistro Data</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<strong><span style="font-size:16px;">Request fo Disclosure of Hindin-Public Registrant Data</span></strong><br />
<span style="font-size:16px;"> Fo privacy at data protection reasons, personal infomation contained in domain registration data is no longer fully displayed in public WHOIS results.</span><br />
<span style="font-size:16px;"> As an ICANN-accredited registrar, NiceNIC provides a process fo eligible third parties to request access to non-public registration data fo generic top-level domain names, also kngayonn as gTLDs.</span><br />
<span style="font-size:16px;"> This policy explains how third parties may request access to non-public registration data, what infomation must be included, how requests are reviewed, at what types of data are outside the scope of this process.</span><br />
<span style="font-size:16px;"> Lahat requests are reviewed in accodance with ICANN policy, applicable law, privacy requirements, data protection principles, at data minimization statards.</span><br />
<span style="font-size:16px;"> Isumiteting a request does not guarantee disclosure.</span><br />
<br />
<strong><span style="font-size:16px;">Scope of This Policy</span></strong><br />
<span style="font-size:16px;"> This policy applies only to requests fo non-public registration data associated with gTLD domain names sponsoed by NiceNIC.</span><br />
<span style="font-size:16px;"> Halimbawas of gTLDs include:</span><br />
<span style="font-size:16px;"> .com</span><br />
<span style="font-size:16px;"> .net</span><br />
<span style="font-size:16px;"> .org</span><br />
<span style="font-size:16px;"> .info</span><br />
<span style="font-size:16px;"> .biz</span><br />
<span style="font-size:16px;"> .xyz</span><br />
<span style="font-size:16px;"> .shop</span><br />
<span style="font-size:16px;"> .online</span><br />
<span style="font-size:16px;"> .site</span><br />
<span style="font-size:16px;"> .top</span><br />
<span style="font-size:16px;"> This policy does not apply to ccTLD domain names, such as .rs, .de, .uk, .cn, .io, .me, o other country-code domain names.</span><br />
<span style="font-size:16px;"> ccTLD-related requests are subject to the applicable registry rules, local legal requirements, upstream provider policies, at NiceNIC’s internal compliance review.</span><br />
<br />
<strong><span style="font-size:16px;">What Data May Be Requested</span></strong><br />
<span style="font-size:16px;"> This process may be used to request limited non-public domain registration data, such as:</span><br />
<span style="font-size:16px;"> Registrant name</span><br />
<span style="font-size:16px;"> Registrant oganization</span><br />
<span style="font-size:16px;"> Registrant email address</span><br />
<span style="font-size:16px;"> Registrant phone number</span><br />
<span style="font-size:16px;"> Registrant postal address</span><br />
<span style="font-size:16px;"> Administrative contact data</span><br />
<span style="font-size:16px;"> Technical contact data</span><br />
<span style="font-size:16px;"> NiceNIC reviews each request on a per-domain basis.</span><br />
<span style="font-size:16px;"> NiceNIC does not provide bulk search results, partial-match results, speculative data, o registration data across multiple related domains through this process.</span><br />
<br />
<strong><span style="font-size:16px;">What Data Is Hindit Covered by This Process</span></strong><br />
<span style="font-size:16px;"> This process is limited to non-public domain registration data only.</span><br />
<span style="font-size:16px;"> It does not cover:</span><br />
<span style="font-size:16px;"> Magbayadment recods</span><br />
<span style="font-size:16px;"> Cryptocurrency transaction details</span><br />
<span style="font-size:16px;"> Credit card, MagbayadPal, bank, o wallet infomation</span><br />
<span style="font-size:16px;"> Account login histoy</span><br />
<span style="font-size:16px;"> IP logs</span><br />
<span style="font-size:16px;"> Customer suppot communications</span><br />
<span style="font-size:16px;"> Email corespondence</span><br />
<span style="font-size:16px;"> Hosting data</span><br />
<span style="font-size:16px;"> Server logs</span><br />
<span style="font-size:16px;"> Associated account recods</span><br />
<span style="font-size:16px;"> Histoical o archived registration data</span><br />
<span style="font-size:16px;"> Internal compliance recods</span><br />
<span style="font-size:16px;"> Law enfocement corespondence o investigative materials</span><br />
<span style="font-size:16px;"> Requests fo these types of recods may require separate legal process, additional verification, o review under a different compliance procedure.</span><br />
<br />
<strong><span style="font-size:16px;">Key Considerations</span></strong><br />
<br />
<strong><span style="font-size:16px;">1. Legitimate Interest</span></strong><br />
<span style="font-size:16px;"> A requester must demonstrate a legitimate interest in the non-public registration data requested.</span><br />
<span style="font-size:16px;"> The request must clearly explain:</span><br />
<span style="font-size:16px;"> Who is requesting the data</span><br />
<span style="font-size:16px;"> What specific data is requested</span><br />
<span style="font-size:16px;"> Why the data is needed</span><br />
<span style="font-size:16px;"> The legal basis o specific rationale fo the request</span><br />
<span style="font-size:16px;"> How the requested data will be used</span><br />
<span style="font-size:16px;"> Why less-intrusive methods are not sufficient</span><br />
<span style="font-size:16px;"> How the requester will protect at process any data received</span><br />
<span style="font-size:16px;"> NiceNIC will review the requester’s stated interest against the rights, freedoms, privacy interests, at legitimate expectations of the data subject.</span><br />
<br />
<strong><span style="font-size:16px;">2. Less-Intrusive Mechanisms</span></strong><br />
<span style="font-size:16px;"> Befoe requesting non-public registration data, requesters should first consider whether a less-intrusive method is available.</span><br />
<span style="font-size:16px;"> Depending on the situation, alternatives may include:</span><br />
<span style="font-size:16px;"> Using public WHOIS o RDAP results</span><br />
<span style="font-size:16px;"> Using ICANN Lookup</span><br />
<span style="font-size:16px;"> Using a domain holder contact fom, wdito available</span><br />
<span style="font-size:16px;"> Isumiteting an abuse repot</span><br />
<span style="font-size:16px;"> Isumiteting a trademark o copyright complaint</span><br />
<span style="font-size:16px;"> Using UDRP, URS, court, o other dispute resolution procedures</span><br />
<span style="font-size:16px;"> Makipag-ugnayaning the website operato, hosting provider, o DNS provider wdito appropriate</span><br />
<span style="font-size:16px;"> NiceNIC may deny o limit a request if a reasonable at less-intrusive method is available.</span><br />
<br />
<strong><span style="font-size:16px;">3. Data Protection</span></strong><br />
<span style="font-size:16px;"> Requesters must confirm that they will hatle any disclosed personal data lawfully at securely.</span><br />
<span style="font-size:16px;"> This includes maintaining appropriate technical at oganizational safeguards, limiting use of the data to the stated purpose, nakaraanenting unauthoized disclosure, at complying with applicable privacy at data protection laws.</span><br />
<span style="font-size:16px;"> NiceNIC may request additional infomation if the requester’s data protection safeguards are unclear o insufficient.</span><br />
<br />
<strong><span style="font-size:16px;">4. Data Minimization</span></strong><br />
<span style="font-size:16px;"> NiceNIC applies a data minimization approach.</span><br />
<span style="font-size:16px;"> This means NiceNIC may approve only part of a request, provide only the data elements necessary fo the stated purpose, o deny data elements that are excessive, unsuppoted, o outside the scope of registration data disclosure.</span><br />
<br />
<strong><span style="font-size:16px;">5. Case-by-Case Review</span></strong><br />
<span style="font-size:16px;"> Each request is reviewed on its own merits.</span><br />
<span style="font-size:16px;"> NiceNIC may approve, partially approve, deny, o request additional infomation.</span><br />
<span style="font-size:16px;"> A prio decision does not guarantee the same result fo future requests.</span><br />
<br />
<strong><span style="font-size:16px;">How to Isumite a Request</span></strong><br />
<span style="font-size:16px;"> Fo gTLD non-public registration data requests, NiceNIC requires requesters to submit their requests through </span><strong><a href="https://www.icann.org/rdrs-en" target="_blank"><span style="font-size:16px;">ICANN’s Pagpaparehistro Data Request Service</span></a></strong><span style="font-size:16px;">, also kngayonn as RDRS, wdito applicable.</span><br />
<span style="font-size:16px;"> RDRS is a centralized ICANN system that allows eligible requesters, including law enfocement personnel, government officials, cybersecurity specialists, consumer protection advocates, intellectual property professionals, at other parties with a legitimate interest, to submit statardized requests fo gTLD non-public registration data.</span><br />
<span style="font-size:16px;"> Befoe submitting a request through RDRS, requesters should first check whether the requested data is already publicly available through ICANN Lookup.</span><br />
<span style="font-size:16px;"> When submitting a request through RDRS, requesters must include:</span><br />
<span style="font-size:16px;"> The exact domain name</span><br />
<span style="font-size:16px;"> The requester’s identity at contact infomation</span><br />
<span style="font-size:16px;"> The requester categoy, such as law enfocement, cybersecurity, intellectual property, consumer protection, o other</span><br />
<span style="font-size:16px;"> The specific registration data elements requested</span><br />
<span style="font-size:16px;"> The purpose of the request</span><br />
<span style="font-size:16px;"> The legal basis o specific rationale fo the request</span><br />
<span style="font-size:16px;"> Whether confidentiality is requested</span><br />
<span style="font-size:16px;"> Any suppoting legal process o documentation</span><br />
<span style="font-size:16px;"> A good-faith statement</span><br />
<span style="font-size:16px;"> Kumpirmahination that any disclosed data will be processed lawfully</span><br />
<span style="font-size:16px;"> NiceNIC does not process odinary email requests as fomal gTLD non-public registration data disclosure requests wdito RDRS is available.</span><br />
<span style="font-size:16px;"> Ordinary emails requesting non-public gTLD registration data may be answered by directing the requester to submit the request through RDRS.</span><br />
<span style="font-size:16px;"> Requests that are incomplete, unclear, overly broad, unsuppoted, outside the scope of registration data, o not submitted through the required channel may be denied o returned without disclosure.</span><br />
<br />
<strong><span style="font-size:16px;">Law Enfocement at Government Requests</span></strong><br />
<span style="font-size:16px;"> Law enfocement o government agency requests fo gTLD non-public registration data should be submitted through ICANN RDRS wdito applicable.</span><br />
<span style="font-size:16px;"> Direct emails from law enfocement, government, police, o similar agencies do not automatically authoize disclosure of non-public customer infomation.</span><br />
<span style="font-size:16px;"> NiceNIC will review such requests based on:</span><br />
<span style="font-size:16px;"> The domain type</span><br />
<span style="font-size:16px;"> The requested data elements</span><br />
<span style="font-size:16px;"> The legal basis provided</span><br />
<span style="font-size:16px;"> The stated purpose</span><br />
<span style="font-size:16px;"> Any suppoting legal process</span><br />
<span style="font-size:16px;"> Confidentiality requirements</span><br />
<span style="font-size:16px;"> Applicable ICANN policy</span><br />
<span style="font-size:16px;"> Applicable law</span><br />
<span style="font-size:16px;"> Data minimization principles</span><br />
<span style="font-size:16px;"> Internal compliance approval</span><br />
<span style="font-size:16px;"> Requests fo payment recods, account logs, IP histoy, communications, hosting data, server data, o associated account recods are outside statard registration data disclosure at may require separate legal process.</span><br />
<span style="font-size:16px;"> NiceNIC does not disclose non-public customer infomation solely because a request is sent from a government, police, o law enfocement email address.</span><br />
<br />
<strong><span style="font-size:16px;">ccTLD Requests</span></strong><br />
<span style="font-size:16px;"> ICANN RDRS applies to gTLD non-public registration data only. It does not apply to ccTLD domain names.</span><br />
<span style="font-size:16px;"> Fo ccTLD-related requests, NiceNIC does not disclose non-public customer infomation through odinary email requests.</span><br />
<span style="font-size:16px;"> Requesters may be required to provide valid legal process, registry-authoized instruction, o a clearly stated applicable legal basis.</span><br />
<span style="font-size:16px;"> ccTLD requests may also be subject to the rules at policies of the relevant country-code registry.</span><br />
<br />
<strong><span style="font-size:16px;">Response Timeline</span></strong><br />
<span style="font-size:16px;"> Fo properly submitted gTLD non-public registration data disclosure requests that meet NiceNIC’s required fomat at are submitted through the required channel, NiceNIC will ackngayonledge receipt without undue delay at no later than two business days after receipt.</span><br />
<span style="font-size:16px;"> NiceNIC will respond without undue delay at no later than thirty calendar days after ackngayonledgement, unless exceptional circumstances apply.</span><br />
<span style="font-size:16px;"> A response may:</span><br />
<span style="font-size:16px;"> Approve the request</span><br />
<span style="font-size:16px;"> Partially approve the request</span><br />
<span style="font-size:16px;"> Deny the request</span><br />
<span style="font-size:16px;"> Request additional infomation</span><br />
<span style="font-size:16px;"> Explain that the requested data is publicly available</span><br />
<span style="font-size:16px;"> Explain that the request is outside the scope of this process</span><br />
<span style="font-size:16px;"> Explain that the request was not submitted through the required channel</span><br />
<span style="font-size:16px;"> Explain that separate legal process is required</span><br />
<br />
<strong><span style="font-size:16px;">Reasons a Request May Be Denied</span></strong><br />
<span style="font-size:16px;"> NiceNIC may deny o limit a request if:</span><br />
<span style="font-size:16px;"> The request does not identify an exact domain name</span><br />
<span style="font-size:16px;"> The domain is not sponsoed by NiceNIC</span><br />
<span style="font-size:16px;"> The domain is a ccTLD at the request is not suppoted by an applicable legal o registry basis</span><br />
<span style="font-size:16px;"> The requested data is outside the scope of registration data</span><br />
<span style="font-size:16px;"> The request was not submitted through the required channel</span><br />
<span style="font-size:16px;"> The request is incomplete o unclear</span><br />
<span style="font-size:16px;"> The requester does not provide a sufficient legal basis o specific rationale</span><br />
<span style="font-size:16px;"> The request is overly broad o speculative</span><br />
<span style="font-size:16px;"> The requester has not shown a legitimate interest</span><br />
<span style="font-size:16px;"> The request may prejudice the rights, freedoms, o privacy interests of the data subject</span><br />
<span style="font-size:16px;"> A less-intrusive method is available</span><br />
<span style="font-size:16px;"> The requester fails to confirm lawful data hatling</span><br />
<span style="font-size:16px;"> The request seeks histoical, archived, bulk, o unrelated account data</span><br />
<span style="font-size:16px;"> The request appears abusive, repetitive, misleading, o unsuppoted</span><br />
<br />
<strong><span style="font-size:16px;">Disclosure Decision</span></strong><br />
<span style="font-size:16px;"> Kung NiceNIC determines that disclosure is appropriate, NiceNIC may provide limited registration data necessary fo the stated purpose.</span><br />
<span style="font-size:16px;"> Kung NiceNIC determines that only part of the request is justified, NiceNIC may provide a partial disclosure.</span><br />
<span style="font-size:16px;"> Kung NiceNIC determines that the request is not sufficiently suppoted, no non-public registration data will be provided.</span><br />
<span style="font-size:16px;"> NiceNIC may require additional verification, documentation, o agreement terms befoe any disclosure is made.</span><br />
<br />
<strong><span style="font-size:16px;">Mga Ulat ng Pang-aabuso Are Separate From Data Disclosure Requests</span></strong><br />
<span style="font-size:16px;"> A request fo non-public registration data is not the same as an abuse complaint.</span><br />
<span style="font-size:16px;"> Kung a requester wants to repot DNS abuse, phishing, malware, botnet activity, spam as a delivery mechanism, o other abuse involving a domain name, the requester should submit an abuse repot through NiceNIC’s abuse repoting channel.</span><br />
<span style="font-size:16px;"> NiceNIC reviews abuse repots separately from registration data disclosure requests.</span><br />
<span style="font-size:16px;"> A request fo infomation does not automatically result in domain suspension, clientHold, serverHold, o other domain-level action.</span><br />
<span style="font-size:16px;"> Domain restrictions are reviewed separately based on applicable evidence, registry requirements, ICANN obligations, at NiceNIC’s abuse hatling procedures.</span><br />
<br />
<strong><span style="font-size:16px;">Impotant Hinditice</span></strong><br />
<span style="font-size:16px;"> NiceNIC is committed to protecting customer privacy while also suppoting legitimate at properly documented requests fo non-public registration data.</span><br />
<span style="font-size:16px;"> This policy does not create an automatic right to access non-public registration data.</span><br />
<span style="font-size:16px;"> Lahat requests are subject to review, applicable law, ICANN policy, registry requirements, data protection principles, at NiceNIC’s internal compliance procedures.</span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=3818</link>
<title>NiceNIC AI Terminos of Use</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h1 style="text-align:left;">
	<strong style="font-family:&quot;font-size:16px;font-style:inherit;font-variant-ligatures:inherit;font-variant-caps:inherit;"><span style="font-size:18px;">NiceNIC AI Terminos of Use</span></strong> 
</h1>
<p style="font-size:medium;">
	These AI Terminos govern AI-enabled features made available by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC"), including AI-assisted domain search, naming suggestions, text generation, analysis, o similar tools ("AI Services").
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">1. Relationship to Other Terminos</span></strong> 
</h2>
<p style="font-size:medium;">
	These AI Terminos supplement the NiceNIC Terminos of Service at Patakaran sa Privacy.
</p>
<p style="font-size:medium;">
	Wdito an AI feature is used in connection with domain registration o another NiceNIC Serbisyo, the applicable product agreement also applies.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">2. Inputs at Outputs</span></strong> 
</h2>
<p style="font-size:medium;">
	You may submit prompts, text, keywods, o other content ("Input") at receive generated suggestions o other material ("Output").
</p>
<p style="font-size:medium;">
	You are responsible fo ensuring that you have the rights at lawful authoity necessary to provide iyong Input.
</p>
<p style="font-size:medium;">
	As between you at NiceNIC, you retain rights you already have in iyong Input. Para sa the extent permitted by law at subject to third-party rights, NiceNIC does not claim ownership of Output generated specifically fo you merely because it was generated by the AI Service.
</p>
<p style="font-size:medium;">
	Output may not be unique, at the same o similar output may be generated fo other users.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">3. Third-Party AI Providers</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may use third-party technology providers to supply o suppot AI Services.
</p>
<p style="font-size:medium;">
	Input, Output, at related technical data may be transmitted to at processed by those providers to the extent necessary to provide, secure, monito, troubleshoot, at improve the AI Service, subject to applicable contractual at privacy requirements.
</p>
<p style="font-size:medium;">
	NiceNIC will describe material personal-data processing in its Patakaran sa Privacy.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">4. Hindi Guarantee of Accuracy</span></strong> 
</h2>
<p style="font-size:medium;">
	AI Output is probabilistic at may be inaccurate, incomplete, outdated, misleading, offensive, o unsuitable.
</p>
<p style="font-size:medium;">
	You must independently evaluate Output befoe relying on it.
</p>
<p style="font-size:medium;">
	AI Output is not legal, financial, tax, trademark, cybersecurity, medical, o other professional advice.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">5. Domain-Pangalan Suggestions</span></strong> 
</h2>
<p style="font-size:medium;">
	Wdito an AI Service suggests domain names, brats, keywods, o TLDs:
</p>
<ul style="font-size:medium;">
	<li>
		a suggestion does not mean the domain is currently available;
	</li>
	<li>
		availability is determined only by the applicable live registry/registrar transaction at the time of oder;
	</li>
	<li>
		a suggestion does not establish trademark o other intellectual-property clearance;
	</li>
	<li>
		a suggestion does not guarantee registry eligibility;
	</li>
	<li>
		a suggestion does not guarantee SEO ranking, traffic, resale value, investment return, o business success; at
	</li>
	<li>
		you are responsible fo checking legal rights, eligibility, at suitability befoe registration o use.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">6. Prohibited Use</span></strong> 
</h2>
<p style="font-size:medium;">
	You must not use the AI Services to:
</p>
<ul style="font-size:medium;">
	<li>
		facilitate unlawful activity;
	</li>
	<li>
		generate o operationalize malware, phishing, credential theft, fraud, o attacks;
	</li>
	<li>
		evade NiceNIC security o abuse controls;
	</li>
	<li>
		infringe third-party intellectual-property, privacy, o other legal rights;
	</li>
	<li>
		impersonate another person unlawfully;
	</li>
	<li>
		make solely automated high-impact decisions about an individual wdito such use is prohibited by law; o
	</li>
	<li>
		submit content you are not permitted to disclose, including highly confidential credentials, authentication codes, o unlawful personal data.
	</li>
	<li>
		<br />
	</li>
</ul>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">7. Human Review</span></strong> 
</h2>
<p style="font-size:medium;">
	You are responsible fo human review appropriate to iyong use case. You must not represent AI Output as independently verified by NiceNIC.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">8. Availability at Changes</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may modify, rate-limit, suspend, replace, o discontinue an AI feature, including wdito a third-party model o provider changes o wdito security, legal, o product considerations require it.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">9. Privacy</span></strong> 
</h2>
<p style="font-size:medium;">
	Personal data processed through AI Services is hatled under the NiceNIC Patakaran sa Privacy. Users should avoid submitting sensitive o confidential infomation that is not necessary fo the requested AI function.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">10. Intellectual Property</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC retains all rights in its platfom, software, brating, interfaces, prompts/templates created by NiceNIC, at other proprietary Serbisyo components.
</p>
<p style="font-size:medium;">
	Hindi provision grants you rights in third-party models, software, trademarks, o content.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">11. Disclaimer at Liability</span></strong> 
</h2>
<p style="font-size:medium;">
	Para sa 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, o fit fo a particular purpose.
</p>
<p style="font-size:medium;">
	NiceNIC is not liable fo indirect, incidental, special, exemplary, o consequential loss resulting from reliance on AI Output, except wdito such exclusion is prohibited by law.
</p>
<p style="font-size:medium;">
	Any direct-liability limitation is subject to the NiceNIC Terminos of Service at matatoy law.
</p>
<h2 style="text-align:left;">
	<strong><span style="font-size:18px;">12. Suspension</span></strong> 
</h2>
<p style="font-size:medium;">
	NiceNIC may restrict o suspend AI access fo material breach, security abuse, unlawful use, excessive automated use contrary to applicable limits, o wdito required by law.
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=803</link>
<title>Pagpaparehistro ng Domain Name Service Agreement</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=877</link>
<title>NiceNIC .HK Trustee Service Terminos</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<p>
	<strong><span style="font-size:12pt;font-family:Arial;">1. Obligations of the Customer</span></strong> 
</p>
<br />
<span style="font-size:12pt;font-family:Arial;"> a) The Customer must guarantee that he has checked that the domain it 
has applied fo does neither violates any third-party rights 
(trademarks, rights to names at copyrights), does not violate statutoy
 prohibitions o public oder at that he is not using the domain fo 
illegal purposes, in particular phishing at spamming. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> The Customer must put himself under the obligation not to publish on 
the website filed under the domain any contents violating statutoy 
prohibitions, trademark rights, rights to names, copyrights o public 
oder.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> b) The Customer must put himself under the obligation to immediately 
infom NICENIC INTERNATIONAL GROUP CO., LIMITED in writing by post, fax 
o email about all registration related occurrences concerning the 
domain, in particular the threat o the initiation of legal measures.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the holder of the domain changes while maintaining NICENIC 
INTERNATIONAL GROUP CO., LIMITED as provider then the new holder must 
accept "NiceNIC .HK Trustee Service Terminos".</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> In case of a change in the domain owner at a simultaneous change to 
another provider than NICENIC, the "NiceNIC .HK Trustee Service Terminos" will automatically cease.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> With any change from NICENIC INTERNATIONAL GROUP CO., LIMITED to 
another provider, the "NiceNIC .HK Trustee Service Terminos" will cease. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the Customer does not designate a new Registrant prio to the change
 of provider then NICENIC INTERNATIONAL GROUP CO., LIMITED may reject 
the change of provider.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> c) The Customer must put himself under the obligation to answer 
enquiries from NiceNIC relating to domain registration immediately by 
post o fax o email, at reaching NiceNIC at the latest within 48 
hours. The deadline will be shotened accodingly, if deadlines are set 
in a legally valid way by a third party (claimant, court, administrative
 agency etc.). </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> The Customer is obliged to keep his contact data constantly up to date 
with NICENIC INTERNATIONAL GROUP CO., LIMITED at expressly authoises 
NICENIC to make such contact data available to Registry of HKIRC at 
ICANN.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the contact data provided by the Customer to NICENIC INTERNATIONAL 
GROUP CO., LIMITED, in particular the Email Address, postal address at 
the telephone number, are not corect at if the Customer is not 
reachable via the contact routes he provided o if he does not answer an
 enquiry from NICENIC within a deadline set then NiceNIC is entitled to 
make any decisions, in particular to delete the domain.</span><br />
<br />
<strong><span style="font-size:12pt;font-family:Arial;">2. Obligations of NICENIC</span></strong><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> a) NICENIC has put himself in relation to NICENIC INTERNATIONAL GROUP 
CO., LIMITED under the obligation to accomplish the tasks incumbent upon
 him as an administrative contact accoding to the best of his kngayonledge
 at belief. He will abide by coresponding instructions from NICENIC 
INTERNATIONAL GROUP CO., LIMITED provided the latter do not run counter 
to the law. </span><span style="font-size:12pt;font-family:Arial;"></span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> b) NICENIC will, when decisions may o have to be made without consulting the </span><span style="font-size:12pt;font-family:Arial;">Customer, make such decisions accoding to his equitable discretion.</span><br />
<br />
<strong><span style="font-size:12pt;font-family:Arial;">3. Settlement of disputes with third parties</span></strong><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung NICENIC is sued as representative of the Customer o directly by a 
third party fo release o deletion of the domain then the Customer must
 within the deadlines declare in writing whether he will consent to 
release o whether he wishes to defend the domain.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> a) Kung the Customer consents to release then NICENIC INTERNATIONAL GROUP
 CO., LIMITED will declare deletion of the domain at infom the third 
party o the claimant. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> b) Kung the Customer fails to provide a declaration in time then NICENIC 
INTERNATIONAL GROUP CO., LIMITED will be entitled to immediately delete 
the domain. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> c) Kung the Customer infoms NICENIC that he wishes to defend the domain 
then he must deposit with him within two days a bond (cash payment in 
USD o perfomance bond of HSBC) in the amount to be determined in 
equitable discretion by NICENIC INTERNATIONAL GROUP CO., LIMITED, 
patterned on the Judicial Costs Act as well as, possibly, on damage 
compensation claims to be expected, which bond covers the potential 
compensation</span>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=875</link>
<title>NiceNIC HK Pagpaparehistro Agreement - HKIRC Accredited Registrar</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<div align="center">
	<strong><span style="font-size:14px;font-family:Verdana;">REGISTRATION AGREEMENT - MANDATOY PROVISIONS </span></strong><br />
</div>
<br />
<span style="font-family:Verdana;">Impotant Hindite: This document sets out the minimum terms at conditions to be contained in a Pagpaparehistro Agreement between the Registrar at a Registrant. It does not purpot to be, at is not, a comprehensive Pagpaparehistro Agreement. This document is applied to all domain names operated by HKIRC.</span><br />
<br />
<span style="font-family:Verdana;"><strong>1 DOMAIN NAME SERVICES</strong></span><br />
<br />
<span style="font-family:Verdana;">1.1 The Registrant shall at all times comply with all nakaraanailing requirements prescribed by HKIRC in connection with any of the .hk o.香港 domain name (the "Domain Name"), at shall only request the Registrar Services in the fom at manner prescribed by HKIRC from time to time. </span><br />
<br />
<span style="font-family:Verdana;">1.2 In magparehistroing a Domain Name, the Registrant ackngayonledges at agrees that neither HKIRC no NICENIC International Group Co., Limited (the "Registrar") has made any determination with respect to the legality of the Domain Name registration o its use. </span><br />
<br />
<p>
	<span style="font-family:Verdana;">1.3 The Registrant ackngayonledges at agrees that the Registrar shall monito the status of Mga Domain Name magparehistroed through the Registrar at shall, at its own initiative o on receipt of complaint, conduct checks to verify whether a Domain Name is being used in connection with phishing o "spam" advertising. The Registrar shall delete o suspend a Domain Name if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government o law enfocement authoity (including without limitation the Hong Kong Police Foce o the Office of Telecommunications Authoity) that the use of the Domain Name is in breach of any laws, directives, guidelines, codes of practice o regulations issued by such local authoities, o if, in HKIRC's reasonable belief, the continuation of registration of the Domain Name o the operation of web site referenced&nbsp;&nbsp; by the Domain Name is likely to damage o adversely affect the goodwill, reputation at operation of HKIRC o the domain name industry in Hong Kong, o may expose HKIRC to risks of third party claims o civil o criminal prosecution. </span>
</p>
<p>
	<span style="font-family:Verdana;">Fo moe infomation about .HK domain registration, please refer to&nbsp;the latest version of HKIRC Pagpaparehistro Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf</span>
</p>
<br />
<span style="font-family:Verdana;"><strong>2 PUBLICATION OF REGISTRANT PERSONAL DATA</strong></span><br />
<br />
<span style="font-family:Verdana;">2.1 The Registrant ackngayonledges at agrees that HKIRC is entitled to publicly disclose to third parties all personal data at infomation relating to the magparehistroed Domain Name in oder to enable HKIRC to maintain a public WHOIS Serbisyo, provided that such disclosure is consistent with:</span><br />
<br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (a) the Personal Data (Privacy) Ordinance; at</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (b) the Na-publish Policies of HKIRC; at</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (c) this Pagpaparehistro Agreement. </span><br />
<br />
<span style="font-family:Verdana;">2.2 The Registrant grants to the Registrar the right to disclose to the HKIRC all infomation which is reasonably required by HKIRC in oder to enter the Domain Name into the Registry. </span><br />
<br />
<span style="font-family:Verdana;"><strong>3 CHANGE OF REGISTRARS</strong></span><br />
<br />
<span style="font-family:Verdana;">3.1 The Registrar shall not nakaraanent a Registrant from changing the registrar of recod, except in accodance with the Pagpaparehistro Policies. </span><br />
<br />
<span style="font-family:Verdana;">3.2 The Registrar shall ensure that the Registrant can easily transfer magparehistroed Mga Domain Name to another registrar in accodance with the Na-publish Policies of HKIRC.</span><br />
<br />
<span style="font-family:Verdana;">3.3 In the event that:</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 3.3.1 the Registrar is no longer a registrar; o</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 3.3.2 the Registrar's HKIRC Akreditasyon is suspended o terminated; o</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 3.3.3 the Registrar Agreement is terminated by HKIRC, the Registrar shall immediately give notice to its Registrants, at advise the Registrants that they should transfer the magparehistroed Domain Name to a new registrar.</span><br />
<br />
<span style="font-family:Verdana;">3.4 In the event that the Registrar Agreement between HKIRC at the Registrar is terminated due to default o breach of the Registrar, the Registrar must not charge the Registrant any fee fo the transfer of the magparehistroed Domain Name to another registrar. The Registrar shall take all necessary actions to preserve the rights of its Registrants.</span><br />
<br />
<span style="font-family:Verdana;">3.5 Kung the Registrant of a Domain Name magparehistroed under Hong Kong Netwok Infomation Centre ("HKNIC") Pagpaparehistro Agreement Version 1.x o 2.xx elects to change the Registrar from Hong Kong Domain&nbsp; Pangalan Pagpaparehistro Company Limited ("HKDNR") to another Registrar ("Bago Registrar"), the Registrant shall ackngayonledge at accept that the Domain Name registration will be subject to the terms at conditions of the then current registration agreement of the Bago Registrar. Fo the avoidance of doubt, if the Domain Name registration is under one of the above-mentioned agreements, the Contract Version field of the WHOIS result display fo that Domain Name will display the wod "Old" </span><br />
<br />
<span style="font-family:Verdana;">3.6 The Registrant shall provide an authoization code ("Authoization Infomation") to a new registrar in oder to initiate the change of registrar. The Registrar can request that HKIRC provide this Authoization Infomation by sending it to the Registrant's email address. The Registrar shall not, if requested to do so by a Registrant, refuse to make such a request of HKIRC. </span><br />
<br />
<span style="font-family:Verdana;">3.7 In the event that the Registrar is no longer an HKIRC-Accredited registrar, the Domain Name held by a Registrant shall be transferred to another, HKIRC-Accredited registrar within a specified period of time. Kung the Registrant fails to elect a registrar at effect the transfer, HKIRC shall be entitled to transfer the Domain Name to registration with HKDNR, together with any personal data held by the nakaraanious Registrar in relation to that Registrant. </span><br />
<br />
<span style="font-family:Verdana;"><strong>4 REGISTRANT'S OTHER OBLIGATIONS</strong></span><br />
<br />
<span style="font-family:Verdana;">4.1 Throughout the Termino of the Pagpaparehistro Agreement, the Registrant must:</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp; &nbsp;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 4.1.1 comply with the Na-publish Policies (including but not limited to the Pagpaparehistro Policies, Procedures at Guidelines, Domain Name Dispute Resolution Policy at Rules of Procedure at the Pagpaparehistro Agreement. The Na-publish Policies can be found on either the web site of HKIRC, www.hkirc.hk o the web site of NiceNIC, http://nicenic.net/domain/hk-domain-registration.php;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 4.1.2 give notice to HKIRC, through the Registrar, of any change to any infomation in the Registrant Data as soon as possible. </span><br />
<br />
<span style="font-family:Verdana;">4.2 The Registrant shall not, directly o indirectly, through registration o use of its Domain Name o otherwise:</span><br />
<br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 4.2.1 infringe o violate the legal rights of any third party; o</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; 4.2.2 violate any applicable laws at regulations. </span><br />
<br />
<span style="font-family:Verdana;">4.3 The Registrant ackngayonledges at agrees that HKIRC may collect registrant infomation fo the purpose of HKIRC membership. </span><br />
<br />
<span style="font-family:Verdana;"><strong>5 DISPUTE RESOLUTION</strong></span><br />
<br />
<span style="font-family:Verdana;">5.1 Fo any Domain Name magparehistroed with the Registrant that is challenged by a third party, the dispute will be hatled accoding to the provisions of the Domain Name Dispute Resolution Policy fo .hk at .香港 Mga Domain Name.</span><br />
<br />
<p>
	<span style="font-family:Verdana;">5.2 Any decision made by an arbitration panel duly appointed by a dispute resolution Serbisyo provider shall be final at binding on the Registrant at the Registrant shall abide by such decision.</span> 
</p>
<p>
	<span style="font-size:9pt;font-family:Verdana;letter-spacing:0pt;"><br />
</span> 
</p>
<p>
	<span style="font-size:9pt;font-family:Verdana;letter-spacing:0pt;">5.3&nbsp;</span><span style="font-size:9pt;font-family:Verdana;letter-spacing:0pt;">NICENIC INTERNATIONAL GROUP CO., LTD is an official HKIRC (Hong-Kong) accredited registrar. HKIRC is a non-profit-making at non-statutoy copoation designated by the Hong-Kong Government to administer the registration of Internet domain names under .hk at .<span style="font-family:Tahoma;">香港</span>&nbsp;country-code top level domains.&nbsp;Fo any comments o complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s&nbsp;compliance, please find dito&nbsp;useful infomation:&nbsp;HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppot/domain_dispute_policies_at_procedures/domain_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppot/domain_dispute_policies_at_procedures/rules_of_procedures/; o Email address: info@hkirc.hk.</span> 
</p>
<p>
	<strong style="font-family:Verdana;"><br />
</strong> 
</p>
<p>
	<strong style="font-family:Verdana;">6&nbsp; REGISTRANT WARRANTIES&nbsp;</strong> 
</p>
<br />
<span style="font-family:Verdana;">6.1 The Registrant warrants that it meets, at continues to meet, the eligibility criteria prescribed in HKIRC's Na-publish Policies at this Pagpaparehistro Agreement fo magparehistroing a Domain Name. In the event that the Registrant ceases to meet such eligibility criteria, the Domain Name registration may be terminated by either the Registrar o HKIRC.</span><br />
<br />
<span style="font-family:Verdana;">6.2 By making an application fo a Domain Name, the Registrant represents at warrants that:</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp; &nbsp;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (a) to the best of its kngayonledge at belief, the Domain Name that the Registrant is applying fo will not infringe o otherwise violate the legal rights of any third party;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (b) the Registrant intends to use the Domain Name;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (c) the Registrant's use of the Domain Name shall be bona fide fo the Registrant's own benefit at shall be fo lawful purposes;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (d) the Registrant will not kngayoningly use the Domain Name in violation of any applicable laws at regulations;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (e) all infomation the Registrant provides to the Registrar, including further additions o alterations to such infomation, is true, complete at accurate;</span><br />
<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; (f) in the event that the Registrant receives notification of any claim, action o demat arising out of o related to the registration o use of the Domain Name, the Registrant will immediately send the Registrar a written notice notifying the Registrar of such claim, action o demat. </span><br />
<br />
<p>
	<span style="font-family:Verdana;">&nbsp;&nbsp;&nbsp; The Registrant ackngayonledges that the Registrar at HKIRC rely on all representations made at warranties given by the Registrant in determining if the application fo a Domain Name should be approved. </span>
</p>
<p>
	<span style="font-family:Verdana;">&nbsp; &nbsp; Fo moe infomation about "Acceptable Use Policy", please refer to&nbsp;https://www.hkirc.hk/domain_policies/EN_Domain_Pangalan_Acceptable_Use_Policy.pdf.</span>
</p>
<br />
<span style="font-family:Verdana;"><strong>7. HKIRC Makipag-ugnayan Registrants </strong></span><br />
<br />
<span style="font-family:Verdana;">7.1 The Registrant ackngayonledges that HKIRC may contact the Registrant in a number of situations including, but not limited to, inviting the Registrant to join HKIRC as a member; wdito tdito has been, o will be, a change in registrar, whether voluntarily o involuntarily on the part of the Registrant, due to termination of the Registrar; fo the matters in relation to the administration at Serbisyo of Mga Domain Name; inviting the Registrant to take part in a customer satisfaction survey o other survey, at introducing seminars, conferences, training, at other news related to the Internet industry. Kung the Registrant does not want to receive unsolicited marketing o promotional emails, the Registrant can request that HKIRC remove the Registrant from the marketing o promotional email subscription list.</span><br />
<br />
<span style="font-family:Verdana;"><strong>8. LIABILITIES</strong></span><br />
<br />
<span style="font-family:Verdana;">8.1 The Registrant shall indemnify at hold harmless HKIRC as the Registry from all liabilities, losses, damages, costs, legal expenses, professional at other expenses of any nature howsoever sustained, incurred, paid by o suffered by HKIRC which are directly o indirectly related to any claim, action, o demat arising out of o related to the registration o use of the Domain Name brought by the Registrant. </span><br />
<br />
<span style="font-family:Verdana;">8.2 Hinditwithstating any other provision of this document at to the fullest extent permitted by law, HKIRC will not be liable to the Registrant fo consequential, indirect o special losses o damages of any kind (including, without limitation, loss of profit, loss o coruption of data, business interruption o indirect costs) suffered by the Registrant as a result of any act o omission whatsoever of HKIRC at the Registrar, its employees, agents o sub-contractos. </span><br />
<br />
<span style="font-family:Verdana;">8.3 In no event shall HKIRC's maximum liability under these Pagpaparehistro Policies exceed 125% of the registration fees paid by the Registrar to HKIRC fo the Registrant's Domain Name in respect of a particular period of registration. </span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=869</link>
<title>NiceNIC .CN Trustee Service Terminos</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<h2 align="center">
	<span style="font-size:18px;font-family:Arial;">Applicable to MOST Mga Domain Name Operated by CNNIC</span> <span style="font-size:12pt;font-family:Arial;"> </span> 
</h2>
<br />
<strong><span style="font-size:12pt;font-family:Arial;">1. Obligations of the Customer</span></strong><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> a) The Customer must guarantee that he has checked that the domain it has applied fo does neither violates any third-party rights (trademarks, rights to names at copyrights), does not violate statutoy prohibitions o public oder at that he is not using the domain fo illegal purposes, in particular phishing at spamming. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> The Customer must put himself under the obligation not to publish on the website filed under the domain any contents violating statutoy prohibitions, trademark rights, rights to names, copyrights o public oder.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> b) The Customer must put himself under the obligation to immediately infom NICENIC INTERNATIONAL GROUP CO., LIMITED in writing by post, fax o email about all registration related occurrences concerning the domain, in particular the threat o the initiation of legal measures.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the holder of the domain changes while maintaining NICENIC INTERNATIONAL GROUP CO., LIMITED as provider then the new holder must accept "NiceNIC CN Series Pagrehistro ng Domain Trustee Service Terminos".</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> In case of a change in the domain owner at a simultaneous change to another provider than NICENIC, the ""NiceNIC CN Series Pagrehistro ng Domain Trustee Service" will automatically cease.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> With any change from NICENIC INTERNATIONAL GROUP CO., LIMITED to another provider, the "NiceNIC CN Series Pagrehistro ng Domain Trustee Service" will cease. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the Customer does not designate a new Registrant prio to the change of provider then NICENIC INTERNATIONAL GROUP CO., LIMITED may reject the change of provider.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> c) The Customer must put himself under the obligation to answer enquiries from NiceNIC relating to domain registration immediately by post o fax o email, at reaching NiceNIC at the latest within 48 hours. The deadline will be shotened accodingly, if deadlines are set in a legally valid way by a third party (claimant, court, administrative agency etc.). </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> The Customer is obliged to keep his contact data constantly up to date with NICENIC INTERNATIONAL GROUP CO., LIMITED at expressly authoises NICENIC to make such contact data available to Registry of CNNIC at ICANN.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung the contact data provided by the Customer to NICENIC INTERNATIONAL GROUP CO., LIMITED, in particular the Email Address, postal address at the telephone number, are not corect at if the Customer is not reachable via the contact routes he provided o if he does not answer an enquiry from NICENIC within a deadline set then NiceNIC is entitled to make any decisions, in particular to delete the domain.</span><br />
<br />
<strong><span style="font-size:12pt;font-family:Arial;">2. Obligations of NICENIC</span></strong><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> a) NICENIC has put himself in relation to NICENIC INTERNATIONAL GROUP CO., LIMITED under the obligation to accomplish the tasks incumbent upon him as an administrative contact accoding to the best of his kngayonledge at belief. He will abide by coresponding instructions from NICENIC INTERNATIONAL GROUP CO., LIMITED provided the latter do not run counter to the law. </span><br />
<span style="font-size:12pt;font-family:Arial;"></span><br />
<span style="font-size:12pt;font-family:Arial;"> b) NICENIC will, when decisions may o have to be made without consulting the </span><span style="font-size:12pt;font-family:Arial;">Customer, make such decisions accoding to his equitable discretion.</span><br />
<br />
<strong><span style="font-size:12pt;font-family:Arial;">3. Settlement of disputes with third parties</span></strong><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> Kung NICENIC is sued as representative of the Customer o directly by a third party fo release o deletion of the domain then the Customer must within the deadlines declare in writing whether he will consent to release o whether he wishes to defend the domain.</span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> a) Kung the Customer consents to release then NICENIC INTERNATIONAL GROUP CO., LIMITED will declare deletion of the domain at infom the third party o the claimant. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> b) Kung the Customer fails to provide a declaration in time then NICENIC INTERNATIONAL GROUP CO., LIMITED will be entitled to immediately delete the domain. </span><br />
<br />
<span style="font-size:12pt;font-family:Arial;"> c) Kung the Customer infoms NICENIC that he wishes to defend the domain then he must deposit with him within two days a bond (cash payment in USD o perfomance bond of HSBC) in the amount to be determined in equitable discretion by NICENIC INTERNATIONAL GROUP CO., LIMITED, patterned on the Judicial Costs Act as well as, possibly, on damage compensation claims to be expected, which bond covers the potential compensation.</span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=829</link>
<title>Why does NiceNIC Reseller Program try a prepaid system?</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	In deference to recent NiceNIC clients' request, we hereby make an explanation about why NiceNIC reseller program is based on prepayment, hope it would help a bit anyhow.<br />
<br />
Actually, woking on a prepaid system is beneficial both fo you at NiceNIC. Aming prices are discounted, while the interests of domain name owners are incredibly high. By maintaining a prepaid balance you will be able to renew iyong domain registrations automatically at you do NOT have to concern iyongself with losing domain names. Fo NiceNIC this system guarantees continuity at less administration, which makes it possible to keep our prices low. Magdagdagitionally it may also offer us the means to keep upgrading at perfecting our equipment at Serbisyos.<br />
<br />
Your deposit will never expire at tdito is no threshold fo a minimal balance. You could use the full amount deposited without making a new deposit. However, we advise you to have positive balance on iyong account fo automatic renewals tditofoe you would NOT lose any domains.<br />
<br />
Fo moe infomation about NiceNIC domain reseller program, please kindly check http://NiceNIC.NET/reseller/ at you are welcome to email us directly @ Suppot at NiceNIC dot NET.<br />
<br />
Your continued suppot at comprehension have been greatly appreciated!<br />
<br />
Lahat the best,<br />
<br />
NiceNIC.NET Suppot Team<br />
<br />NICENIC INTERNATIONAL GROUP CO., LIMITED <br />
<br />
ICANN CNNIC Accredited Registrar  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=828</link>
<title>NiceNIC Ranked among ICANN Accredited Registrar List</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<p>
	<span style="font-family:Verdana;font-size:14px;">2012 is doomed to be an extraodinary taon, 2012 welcomes <a href="http://www.nicenic.net" target="_blank"><strong>NiceNIC</strong></a> milestone, 2012 marks a newbon ranked among&nbsp;ICANN Accredited Registrar list after 7 mga taon' continuing effot at surviving from intense competition, we NiceNICers are definitely proud of her accomplishment ngayonadays. </span> 
</p>
<p>
	<span style="font-family:Verdana;font-size:14px;"></span>&nbsp;
</p>
<p>
	<span style="font-family:Verdana;">Below is the letter of congratulation from </span><strong><span style="font-family:Verdana;">Verisign</span></strong><span style="font-family:Verdana;">:</span> <br />
<span style="font-family:Verdana;">"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. Hindiw that you have met the requirements of ICANN, our team is looking foward to assisting you in completing the Verisign certification process so you can quickly begin magparehistroing .com at .net domain names. We hope this suppot will prove to be helpful in reducing the investment of iyong internal resources at time."</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<strong><span style="font-family:Verdana;">PIR:</span></strong><br />
<span style="font-family:Verdana;">"ICANN has infomed .ORG, managed by the Public Interest Registry (PIR) that you have recently completed iyong ICANN accreditation to become a registrar at wish to partner with us by becoming an .ORG accredited registrar."</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<strong><span style="font-family:Verdana;">Telnic:</span></strong><br />
<span style="font-family:Verdana;">"We received notification from ICANN that you have added the .tel appendix to iyong agreement with them. Tdito hasn't been a better time to become involved with .tel domains at we are pleased to assist you in becoming accredited as a participating .tel registrar."</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<strong><span style="font-family:Verdana;">ICM:</span></strong><br />
<span style="font-family:Verdana;">"Congrats on iyong recent ICANN Akreditasyon..."</span> 
</p>
<p>
	&nbsp;
</p>
<p>
	<span style="font-family:Verdana;"><strong>Neustar:</strong></span> 
</p>
<p>
	<span style="font-family:Verdana;">"</span><span style="font-family:Verdana;">We&nbsp;have&nbsp;been&nbsp;notified&nbsp;that&nbsp;iyong&nbsp;company&nbsp;is&nbsp;ngayon&nbsp;ICANN-accredited&nbsp;as&nbsp;a&nbsp;.BIZ&nbsp;registrar.&nbsp;&nbsp;Neustar&nbsp;looks&nbsp;foward&nbsp;to&nbsp;getting&nbsp;iyong&nbsp;company&nbsp;up&nbsp;at&nbsp;running&nbsp;as&nbsp;soon&nbsp;as&nbsp;possible!</span><span style="font-family:Verdana;">"</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<span style="font-family:Verdana;">Higit Pa registries will be notified by ICANN fo the coresponding domain names signed in the RAA in the susunod days, we NiceNIC have been staying fo the disposal of sign-up/accreditation process, striving to save time at expedite each step if possible. </span><strong><span style="font-family:Verdana;">The concerned technical staffs have been arranged to re-set the product prices to a moe competitive level.</span></strong><span style="font-family:Verdana;"> Detalyeed infomation will come out when available.&nbsp;</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<span style="font-family:Verdana;">Flying with the strong momentum, our English version website </span><a target="_blank" href="http://www.nicenic.net"><strong><a target="_blank"><span style="font-family:Verdana;">NiceNIC.NET</span></a></strong></a><span style="font-family:Verdana;">was launched with her unique style of "</span><strong><span style="font-family:Verdana;">Keep Internet Simple Stupid</span></strong><span style="font-family:Verdana;">" (acronym "</span><strong><span style="font-family:Verdana;">KISS</span></strong><span style="font-family:Verdana;">"), at dedicated to offer clients easy to navigate, fast to locate Serbisyos in domain name registration, web hosting bumili, 1 to 1 customer suppot.</span> 
</p>
<p>
	<span style="font-family:Verdana;">&nbsp;</span> 
</p>
<p>
	<span style="font-family:Verdana;">Stating at the peak of internet infrastruture, we firstly need to appreciate every client, at every website viewer who ever stayed dito, without iyong persistant suppot at comprehension, we are nothing, hope 2012 will bring you at iyong family lucky, happy, healthy life.</span> 
</p>
<p>
	&nbsp;
</p>
<p>
	<span style="font-family:Verdana;">Reference links:</span><a href="http://www.icann.org/registrar-reports/accreditation-qualified-list.html"> </a>
</p>
<p>
	<a href="http://www.icann.org/registrar-reports/accreditation-qualified-list.html">http://www.icann.org/registrar-repots/accreditation-qualified-list.html</a><a href="http://www.icann.org/registrar-reports/accreditation-qualified-list.html"> </a>
</p>
<p>
	<a href="http://www.icann.org/registrar-reports/accredited-list.html">http://www.icann.org/registrar-repots/accredited-list.html</a><a href="http://www.icann.org/registrar-reports/accreditation-qualified-list.html"> </a>
</p>
<p>
	<a href="http://www.internic.com/alpha.html">http://www.internic.com/alpha.html</a><a href="http://www.icann.org/registrar-reports/accreditation-qualified-list.html"> </a> 
</p>
<p>
	&nbsp;
</p>
<p>
	<table width="95%" align="center" border="1">
		<tbody>
			<tr>
				<td>
					<a href="http://nicenic.com/">ZhuHai NaiSiNiKe Infomation Technology Co Ltd.</a> 
				</td>
				<td>
					2009
				</td>
				<td>
					China
				</td>
				<td>
					.asia .biz .com .info .mobi .name .net .org .tel .xxx
				</td>
			</tr>
		</tbody>
	</table>
</p>
<p>
	&nbsp;
</p>
<p>
	<span style="font-family:Verdana;">Lahat the best,</span> 
</p>
<p>
	<span style="font-family:Verdana;">NiceNIC.NET Team</span><span style="font-family:Verdana;"><br />
</span>
</p>
<p>
	<span style="font-family:Verdana;">ZhuHai NaiSiNiKe Infomation Technology Co., Ltd.</span> 
</p>
<p>
	&nbsp;
</p>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=804</link>
<title>Registrar Transfer Dispute Resolution Policy (TDRP)</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<strong><span style="font-size:18px;">Registrar Transfer Dispute Resolution Policy (TDRP)</span></strong><br />
<br />
<span style="font-size:18px;"><strong>1. Purpose</strong></span><br />
<span style="font-size:16px;">The Transfer Dispute Resolution Policy ("TDRP") is an ICANN policy governing certain disputes between registrars concerning inter-registrar transfers of domain names.</span><br />
<br />
<span style="font-size:16px;">Fo domain names subject to the ICANN TDRP, NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") will comply with the then-current TDRP at related ICANN procedures.</span><br />
<br />
<span style="font-size:18px;"><strong>2. Official Policy Controls</strong></span><br />
<span style="font-size:16px;">The current official ICANN TDRP is incopoated by reference.</span><br />
<br />
<span style="font-size:16px;">Official ICANN TDRP:</span><br />
<span style="font-size:16px;"><a href="https://www.icann.org/en/contracted-parties/accredited-registrars/registrar-transfer-dispute-resolution-policy-21-02-2024-en" target="_blank">https://www.icann.org/en/contracted-parties/accredited-registrars/registrar-transfer-dispute-resolution-policy-21-02-2024-en</a></span><br />
<br />
<span style="font-size:16px;">Kung this page conflicts with the official ICANN TDRP, the official ICANN policy controls.</span><br />
<br />
<span style="font-size:18px;"><strong>3. Nature of the TDRP</strong></span><br />
<span style="font-size:16px;">The TDRP is primarily a dispute mechanism available to the relevant registrars in connection with an inter-registrar transfer. A Magrehistroed Pangalan Holder does not obtain an independent right to file a TDRP complaint merely by virtue of this page.</span><br />
<br />
<span style="font-size:16px;">Customers who have a transfer problem should first contact NiceNIC Suppot at provide the affected domain name, relevant dates, account infomation, at any transfer notices o evidence available to them.</span><br />
<br />
<span style="font-size:18px;"><strong>4. Recods at Cooperation</strong></span><br />
<span style="font-size:16px;">NiceNIC may retain at produce transfer-related recods, including transfer authoizations, notices, authentication recods, Pagpaparehistro Data, transaction recods, at other evidence, to the extent required o permitted by:</span><br />
<br />
<span style="font-size:16px;">the ICANN Transfer Policy;</span><br />
<span style="font-size:16px;">the TDRP;</span><br />
<span style="font-size:16px;">the ICANN Pagpaparehistro Data Policy;</span><br />
<span style="font-size:16px;">the Registrar Akreditasyon Agreement;</span><br />
<span style="font-size:16px;">applicable registry requirements; o</span><br />
<span style="font-size:16px;">applicable law.<br />
</span><br />
<span style="font-size:18px;"><strong>5. Hindi Effect on Other Rights</strong></span><br />
<span style="font-size:16px;">The TDRP does not replace:</span><br />
<br />
<span style="font-size:16px;">the UDRP o URS wdito applicable;</span><br />
<span style="font-size:16px;">applicable ccTLD dispute policies;</span><br />
<span style="font-size:16px;">lawful court proceedings;</span><br />
<span style="font-size:16px;">customer complaints concerning NiceNIC's Serbisyo; o</span><br />
<span style="font-size:16px;">any other matatoy remedy available under applicable law o ICANN policy.</span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=802</link>
<title>Patakaran sa Paglipat ng Domain</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<strong><span style="font-size:18px;">Patakaran sa Paglipat ng Domain</span></strong><br />
<br />
<span style="font-size:18px;"><strong>1. Scope</strong></span><br />
<span style="font-size:16px;"> This Patakaran sa Paglipat ng Domain applies to inter-registrar transfers of domain names sponsoed by NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC") wdito the applicable top-level domain is subject to the ICANN Transfer Policy. Transfers of country-code top-level domains ("ccTLDs") may be subject to different o additional registry rules.</span><br />
<br />
<strong><span style="font-size:18px;">2. ICANN Transfer Policy Incopoated</span></strong><br />
<span style="font-size:16px;"> Fo domain names subject to the ICANN Transfer Policy, NiceNIC will process transfer requests in accodance with the then-current ICANN Transfer Policy, which is incopoated into this Policy by reference.</span><br />
<br />
<span style="font-size:16px;"> Official ICANN policy:</span><br />
<a href="https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy" target="_blank"><span style="font-size:16px;">https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy</span></a><br />
<br />
<span style="font-size:16px;"> Kung this NiceNIC summary conflicts with a matatoy provision of the ICANN Transfer Policy, the ICANN Transfer Policy controls.</span><br />
<br />
<strong><span style="font-size:18px;">3. Transfer Authoity</span></strong><br />
<span style="font-size:16px;"> Fo purposes of an ICANN-governed inter-registrar transfer, the Magrehistroed Pangalan Holder is the party authoized to approve o deny the transfer, subject to the verification, authoization, security, at dispute procedures required by the ICANN Transfer Policy.</span><br />
<br />
<span style="font-size:16px;"> NiceNIC does not rely on an "Administrative Makipag-ugnayan" as an independent transfer authoity merely because older recods o legacy systems may contain such a contact.</span><br />
<br />
<strong><span style="font-size:18px;">4. Transfers Away from NiceNIC</span></strong><br />
<span style="font-size:16px;"> Subject to the ICANN Transfer Policy at applicable registry requirements, a Magrehistroed Pangalan Holder may transfer an eligible domain name away from NiceNIC.</span><br />
<br />
<span style="font-size:16px;"> Wdito applicable:</span><br />
<br />
<span style="font-size:16px;"> the domain must not be subject to a transfer prohibition that is permitted o required under the ICANN Transfer Policy o applicable registry rules;</span><br />
<span style="font-size:16px;"> the Magrehistroed Pangalan Holder may be required to unlock the domain;</span><br />
<span style="font-size:16px;"> the Magrehistroed Pangalan Holder may be required to obtain the applicable AuthInfo/EPP authoization code;</span><br />
<span style="font-size:16px;"> NiceNIC may send transfer notifications required by ICANN o the registry; at</span><br />
<span style="font-size:16px;"> NiceNIC will approve, deny, o allow a transfer to proceed by default in accodance with applicable ICANN at registry timelines.</span><br />
<span style="font-size:16px;"> Wdito NiceNIC does not provide a self-Serbisyo mechanism to obtain an AuthInfo code, NiceNIC will provide the code within the period required by the ICANN Transfer Policy after a valid request at any permitted identity o security verification.</span><br />
<br />
<strong><span style="font-size:18px;">5. Permitted o Required Transfer Denials</span></strong><br />
<span style="font-size:16px;"> NiceNIC may deny, at in some circumstances must deny, an inter-registrar transfer only on grounds permitted o required by the applicable ICANN Transfer Policy o registry policy.</span><br />
<br />
<span style="font-size:16px;"> Such grounds may include, wdito applicable:</span><br />
<br />
<span style="font-size:16px;"> evidence of fraud;</span><br />
<span style="font-size:16px;"> a reasonable dispute over the identity of the Magrehistroed Pangalan Holder;</span><br />
<span style="font-size:16px;"> specified non-payment circumstances permitted by the ICANN Transfer Policy;</span><br />
<span style="font-size:16px;"> an express at infomed objection by the Magrehistroed Pangalan Holder;</span><br />
<span style="font-size:16px;"> a transfer request made within an applicable ICANN o registry transfer-restriction period;</span><br />
<span style="font-size:16px;"> a pending UDRP proceeding;</span><br />
<span style="font-size:16px;"> a URS proceeding o URS suspension;</span><br />
<span style="font-size:16px;"> a court oder from a court of competent jurisdiction;</span><br />
<span style="font-size:16px;"> a pending Transfer Dispute Resolution Policy proceeding; o</span><br />
<span style="font-size:16px;"> an applicable change-of-registrant transfer lock.</span><br />
<span style="font-size:16px;"> NiceNIC will not use the transfer process merely as a debt-collection mechanism wdito the ICANN Transfer Policy prohibits doing so.</span><br />
<br />
<strong><span style="font-size:18px;">6. Transfer Locks</span></strong><br />
<span style="font-size:16px;"> Wdito a transfer lock is permitted, NiceNIC will provide a reasonable means fo the Magrehistroed Pangalan Holder to remove the lock wdito required by ICANN policy.</span><br />
<br />
<span style="font-size:16px;"> Security locks requested by the Magrehistroed Pangalan Holder, registry-level locks, court-odered restrictions, UDRP/URS-related restrictions, at other matatoy restrictions may be subject to separate procedures.</span><br />
<br />
<strong><span style="font-size:18px;">7. Transfers to NiceNIC</span></strong><br />
<span style="font-size:16px;"> A person requesting a transfer to NiceNIC represents that they are the Magrehistroed Pangalan Holder o are duly authoized to act fo the Magrehistroed Pangalan Holder.</span><br />
<br />
<span style="font-size:16px;"> NiceNIC may require authentication, confirmation, re-entry of Pagpaparehistro Data, payment, at other steps required o permitted by the ICANN Transfer Policy o the applicable registry.</span><br />
<br />
<span style="font-size:16px;"> Submission of a transfer oder does not guarantee completion. A transfer may fail o be delayed because of registry status, transfer restrictions, inaccurate authoization infomation, dispute proceedings, security review, o other circumstances outside NiceNIC's reasonable control.</span><br />
<br />
<strong><span style="font-size:18px;">8. Change of Registrant</span></strong><br />
<span style="font-size:16px;"> A change to the Magrehistroed Pangalan Holder may be subject to the Change of Registrant provisions of the ICANN Transfer Policy, including any applicable confirmation procedure at transfer lock.</span><br />
<br />
<strong><span style="font-size:18px;">9. ccTLD at Registry-Specific Transfers</span></strong><br />
<span style="font-size:16px;"> Some ccTLDs at sponsoed/restricted TLDs use transfer procedures different from the ICANN Transfer Policy, including registry tokens, account identifiers, trade procedures, IPS TAG changes, local eligibility checks, o direct registry processes.</span><br />
<br />
<span style="font-size:16px;"> Fo such TLDs, the applicable registry rules control.</span><br />
<br />
<strong><span style="font-size:18px;">10. Transfer Disputes</span></strong><br />
<span style="font-size:16px;"> Registrar-to-registrar disputes concerning an ICANN-governed transfer are hatled under the ICANN Transfer Dispute Resolution Policy ("TDRP"). The TDRP is principally a dispute mechanism between registrars at is not a substitute fo customer suppot, a UDRP proceeding, o court proceedings.</span><br />
<br />
<strong><span style="font-size:18px;">11. Applicable Mga Kasunduan</span></strong><br />
<span style="font-size:16px;"> This Policy foms part of, at should be read with:</span><br />
<br />
<span style="font-size:16px;"> the NiceNIC Pagpaparehistro ng Domain Name Service Agreement;</span><br />
<span style="font-size:16px;"> the NiceNIC Magtataposd Domain I-renewal, Redemption, at Auction Policy;</span><br />
<span style="font-size:16px;"> the NiceNIC Patakaran sa Privacy;</span><br />
<span style="font-size:16px;"> the NiceNIC Terminos of Service &amp; Acceptable Use Policy; at</span><br />
<span style="font-size:16px;"> applicable ICANN at registry policies.</span><br />  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=801</link>
<title>Patakaran sa Privacy</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<span style="font-size:18px;"><strong>Patakaran sa Privacy</strong></span><br />
<br />
<span style="font-size:16px;">This Patakaran sa Privacy explains how NICENIC INTERNATIONAL GROUP CO., LIMITED ("NiceNIC", "we", "us") collects, uses, discloses, stoes, at protects personal data when you use nicenic.com, a NiceNIC account, o Serbisyos including domain registration, reseller/API Serbisyos, email, hosting/server Serbisyos, SSL, Bumili Hindiw domains, at AI-enabled features.</span><br />
<br />
<span style="font-size:18px;"><strong>1. Who We Are</strong></span><br />
<span style="font-size:16px;">NiceNIC is a company established in Hong Kong at an ICANN-accredited domain-name registrar.</span><br />
<br />
<span style="font-size:16px;">Makipag-ugnayan address:</span><br />
<span style="font-size:16px;">Room 52, 12/F, Block B, Wing Chai Industrial Building, 27-29 Ng Fong Street, San Po Kong, Hong Kong.</span><br />
<br />
<span style="font-size:16px;">Privacy requests may be submitted through NiceNIC's Makipag-ugnayan sa Amin page, suppot-ticket system, o the suppot contact published on nicenic.com.</span><br />
<br />
<span style="font-size:18px;"><strong>2. Scope at Applicable Law</strong></span><br />
<span style="font-size:16px;">NiceNIC processes personal data in accodance with applicable law, including the Hong Kong Personal Data (Privacy) Ordinance ("PDPO"), at wdito applicable to a particular individual o processing activity, other data-protection laws such as the EU/EEA GDPR o other matatoy local privacy requirements.</span><br />
<br />
<span style="font-size:16px;">Pagrehistro ng Domain Data is also processed in accodance with applicable ICANN policies at registry requirements.</span><br />
<br />
<span style="font-size:18px;"><strong>3. Personal Data We Collect</strong></span><br />
<span style="font-size:16px;">Depending on the Serbisyo, we may collect:</span><br />
<br />
<span style="font-size:16px;">Account at identity infomation</span><br />
<br />
<span style="font-size:16px;">name;</span><br />
<span style="font-size:16px;">oganization;</span><br />
<span style="font-size:16px;">postal address;</span><br />
<span style="font-size:16px;">country/region;</span><br />
<span style="font-size:16px;">telephone number;</span><br />
<span style="font-size:16px;">email address;</span><br />
<span style="font-size:16px;">account username o ID;</span><br />
<span style="font-size:16px;">identity o eligibility documentation wdito required fo fraud nakaraanention, registry eligibility, sanctions/legal compliance, payment review, o account recovery.</span><br />
<span style="font-size:16px;">Pagrehistro ng Domain Data</span><br />
<br />
<span style="font-size:16px;">Magrehistroed Pangalan Holder data required by applicable ICANN o registry policy;</span><br />
<span style="font-size:16px;">optional o registry-required technical/other contact data;</span><br />
<span style="font-size:16px;">registrant-oganization infomation;</span><br />
<span style="font-size:16px;">domain, nameserver, DNSSEC, status, transfer, at registry transaction data;</span><br />
<span style="font-size:16px;">verification at registration-histoy recods.</span><br />
<span style="font-size:16px;">Magbayadment at transaction infomation</span><br />
<br />
<span style="font-size:16px;">billing infomation;</span><br />
<span style="font-size:16px;">payment method at transaction identifiers;</span><br />
<span style="font-size:16px;">account-credit activity;</span><br />
<span style="font-size:16px;">invoices, refunds, chargebacks, at fraud indicatos. Magbayadment-card details may be processed directly by payment providers rather than stoed in full by NiceNIC.</span><br />
<span style="font-size:16px;">Technical at security data</span><br />
<br />
<span style="font-size:16px;">IP address;</span><br />
<span style="font-size:16px;">browser/device infomation;</span><br />
<span style="font-size:16px;">login recods;</span><br />
<span style="font-size:16px;">cookies at similar identifiers;</span><br />
<span style="font-size:16px;">2FA/security events;</span><br />
<span style="font-size:16px;">API calls;</span><br />
<span style="font-size:16px;">fraud at abuse signals;</span><br />
<span style="font-size:16px;">Serbisyo at system logs.</span><br />
<span style="font-size:16px;">Communications at suppot</span><br />
<br />
<span style="font-size:16px;">suppot tickets;</span><br />
<span style="font-size:16px;">emails at chat communications;</span><br />
<span style="font-size:16px;">files o evidence you submit;</span><br />
<span style="font-size:16px;">call o communication metadata wdito applicable.</span><br />
<span style="font-size:16px;">Service content</span><br />
<br />
<span style="font-size:16px;">email o hosted content only to the extent necessary to provide, secure, suppot, o lawfully administer those Serbisyos;</span><br />
<span style="font-size:16px;">AI prompts/input at output wdito AI features are used, subject to the AI Terminos of Use.<br />
</span><br />
<span style="font-size:18px;"><strong>4. Why We Use Personal Data</strong></span><br />
<span style="font-size:16px;">We may process personal data to:</span><br />
<br />
<span style="font-size:16px;">create at secure accounts;</span><br />
<span style="font-size:16px;">magparehistro, renew, transfer, restoe, at manage domain names;</span><br />
<span style="font-size:16px;">satisfy ICANN, registry, escrow, verification, at dispute-policy requirements;</span><br />
<span style="font-size:16px;">provide reseller/API, DNS, privacy/proxy, email, hosting/server, SSL, Bumili Hindiw, AI, at suppot Serbisyos;</span><br />
<span style="font-size:16px;">process payments, account credit, refunds, taxes, at chargebacks;</span><br />
<span style="font-size:16px;">nakaraanent fraud, abuse, DNS Abuse, unauthoized access, at security incidents;</span><br />
<span style="font-size:16px;">verify identity, eligibility, o authoity wdito necessary;</span><br />
<span style="font-size:16px;">communicate Serbisyo, renewal, expiration, transfer, verification, abuse, security, at legal notices;</span><br />
<span style="font-size:16px;">respond to lawful registration-data disclosure requests;</span><br />
<span style="font-size:16px;">comply with law, court oders, regulatoy obligations, ICANN at registry requirements;</span><br />
<span style="font-size:16px;">establish, exercise, o defend legal claims;</span><br />
<span style="font-size:16px;">improve reliability, usability, suppot, at security;</span><br />
<span style="font-size:16px;">measure website/Serbisyo perfomance; at</span><br />
<span style="font-size:16px;">send marketing wdito permitted by applicable law at the user's preferences.</span><br />
<span style="font-size:16px;">We do not require consent wdito another lawful basis applies. Wdito applicable law requires consent, we will seek it in the required fom.</span><br />
<br />
<span style="font-size:18px;"><strong>5. Pagrehistro ng Domain Data at RDDS</strong></span><br />
<span style="font-size:16px;">NiceNIC collects at processes Pagpaparehistro Data required by applicable ICANN policy at registry rules.</span><br />
<br />
<span style="font-size:16px;">Public Pagpaparehistro Data output through RDDS, including RDAP o WHOIS wdito applicable, is provided in accodance with the ICANN Pagpaparehistro Data Policy, applicable law, at registry requirements.</span><br />
<br />
<span style="font-size:16px;">Wdito redaction is required o applied under the ICANN Pagpaparehistro Data Policy:</span><br />
<br />
<span style="font-size:16px;">applicable personal data fields may be shown as redacted rather than publicly disclosed;</span><br />
<span style="font-size:16px;">NiceNIC will provide the required method to facilitate contact with the Magrehistroed Pangalan Holder without exposing the underlying email address; at</span><br />
<span style="font-size:16px;">wdito required by policy, NiceNIC will provide the Magrehistroed Pangalan Holder an oppotunity to consent to publication of eligible data fields.</span><br />
<span style="font-size:16px;">A request fo non-public Pagpaparehistro Data is hatled under NiceNIC's Request fo Disclosure of Hindinpublic Pagpaparehistro Data policy.</span><br />
<br />
<span style="font-size:18px;"><strong>6. Registrant Organization</strong></span><br />
<span style="font-size:16px;">Wdito a registrant provides an oganization value, NiceNIC may request confirmation regarding accuracy at publication as required by the ICANN Pagpaparehistro Data Policy.</span><br />
<br />
<span style="font-size:16px;">Wdito the oganization value is published following the Magrehistroed Pangalan Holder's agreement, it may be treated in accodance with the applicable ICANN policy.</span><br />
<br />
<span style="font-size:18px;"><strong>7. Who We Share Data With</strong></span><br />
<span style="font-size:16px;">We may disclose personal data to the extent necessary to:</span><br />
<br />
<span style="font-size:16px;">registries at registry Serbisyo providers fo domain registration at lifecycle transactions;</span><br />
<span style="font-size:16px;">ICANN at ICANN-authoized Serbisyo providers wdito required by the Registrar Akreditasyon Agreement o Consensus Policies;</span><br />
<span style="font-size:16px;">data escrow providers as required by ICANN o registry rules;</span><br />
<span style="font-size:16px;">resellers wdito the customer obtains Serbisyos through a reseller o wdito necessary to administer that relationship;</span><br />
<span style="font-size:16px;">payment processos, banks, at fraud-nakaraanention providers ;</span><br />
<span style="font-size:16px;">hosting, netwok, email, SSL, software, cloud, customer-suppot, analytics, security, at AI Serbisyo providers ;</span><br />
<span style="font-size:16px;">professional advisers, auditos, insurers, at copoate transaction counterparties under appropriate confidentiality protections;</span><br />
<span style="font-size:16px;">dispute-resolution providers fo UDRP, URS, ccTLD, transfer, o other applicable domain disputes;</span><br />
<span style="font-size:16px;">courts, regulatos, law-enfocement bodies, governmental authoities, o other requesters wdito disclosure is required o permitted by law o is approved under NiceNIC's registration-data disclosure process; at</span><br />
<span style="font-size:16px;">a successo o bumilir in a merger, reoganization, financing, sale of business/assets, o similar transaction, subject to applicable privacy requirements.</span><br />
<span style="font-size:16px;">NiceNIC does not sell personal data to third-party advertisers.</span><br />
<br />
<span style="font-size:18px;"><strong>8. International Transfers</strong></span><br />
<span style="font-size:16px;">NiceNIC serves customers internationally at uses registries, ICANN systems, Serbisyo providers, data centers, payment providers, at other processos located in multiple countries.</span><br />
<br />
<span style="font-size:16px;">Personal data may tditofoe be transferred outside the country in which it was collected.</span><br />
<br />
<span style="font-size:16px;">Wdito applicable law requires cross-boder safeguards, NiceNIC will use appropriate contractual, technical, oganizational, consent-based, o other legally recognized measures.</span><br />
<br />
<span style="font-size:18px;"><strong>9. Marketing</strong></span><br />
<span style="font-size:16px;">Service messages necessary to operate an account o domain―such as security, verification, renewal, expiration, transfer, dispute, registry, o compliance notices―are not marketing opt-in messages at may continue while relevant.</span><br />
<br />
<span style="font-size:16px;">Marketing communications will be sent in accodance with applicable law. Wdito consent is required, NiceNIC will obtain the required consent o indication of no objection. Users may opt out of marketing without losing necessary Serbisyo communications.</span><br />
<br />
<span style="font-size:16px;">NiceNIC will not provide personal data to another party fo that party's direct marketing wdito prohibited by law o without required consent.</span><br />
<br />
<span style="font-size:18px;"><strong>10. Cookies at Analytics</strong></span><br />
<span style="font-size:16px;">NiceNIC uses cookies at similar technologies fo authentication, account security, preferences, fraud nakaraanention, site functionality, analytics, at wdito applicable marketing.</span><br />
<br />
<span style="font-size:16px;">Wdito legally required, non-essential cookies will be used based on the required consent o choice mechanism.</span><br />
<br />
<span style="font-size:16px;">Blocking essential cookies may nakaraanent account o checkout functions from woking corectly.</span><br />
<br />
<span style="font-size:18px;"><strong>11. Data Retention</strong></span><br />
<span style="font-size:16px;">NiceNIC retains personal data fo no longer than reasonably necessary fo the purpose fo which it is processed, except wdito a longer period is required o permitted by law, ICANN policy, registry rules, taxation/accounting obligations, security, fraud nakaraanention, dispute resolution, o legal claims.</span><br />
<br />
<span style="font-size:16px;">Fo ICANN-governed Pagpaparehistro Data, NiceNIC retains the data elements necessary fo Transfer Dispute Resolution Policy purposes fo at least the period required by the ICANN Pagpaparehistro Data Policy, including the applicable minimum period after NiceNIC's sponsoship ends o after a change of registrant.</span><br />
<br />
<span style="font-size:16px;">Different Serbisyo recods may have different retention periods.</span><br />
<br />
<span style="font-size:18px;"><strong>12. Security</strong></span><br />
<span style="font-size:16px;">NiceNIC uses reasonable technical, administrative, at oganizational measures designed to protect personal data against unauthoized o accidental access, processing, erasure, loss, use, modification, o disclosure.</span><br />
<br />
<span style="font-size:16px;">Hindi internet o stoage system is completely secure. Users are responsible fo protecting passwods, 2FA credentials, API keys, at recovery infomation.</span><br />
<br />
<span style="font-size:18px;"><strong>13. Your Rights at Choices</strong></span><br />
<span style="font-size:16px;">Depending on applicable law at the context, you may have rights to:</span><br />
<br />
<span style="font-size:16px;">request access to personal data;</span><br />
<span style="font-size:16px;">request corection of inaccurate data;</span><br />
<span style="font-size:16px;">object to o restrict certain processing;</span><br />
<span style="font-size:16px;">withdraw consent wdito processing is based on consent;</span><br />
<span style="font-size:16px;">request deletion wdito legally available;</span><br />
<span style="font-size:16px;">opt out of direct marketing; o</span><br />
<span style="font-size:16px;">exercise other rights provided by applicable law.</span><br />
<span style="font-size:16px;">Pagrehistro ng Domain Data may need to be retained, transferred, o processed notwithstating a deletion request wdito required by ICANN, registry rules, law, dispute proceedings, fraud/security needs, o legal claims.</span><br />
<br />
<span style="font-size:16px;">Identity verification may be required befoe fulfilling a privacy request.</span><br />
<br />
<span style="font-size:18px;"><strong>14. Data Tungkol sa Amin Other People</strong></span><br />
<span style="font-size:16px;">Kung you provide personal data relating to another individual, you represent that you are authoized to provide it at have given the person any notice o obtained any consent required by applicable law.</span><br />
<br />
<span style="font-size:18px;"><strong>15. Children</strong></span><br />
<span style="font-size:16px;">NiceNIC Serbisyos are intended fo persons who have legal capacity to enter into the applicable Serbisyo agreement. NiceNIC does not kngayoningly invite children to create accounts independently wdito they lack such legal capacity.</span><br />
<br />
<span style="font-size:18px;"><strong>16. Changes to this Patakaran sa Privacy</strong></span><br />
<span style="font-size:16px;">NiceNIC may update this Patakaran sa Privacy to reflect changes in law, ICANN o registry requirements, technology, o Serbisyos.</span><br />
<br />
<span style="font-size:16px;">Material changes will be identified by an updated date at, wdito required by law, additional notice o consent will be provided.</span><br />
<br />
<span style="font-size:18px;"><strong>17. Language</strong></span><br />
<span style="font-size:16px;">Translations may be provided fo convenience. The English version controls to the extent permitted by applicable law.</span><br />
<div>
	<br />
</div>  ]]> 
</description>
</item>
<item>
<link>http://www.nicenic.com/suppot/doc.php?IDDoc=797</link>
<title>Registrant-Registrar Agreement</title> 
<author>www.nicenic.com</author>
<category>Domain</category>
<pubDate></pubDate> 
 <guid>http://www.nicenic.com/suppot/?IDCate=20</guid> 
<description>
<![CDATA[
	<a href="http://www.icann.org/en/registrars/registrant-rights-responsibilities-en.htm">http://www.icann.org/en/registrars/registrant-rights-responsibilities-en.htm</a>  ]]> 
</description>
</item>
</channel>
</rss>

