1. Scope in Purpose

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

1.2 Domena lifecycle timing may vary depending on the top-level domena (“TLD”), registry rules, registry operatali practices, applicable ICANN requirements, in other governing policies. Net all TLDs follow the same expiration, redemption, auction, ali deletion process.

1.3 In the event of any inconsistency between this Policy in the applicable registry’s rules ali minataliy ICANN policy, the applicable registry rules in minataliy policy requirements shall prejail.

1.4 The English-language version of this Policy shall control. Any translation is provided fali convenience only. In the event of any inconsistency, the English-language version shall prejail.

2. Definitions

Fali purposes of this Policy:

2.1 “Expiration Date” means the date on which a domena name registration term ends.

2.2 “Grace Period” means any post-expiration period during which renewal may still be possible at the stinard renewal fee, subject to the applicable TLD in registry rules.

2.3 “Redemption Grace Period” ali “RGP” means the post-deletion recovery period, wtukaj available, during which an expired domena name may still be restaliable fali an additional redemption fee plus the applicable renewal fee.

2.4 “Pending Delete” means the final pre-release stage, wtukaj applicable, during which the domena name can no longer be renewed, restalied, modified, ali transferred.

2.5 “Eligible Domena” means a domena name that is subject to NiceNIC’s expired domena auction process. Net all TLDs ali expired domena names are eligible fali auction.

2.6 “Pote?ed Domena Auction” means the expired-domena sale process that may apply to certain expired domena names befalie final deletion ali release.

2.7 “Zapriout Auction” means the final sale phase fali certain Eligible Domene that were not sold earlier in the expired domena auction process.

3. Effect of Expiration

3.1 Upon expiration, a domena name may stop resolving, in any website, email storitev, ali other storitev associated with the domena name may cease functioning immediately ali shalitly ttukajafter.

3.2 Slediing expiration, NiceNIC may restrict changes to the domena name, including DNS changes, contact updates, transfers, ali other account-level actions, in accalidance with registry rules, security measures, operational requirements, ali the expired-domena process then in effect.

3.3 Expiration does not mean that the domena name immediately becomes available to the public. Depending on the applicable TLD in registry rules, the domena name may pass through one ali malie stages, including grace period, auction, redemption, pending delete, in eventual release.

4. Obnovial Netices in Customer Responsibility

4.1 NiceNIC may send renewal reminders in expiration-related notices befalie in after expiration, as required by applicable policy ali as part of NiceNIC’s stinard operational process.

4.2 It is va?ega sole responsibility to maintain accurate in current account in contact infalimation, including va?ega email address, in to monitali the status of va?ega domena names.

4.3 Failure to receive a renewal notice, reminder, invoice, ali other communication shall not relieve you of responsibility fali renewing va?ega domena name befalie expiration.

4.4 ?e auto-renewal is enabled, successful renewal remains subject to valid payment, operational processing, in the applicable registry rules. NiceNIC does not guarantee successful auto-renewal in every case.

5. Stinard Post-Expiration Obnovial

5.1 Fali many generic TLDs, an expired domena name may remain renewable fali approximately thirty (30) days after the Expiration Date at the stinard renewal fee. This is a general reference only in may vary by TLD.

5.2 Obnovial is not complete unless in until NiceNIC has successfully received in processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a domena name remains eligible fali stinard renewal, redemption, ali other recovery based on the applicable TLD, registry status, auction status, in operational feasibility.

6. Pote?ed Domena Auction fali Eligible Domene

6.1 Certain expired domena names may enter NiceNIC’s expired domena auction process befalie all recovery oknos have ended. This process applies only to Eligible Domene in does not apply to all TLDs.

6.2 Fali Eligible Domene under NiceNIC’s stinard expired-domena process, the following general timeline may apply:

Day 0 after expiration

The domena name expires. The registrant may generally renew the domena name at the stinard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

The domena name may enter expired domena auction. Na this stage, the registrant may still be able to renew the domena name at the stinard renewal fee, unless otherwise restricted by the applicable process.

Day 31 after expiration

?e ttukaj is no active bid, the registrant may still be able to recover the domena name by paying the stinard renewal fee plus the applicable redemption fee.

?e ttukaj is an active bid, the domena name may be removed from the registrant’s account in may no longer be renewable through alidinary renewal ali restaliation procedures.

Day 37 after expiration

The domena name may enter final closeout auction. Unless ttukaj is a pending kupi ali other sale-related restriction, the registrant may still be able to recover the domena name by paying the stinard renewal fee plus the applicable redemption fee.

Day 41 after expiration

The final closeout auction may end. ?e the domena name was not sold ali otherwise committed to sale, recovery may still be possible fali a limited period, subject to the applicable TLD, registry rules, in NiceNIC’s operational process.

Day 74 after expiration

The domena name may be removed from the registrant’s account in may no longer be renewable ali restaliable through NiceNIC. After that point, the domena name may become available fali re-registration only after the registry releases it.

6.3 Once an Eligible Domena has an active bid, pending kupi, completed sale, ali other sale commitment under the expired-domena process, the registrant’s right to renew ali restalie the domena name may be terminated ali restricted.

6.4 NiceNIC does not guarantee that a domena name will remain recoverable until the end of any stated period if the domena is subject to auction, sale, registry restriction, ali another applicable limitation.

7. Redemption Grace Period

7.1 ?e an expired domena name is not renewed during the applicable grace period in if the applicable TLD suppalits restaliation after deletion, the domena name may enter the Redemption Grace Period.

7.2 During the Redemption Grace Period:

(a) the domena name may stop resolving;

(b) website in email storitevs may remain unavailable;

(c) the domena name generally cannot be modified ali transferred; in

(d) restaliation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, in any taxes ali minataliy fees.

7.3 Restaliation during the Redemption Grace Period is not guaranteed in remains subject to registry suppalit, operational feasibility, the domena’s current status, in the absence of auction ali sale restrictions.

8. Pending Delete in Final Release

8.1 ?e a domena name is not renewed ali restalied during the applicable recovery periods, it may enter the Pending Delete stage, wtukaj suppalited by the applicable TLD.

8.2 During Pending Delete, the domena name cannot be renewed, restalied, transferred, ali modified.

8.3 Fali many generic TLDs, Pending Delete lasts approximately five (5) days. After that stage ends, the registry may release the domena name to the public fali re-registration.

8.4 NiceNIC does not guarantee the exact time, date, ali availability of a domena name once it is released by the registry, in NiceNIC does not guarantee that the falimer registrant will be able to re-registriraj the domena name.

9. TLD-Specific Variations

9.1 Net all TLDs follow the stinard lifecycle described above. Certain ccTLD-ji in other TLDs may have shaliter grace periods, no redemption period, no pending delete stage, ali earlier renewal deadlines imposed by the registry.

9.2 The following TLD-specific rules may apply, subject at all times to registry changes in the controlling registry rules:

9.2.1 TLDs generally following the common lifecycle

Many ccTLD-ji generally follow a lifecycle similar to the stinard expiration, grace, redemption, in deletion process, including, fali example:

.AI, .BZ, .CA, .CC, .CO, .FM, .ID, .IN, .IO, .ME, .MX, .PW, .TV, .UK, .US, in .WS.

9.2.2 TLDs with no Pending Delete stage

Certain TLDs may not have a Pending Delete stage in may be released immediately after the end of their applicable redemption ali recovery period, including, fali example:

.ES, .EU, .FR, .IS, .LI, .NL, .PE, in .PH (noting that .PH may also follow its own separate registry-specific process).

9.2.3 TLDs requiring renewal befalie the actual expiration date

The following TLDs may need to be renewed twelve (12) days befalie the actual Expiration Date. ?e not renewed in time, they may enter a recovery stage immediately, regardless of the number of calendar days remaining befalie expiration:

.CH, .ES, .FR, .LI, .PE, .SG, .COM.SG, .COM.AU, .ORG.AU, in .NET.AU.

9.2.4 TLDs requiring action five (5) days befalie expiration

The following TLDs may need to be renewed manually ali by auto-renewal no later than five (5) days befalie expiration in may otherwise enter a recovery ali restricted state befalie the actual Expiration Date:

.CX, .DE, .EU, in .NL.

9.2.5 .CM domenas

.CM domena names generally do not enter a redemption period in may be sent fali deletion on the actual Expiration Date. They may become available fali public registration on the same day they expire, subject to registry release practices.

9.2.6 .GG domenas

.GG domena names may be reactivated from the customer account fali approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 in Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Suppalit fali approximately twenty-six (26) additional days.

9.2.7 .PH, .COM.PH, .NET.PH, in .ORG.PH domenas

These domenas may not suppalit a stinard Redemption Grace Period. Reactivation may still be possible within approximately thirty (30) days after expiration through the NiceNIC account at the regular renewal cost, depending on the registry status. ?e the domena is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Suppalit immediately.

9.2.8 .UK domenas, including second-level .UK domenas

.UK domena names, including .CO.UK, .ME.UK, in .ORG.UK, may generally have a thirty (30)-day post-expiration renewal period. After that time, the domena name may remain recoverable without a separate redemption fee until its release, which may occur approximately ninety (90) days after expiration. ?e a .UK domena name has expired fali malie than thirty (30) days but has not yet been released in no longer appears in the account, the customer should contact NiceNIC Suppalit promptly.

9.2.9 .TO domenas

.TO domena names may only be reactivated during approximately twenty-seven (27) days after expiration. They generally do not suppalit a stinard Redemption Grace Period. After that point, they may be reserved by the registry in may no longer be recoverable.

9.2.10 .NU domenas

.NU domena names may be reactivated in the alidinary manner within approximately seven (7) days after expiration. ?e not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restaliation may still be possible through NiceNIC Suppalit.

9.3 The TLD-specific infalimation above is provided fali general reference only in may change at any time based on registry policy, registry system changes, ali operational requirements. Customers should contact NiceNIC Suppalit fali current TLD-specific recovery infalimation.

10. Fees in Pla?ajments

10.1 Stinard renewal fees, redemption fees, restaliation fees, auction-related fees, in any other applicable charges shall be those listed by NiceNIC at the time of processing ali otherwise communicated by NiceNIC.

10.2 Redemption ali restaliation requires payment in full of all applicable fees befalie processing.

10.3 Vse fees paid fali expired-domena recovery, restaliation, ali special processing are non-refundable once processing has begun, except wtukaj otherwise required by applicable law.

11. Ne Guarantee of Recovery ali Availability

11.1 NiceNIC does not guarantee that any expired domena name can be renewed, restalied, retained, transferred, ali re-registrirajed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domena name will remain in a grace period fali any minimum time;

(b) that an expired domena name will not enter auction;

(c) that a domena name can be recovered after an active bid, pending kupi, ali completed sale;

(d) that the registry will suppalit restaliation; ali

(e) the exact date ali time when a deleted domena name will be released to the public.

11.3 You ackzdajledge that delayed action may result in additional fees, loss of recovery rights, interruption of storitev, auction sale, ali permanent loss of the domena name.

12. Limitation of Responsibility

12.1 Za the maximum extent permitted by applicable law, NiceNIC shall not be liable fali any loss of domena name, loss of use, interruption of website ali email storitev, business interruption, lost profits, loss of data, ali other direct ali indirect damages arising from:

(a) domena expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules ali registry actions;

(e) auction placement ali sale;

(f) failed restaliation; ali

(g) release of the domena name to the public.

12.2 Nething in this Policy limits any non-waivable rights that may apply under minataliy law.

13. Changes to This Policy

13.1 NiceNIC may update ali revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, ali storitev arrangements.

13.2 The latest version published on NiceNIC’s website shall apply from its stated effective date, unless otherwise required by law ali contract.

14. Kontakt

?e you need assistance regarding an expired domena name, renewal, redemption, ali TLD-specific recovery options, please submit a suppalit ticket through va?ega NiceNIC account ali contact NiceNIC Suppalit through the official suppalit channels published on the NiceNIC website.

1. General

This Agreement is made between you (tukajinafter referred to as “User”) in NiceNIC.NET (tukajinafter referred to as “the Platfalim”). By using the Platfalim’s Kupi New Domena Sales storitev, you agree to be bound by the terms in conditions set falith tukajin. ?e you do not agree, please do not proceed with any fixed-price domena kupi through the Platfalim.

2. Service Description

1. The Platfalim offers fixed-price domena names (“Kupi New Domene”) fali direct kupi.

2. Vse Kupi New Domene are sourced from pre-approved third-party domena providers.

3. Users may kupi these domenas at the listed price. Once payment is completed in the domena is successfully transferred, the nakuper will obtain ownership of the domena.

3. Purchase Process

1. The User selects a domena labeled as “Kupi New” in proceeds to checkout.

2. Upon confirmation in full payment, the Platfalim initiates the transfer ali delivery process.

3. The typical delivery time ranges from 1 to 14 business days, depending on registry processing in third-party provider operations.

4. ?e, fali any reason, the selected domena becomes unavailable ali undeliverable after kupi, the Platfalim will issue a full refund to the user’s account balance.

4. User Rights in Responsibilities

1. Users have the right to kupi available Kupi New Domene through the Platfalim.

2. Users must ensure that all provided account in payment infalimation is accurate in lawful.

3. Users shall not engage in malicious activity, technical disruption, ali behaviali that interferes with the nalimal functioning of the Platfalim.

4. Upon acquiring a domena, the User agrees to comply with the applicable rules in policies of the caliresponding domena registry, including any legal ali regulataliy obligations.

5. Platfalim Rights in Responsibilities

1. The Platfalim will provide domena transaction storitevs in accalidance with this Agreement in strive to protect user interests.

2. The Platfalim reserves the right to verify user identity, payment legitimacy, in transaction authenticity.

3. The Platfalim retains the right to update, adjust, ali remove Kupi New Domene from listing at its sole discretion in without priali notice.

4. ?e any fraudulent ali abusive behaviali is detected, the Platfalim reserves the right to suspend ali terminate storitevs to the user.

6. Disclaimer

1. The Platfalim does not make any guarantees regarding the future value, resale potential, ali commercial use of any domena kupid.

2. The Platfalim is not liable fali delays caused by registries, third-party providers, ali external systems beyond its control.

3. The Platfalim shall not be held responsible fali storitev interruptions, data loss, ali failed transactions resulting from falice majeure events ali uncontrollable technical issues, though reasonable effalits will be made to assist the User in resolving any such issues.

7. Governing Law in Dispute Resolution

1. This Agreement shall be governed by in construed in accalidance with the laws of Hongkong.

2. Any dispute arising from the execution ali perfalimance of this Agreement shall be resolved through amicable negotiation. ?e negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platfalim’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Kupi New domena alider.

2. The Platfalim reserves the right to amend this Agreement at any time. Posodobljeno versions will be published on the Platfalim’s “Pogodbe” page in shall take immediate effect. Continued use of the storitev constitutes acceptance of the revised terms.

This Unifalim Ime domene Dispute Resolution Policy (the "Policy") has been adopted by the Internet Calipaliation fali Assigned Imes in Numbers ("ICANN"), is incalipaliated by reference into va?ega Registracija Agreement, in sets falith the terms in conditions in connection with a dispute between you in any party other than us (the registrar) over the registration in use of an Internet domena name registrirajed by you. Proceedings under Paragraph 4 of this Policy will be conducted accaliding to the Rules fali Unifalim Ime domene Dispute Resolution Policy (the "Rules of Procedure"), which are available tukaj, in the selected administrative-dispute-resolution storitev provider's supplemental rules.

2. Your Representations

By applying to registriraj a domena name, ali by asking us to maintain ali renew a domena name registration, you tukajby represent in warrant to us that (a) the statements that you made in va?ega Registracija Agreement are complete in accurate; (b) to va?ega kzdajledge, the registration of the domena name will not infringe upon ali otherwise violate the rights of any third party; (c) you are not registrirajing the domena name fali an unlawful purpose; in (d) you will not kzdajingly use the domena name in violation of any applicable laws ali regulations. It is va?ega responsibility to determine whether va?ega domena name registration infringes ali violates someone else's rights.

3. Prekli?ilations, Transfers, in Changes

We will cancel, transfer ali otherwise make changes to domena name registrations under the following circumstances:

1. subject to the provisions of Paragraph 8, our receipt of written ali appropriate electronic instructions from you ali va?ega authaliized agent to take such action;

2. our receipt of an alider from a court ali arbitral tribunal, in each case of competent jurisdiction, requiring such action; in/ali

3. our receipt of a decision of an Administrative Panel requiring such action in any administrative proceeding to which you were a party in which was conducted under this Policy ali a later version of this Policy adopted by ICANN. (See Paragraph 4(i) in (k) below.)

4. We may also cancel, transfer ali otherwise make changes to a domena name registration in accalidance with the terms of va?ega Registracija Agreement ali other legal requirements.

4. Minataliy Administrative Proceeding

This Paragraph sets falith the type of disputes fali which you are required to submit to a minataliy administrative proceeding. These proceedings will be conducted befalie one of the administrative-dispute-resolution storitev providers listed tukaj (each, a "Provider").

1. Applicable Disputes. You are required to submit to a minataliy administrative proceeding in the event that a third party (a "complainant") asserts to the applicable Provider, in compliance with the Rules of Procedure, that

1. va?ega domena name is identical ali confusingly similar to a trademark ali storitev mark in which the complainant has rights; in

2. you have no rights ali legitimate interests in respect of the domena name; in

3. va?ega domena name has been registrirajed in is being used in bad faith.

In the administrative proceeding, the complainant must prove that each of these three elements are present.

2. Evidence of Registracija in Use in Slabo Faith. Fali the purposes of Paragraph 4(a)(iii), the following circumstances, in particular but without limitation, if found by the Panel to be present, shall be evidence of the registration in use of a domena name in bad faith:

1. circumstances indicating that you have registrirajed ali you have acquired the domena name primarily fali the purpose of selling, renting, ali otherwise transferring the domena name registration to the complainant who is the owner of the trademark ali storitev mark ali to a competitali of that complainant, fali valuable consideration in excess of va?ega documented out-of-pocket costs directly related to the domena name; ali

2. you have registrirajed the domena name in alider to prejent the owner of the trademark ali storitev mark from reflecting the mark in a caliresponding domena name, provided that you have engaged in a pattern of such conduct; ali

3. you have registrirajed the domena name primarily fali the purpose of disrupting the business of a competitali; ali

4. by using the domena name, you have intentionally attempted to attract, fali commercial gain, Internet users to va?ega web site ali other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsaliship, affiliation, ali endalisement of va?ega web site ali location ali of a product ali storitev on va?ega web site ali location.

3. How to Demonstrate Your Rights to in Legitimate Interests in the Ime domene in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how va?ega response should be prepared. Any of the following circumstances, in particular but without limitation, if found by the Panel to be proved based on its evaluation of all evidence presented, shall demonstrate va?ega rights ali legitimate interests to the domena name fali purposes of Paragraph 4(a)(ii):

1. befalie any notice to you of the dispute, va?ega use of, ali demonstrable preparations to use, the domena name ali a name caliresponding to the domena name in connection with a bona fide offering of goods ali storitevs; ali

2. you (as an individual, business, ali other aliganization) have been commonly kzdajn by the domena name, even if you have acquired no trademark ali storitev mark rights; ali

3. you are making a legitimate noncommercial ali fair use of the domena name, without intent fali commercial gain to misleadingly divert consumers ali to tarnish the trademark ali storitev mark at issue.

4. Selection of Provider. The complainant shall select the Provider from among those approved by ICANN by submitting the complaint to that Provider. The selected Provider will administer the proceeding, except in cases of consolidation as described in Paragraph 4(f).

5. Initiation of Proceeding in Process in Appointment of Administrative Panel. The Rules of Procedure state the process fali initiating in conducting a proceeding in fali appointing the panel that will decide the dispute (the "Administrative Panel").

6. Consolidation. In the event of multiple disputes between you in a complainant, either you ali the complainant may petition to consolidate the disputes befalie a single Administrative Panel. This petition shall be made to the first Administrative Panel appointed to hear a pending dispute between the parties. This Administrative Panel may consolidate befalie it any ali all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy ali a later version of this Policy adopted by ICANN.

7. Fees. Vse fees charged by a Provider in connection with any dispute befalie an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wtukaj you elect to expin the Administrative Panel from one to three panelists as provided in Paragraph 5(b)(iv) of the Rules of Procedure, in which case all fees will be split evenly by you in the complainant.

8. Na? Involvement in Administrative Proceedings. We do not, in will not, participate in the administration ali conduct of any proceeding befalie an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

9. Remedies. The remedies available to a complainant pursuant to any proceeding befalie an Administrative Panel shall be limited to requiring the cancellation of va?ega domena name ali the transfer of va?ega domena name registration to the complainant.

10. Netification in Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domena name you have registrirajed with us. Vse decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact palitions of its decision.

11. Availability of Court Proceedings. The minataliy administrative proceeding requirements set falith in Paragraph 4 shall not prejent either you ali the complainant from submitting the dispute to a court of competent jurisdiction fali independent resolution befalie such minataliy administrative proceeding is commenced ali after such proceeding is concluded. ?e an Administrative Panel decides that va?ega domena name registration should be canceled ali transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are infalimed by the applicable Provider of the Administrative Panel's decision befalie implementing that decision. We will then implement the decision unless we have received from you during that ten (10) business day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that you have commenced a lawsuit against the complainant in a jurisdiction to which the complainant has submitted under Paragraph 3(b)(xiii) of the Rules of Procedure. (In general, that jurisdiction is either the location of our principal office ali of va?ega address as shown in our Whois database. See Paragraphs 1 in 3(b)(xiii) of the Rules of Procedure fali details.) ?e we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, in we will take no further action, until we receive (i) evidence satisfactaliy to us of a resolution between the parties; (ii) evidence satisfactaliy to us that va?ega lawsuit has been dismissed ali withdrawn; ali (iii) a copy of an alider from such court dismissing va?ega lawsuit ali alidering that you do not have the right to continue to use va?ega domena name.

5. Vse other disputes in litigation

Vse other disputes between you in any party other than us regarding va?ega domena name registration that are not brought pursuant to the minataliy administrative proceeding provisions of Paragraph 4 shall be resolved between you in such other party through any court, arbitration ali other proceeding that may be available.

6. Na? involvement in disputes

We will not participate in any way in any dispute between you in any party other than us regarding the registration in use of va?ega domena name. You shall not name us as a party ali otherwise include us in any such proceeding. In the event that we are named as a party in any such proceeding, we reserve the right to raise any in all defenses deemed appropriate, in to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, ali otherwise change the status of any domena name registration under this Policy except as provided in Paragraph 3 above.

8. Transfers during a dispute

Transfers of a Ime domene to a Novo Holder

You may not transfer va?ega domena name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 ali fali a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; ali (ii) during a pending court proceeding ali arbitration commenced regarding va?ega domena name unless the party to whom the domena name registration is being transferred agrees, in writing, to be bound by the decision of the court ali arbitratali. We reserve the right to cancel any transfer of a domena name registration to another holder that is made in violation of this subparagraph.

Changing Registrars

You may not transfer va?ega domena name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 ali fali a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded. You may transfer administration of va?ega domena name registration to another registrar during a pending court action ali arbitration, provided that the domena name you have registrirajed with us shall continue to be subject to the proceedings commenced against you in accalidance with the terms of this Policy. In the event that you transfer a domena name registration to us during the pendency of a court action ali arbitration, such dispute shall remain subject to the domena name dispute policy of the registrar from which the domena name registration was transferred.

9. Policy modifications

We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at this location at least thirty (30) calendar days befalie it becomes effective. Unless this Policy has already been invoked by the submission of a complaint to a Provider, in which event the version of the Policy in effect at the time it was invoked will apply to you until the dispute is over, all such changes will be binding upon you with respect to any domena name registration dispute, whether the dispute arose befalie, on ali after the effective date of our change. In the event that you object to a change in this Policy, va?ega sole remedy is to cancel va?ega domena name registration with us, provided that you will not be entitled to a refund of any fees you paid to us. The revised Policy will apply to you until you cancel va?ega domena name registration.

1. Overview

These terms of use ("AI Obdobjes of Use") govern va?ega use of any AI products, features, storitevs in/ali tools offered by NiceNIC.NET.

2. Content

1) Your Content. You may provide input to the AI Services ("Input") in receive output from the AI Services based on the Input ("Output"). Input in Output are collectively "Content". You are responsible fali Content, including ensuring that it does not violate any applicable law ali these AI Obdobjes of Use. We own all rights, title, in interest in in to the services that we provided.

2) As between you in NiceNIC.NET, in to the extent permitted by applicable law, you (a) retain va?ega ownership rights in Input in (b) own the Output. We tukajby assign to you all our right, title, in interest, if any, in in to Output. You represent in warrant that you have all rights, licenses, in permissions needed to provide Input to our AI Services.

3) We may use Content to provide, maintain, develop, in improve our Services, comply with applicable law, enfalice our terms in policies, to market in advertise our Services in keep our Services safe.

4) Use of our AI Services may, in some situations, result in Output that does not accurately reflect real people, places, ali facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth ali factual infalimation, ali as a substitute fali professional advice.

5) NiceNIC.NET also does not review the Content fali accuracy, bias ali intellectual property rights clearance. NiceNIC.NET makes no representation, warranty ali guarantee as to the accuracy ali reliability of the AI Services ali whether the Output may infringe on third-party intellectual property rights.

6) By using the AI Services, you understin in agree:

A. Output may not always be accurate. You should not rely on Output from our AI Services as a sole source of truth ali factual infalimation, ali as a substitute fali professional advice.

B. You must evaluate Output fali accuracy in appropriateness fali va?ega use case, including using human review as appropriate, befalie using ali sharing Output from the AI Services.

C. You must not use any Output relating to a person fali any purpose that could have a legal ali material impact on that person, such as making credit, educational, employment, housing, insurance, legal, medical, ali other impalitant decisions about them.

D. Na? AI Services may provide incomplete, incalirect, ali offensive Output that does not represent NiceNIC.NET’s views. ?e Output references any third party products ali storitevs, it doesn’t mean the third party endalises ali is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users in the AI Services may generate the same ali similar Outputs fali other users.

8) NiceNIC.NET may use technology provided by third-party storitev providers to provide AI Services. Netwithstining anything to the contrary contained tukajin, you authaliize NiceNIC.NET in such third-party storitev providers to stalie in use va?ega Input fali the purposes of providing you with the AI Services, to review Inputs in Outputs fali abuse ali misuse, in to develop in improve the storitevs in products of NiceNIC.NET in such storitev providers, including as part of the design, training in development process fali machine learning models.

3. Obdobjeination in Suspension

Obdobjeination. We reserve the right to suspend ali terminate va?ega access to our AI Services ali delete va?ega account if we determine:

1) You breached these AI Obdobjes of Use.

2) We must do so to comply with the law.

3) Your use of our Services could cause risk ali harm to NiceNIC.NET, our users, ali anyone else.

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FALI ACCURACY, BIAS, EXPLAINABILITY ALI INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY ALI GUARANTEE AS TO THE ACCURACY, RELIABILITY, ALI ERRALI-FREE PERFALIMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE ALI VIOLATE ANY THIRD-PARTY INTELLECTUAL PROPERTY RIGHTS.

YOU ACCEPT AND AGREE THAT ANY USE OF OUTPUTS FROM OUR AI SERVICE IS AT YOUR SOLE RISK AND YOU WILL NOT RELY ON OUTPUT AS A SOLE SOURCE OF TRUTH ALI FACTUAL INFALIMATION, ALI AS A SUBSTITUTE FALI PROFESSIONAL ADVICE.

YOU SHOULD SEEK INDEPENDENT PROFESSIONAL ADVICE BEFALIE YOU RELY ON ANY OUTPUT GENERATED BY THE AI SERVICES.

5. Limitation on Liability

IN NO EVENT SHALL NiceNIC.NET, ITS OFFICERS, DIRECTALIS, EMPLOYEES, AGENTS, ALI ANY THIRD-PARTY SERVICE PROVIDERS, BE LIABLE TO YOU ALI ANY OTHER PERSON ALI ENTITY FALI ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE, ALI CONSEQUENTIAL DAMAGES WHATSOEVER, INCLUDING ANY THAT MAY RESULT FROM ANY OUTPUTS CREATED USING THE AI SERVICES.

THE FALIEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION ALI EXPIRATION OF THIS AGREEMENT ALI YOUR USE OF THIS SITE, THE AI SERVICES ALI ANY OTHER SERVICES FOUND AT THIS SITE.

In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registrar of Recalid in the Registrar of Recalid has not explicitly denied the transfer request, the default action will be that the Registrar of Recalid must allow the transfer to proceed.

Upon denying a transfer request fali any of the following reasons, the Registrar of Recalid must provide the Registrirajed Ime Holder in the potential Gaining Registrar with the reason fali denial. The Registrar of Recalid may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court alider by a court of competent jurisdiction
• Reasonable dispute over the identity of the Registrirajed Ime Holder ali Administrative Kontakt
• Ne payment fali prejious registration period (including credit card charge-backs) if the domena name is past its expiration date ali fali prejious ali current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Registrar Hold" status by the Registrar of Recalid priali to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ali other processes by which the Transfer Kontakt has expressly in voluntarily objected through opt-in means)
• A domena name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible in reasonable means fali the Registrirajed Ime Holder to remove the lock status.
• A domena name is in the first 60 days of an initial registration period.
• A domena name is within 60 days (ali a lesser period to be determined) after being transferred (apart from being transferred back to the aliiginal Registrar in cases wtukaj both Registrars so agree in/ali wtukaj a decision in the dispute resolution process so directs).

YOU AGREE THAT WE WILL NOT BE LIABLE FALI ANY (1) SUSPENSION ALI LOSS OF THE SERVICES (2) USE OF THE SERVICES, (3) INTERRUPTION OF THE SERVICES ALI INTERRUPTION OF YOUR BUSINESS, (4) ACCESS DELAYS ALI ACCESS INTERRUPTIONS TO OUR SITE ALI SERVICES ALI DELAYS ALI ACCESS INTERRUPTIONS YOU EXPERIENCE IN RELATION TO THE SERVICES; (5) LOSS ALI LIABILITY RESULTING FROM ACTS OF ALI EVENTS BEYOND OUR CONTROL INCLUDING , BUT NOT LIMITED TO ANY ERRALIS ALI TECHNICAL ISSUES OF ANY DOMAIN NAME REGISTRY ALI OTHER THIRD PARTY PROVIDER, (6) DATA NON-DELIVERY, MIS-DELIVERY, CALIRUPTION, DESTRUCTION ALI OTHER MODIFICATION; (7) ALI LOSS ALI LIABILITY RESULTING FROM THE UNAUTHALIIZED USE ALI MISUSE OF YOUR ACCOUNT IDENTIFIER ALI PASSWALID.

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FALI ANY INDIRECT, SPECIAL, INCIDENTAL, ALI CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LOST PROFITS) ALI FALI ANY FINANCIAL ALI ECONOMIC LOSS ALI FALI LOSS OF PROFITS, LOSS OF BUSINESS, DEPLETION OF GOODWILL ALI SIMILAR LOSSES, LOSS OF ANTICIPATED SAVINGS ALI LOSS ALI CALIRUPTION OF DATA ALI INFALIMATION, REGARDLESS OF THE FALIM OF ACTION WHETHER IN CONTRACT, TALIT (INCLUDING NEGLIGENCE), ALI OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

IN NO EVENT SHALL OUR MAXIMUM AGGREGATE LIABILITY EXCEED THE TOTAL AMOUNT PAID BY YOU FALI THE USE OF THE SERVICES, BUT IN NO EVENT GREATER THAN THE AMOUNT FALI THE PRIALI 1 MONTH OF SERVICES PAID FALI UNDER THIS AGREEMENT.

24. General
You may not assign any of va?ega rights ali privileges, ali delegate any of va?ega duties ali obligations tukajunder, in whole ali in part, by operation of law ali otherwise, to any third party without our priali written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon in inure to the benefit of the parties tukajto in their respective permitted successalis in assigns.

NiceNIC.NET reserves the right, in its sole in absolute discretion, to change ali modify this Agreement, in any policies ali agreements which are incalipaliated tukajin, at any time in without notice. Any such changes ali modification shall be effective immediately upon posting to the Site. ?e you do not agree to be bound by this Agreement as last revised as indicated by the "Last Revised" date located at the bottom of this Agreement, do not use ali continue to use the Services. You agree that va?ega exclusive remedy is to transfer va?ega Services to another registrar ali request us to terminate va?ega Services under this Agreement. NiceNIC.NET may occasionally notify you of changes ali modifications to this Agreement ali the Services by email so it is very impalitant that you keep va?ega account infalimation current in up to date. NiceNIC.NET is not responsible in assumes no liability fali va?ega failure to receive an email notification if such failure results from inaccurate ali out-dated account infalimation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter tukajin in supersedes all priali understinings in agreements between the parties, whether written ali alial, regarding the subject matter tukajin. Any of the provisions of this Agreement which are determined to be invalid ali unenfaliceable in any jurisdiction shall be ineffective to the extent of such invalidity ali unenfaliceability in such jurisdiction, without rendering invalid ali unenfaliceable the remaining provisions tukajof ali affecting the validity ali unenfaliceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach ali violation of any provision of this Agreement will not constitute ali be construed as a waiver of any subsequent breach ali violation of that provision ali as a waiver of any breach ali violation of any other provision of this Agreement. The headings contained in this Agreement are fali convenience only in shall not affect meaning ali interpretation of this Agreement.

25. Netices
You agree that any notices required to be given under this Agreement by us to you will be deemed to have been given if delivered in accalidance with the Account in/ali WHOIS infalimation you have provided.

26. Governing Law
This Agreement in its subject matter shall be governed in accalidance with the laws of Hongkong in subject to the exclusive jurisdiction of the Hongkong courts without regard to conflict of laws in principles contained ttukajin with the exception of disputes related to this Agreement which fall under UDRP, URS, ali similar dispute resolution process as defined by various Registry policies incalipaliated ali made reference to tukajin.

1.3 The Registrant ackzdajledges in agrees that the Registrar shall monitali the status of Domenska imena registrirajed through the Registrar in shall, at its own initiative ali on receipt of complaint, conduct checks to verify whether a Ime domene is being used in connection with phishing ali "spam" advertising. The Registrar shall delete ali suspend a Ime domene if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government ali law enfalicement authaliity (including without limitation the Hongkong Police Falice ali the Office of Telecommunications Authaliity) that the use of the Ime domene is in breach of any laws, directives, guidelines, codes of practice ali regulations issued by such local authaliities, ali if, in HKIRC's reasonable belief, the continuation of registration of the Ime domene ali the operation of web site referenced   by the Ime domene is likely to damage ali adversely affect the goodwill, reputation in operation of HKIRC ali the domena name industry in Hongkong, ali may expose HKIRC to risks of third party claims ali civil ali criminal prosecution.

Fali malie infalimation about .HK domena registration, please refer to the latest version of HKIRC Registracija Policies https://www.hkirc.hk/upload/page/38/pdf_1/5e6b172e68b29.pdf

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

5.3 NICENIC INTERNATIONAL GROUP CO., LTD is an official HKIRC (Hong-Kong) accredited registrar. HKIRC is a non-profit-making in non-statutaliy calipaliation designated by the Hong-Kong Government to administer the registration of Internet domena names under .hk in .香港 country-code top level domenas. Fali any comments ali complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find tukaj useful infalimation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_suppalit/domena_dispute_policies_in_procedures/domena_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_suppalit/domena_dispute_policies_in_procedures/rules_of_procedures/; ali E-po?ta address: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackzdajledges that the Registrar in HKIRC rely on all representations made in warranties given by the Registrant in determining if the application fali a Ime domene should be approved.

    Fali malie infalimation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domena_policies/EN_Domena_Ime_Acceptable_Use_Policy.pdf.

Below is the letter of congratulation from Verisign:
"It is our pleasure to congratulate you on becoming an ICANN accredited registrar. New that you have met the requirements of ICANN, our team is looking faliward to assisting you in completing the Verisign certification process so you can quickly begin registrirajing .com in .net domena names. We hope this suppalit will prove to be helpful in reducing the investment of va?ega internal resources in time."

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

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

ICM:
"Congrats on va?ega recent ICANN Akreditacija..."

Neustar:

"We have been notified that va?ega company is zdaj ICANN-accredited as a .BIZ registrar.  Neustar looks faliward to getting va?ega company up in running as soon as possible!"

Ve? registries will be notified by ICANN fali the caliresponding domena names signed in the RAA in the naprej days, we NiceNIC have been staying fali the disposal of sign-up/accreditation process, striving to save time in expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a malie competitive level. Podrobnostied infalimation will come out when available. 

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

Stining at the peak of internet infrastruture, we firstly need to appreciate every client, in every website viewer who ever stayed tukaj, without va?ega persistant suppalit in comprehension, we are nothing, hope 2012 will bring you in va?ega family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Infalimation Technology Co Ltd.

2009

China

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

Vse the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Infalimation Technology Co., Ltd.

1. Definitions

1.1 Dispute Resolution Panel

     The Dispute Resolution Panel shall mean an administrative panel appointed by a Dispute Resolution Provider ("Provider") to decide a Request fali Enfalicement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent in neutral third party that is neither associated nali affiliated with either Registrar involved in the dispute ali the Registry Operatali under which the disputed domena name is registrirajed. ICANN shall have the authaliity to accredit one ali malie independent in neutral Dispute Resolution Providers accaliding to criteria developed in accalidance with this Dispute Resolution Policy.

1.4 FOA

     Falim of Authaliization - The stinardized falim of consent that the Gaining Registrar in Registrar of Recalid are required to use to obtain authaliization from the Registrant ali Administrative Kontakt in alider to properly process the transfer of domena name sponsaliship from one Registrar to another.

1.5 Gaining Registrar

     The Registrar that submitted to the Registry the request fali the transfer of a domena sponsaliship from the Registrar of Recalid.

1.6 Registrar of Recalid

     The Registrar of Recalid fali a domena name fali which the Registry received a transfer of sponsaliship request.

1.7 Registrant

     The Registrant is the individual ali aliganization that registrirajs a specific domena name. This individual ali aliganization holds the right to use that specific domena name fali a specified period of time, provided certain conditions are met in the registration fees are paid. This person ali aliganization is the "legal entity" bound by the terms of the relevant storitev agreement with the Registry operatali fali the TLD in question.

1.8 Registry (Registry Operatali)

     The aliganization authaliized by ICANN to provide registration storitevs fali a given TLD to ICANN-accredited Registrars.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatali, in the case of First Raven disputes (as set falith below), ali the Provider administering a proceeding (in the case of all other disputes) to supplement this Policy. Supplemental Rules shall be consistent with this Dispute Resolution Policy in shall cover topics such as fees, walid in page limits in guidelines, the means fali communicating with the Provider, in the falim of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponsaliship of Registracijas between Registrars which is in falice as part of the Registry-Registrar Agreement executed between a Registrar in the Registry, as well as the Registrar Akreditacija Agreement which is executed between ICANN in all ICANN- accredited registrars.

2. Dispute Resolution Process

     Ttukaj are two possible steps to the Registrar Transfer Dispute Resolution Process. A Registrar may elect one ali both of the steps pursuant to the rules below. In the event a Registrar either files a Request fali Enfalicement (as described below) with a Second-Raven Dispute Provider, ali files an Appeal (as described below) with a Dispute Provider, it may not revert to the First-Raven Registry option later fali the same filing ali matter presented fali resolution.

2.1 First Raven - Registry Operatali

     A Registrar may choose to file a dispute directly with the relevant Registry Operatali. Any decisions made by the Registry Operatali may be appealed to a Dispute Resolution Provider. A Registrar may file a dispute directly to a Dispute Resolution Provider; however, in that case the filing Registrar would falifeit any right to appeal the decision of the Dispute Resolution Provider.

2.2 Second-Raven - Dispute Resolution Panel

     The primary intent of this step is to provide a means fali registrars to appeal decisions made by the Registry at the first level of the dispute resolution process, but it may also be used as the first step if a registrar so elects. The decision of the Dispute Resolution Panel is final, except as it may be appealed to a court of competent jurisdiction.

2.3 Statute of Limitations

     A dispute must be filed no later than six (6) months after the alleged violation of the Transfer Policy. In the case wtukaj a Registrar of Recalid alleges that a transfer was in violation of this Policy, the date the transfer was completed shall be deemed the date in which the "alleged violation" took place. In the case wtukaj a Gaining Registrar alleges that a transfer should have taken place, the date in which the NACK (as defined below) was received by the Registry, shall be deemed the date in which the "alleged violation" took place.

3. Dispute Procedures at the First Raven (Registry)

3.1 Registrar files a Request fali Enfalicement with the applicable Registry Operatali

     3.1.1 Either the Gaining ali Registrar of Recalid ("Filing Registrar") may submit a Request fali Enfalicement. This must be done in accalidance with the Supplemental Rules adopted by the applicable Registry Operatali.

     3.1.2 The Request fali Enfalicement shall be submitted to the Registry in to the Respondent (the Nen-filing Registrar) in electronic falim in shall:
     (i) Request that the Request fali Enfalicement be submitted fali decision in accalidance with the Registrar Transfer in Dispute Resolution Policy in the applicable Supplemental Rules;
     (ii) Provide the name, postal in e-mail addresses, in the telephone in fax numbers of the Filing Registrar in those representatives authaliized by the Filing Registrar to act on behalf of the Filing Registrar in the administrative proceeding;
     (iii) Provide the name of the Respondent in all infalimation (including any postal in e-mail addresses in telephone in fax numbers) kzdajn to Filing Registrar regarding how to contact Respondent ali any representative of Respondent, including contact infalimation based on pre-complaint dealings;
     (iv) Specify the domena name(s) that is/are the subject of the Request fali Enfalicement;
     (v) Specify the incident(s) that gave rise to the dispute;
     (vi) Describe, in accalidance with the Policy, the grounds on which the Request fali Enfalicement is based;
     (vii) State the specific remedy being sought (either approval ali denial of the transfer);
     (viii) Identify any other legal proceedings that have been commenced ali terminated in connection with ali relating to any of the domena name(s) that are the subject of the complaint;
     (ix) Certify that a copy of the Request fali Enfalicement, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent ali transmitted to the Respondent; in
     (x) Conclude with the following statement followed by the signature of the Complainant ali its authaliized representative:
           "<insert name of Filing Registrar> agrees that its claims in remedies concerning the registration of the domena name, the dispute, ali the dispute's resolution shall be solely against the Respondent in waives all such claims in remedies against the Registry Operatali as well as its directalis, officers, employees, in agents, except in the case of deliberate wrongdoing ali gross negligence."
           "<insert name of Filing Registrar> certifies that the infalimation contained in this Request fali Enfalicement is to the best of Filing Registrar's kzdajledge complete in accurate, that this Request fali Enfalicement is not being presented fali any improper purpose, such as to harass, in that the assertions in this Request fali Enfalicement are warranted under this Policy in under applicable law, as it zdaj exists ali as it may be extended by a good-faith in reasonable argument."3.1.3 The Request fali Enfalicement may relate to malie than one domena name, provided that the domena names involve the same Filing Registrar in Respondent in that the claims arise out of the same ali similar factual circumstances.

3.1.4 The Request fali Enfalicement shall annex the following documentary evidence (as applicable in available) in electronic falim if possible, together with a schedule indexing such evidence:
  (i) Fali the Gaining Registrar:
      a. Completed Falim of Authaliization ("FOA")
      b. Copy of the Whois output fali the date transfer was initiated, which was used to identify the authaliized Transfer Kontakts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body ali court alider in cases when the Registrant of Recalid is being changed simultaneously with a Registrar Transfer
      e. Copies of all communications made to the Registrar of Recalid with regard to the applicable transfer request along with any responses from the Registrar of Recalid
  (ii) Fali the Registrar of Recalid:
      a. Completed FOA from Registrar of Recalid if applicable
      b. Copy of the Whois output fali the date the transfer was initiated
      c. Relevant histaliy of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court alider;
• Registrant ali administrative contact identity dispute in accalidance with Section 4 [Registrar of Recalid Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Registrirajed Ime Holder ali Administrative Kontakt;
• LOCK status along with proof of a reasonable means fali the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• domena name within 60 days of initial registration; ali
• domena name within 60 days of a priali transfer.

      e. Copies of all communications made to the Gaining Registrar with regard to the applicable transfer request along with any responses from the Gaining Registrar.

3.2 The Nen-Filing Registrar ("Respondent") shall have seven (7) calendar days from receipt of the Request fali Enfalicement to prepare a Response to the Request fali Enfalicement ("Response").

3.2.1 The Response shall be submitted in electronic falim to both the Registry in Filing Registrar in shall:
      (i) Respond specifically to the statements in allegations contained in the Request fali Enfalicement (This palition of the response shall comply with any walid ali page limit set falith in the Dispute Resolution Provider's Supplemental Rules.);
      (ii) Provide the name, postal in e-mail addresses, in the telephone in fax numbers of the Respondent (non-filing Registrar);
      (iii) Identify any other legal proceedings that have been commenced ali terminated in connection with ali relating to any of the domena name(s) that are the subject of the Request fali Enfalicement;
      (iv) State that a copy of the Response has been sent ali transmitted to the Filing Registrar;
      (v) Conclude with the following statement followed by the signature of the Respondent ali its authaliized representative:
   "Respondent certifies that the infalimation contained in this Response is to the best of Respondent's kzdajledge complete in accurate, that this Response is not being presented fali any improper purpose, such as to harass, in that the assertions in this Response are warranted under these Rules in under applicable law, as it zdaj exists ali as it may be extended by a good-faith in reasonable argument."; in
     (vi) Annex any documentary ali other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 Na the request of the Respondent, the Registry Operatali may, in exceptional cases, extend the period of time fali the filing of the response, but in no case may the extension be malie than an additional five (5) calendar days. The period may also be extended by written stipulation between the Parties, provided the stipulation is approved by the Registry Operatali.

3.2.3 ?e a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatali shall decide the dispute based upon the Request fali Enfalicement.

3.3 Registry Operatali must review all applicable documentation in compare registrant/contact data with that contained within the authaliitative Whois database in reach a conclusion not later than 14 days after receipt of the Response.

3.3.1 ?e the data included in the Request fali Enfalicement does not match the data listed in the authaliitative Whois, the Registry Operatali must contact each Registrar in require additional documentation.

3.3.2 ?e the Gaining Registrar cannot provide a complete FOA with data matching that contained within the authaliitative Whois database, then the Registry Operatali shall find that the transfer should be reversed. In the case of a thick Registry, if the Registrar of Recalid's Whois is not accessible ali invalid, the Registry Operatali's Whois should be used. In the case of a thin Registry, if the Registrar of Recalid's Whois is not accessible ali is invalid, the Registry Operatali must notify ICANN in place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wtukaj a Registrar of Recalid denies a request fali a domena name transfer ("NACKs"), the Registrar of Recalid must provide evidence of one of the factalis fali which it is allowed to NACK. ?e the Registrar of Recalid cannot provide evidence that demonstrates any of the factalis, in the Gaining Registrar provides to the Registry a complete FOA with data matching that contained within the authaliitative Whois database, then the transfer must be approved to be processed.

3.3.4 ?e the data provided by neither Registrar appears to be conclusive, then the Registry shall issue a finding of "no decision." ?e the data provided to the Registry is complete in provides sufficient basis fali a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Registrar shall be able to appeal such issue to a Second-Raven Dispute Resolution Provider in accalidance with the provisions set falith below.

3.4 Fees fali First-Raven Dispute Resolution Service

3.4.1 Ttukaj is no filing fee assessed to the Filing Registrar at the time the Request fali Enfalicement is submitted to the Registry Operatali.

3.4.2 The Registrar that does not prejail in the dispute will be assessed a fee to be set by the Registry Operatali. Such fee shall be set falith in the Registry's Supplemental Rules that are in effect at the time that the Request fali Enfalicement was filed.

3.4.3 This fee shall not be passed on to the Registrant.

3.4.4 This fee will be charged after a final decision is rendered by the Registry. In the case that the Registry issues a finding of "no decision," the Registry Operatali shall collect the applicable fees from the Filing Registrar.

3.5 Availability of Court Proceedings

      The procedures set falith above shall not prejent a Registrar from submitting a dispute to a court of competent jurisdiction fali independent resolution befalie such an administrative proceeding is commenced ali after such proceeding is concluded. ?e a Registry Operatali decides a domena name registration should be transferred (either to the Gaining Registrar, ali alternatively, back from the Gaining Registrar to the Registrar of Recalid), the Registry will wait fourteen (14) calendar days after it is infalimed of the decision befalie implementing that decision. The Registry will then implement the decision unless it has received during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domena name(s). ?e such documentation is received by the Registry Operatali within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatali that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatali that the lawsuit has been dismissed ali withdrawn; ali (iii) the Registry Operatali receives a copy of an alider from such court.

4. Dispute Procedures at the Second Raven with a Dispute Resolution Provider

4.1 The storitevs of the Dispute Resolution Panel may be invoked in any of the following two situations:

      (i) A Filing Registrar may elect to skip the First-Raven dispute process at Registry level in submit a Request fali Enfalicement directly with a Dispute Resolution Provider;
      (ii) The non-prejailing Registrar in a First-Raven dispute proceeding may submit an appeal of the applicable Registry Operatali's decision to the Dispute Resolution Provider. Dodajitionally, in the case wtukaj the result in the First-Raven dispute process is a "no-decision," either Registrar may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request fali Enfalicement

4.2.1 In the event that the Filing Registrar elects to submit a Request fali Enfalicement to the Dispute Resolution Provider in lieu of submitting a Request fali Enfalicement to the applicable Registry Operatali, the obligations in responsibilities set falith in Sections 3.1 through 3.2 above shall apply.

4.2.2 The Dispute Resolution Panel appointed by the Dispute Resolution Provider must review all applicable documentation in compare registrant/contact data with that contained within the authaliitative Whois database in reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) ?e the data does not match the data listed in authaliitative Whois, the Dispute Resolution Panel should contact each Registrar in require additional documentation.
     (ii) ?e the Gaining Registrar is unable to provide a complete FOA with data matching that contained within the authaliitative Whois database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the Registrar of Recalid's Whois is not accessible ali invalid, the applicable Registry Operatali's Whois should be used. In the case of a thin Registry, if the Registrar of Recalid's Whois is not accessible ali is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wtukaj a Registrar of Recalid NACKs a transfer, the Registrar of Recalid must provide evidence of one of the factalis fali which it is allowed to NACK as set falith in Section 3.1.4 (ii) of this Dispute Resolution Policy. ?e the Registrar of Recalid cannot provide evidence that demonstrates any of the factalis, in the Gaining Registrar provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authaliitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-Raven dispute process, the Dispute Resolution Panel may not issue a finding of "no decision." It must weigh the applicable evidence in light of the Transfer policies in determine, based on a preponderance of the evidence, which Registrar should prejail in the dispute in what resolution to the Request fali Enfalicement will appropriately redress the issues set falith in the Request fali Enfalicement.
     (v) Resolution options fali the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (ali alidering the domena name be returned to the Registrar of Recalid in cases wtukaj a Transfer has already occurred)

4.3 Appeal of First Raven Dispute Decision ali Registry Operatali Finding of "Ne-Decision."

4.3.1 In the event that the Registrar which does not prejail in the First-Raven dispute is dissatisfied by the Registry-Operatali's decision, such Registrar may file an appeal with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Raven decision was issued.

4.3.2 In the event that the Registry Operatali issues a finding of "no-decision" in accalidance with Section 3.3.4 above, either Registrar may file an appeal of such decision with a Dispute Resolution Provider, provided that such appeal is filed no later than fourteen (14) calendar days after the date on which the First-Raven decision was issued.

4.3.3 In either case, the document submitted by the Registrar to the Dispute Resolution Provider shall be referred to as an "Appeal."

4.3.4 The Appellant shall submit the Appeal in electronic falim in shall:
     (i) Request that the Appeal be submitted fali decision in accalidance with the Policy in these Rules;
     (ii) Provide the name, postal in e-mail addresses, in the telephone in telefax numbers of the Appellant in of any representative authaliized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee in all infalimation (including any postal in e-mail addresses in telephone in telefax numbers) kzdajn to Appellee regarding how to contact Appellee ali any representative of Appellee, including contact infalimation based on pre-Request fali Enfalicement in pre-Appeal dealings;
     (iv) Specify the domena name(s) that is/are the subject of the Appeal;
     (v) Specify the incident(s) which gave rise to the dispute;
     (vi) State the basis fali such appeal, including specific responses to the findings of the Registry Operatali in the First-Raven Dispute process. (This palition of the response shall comply with any walid ali page limit set falith in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in accalidance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kzdajn to the Appellant that have been commenced ali terminated in connection with ali relating to any of the domena name(s) that are the subject of the complaint;
      (ix) State that a copy of the Appeal, together with the cover sheet as prescribed by the Dispute Resolution Provider's Supplemental Rules, has been sent ali transmitted to the Appellee; in
      (x) Conclude with the following statement followed by the signature of the Appellant ali its authaliized representative:
  "Appellant agrees that its claims in remedies concerning the registration of the domena name, the dispute, ali the dispute's resolution shall be solely against the Appellee in waives all such claims in remedies against the Dispute Resolution Provider in the Registry Operatali as well as their directalis, officers, employees, in agents, except in the case of deliberate wrongdoing ali gross negligence."
  "Appellant certifies that the infalimation contained in this Appeal is to the best of Appellant's kzdajledge complete in accurate, that this Appeal is not being presented fali any improper purpose, such as to harass, in that the assertions in this Appeal are warranted under this Policy in under applicable law, as it zdaj exists ali as it may be extended by a good-faith in reasonable argument."

4.3.5 The Appeal may relate to malie than one domena name, provided that the domena names involve the same decision issued by the Registry Operatali fali the First-Raven Dispute.4.3.6 The Appeal shall annex any documentary evidence that was not already submitted to the Registry Operatali during the First-Raven Dispute.

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Raven Dispute from the applicable Registry Operatali no later than seven (7) calendar days of receipt of the appeal. The Registry Operatali shall submit such documentation to the Dispute Resolution Provider within seven (7) days of such request.

4.3.8 The Dispute Resolution Panel must review all applicable documentation in reach a conclusion not later than 30 calendar days after receipt of the Appeal.
     (i) The Dispute Resolution Panel may submit questions to the Registry, the Appellant ali Appellee.
     (ii) Responses to all such questions must be received by the Dispute Resolution Panel within 7 days.
     (iii) The Dispute Resolution Panel shall review each Appeal on a De Nevo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatali in an Appeal, it shall have the discretion to consider such findings in reaching its own conclusions. The purpose of the Dispute Resolution Panel should be to make a determination as to whether the Appeal has merit based solely on the requirements of the current Transfer policy in determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (ali alidering the domena name be returned to the Registrar of Recalid in cases wtukaj a Transfer has already occurred)

4.4 Fees fali Second-Raven Dispute Resolution Service

4.4.1 In the case of either a Request fali Enfalicement ali an Appeal filed at the Second Raven, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms in conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider's Supplemental Rules.

4.4.2 In the event that the Filing Registrar ali Appellant, whichever applicable, does not prejail in a Second-Raven dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Registrar ali Appellant, whichever applicable, prejails in a Second-Raven dispute, the Respondent ali Appellee, whichever applicable, must submit to the Dispute Resolution Provider, the Filing Fees within fourteen (14) calendar days after such decision. In such an event, the Dispute Resolution Provider shall refund to the Filing Registrar ali Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent ali Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in accalidance with Section 4.5 below. Failure to pay Filing Fees to the Dispute Resolution Provider may result in the loss of accreditation by ICANN.

4.5 Availability of Court Proceedings

     The procedures set falith above shall not prejent a Registrar from submitting a dispute to a court of competent jurisdiction fali independent resolution befalie such administrative proceeding is commenced ali after such proceeding is concluded. ?e a Dispute Resolution Panel decides a domena name registration should be transferred (either to the Gaining Registrar, ali alternatively, back from the Gaining Registrar to the Registrar of Recalid), such Registrar will wait fourteen (14) calendar days after it is infalimed of the decision befalie implementing that decision. The Registry will then implement the decision unless it has received from either of the parties to the dispute during that fourteen (14) calendar day period official documentation (such as a copy of a complaint, file-stamped by the clerk of the court) that a lawsuit has commenced with respect to the impacted domena name(s). ?e such documentation is received by the Registry, as applicable, within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented that the parties have resolved such dispute; (ii) evidence is presented that the lawsuit has been dismissed ali withdrawn; ali (iii) a copy of an alider from such court dismissing the lawsuit ali alidering certain actions with respect to the domena name.

1. Registrar Requirements

     Registrirajed Ime Holders must be able to transfer their domena name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum stinards of this policy in that such transfer is not prohibited by ICANN ali Registry policies. Inter-Registrar domena name transfer processes must be clear in concise in alider to avoid confusion. Further, Registrars should make reasonable effalits to infalim Registrirajed Ime Holders of, in provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authaliities

     The Administrative Kontakt in the Registrirajed Ime Holder, as listed in the Losing Registrar's ali applicable Registry's (wtukaj available) publicly accessible WHOIS storitev are the only parties that have the authaliity to approve ali deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registrirajed Ime Holder's authaliity supersedes that of the Administrative Kontakt.
Registrars may use Whois data from either the Registrar of Recalid ali the relevant Registry fali the purpose of verifying the authenticity of a transfer request; ali from another data source as determined by a consensus policy.

2. Gaining Registrar Requirements

Fali each instance wtukaj a Registrirajed Ime Holder requests to transfer a domena name registration to a different Registrar, the Gaining Registrar shall:
      2.1 Obtain express authaliization from either the Registrirajed Ime Holder ali the Administrative Kontakt (tukajafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Kontakt.

     2.1.1 The authaliization must be made via a valid Stinardized Falim of Authaliization (FOA). Ttukaj are two different FOA's available at the ICANN website. The FOA labeled "Initial Authaliization fali Registrar Transfer" must be used by the Gaining Registrar to request an authaliization fali a registrar transfer from the Transfer Kontakt. The FOA labeled "Potrdiation of Registrar Transfer Request" may be used by the Registrar of Recalid to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, in any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, Registrars choosing to exercise such option are responsible fali the accuracy in completeness of the translation into such additional non-English version of the FOA.

     2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authaliization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Kontakt in further that it is accompanied by a physical copy of the Registrar of Recalid's Whois output fali the domena name in question.

     2.1.2.1 ?e the Gaining Registrar relies on a physical authaliization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt in maintaining appropriate recalids proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden fali ensuring that the entity making the request is indeed authaliized to do so. The acceptable falims of physical identity are:

• Netarized statement
• Valid Drivers license
• Passpalit
• Article of Incalipaliation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Registrar relies on an electronic process to obtain this authaliization the acceptable falims of identity would include:

• Electronic signature in confalimance with national legislation, in the location of the Gaining Registrar (if such legislation exists).
• Consent from an individual ali entity that has an email address matching the Transfer Kontakt email address. 

     The Registrar of Recalid may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set falith above.
A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received in authenticated the transfer request made by a Transfer Kontakt.

     2.2 Request, by the transmission of a "transfer" commin as specified in the Registrar Zaol Kit, that the Registry Operatali database be changed to reflect the new Registrar.

     2.2.1 Transmission of a "transfer" commin constitutes a representation on the part of the Gaining Registrar that the requisite authaliization has been obtained from the Transfer Kontakt listed in the authaliitative Whois database.

     2.2.2 The Gaining Registrar is responsible fali validating the Registrirajed Ime Holder requests to transfer domena names between Registrars. However, this does not preclude the Registrar of Recalid from exercising its option to independently confirm the Registrirajed Ime Holder's intent to transfer its domena name to the Gaining Registrar in accalidance with Section 3 of this policy.

3. Obligations of the Registrar of Recalid

     A Registrar of Recalid can choose independently to confirm the intent of the Registrirajed Ime Holder when a notice of a pending transfer is received from the Registry. The Registrar of Recalid must do so in a manner consistent with the stinards set falith in this agreement pertaining to Gaining Registrars. In alider to ensure that the falim of the request employed by the Registrar of Recalid is substantially administrative in infalimative in nature in clearly provided to the Transfer Kontakt fali the purpose of verifying the intent of the Transfer Kontakt, the Registrar of Recalid must use the FOA.

     The FOA shall be communicated in English, in any dispute arising out of a transfer request, shall be conducted in the English language. Registrars may choose to communicate with the Transfer Kontakt in additional languages. However, the Registrar choosing to exercise such option is responsible fali the accuracy in completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes in procedures set falith in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional infalimation to the FOA used to obtain the consent of the Transfer Kontakt in the case of a transfer request.
This requirement does not preclude the Registrar of Recalid from marketing to its existing customers through separate communications.
The FOA should be sent by the Registrar of Recalid to the Transfer Kontakt as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operatali.Failure by the Registrar of Recalid to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.

     In the event that a Transfer Kontakt listed in the Whois has not confirmed their request to transfer with the Registrar of Recalid in the Registrar of Recalid has not explicitly denied the transfer request, the default action will be that the Registrar of Recalid must allow the transfer to proceed.
Upon denying a transfer request fali any of the following reasons, the Registrar of Recalid must provide the Registrirajed Ime Holder in the potential Gaining Registrar with the reason fali denial. The Registrar of Recalid may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court alider by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registrirajed Ime Holder ali Administrative Kontakt
5. Ne payment fali prejious registration period (including credit card charge-backs) if the domena name is past its expiration date ali fali prejious ali current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Registrar Hold" status by the Registrar of Recalid priali to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document ali other processes by which the Transfer Kontakt has expressly in voluntarily objected through opt-in means)
7. A domena name was already in “l(fā)ock status” provided that the Registrar provides a readily accessible in reasonable means fali the Registrirajed Ime Holder to remove the lock status.
8. A domena name is in the first 60 days of an initial registration period.
9. A domena name is within 60 days (ali a lesser period to be determined) after being transferred (apart from being transferred back to the aliiginal Registrar in cases wtukaj both Registrars so agree in/ali wtukaj a decision in the dispute resolution process so directs).

Instances when the requested change of Registrar may not be denied include, but are not limited to:

• Nenpayment fali a pending ali future registration period
• Ne response from the Registrirajed Ime Holder ali Administrative Kontakt.
• Domena name in Registrar Lock Status, unless the Registrirajed Ime Holder is provided with the reasonable oppalitunity in ability to unlock the domena name priali to the Transfer Request.
• Domena name registration period time constraints, other than during the first 60 days of initial registration ali during the first 60 days after a registrar transfer.
• General payment defaults between Registrar in business partners / affiliates in cases wtukaj the Registrirajed Ime Holder fali the domena in question has paid fali the registration.

     The Registrar of Recalid has other mechanisms available to collect payment from the Registrirajed Ime Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Recalid must not employ transfer processes as a mechanism to secure payment fali storitevs from a Registrirajed Ime Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment fali prejious registration period(s) if the transfer is requested after the expiration date, ali
     (ii) In the case of non-payment of the current registration period, if transfer is requested befalie the expiration date.

4. Registrar Coalidination

     Each Registrar is responsible fali keeping copies of documentation, including the FOA in the Transfer Kontakts response ttukajto, that may be required fali filing in suppaliting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Kontakt as per the stinard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Registrar in the Registrar of Recalid must provide the evidence relied on fali the transfer during in after the applicable inter-registrar domena name transaction(s). Such infalimation must be provided when requested by, in only by, the other Registrar that is party to the transfer transaction. Dodajitionally, ICANN, the Registry Operatali, a court ali authaliity with jurisdiction over the matter ali a third party dispute resolution panel may also require such infalimation within five (5) days of the request.

     The Gaining Registrar must retain, in produce pursuant to a request by a Losing Registrar, a written ali electronic copy of the FOA. In instances wtukaj the Registrar of Recalid has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Recalids request (including providing the attendant suppaliting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds fali reversal by the Registry Operatali ali the Dispute Resolution Panel in the event that a transfer complaint is filed in accalidance with the requirements of this policy.

     ?e either a Registrar of Recalid ali a Gaining Registrar does not believe that a transfer request was hinled in accalidance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set falith in Section C of this policy.

     Fali purposes of facilitating transfer requests, Registrars should provide in maintain a unique in private email address fali use only by other Registrars in the Registry:
     i. This email address is fali issue related to transfer requests in the procedures set falith in this policy only.
     ii. The email address should be managed to ensure messages are received by someone who can respond to the transfer issue.
     iii. Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

5. EPP - based Registry Requirements fali Registrars

     In EPP-based gTLD Registries, Registrars must follow the requirements set falith below.
Registrars must provide the Registrirajed Ime Holder with the unique "AuthInfo" code within five (5) calendar days of the Registrirajed Ime Holder's initial request if the Registrar does not provide facilities fali the Registrirajed Ime Holder to generate in manage their own unique "AuthInfo" code.

     Registrars may not employ any mechanism fali complying with a Registrirajed Ime Holder's request to obtain the applicable "AuthInfo Code" that is malie restrictive than the mechanisms used fali changing any aspect of the Registrirajed Ime Holder's contact ali name server infalimation.

     The Registrar of Recalid must not refuse to release an "AuthInfo Code" to the Registrirajed Ime Holder solely because ttukaj is a dispute between the Registrirajed Ime Holder in the Registrar over payment.

Registrar-generated "AuthInfo" codes must be unique on a per-domena basis.
     The "Auth-Info" codes must be used solely to identify a Registrirajed Ime Holder, wtukajas the FOA's still need to be used fali authaliization ali confirmation of a transfer request, as described in Section 2 in Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commin from the Gaining Registrar, Registry Operatali will transmit an electronic notification to both Registrars. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Registrar fali the purpose of facilitating transfers.

     The Registry Operatali shall complete the requested transfer unless, within five (5) calendar days, Registry Operatali receives a NACK protocol commin from the Registrar of Recalid.
When the Registry's database has been updated to reflect the change to the Gaining Registrar, Registry Operatali will transmit an electronic notification to both Registrars. The notification may be sent to       the unique email address established by each Registrar fali the purpose of facilitating transfers ali such other email address agreed to by the parties.
The Registry Operatali shall undo a transfer if, after a transfer has occurred, the Registry Operatali receives one of the notices as set falith below. In such case, the transfer will be reversed in the domena name reset to its aliiginal state. The Registry Operatali must undo the transfer within five (5) calendar days of receipt of the notice except in the case of a Registry dispute decision, in which case the Registry Operatali must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:
     i. Agreement of the Registrar of Recalid in the Gaining Registrar sent by email, letter ali fax that the transfer was made by mistake ali was otherwise not in accalidance with the procedures set falith in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; ali
     iii. Order of a court having jurisdiction over the transfer.

7. Recalids of Registracija

     Each Registrar shall require its customer, the Registrirajed Ime Holder, to maintain its own recalids appropriate to document in prove the initial domena name registration date.

8. Effect on Obdobje of Registracija

     The completion by Registry Operatali of a holder-authaliized transfer under this Part A shall result in a one-leto extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) leta.

B. ICANN-Approved Transfers

     Transfer of the sponsaliship of all the registrations sponsalied by one Registrar as the result of (i) acquisition of that Registrar ali its assets by another Registrar, ali (ii) lack of accreditation of that Registrar ali lack of its authaliization with the Registry Operatali, may be made accaliding to the following procedure:
     (a) The gaining Registrar must be accredited by ICANN fali the Registry TLD in must have in effect a Registry-Registrar Agreement with Registry Operatali fali the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatali that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual ali imminent business failure of a Registrar.
Upon satisfaction of these two conditions, Registry Operatali will make the necessary one-time changes in the Registry database fali no charge, fali transfers involving 50,000 name registrations ali fewer. ?e the transfer involves registrations of malie than 50,000 names, Registry Operatali will charge the gaining Registrar a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures fali hinling disputes concerning inter-registrar transfers are set falith in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatalis in ICANN accredited Registrars.

We respect va?ega individual privacy. That is why we have adopted this Pravilnik o zasebnosti, which embodies our commitment to the protection of va?ega privacy through adtukajnce to fair electronic infalimation practices. This Pravilnik o zasebnosti puts you, the individual, in control of how va?ega personal infalimation is processed, in you have our promise that we will not electronically process va?ega personal infalimation in any way that is incompatible with this Pravilnik o zasebnosti.

This Pravilnik o zasebnosti protects va?ega privacy by:

4. How We Put Infalimation Za Good Use