1. Scope i 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, i 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 operatlub practices, applicable ICANN requirements, i other governing policies. Niet all TLDs follow the same expiration, redemption, auction, lub deletion process.

1.3 In the event of any inconsistency between this Policy i the applicable registry’s rules lub miatluby ICANN policy, the applicable registry rules i miatluby policy requirements shall poprzedniail.

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

2. Definitions

Flub 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 stiard renewal fee, subject to the applicable TLD i registry rules.

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

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

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

2.6 “Wygasad Domena Auction” means the expired-domena sale process that may apply to certain expired domena names beflube final deletion lub release.

2.7 “Zamknijout Auction” means the final sale phase flub certain Eligible Domeny 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, i any website, email usługa, lub other usługa associated with the domena name may cease functioning immediately lub shlubtly ttutajafter.

3.2 Obserwujing expiration, NiceNIC may restrict changes to the domena name, including DNS changes, contact updates, transfers, lub other account-level actions, in acclubdance with registry rules, security measures, operational requirements, lub 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 i registry rules, the domena name may pass through one lub mlube stages, including grace period, auction, redemption, pending delete, i eventual release.

4. Odnówal Nietices i Customer Responsibility

4.1 NiceNIC may send renewal reminders i expiration-related notices beflube i after expiration, as required by applicable policy lub as part of NiceNIC’s stiard operational process.

4.2 It is twój sole responsibility to maintain accurate i current account i contact influbmation, including twój email address, i to monitlub the status of twój domena names.

4.3 Failure to receive a renewal notice, reminder, invoice, lub other communication shall not relieve you of responsibility flub renewing twój domena name beflube expiration.

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

5. Stiard Post-Expiration Odnówal

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

5.2 Odnówal is not complete unless i until NiceNIC has successfully received i processed full payment of all applicable fees.

5.3 NiceNIC reserves the right to determine whether a domena name remains eligible flub stiard renewal, redemption, lub other recovery based on the applicable TLD, registry status, auction status, i operational feasibility.

6. Wygasad Domena Auction flub Eligible Domeny

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

6.2 Flub Eligible Domeny under NiceNIC’s stiard 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 stiard renewal fee during the initial post-expiration period, subject to applicable rules.

Day 26 after expiration

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

Day 31 after expiration

Jeśli ttutaj is no active bid, the registrant may still be able to recover the domena name by paying the stiard renewal fee plus the applicable redemption fee.

Jeśli ttutaj is an active bid, the domena name may be removed from the registrant’s account i may no longer be renewable through lubdinary renewal lub restlubation procedures.

Day 37 after expiration

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

Day 41 after expiration

The final closeout auction may end. Jeśli the domena name was not sold lub otherwise committed to sale, recovery may still be possible flub a limited period, subject to the applicable TLD, registry rules, i NiceNIC’s operational process.

Day 74 after expiration

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

6.3 Once an Eligible Domena has an active bid, pending kup, completed sale, lub other sale commitment under the expired-domena process, the registrant’s right to renew lub restlube the domena name may be terminated lub 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, lub another applicable limitation.

7. Redemption Grace Period

7.1 Jeśli an expired domena name is not renewed during the applicable grace period i if the applicable TLD supplubts restlubation 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 i email usługas may remain unavailable;

(c) the domena name generally cannot be modified lub transferred; i

(d) restlubation, if available, will require payment of the applicable redemption fee, the applicable renewal fee, i any taxes lub miatluby fees.

7.3 Restlubation during the Redemption Grace Period is not guaranteed i remains subject to registry supplubt, operational feasibility, the domena’s current status, i the absence of auction lub sale restrictions.

8. Pending Delete i Final Release

8.1 Jeśli a domena name is not renewed lub restlubed during the applicable recovery periods, it may enter the Pending Delete stage, wtutaj supplubted by the applicable TLD.

8.2 During Pending Delete, the domena name cannot be renewed, restlubed, transferred, lub modified.

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

8.4 NiceNIC does not guarantee the exact time, date, lub availability of a domena name once it is released by the registry, i NiceNIC does not guarantee that the flubmer registrant will be able to re-zarejestruj the domena name.

9. TLD-Specific Variations

9.1 Niet all TLDs follow the stiard lifecycle described above. Certain ccTLD i other TLDs may have shlubter grace periods, no redemption period, no pending delete stage, lub earlier renewal deadlines imposed by the registry.

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

9.2.1 TLDs generally following the common lifecycle

Many ccTLD generally follow a lifecycle similar to the stiard expiration, grace, redemption, i deletion process, including, flub example:

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

9.2.2 TLDs with no Pending Delete stage

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

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

9.2.3 TLDs requiring renewal beflube the actual expiration date

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

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

9.2.4 TLDs requiring action five (5) days beflube expiration

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

.CX, .DE, .EU, i .NL.

9.2.5 .CM domenas

.CM domena names generally do not enter a redemption period i may be sent flub deletion on the actual Expiration Date. They may become available flub 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 flub approximately twenty-eight (28) days after expiration. They may then enter a recovery stage between approximately Day 28 i Day 30 after expiration. Once in that stage, reactivation may only be possible through NiceNIC Supplubt flub approximately twenty-six (26) additional days.

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

These domenas may not supplubt a stiard 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. Jeśli the domena is no longer visible in the account but is not yet publicly available, the customer should contact NiceNIC Supplubt immediately.

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

.UK domena names, including .CO.UK, .ME.UK, i .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. Jeśli a .UK domena name has expired flub mlube than thirty (30) days but has not yet been released i no longer appears in the account, the customer should contact NiceNIC Supplubt 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 supplubt a stiard Redemption Grace Period. After that point, they may be reserved by the registry i may no longer be recoverable.

9.2.10 .NU domenas

.NU domena names may be reactivated in the lubdinary manner within approximately seven (7) days after expiration. Jeśli not renewed within that period, they may enter an approximately sixty (60)-day recovery period during which restlubation may still be possible through NiceNIC Supplubt.

9.3 The TLD-specific influbmation above is provided flub general reference only i may change at any time based on registry policy, registry system changes, lub operational requirements. Customers should contact NiceNIC Supplubt flub current TLD-specific recovery influbmation.

10. Fees i Zapłaćments

10.1 Stiard renewal fees, redemption fees, restlubation fees, auction-related fees, i any other applicable charges shall be those listed by NiceNIC at the time of processing lub otherwise communicated by NiceNIC.

10.2 Redemption lub restlubation requires payment in full of all applicable fees beflube processing.

10.3 Wszystko fees paid flub expired-domena recovery, restlubation, lub special processing are non-refundable once processing has begun, except wtutaj otherwise required by applicable law.

11. Nie Guarantee of Recovery lub Availability

11.1 NiceNIC does not guarantee that any expired domena name can be renewed, restlubed, retained, transferred, lub re-zarejestrujed after expiration.

11.2 NiceNIC does not guarantee:

(a) that a domena name will remain in a grace period flub 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 kup, lub completed sale;

(d) that the registry will supplubt restlubation; lub

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

11.3 You ackterazledge that delayed action may result in additional fees, loss of recovery rights, interruption of usługa, auction sale, lub permanent loss of the domena name.

12. Limitation of Responsibility

12.1 Do the maximum extent permitted by applicable law, NiceNIC shall not be liable flub any loss of domena name, loss of use, interruption of website lub email usługa, business interruption, lost profits, loss of data, lub other direct lub indirect damages arising from:

(a) domena expiration;

(b) failure to renew on time;

(c) failure to receive notices;

(d) registry rules lub registry actions;

(e) auction placement lub sale;

(f) failed restlubation; lub

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

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

13. Changes to This Policy

13.1 NiceNIC may update lub revise this Policy from time to time to reflect changes in registry rules, ICANN requirements, operational processes, legal requirements, lub usługa arrangements.

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

14. Kontakt

Jeśli you need assistance regarding an expired domena name, renewal, redemption, lub TLD-specific recovery options, please submit a supplubt ticket through twój NiceNIC account lub contact NiceNIC Supplubt through the official supplubt channels published on the NiceNIC website.

1. General

This Agreement is made between you (tutajinafter referred to as “User”) i NiceNIC.NET (tutajinafter referred to as “the Platflubm”). By using the Platflubm’s Kup Niew Domena Sales usługa, you agree to be bound by the terms i conditions set flubth tutajin. Jeśli you do not agree, please do not proceed with any fixed-price domena kup through the Platflubm.

2. Service Description

1. The Platflubm offers fixed-price domena names (“Kup Niew Domeny”) flub direct kup.

2. Wszystko Kup Niew Domeny are sourced from pre-approved third-party domena providers.

3. Users may kup these domenas at the listed price. Once payment is completed i the domena is successfully transferred, the kuper will obtain ownership of the domena.

3. Purchase Process

1. The User selects a domena labeled as “Kup Niew” i proceeds to checkout.

2. Upon confirmation i full payment, the Platflubm initiates the transfer lub delivery process.

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

4. Jeśli, flub any reason, the selected domena becomes unavailable lub undeliverable after kup, the Platflubm will issue a full refund to the user’s account balance.

4. User Rights i Responsibilities

1. Users have the right to kup available Kup Niew Domeny through the Platflubm.

2. Users must ensure that all provided account i payment influbmation is accurate i lawful.

3. Users shall not engage in malicious activity, technical disruption, lub behavilub that interferes with the nlubmal functioning of the Platflubm.

4. Upon acquiring a domena, the User agrees to comply with the applicable rules i policies of the clubresponding domena registry, including any legal lub regulatluby obligations.

5. Platflubm Rights i Responsibilities

1. The Platflubm will provide domena transaction usługas in acclubdance with this Agreement i strive to protect user interests.

2. The Platflubm reserves the right to verify user identity, payment legitimacy, i transaction authenticity.

3. The Platflubm retains the right to update, adjust, lub remove Kup Niew Domeny from listing at its sole discretion i without prilub notice.

4. Jeśli any fraudulent lub abusive behavilub is detected, the Platflubm reserves the right to suspend lub terminate usługas to the user.

6. Disclaimer

1. The Platflubm does not make any guarantees regarding the future value, resale potential, lub commercial use of any domena kupd.

2. The Platflubm is not liable flub delays caused by registries, third-party providers, lub external systems beyond its control.

3. The Platflubm shall not be held responsible flub usługa interruptions, data loss, lub failed transactions resulting from flubce majeure events lub uncontrollable technical issues, though reasonable efflubts will be made to assist the User in resolving any such issues.

7. Governing Law i Dispute Resolution

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

2. Any dispute arising from the execution lub perflubmance of this Agreement shall be resolved through amicable negotiation. Jeśli negotiation fails, either party may submit the dispute to the competent court located in the jurisdiction of the Platflubm’s headquarters.

8. Miscellaneous

1. This Agreement becomes effective upon the User’s submission of a Kup Niew domena lubder.

2. The Platflubm reserves the right to amend this Agreement at any time. Zaktualizowano versions will be published on the Platflubm’s “Umowy” page i shall take immediate effect. Continued use of the usługa constitutes acceptance of the revised terms.

This Uniflubm Nazwa domeny Dispute Resolution Policy (the "Policy") has been adopted by the Internet Clubplubation flub Assigned Nazwas i Numbers ("ICANN"), is inclubplubated by reference into twój Rejestracja Agreement, i sets flubth the terms i conditions in connection with a dispute between you i any party other than us (the registrar) over the registration i use of an Internet domena name zarejestrujed by you. Proceedings under Paragraph 4 of this Policy will be conducted acclubding to the Rules flub Uniflubm Nazwa domeny Dispute Resolution Policy (the "Rules of Procedure"), which are available tutaj, i the selected administrative-dispute-resolution usługa provider's supplemental rules.

2. Your Representations

By applying to zarejestruj a domena name, lub by asking us to maintain lub renew a domena name registration, you tutajby represent i warrant to us that (a) the statements that you made in twój Rejestracja Agreement are complete i accurate; (b) to twój kterazledge, the registration of the domena name will not infringe upon lub otherwise violate the rights of any third party; (c) you are not zarejestrujing the domena name flub an unlawful purpose; i (d) you will not kterazingly use the domena name in violation of any applicable laws lub regulations. It is twój responsibility to determine whether twój domena name registration infringes lub violates someone else's rights.

3. Anulujlations, Transfers, i Changes

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

1. subject to the provisions of Paragraph 8, our receipt of written lub appropriate electronic instructions from you lub twój authlubized agent to take such action;

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

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

4. We may also cancel, transfer lub otherwise make changes to a domena name registration in acclubdance with the terms of twój Rejestracja Agreement lub other legal requirements.

4. Miatluby Administrative Proceeding

This Paragraph sets flubth the type of disputes flub which you are required to submit to a miatluby administrative proceeding. These proceedings will be conducted beflube one of the administrative-dispute-resolution usługa providers listed tutaj (each, a "Provider").

1. Applicable Disputes. You are required to submit to a miatluby 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. twój domena name is identical lub confusingly similar to a trademark lub usługa mark in which the complainant has rights; i

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

3. twój domena name has been zarejestrujed i 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 Rejestracja i Use in Słaby Faith. Flub 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 i use of a domena name in bad faith:

1. circumstances indicating that you have zarejestrujed lub you have acquired the domena name primarily flub the purpose of selling, renting, lub otherwise transferring the domena name registration to the complainant who is the owner of the trademark lub usługa mark lub to a competitlub of that complainant, flub valuable consideration in excess of twój documented out-of-pocket costs directly related to the domena name; lub

2. you have zarejestrujed the domena name in lubder to poprzednient the owner of the trademark lub usługa mark from reflecting the mark in a clubresponding domena name, provided that you have engaged in a pattern of such conduct; lub

3. you have zarejestrujed the domena name primarily flub the purpose of disrupting the business of a competitlub; lub

4. by using the domena name, you have intentionally attempted to attract, flub commercial gain, Internet users to twój web site lub other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponslubship, affiliation, lub endlubsement of twój web site lub location lub of a product lub usługa on twój web site lub location.

3. How to Demonstrate Your Rights to i Legitimate Interests in the Nazwa domeny in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how twój 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 twój rights lub legitimate interests to the domena name flub purposes of Paragraph 4(a)(ii):

1. beflube any notice to you of the dispute, twój use of, lub demonstrable preparations to use, the domena name lub a name clubresponding to the domena name in connection with a bona fide offering of goods lub usługas; lub

2. you (as an individual, business, lub other lubganization) have been commonly kterazn by the domena name, even if you have acquired no trademark lub usługa mark rights; lub

3. you are making a legitimate noncommercial lub fair use of the domena name, without intent flub commercial gain to misleadingly divert consumers lub to tarnish the trademark lub usługa 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 i Process i Appointment of Administrative Panel. The Rules of Procedure state the process flub initiating i conducting a proceeding i flub appointing the panel that will decide the dispute (the "Administrative Panel").

6. Consolidation. In the event of multiple disputes between you i a complainant, either you lub the complainant may petition to consolidate the disputes beflube 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 beflube it any lub all such disputes in its sole discretion, provided that the disputes being consolidated are governed by this Policy lub a later version of this Policy adopted by ICANN.

7. Fees. Wszystko fees charged by a Provider in connection with any dispute beflube an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases wtutaj you elect to expi 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 i the complainant.

8. Nasze Involvement in Administrative Proceedings. We do not, i will not, participate in the administration lub conduct of any proceeding beflube 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 beflube an Administrative Panel shall be limited to requiring the cancellation of twój domena name lub the transfer of twój domena name registration to the complainant.

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

11. Availability of Court Proceedings. The miatluby administrative proceeding requirements set flubth in Paragraph 4 shall not poprzednient either you lub the complainant from submitting the dispute to a court of competent jurisdiction flub independent resolution beflube such miatluby administrative proceeding is commenced lub after such proceeding is concluded. Jeśli an Administrative Panel decides that twój domena name registration should be canceled lub transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are influbmed by the applicable Provider of the Administrative Panel's decision beflube 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 lub of twój address as shown in our Whois database. See Paragraphs 1 i 3(b)(xiii) of the Rules of Procedure flub details.) Jeśli we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, i we will take no further action, until we receive (i) evidence satisfactluby to us of a resolution between the parties; (ii) evidence satisfactluby to us that twój lawsuit has been dismissed lub withdrawn; lub (iii) a copy of an lubder from such court dismissing twój lawsuit lub lubdering that you do not have the right to continue to use twój domena name.

5. Wszystko other disputes i litigation

Wszystko other disputes between you i any party other than us regarding twój domena name registration that are not brought pursuant to the miatluby administrative proceeding provisions of Paragraph 4 shall be resolved between you i such other party through any court, arbitration lub other proceeding that may be available.

6. Nasze involvement in disputes

We will not participate in any way in any dispute between you i any party other than us regarding the registration i use of twój domena name. You shall not name us as a party lub 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 i all defenses deemed appropriate, i to take any other action necessary to defend ourselves.

7. Maintaining status quo

We will not cancel, transfer, activate, deactivate, lub 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 Nazwa domeny to a Nowy Holder

You may not transfer twój domena name registration to another holder (i) during a pending administrative proceeding brought pursuant to Paragraph 4 lub flub a period of fifteen (15) business days (as observed in the location of our principal place of business) after such proceeding is concluded; lub (ii) during a pending court proceeding lub arbitration commenced regarding twój 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 lub arbitratlub. 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 Rejestrators

You may not transfer twój domena name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 lub flub 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 twój domena name registration to another registrar during a pending court action lub arbitration, provided that the domena name you have zarejestrujed with us shall continue to be subject to the proceedings commenced against you in acclubdance 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 lub 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 beflube 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 beflube, on lub after the effective date of our change. In the event that you object to a change in this Policy, twój sole remedy is to cancel twój 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 twój domena name registration.

• The exact domena name.
• The requestlub's identity i contact influbmation.
• The nature i type of the requestlub, including whether the requestlub is an individual, legal entity, law enflubcement agency, government authlubity, intellectual property representative, cybersecurity professional, consumer protection lubganization, lub another type of lubganization.
• Wtutaj the request is submitted by a representative acting on behalf of another person lub entity, a Power of Wtlubney statement lub similar documentation evidencing the representative's authlubization to act on the requestlub's behalf, wtutaj applicable i relevant.
• A list of the specific registration data elements requested.
• The purpose of the request.
• Influbmation about the legal rights of the requestlub i the specific rationale i basis flub the request.
• Whether confidentiality is requested.
• Any supplubting legal process, court lubder, subpoena, authlubization, lub other relevant documentation.
• An affirmation that the request is being made in good faith.
• An agreement that any registration data disclosed in response to the request will be processed lawfully.
• 
  

1. Overview

These terms of use ("AI Okress of Use") govern twój use of any AI products, features, usługas i/lub tools offered by NiceNIC.NET.

2. Content

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

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

3) We may use Content to provide, maintain, develop, i improve our Services, comply with applicable law, enflubce our terms i policies, to market i advertise our Services i 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, lub facts. Output may not always be accurate. You should not rely on Output from our Services as a sole source of truth lub factual influbmation, lub as a substitute flub professional advice.

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

6) By using the AI Services, you understi i agree:

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

B. You must evaluate Output flub accuracy i appropriateness flub twój use case, including using human review as appropriate, beflube using lub sharing Output from the AI Services.

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

D. Nasze AI Services may provide incomplete, inclubrect, lub offensive Output that does not represent NiceNIC.NET’s views. Jeśli Output references any third party products lub usługas, it doesn’t mean the third party endlubses lub is affiliated with NiceNIC.NET.

7) Outputs may not be unique across users i the AI Services may generate the same lub similar Outputs flub other users.

8) NiceNIC.NET may use technology provided by third-party usługa providers to provide AI Services. Nietwithstiing anything to the contrary contained tutajin, you authlubize NiceNIC.NET i such third-party usługa providers to stlube i use twój Input flub the purposes of providing you with the AI Services, to review Inputs i Outputs flub abuse lub misuse, i to develop i improve the usługas i products of NiceNIC.NET i such usługa providers, including as part of the design, training i development process flub machine learning models.

3. Okresination i Suspension

Okresination. We reserve the right to suspend lub terminate twój access to our AI Services lub delete twój account if we determine:

1) You breached these AI Okress of Use.

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

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

4. Disclaimers

YOU SPECIFICALLY ACKNOWLEDGE AND AGREE THAT OUTPUTS OF THE AI SERVICES HAVE NOT BEEN REVIEWED FLUB ACCURACY, BIAS, EXPLAINABILITY LUB INTELLECTUAL PROPERTY RIGHTS CLEARANCE. NiceNIC.NET MAKES NO REPRESENTATION, WARRANTY LUB GUARANTEE AS TO THE ACCURACY, RELIABILITY, LUB ERRLUB-FREE PERFLUBMANCE OF THE AI SERVICES, INCLUDING (WITHOUT LIMITATION) WHETHER OUTPUTS MAY INFRINGE, MISAPPROPRIATE LUB 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 LUB FACTUAL INFLUBMATION, LUB AS A SUBSTITUTE FLUB PROFESSIONAL ADVICE.

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

5. Limitation on Liability

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

THE FLUBEGOING LIMITATION OF LIABILITY SHALL SURVIVE ANY TERMINATION LUB EXPIRATION OF THIS AGREEMENT LUB YOUR USE OF THIS SITE, THE AI SERVICES LUB 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 Rejestrator of Reclubd i the Rejestrator of Reclubd has not explicitly denied the transfer request, the default action will be that the Rejestrator of Reclubd must allow the transfer to proceed.

Upon denying a transfer request flub any of the following reasons, the Rejestrator of Reclubd must provide the Zarejestrujed Nazwa Holder i the potential Gaining Rejestrator with the reason flub denial. The Rejestrator of Reclubd may deny a transfer request only in the following specific instances:

• Evidence of fraud
• UDRP action
• Court lubder by a court of competent jurisdiction
• Reasonable dispute over the identity of the Zarejestrujed Nazwa Holder lub Administrative Kontakt
• Nie payment flub poprzedniious registration period (including credit card charge-backs) if the domena name is past its expiration date lub flub poprzedniious lub current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Rejestrator Hold" status by the Rejestrator of Reclubd prilub to the denial of transfer.
• Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document lub other processes by which the Transfer Kontakt has expressly i voluntarily objected through opt-in means)
• A domena name was already in “lock status” provided that the Rejestrator provides a readily accessible i reasonable means flub the Zarejestrujed Nazwa 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 (lub a lesser period to be determined) after being transferred (apart from being transferred back to the lubiginal Rejestrator in cases wtutaj both Rejestrators so agree i/lub wtutaj a decision in the dispute resolution process so directs).

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

YOU ALSO AGREE THAT WE WILL NOT BE LIABLE FLUB ANY INDIRECT, SPECIAL, INCIDENTAL, LUB CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING LSystem operacyjnyT PROFITS) LUB FLUB ANY FINANCIAL LUB ECONOMIC LSystem operacyjnyS LUB FLUB LSystem operacyjnyS OF PROFITS, LSystem operacyjnyS OF BUSINESS, DEPLETION OF GOODWILL LUB SIMILAR LSystem operacyjnySES, LSystem operacyjnyS OF ANTICIPATED SAVINGS LUB LSystem operacyjnyS LUB CLUBRUPTION OF DATA LUB INFLUBMATION, REGARDLESS OF THE FLUBM OF ACTION WHETHER IN CONTRACT, TLUBT (INCLUDING NEGLIGENCE), LUB OTHERWISE, EVEN IF WE HAVE BEEN ADVISED OF THE PSystem operacyjnySIBILITY OF SUCH DAMAGES.

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

24. General
You may not assign any of twój rights lub privileges, lub delegate any of twój duties lub obligations tutajunder, in whole lub in part, by operation of law lub otherwise, to any third party without our prilub written consent. We may at any time assign, transfer, charge, sub-contract this Agreement. This Agreement shall be binding upon i inure to the benefit of the parties tutajto i their respective permitted successlubs i assigns.

NiceNIC.NET reserves the right, in its sole i absolute discretion, to change lub modify this Agreement, i any policies lub agreements which are inclubplubated tutajin, at any time i without notice. Any such changes lub modification shall be effective immediately upon posting to the Site. Jeśli 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 lub continue to use the Services. You agree that twój exclusive remedy is to transfer twój Services to another registrar lub request us to terminate twój Services under this Agreement. NiceNIC.NET may occasionally notify you of changes lub modifications to this Agreement lub the Services by email so it is very implubtant that you keep twój account influbmation current i up to date. NiceNIC.NET is not responsible i assumes no liability flub twój failure to receive an email notification if such failure results from inaccurate lub out-dated account influbmation.

This Agreement constitutes the entire agreement between the parties concerning the subject matter tutajin i supersedes all prilub understiings i agreements between the parties, whether written lub lubal, regarding the subject matter tutajin. Any of the provisions of this Agreement which are determined to be invalid lub unenflubceable in any jurisdiction shall be ineffective to the extent of such invalidity lub unenflubceability in such jurisdiction, without rendering invalid lub unenflubceable the remaining provisions tutajof lub affecting the validity lub unenflubceability of any of the terms of this Agreement in any other jurisdiction. A waiver by either party of a breach lub violation of any provision of this Agreement will not constitute lub be construed as a waiver of any subsequent breach lub violation of that provision lub as a waiver of any breach lub violation of any other provision of this Agreement. The headings contained in this Agreement are flub convenience only i shall not affect meaning lub interpretation of this Agreement.

25. Nietices
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 acclubdance with the Account i/lub WHOIS influbmation you have provided.

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

1.3 The Registrant ackterazledges i agrees that the Rejestrator shall monitlub the status of Nazwy domen zarejestrujed through the Rejestrator i shall, at its own initiative lub on receipt of complaint, conduct checks to verify whether a Nazwa domeny is being used in connection with phishing lub "spam" advertising. The Rejestrator shall delete lub suspend a Nazwa domeny if so directed by HKIRC. HKIRC may issue such a direction on receipt of any notice from any government lub law enflubcement authlubity (including without limitation the Hongkong Police Flubce lub the Office of Telecommunications Authlubity) that the use of the Nazwa domeny is in breach of any laws, directives, guidelines, codes of practice lub regulations issued by such local authlubities, lub if, in HKIRC's reasonable belief, the continuation of registration of the Nazwa domeny lub the operation of web site referenced   by the Nazwa domeny is likely to damage lub adversely affect the goodwill, reputation i operation of HKIRC lub the domena name industry in Hongkong, lub may expose HKIRC to risks of third party claims lub civil lub criminal prosecution.

Flub mlube influbmation about .HK domena registration, please refer to the latest version of HKIRC Rejestracja 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 usługa provider shall be final i binding on the Registrant i 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 i non-statutluby clubplubation designated by the Hong-Kong Government to administer the registration of Internet domena names under .hk i .香港 country-code top level domenas. Flub any comments lub complaints against NICENIC INTERNATIONAL GROUP CO., LTD regarding its accreditation’s compliance, please find tutaj useful influbmation: HKIRC Dispute Resolution Policies - https://www.hkirc.hk/en/our_supplubt/domena_dispute_policies_i_procedures/domena_name_dispute_resolution_policies/; HKIRC DNDRP Rules of Procedure - https://www.hkirc.hk/en/our_supplubt/domena_dispute_policies_i_procedures/rules_of_procedures/; lub Adres e-mail: info@hkirc.hk.

6  REGISTRANT WARRANTIES 

    The Registrant ackterazledges that the Rejestrator i HKIRC rely on all representations made i warranties given by the Registrant in determining if the application flub a Nazwa domeny should be approved.

    Flub mlube influbmation about "Acceptable Use Policy", please refer to https://www.hkirc.hk/domena_policies/EN_Domena_Nazwa_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. Niew that you have met the requirements of ICANN, our team is looking flubward to assisting you in completing the Verisign certification process so you can quickly begin zarejestrujing .com i .net domena names. We hope this supplubt will prove to be helpful in reducing the investment of twój internal resources i time."

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

ICM:
"Congrats on twój recent ICANN Akredytacja..."

Neustar:

"We have been notified that twój company is teraz ICANN-accredited as a .BIZ registrar.  Neustar looks flubward to getting twój company up i running as soon as possible!"

Więcej registries will be notified by ICANN flub the clubresponding domena names signed in the RAA in the następny days, we NiceNIC have been staying flub the disposal of sign-up/accreditation process, striving to save time i expedite each step if possible. The concerned technical staffs have been arranged to re-set the product prices to a mlube competitive level. Szczegółyed influbmation 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"), i dedicated to offer clients easy to navigate, fast to locate usługas in domena name registration, web hosting kup, 1 to 1 customer supplubt.

Stiing at the peak of internet infrastruture, we firstly need to appreciate every client, i every website viewer who ever stayed tutaj, without twój persistant supplubt i comprehension, we are nothing, hope 2012 will bring you i twój family lucky, happy, healthy life.

Reference links:

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

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

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

ZhuHai NaiSiNiKe Influbmation Technology Co Ltd.

2009

China

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

Wszystko the best,

NiceNIC.NET Team

ZhuHai NaiSiNiKe Influbmation 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 flub Enflubcement concerning a dispute under this Dispute Resolution Policy.

1.2 Dispute Resolution Provider

1.3 The Dispute Resolution Provider must be an independent i neutral third party that is neither associated nlub affiliated with either Rejestrator involved in the dispute lub the Registry Operatlub under which the disputed domena name is zarejestrujed. ICANN shall have the authlubity to accredit one lub mlube independent i neutral Dispute Resolution Providers acclubding to criteria developed in acclubdance with this Dispute Resolution Policy.

1.4 FOA

     Flubm of Authlubization - The stiardized flubm of consent that the Gaining Rejestrator i Rejestrator of Reclubd are required to use to obtain authlubization from the Registrant lub Administrative Kontakt in lubder to properly process the transfer of domena name sponslubship from one Rejestrator to another.

1.5 Gaining Rejestrator

     The Rejestrator that submitted to the Registry the request flub the transfer of a domena sponslubship from the Rejestrator of Reclubd.

1.6 Rejestrator of Reclubd

     The Rejestrator of Reclubd flub a domena name flub which the Registry received a transfer of sponslubship request.

1.7 Registrant

     The Registrant is the individual lub lubganization that zarejestrujs a specific domena name. This individual lub lubganization holds the right to use that specific domena name flub a specified period of time, provided certain conditions are met i the registration fees are paid. This person lub lubganization is the "legal entity" bound by the terms of the relevant usługa agreement with the Registry operatlub flub the TLD in question.

1.8 Registry (Registry Operatlub)

     The lubganization authlubized by ICANN to provide registration usługas flub a given TLD to ICANN-accredited Rejestrators.

1.9 Supplemental Rules

     The Supplemental Rules shall mean those rules adopted by the Registry Operatlub, in the case of First Poziom disputes (as set flubth below), lub 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 i shall cover topics such as fees, wlubd i page limits i guidelines, the means flub communicating with the Provider, i the flubm of cover sheets.

1.10 Transfer Policy

     The Policy on Transfer of Sponslubship of Rejestracjas between Rejestrators which is in flubce as part of the Registry-Rejestrator Agreement executed between a Rejestrator i the Registry, as well as the Rejestrator Akredytacja Agreement which is executed between ICANN i all ICANN- accredited registrars.

2. Dispute Resolution Process

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

2.1 First Poziom - Registry Operatlub

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

2.2 Second-Poziom - Dispute Resolution Panel

     The primary intent of this step is to provide a means flub 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 wtutaj a Rejestrator of Reclubd 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 wtutaj a Gaining Rejestrator 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 Poziom (Registry)

3.1 Rejestrator files a Request flub Enflubcement with the applicable Registry Operatlub

     3.1.1 Either the Gaining lub Rejestrator of Reclubd ("Filing Rejestrator") may submit a Request flub Enflubcement. This must be done in acclubdance with the Supplemental Rules adopted by the applicable Registry Operatlub.

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

3.1.4 The Request flub Enflubcement shall annex the following documentary evidence (as applicable i available) in electronic flubm if possible, together with a schedule indexing such evidence:
  (i) Flub the Gaining Rejestrator:
      a. Completed Flubm of Authlubization ("FOA")
      b. Copy of the Whois output flub the date transfer was initiated, which was used to identify the authlubized Transfer Kontakts
      c. Copy of evidence of identity used
      d. Copy of a bilateral agreement, final determination of a dispute resolution body lub court lubder in cases when the Registrant of Reclubd is being changed simultaneously with a Rejestrator Transfer
      e. Copies of all communications made to the Rejestrator of Reclubd with regard to the applicable transfer request along with any responses from the Rejestrator of Reclubd
  (ii) Flub the Rejestrator of Reclubd:
      a. Completed FOA from Rejestrator of Reclubd if applicable
      b. Copy of the Whois output flub the date the transfer was initiated
      c. Relevant histluby of Whois modifications made to the applicable registration
      d. Evidence of one of the following if a transfer was denied:

• fraud;
• UDRP action;
• court lubder;
• Registrant lub administrative contact identity dispute in acclubdance with Section 4 [Rejestrator of Reclubd Requirements]
• applicable payment dispute along with evidence that the registration was put on HOLD status;
• express written objection from the Zarejestrujed Nazwa Holder lub Administrative Kontakt;
• LOCK status along with proof of a reasonable means flub the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
• domena name within 60 days of initial registration; lub
• domena name within 60 days of a prilub transfer.

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

3.2 The Nien-Filing Rejestrator ("Respondent") shall have seven (7) calendar days from receipt of the Request flub Enflubcement to prepare a Response to the Request flub Enflubcement ("Response").

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

3.2.2 W the request of the Respondent, the Registry Operatlub may, in exceptional cases, extend the period of time flub the filing of the response, but in no case may the extension be mlube 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 Operatlub.

3.2.3 Jeśli a Respondent does not submit a response, in the absence of exceptional circumstances, the Registry Operatlub shall decide the dispute based upon the Request flub Enflubcement.

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

3.3.1 Jeśli the data included in the Request flub Enflubcement does not match the data listed in the authlubitative Whois, the Registry Operatlub must contact each Rejestrator i require additional documentation.

3.3.2 Jeśli the Gaining Rejestrator cannot provide a complete FOA with data matching that contained within the authlubitative Whois database, then the Registry Operatlub shall find that the transfer should be reversed. In the case of a thick Registry, if the Rejestrator of Reclubd's Whois is not accessible lub invalid, the Registry Operatlub's Whois should be used. In the case of a thin Registry, if the Rejestrator of Reclubd's Whois is not accessible lub is invalid, the Registry Operatlub must notify ICANN i place the dispute on hold until such time as the specific problem is resolved by ICANN.

3.3.3 In the case wtutaj a Rejestrator of Reclubd denies a request flub a domena name transfer ("NACKs"), the Rejestrator of Reclubd must provide evidence of one of the factlubs flub which it is allowed to NACK. Jeśli the Rejestrator of Reclubd cannot provide evidence that demonstrates any of the factlubs, i the Gaining Rejestrator provides to the Registry a complete FOA with data matching that contained within the authlubitative Whois database, then the transfer must be approved to be processed.

3.3.4 Jeśli the data provided by neither Rejestrator appears to be conclusive, then the Registry shall issue a finding of "no decision." Jeśli the data provided to the Registry is complete i provides sufficient basis flub a determination based on the Policy, the Registry may not issue a finding of "no decision." Either Rejestrator shall be able to appeal such issue to a Second-Poziom Dispute Resolution Provider in acclubdance with the provisions set flubth below.

3.4 Fees flub First-Poziom Dispute Resolution Service

3.4.1 Ttutaj is no filing fee assessed to the Filing Rejestrator at the time the Request flub Enflubcement is submitted to the Registry Operatlub.

3.4.2 The Rejestrator that does not poprzedniail in the dispute will be assessed a fee to be set by the Registry Operatlub. Such fee shall be set flubth in the Registry's Supplemental Rules that are in effect at the time that the Request flub Enflubcement 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 Operatlub shall collect the applicable fees from the Filing Rejestrator.

3.5 Availability of Court Proceedings

      The procedures set flubth above shall not poprzednient a Rejestrator from submitting a dispute to a court of competent jurisdiction flub independent resolution beflube such an administrative proceeding is commenced lub after such proceeding is concluded. Jeśli a Registry Operatlub decides a domena name registration should be transferred (either to the Gaining Rejestrator, lub alternatively, back from the Gaining Rejestrator to the Rejestrator of Reclubd), the Registry will wait fourteen (14) calendar days after it is influbmed of the decision beflube 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). Jeśli such documentation is received by the Registry Operatlub within the fourteen (14) calendar day period, the decision will not be implemented until (i) evidence is presented to the Registry Operatlub that the parties have resolved such dispute; (ii) evidence is presented to the Registry Operatlub that the lawsuit has been dismissed lub withdrawn; lub (iii) the Registry Operatlub receives a copy of an lubder from such court.

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

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

      (i) A Filing Rejestrator may elect to skip the First-Poziom dispute process at Registry level i submit a Request flub Enflubcement directly with a Dispute Resolution Provider;
      (ii) The non-poprzedniailing Rejestrator in a First-Poziom dispute proceeding may submit an appeal of the applicable Registry Operatlub's decision to the Dispute Resolution Provider. Dodajitionally, in the case wtutaj the result in the First-Poziom dispute process is a "no-decision," either Rejestrator may file an Appeal of such decision to a Dispute Resolution Provider.

4.2 Initial Request flub Enflubcement

4.2.1 In the event that the Filing Rejestrator elects to submit a Request flub Enflubcement to the Dispute Resolution Provider in lieu of submitting a Request flub Enflubcement to the applicable Registry Operatlub, the obligations i responsibilities set flubth 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 i compare registrant/contact data with that contained within the authlubitative Whois database i reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.
     (i) Jeśli the data does not match the data listed in authlubitative Whois, the Dispute Resolution Panel should contact each Rejestrator i require additional documentation.
     (ii) Jeśli the Gaining Rejestrator is unable to provide a complete FOA with data matching that contained within the authlubitative 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 Rejestrator of Reclubd's Whois is not accessible lub invalid, the applicable Registry Operatlub's Whois should be used. In the case of a thin Registry, if the Rejestrator of Reclubd's Whois is not accessible lub is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.
     (iii) In the case wtutaj a Rejestrator of Reclubd NACKs a transfer, the Rejestrator of Reclubd must provide evidence of one of the factlubs flub which it is allowed to NACK as set flubth in Section 3.1.4 (ii) of this Dispute Resolution Policy. Jeśli the Rejestrator of Reclubd cannot provide evidence that demonstrates any of the factlubs, i the Gaining Rejestrator provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authlubitative Whois database at the time of the transfer request, then the transfer should be approved.
     (iv) Unlike under the First-Poziom 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 i determine, based on a preponderance of the evidence, which Rejestrator should poprzedniail in the dispute i what resolution to the Request flub Enflubcement will appropriately redress the issues set flubth in the Request flub Enflubcement.
     (v) Resolution options flub the Dispute Resolution Panel are limited to the following:
  a. Approve Transfer
  b. Deny the Transfer (lub lubdering the domena name be returned to the Rejestrator of Reclubd in cases wtutaj a Transfer has already occurred)

4.3 Appeal of First Poziom Dispute Decision lub Registry Operatlub Finding of "Nie-Decision."

4.3.1 In the event that the Rejestrator which does not poprzedniail in the First-Poziom dispute is dissatisfied by the Registry-Operatlub's decision, such Rejestrator 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-Poziom decision was issued.

4.3.2 In the event that the Registry Operatlub issues a finding of "no-decision" in acclubdance with Section 3.3.4 above, either Rejestrator 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-Poziom decision was issued.

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

4.3.4 The Appellant shall submit the Appeal in electronic flubm i shall:
     (i) Request that the Appeal be submitted flub decision in acclubdance with the Policy i these Rules;
     (ii) Provide the name, postal i e-mail addresses, i the telephone i telefax numbers of the Appellant i of any representative authlubized by the Appellant to act on behalf of the Appellant in the administrative proceeding;
     (iii) Provide the name of the Appellee i all influbmation (including any postal i e-mail addresses i telephone i telefax numbers) kterazn to Appellee regarding how to contact Appellee lub any representative of Appellee, including contact influbmation based on pre-Request flub Enflubcement i 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 flub such appeal, including specific responses to the findings of the Registry Operatlub in the First-Poziom Dispute process. (This plubtion of the response shall comply with any wlubd lub page limit set flubth in the Dispute Resolution Provider's Supplemental Rules);
     (vii) Specify, in acclubdance with the Policy, the remedies sought;
     (viii) Identify any other related legal proceedings kterazn to the Appellant that have been commenced lub terminated in connection with lub 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 lub transmitted to the Appellee; i
      (x) Conclude with the following statement followed by the signature of the Appellant lub its authlubized representative:
  "Appellant agrees that its claims i remedies concerning the registration of the domena name, the dispute, lub the dispute's resolution shall be solely against the Appellee i waives all such claims i remedies against the Dispute Resolution Provider i the Registry Operatlub as well as their directlubs, officers, employees, i agents, except in the case of deliberate wrongdoing lub gross negligence."
  "Appellant certifies that the influbmation contained in this Appeal is to the best of Appellant's kterazledge complete i accurate, that this Appeal is not being presented flub any improper purpose, such as to harass, i that the assertions in this Appeal are warranted under this Policy i under applicable law, as it teraz exists lub as it may be extended by a good-faith i reasonable argument."

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

4.3.7 A Dispute Resolution Provider must request all documentation relating to the First-Poziom Dispute from the applicable Registry Operatlub no later than seven (7) calendar days of receipt of the appeal. The Registry Operatlub 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 i 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 lub 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 Nievo basis. Although the Dispute Resolution Panel is not bound by the findings of the Registry Operatlub 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 i determine the appropriate resolution to the issues presented.

• Approval of a Transfer
• Denial of the Transfer (lub lubdering the domena name be returned to the Rejestrator of Reclubd in cases wtutaj a Transfer has already occurred)

4.4 Fees flub Second-Poziom Dispute Resolution Service

4.4.1 In the case of either a Request flub Enflubcement lub an Appeal filed at the Second Poziom, the applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fee"). The specific fees along with the terms i 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 Rejestrator lub Appellant, whichever applicable, does not poprzedniail in a Second-Poziom dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

4.4.3 In the event that the Filing Rejestrator lub Appellant, whichever applicable, poprzedniails in a Second-Poziom dispute, the Respondent lub 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 Rejestrator lub Appellant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent lub Appellee. Such fees must be paid regardless of whether a Court Proceeding is commenced in acclubdance 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 flubth above shall not poprzednient a Rejestrator from submitting a dispute to a court of competent jurisdiction flub independent resolution beflube such administrative proceeding is commenced lub after such proceeding is concluded. Jeśli a Dispute Resolution Panel decides a domena name registration should be transferred (either to the Gaining Rejestrator, lub alternatively, back from the Gaining Rejestrator to the Rejestrator of Reclubd), such Rejestrator will wait fourteen (14) calendar days after it is influbmed of the decision beflube 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). Jeśli 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 lub withdrawn; lub (iii) a copy of an lubder from such court dismissing the lawsuit lub lubdering certain actions with respect to the domena name.

1. Rejestrator Requirements

     Zarejestrujed Nazwa Holders must be able to transfer their domena name registrations between Rejestrators provided that the Gaining Rejestrator's transfer process meets the minimum stiards of this policy i that such transfer is not prohibited by ICANN lub Registry policies. Inter-Rejestrator domena name transfer processes must be clear i concise in lubder to avoid confusion. Further, Rejestrators should make reasonable efflubts to influbm Zarejestrujed Nazwa Holders of, i provide access to, the published documentation of the specific transfer process employed by the Rejestrators.

1.1 Transfer Authlubities

     The Administrative Kontakt i the Zarejestrujed Nazwa Holder, as listed in the Losing Rejestrator's lub applicable Registry's (wtutaj available) publicly accessible WHOIS usługa are the only parties that have the authlubity to approve lub deny a transfer request to the Gaining Rejestrator. In the event of a dispute, the Zarejestrujed Nazwa Holder's authlubity supersedes that of the Administrative Kontakt.
Rejestrators may use Whois data from either the Rejestrator of Reclubd lub the relevant Registry flub the purpose of verifying the authenticity of a transfer request; lub from another data source as determined by a consensus policy.

2. Gaining Rejestrator Requirements

Flub each instance wtutaj a Zarejestrujed Nazwa Holder requests to transfer a domena name registration to a different Rejestrator, the Gaining Rejestrator shall:
      2.1 Obtain express authlubization from either the Zarejestrujed Nazwa Holder lub the Administrative Kontakt (tutajafter, "Transfer Kontakt"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Rejestrator from the Transfer Kontakt.

     2.1.1 The authlubization must be made via a valid Stiardized Flubm of Authlubization (FOA). Ttutaj are two different FOA's available at the ICANN website. The FOA labeled "Initial Authlubization flub Rejestrator Transfer" must be used by the Gaining Rejestrator to request an authlubization flub a registrar transfer from the Transfer Kontakt. The FOA labeled "Potwierdźation of Rejestrator Transfer Request" may be used by the Rejestrator of Reclubd to request confirmation of the transfer from the Transfer Kontakt.
The FOA shall be communicated in English, i any dispute arising out of a transfer request shall be conducted in the English language. Rejestrators may choose to communicate with the Transfer Kontakt in additional languages. However, Rejestrators choosing to exercise such option are responsible flub the accuracy i completeness of the translation into such additional non-English version of the FOA.

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

     2.1.2.1 Jeśli the Gaining Rejestrator relies on a physical authlubization process, then the Gaining Rejestrator assumes the burden of obtaining reliable evidence of the identity of the Transfer Kontakt i maintaining appropriate reclubds proving that such evidence was obtained. Further the Gaining Rejestrator also assumes the burden flub ensuring that the entity making the request is indeed authlubized to do so. The acceptable flubms of physical identity are:

• Nietarized statement
• Valid Drivers license
• Paszport
• Article of Inclubplubation
• Military ID
• State/Government issued ID
• Birth Certificate

     2.1.3 In the event that the Gaining Rejestrator relies on an electronic process to obtain this authlubization the acceptable flubms of identity would include:

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

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

     2.2 Request, by the transmission of a "transfer" commi as specified in the Rejestrator Dool Kit, that the Registry Operatlub database be changed to reflect the new Rejestrator.

     2.2.1 Transmission of a "transfer" commi constitutes a representation on the part of the Gaining Rejestrator that the requisite authlubization has been obtained from the Transfer Kontakt listed in the authlubitative Whois database.

     2.2.2 The Gaining Rejestrator is responsible flub validating the Zarejestrujed Nazwa Holder requests to transfer domena names between Rejestrators. However, this does not preclude the Rejestrator of Reclubd from exercising its option to independently confirm the Zarejestrujed Nazwa Holder's intent to transfer its domena name to the Gaining Rejestrator in acclubdance with Section 3 of this policy.

3. Obligations of the Rejestrator of Reclubd

     A Rejestrator of Reclubd can choose independently to confirm the intent of the Zarejestrujed Nazwa Holder when a notice of a pending transfer is received from the Registry. The Rejestrator of Reclubd must do so in a manner consistent with the stiards set flubth in this agreement pertaining to Gaining Rejestrators. In lubder to ensure that the flubm of the request employed by the Rejestrator of Reclubd is substantially administrative i influbmative in nature i clearly provided to the Transfer Kontakt flub the purpose of verifying the intent of the Transfer Kontakt, the Rejestrator of Reclubd must use the FOA.

     The FOA shall be communicated in English, i any dispute arising out of a transfer request, shall be conducted in the English language. Rejestrators may choose to communicate with the Transfer Kontakt in additional languages. However, the Rejestrator choosing to exercise such option is responsible flub the accuracy i completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes i procedures set flubth in this policy. This includes but is not limited to the requirement that no Rejestrator shall add any additional influbmation 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 Rejestrator of Reclubd from marketing to its existing customers through separate communications.
The FOA should be sent by the Rejestrator of Reclubd 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 Operatlub.Failure by the Rejestrator of Reclubd 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 Rejestrator of Reclubd i the Rejestrator of Reclubd has not explicitly denied the transfer request, the default action will be that the Rejestrator of Reclubd must allow the transfer to proceed.
Upon denying a transfer request flub any of the following reasons, the Rejestrator of Reclubd must provide the Zarejestrujed Nazwa Holder i the potential Gaining Rejestrator with the reason flub denial. The Rejestrator of Reclubd may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court lubder by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Zarejestrujed Nazwa Holder lub Administrative Kontakt
5. Nie payment flub poprzedniious registration period (including credit card charge-backs) if the domena name is past its expiration date lub flub poprzedniious lub current registration periods if the domena name has not yet expired. In all such cases, however, the domena name must be put into "Rejestrator Hold" status by the Rejestrator of Reclubd prilub to the denial of transfer.
6. Express written objection to the transfer from the Transfer Kontakt. (e.g. - email, fax, paper document lub other processes by which the Transfer Kontakt has expressly i voluntarily objected through opt-in means)
7. A domena name was already in “lock status” provided that the Rejestrator provides a readily accessible i reasonable means flub the Zarejestrujed Nazwa 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 (lub a lesser period to be determined) after being transferred (apart from being transferred back to the lubiginal Rejestrator in cases wtutaj both Rejestrators so agree i/lub wtutaj a decision in the dispute resolution process so directs).

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

• Nienpayment flub a pending lub future registration period
• Nie response from the Zarejestrujed Nazwa Holder lub Administrative Kontakt.
• Domena name in Rejestrator Lock Status, unless the Zarejestrujed Nazwa Holder is provided with the reasonable opplubtunity i ability to unlock the domena name prilub to the Transfer Request.
• Domena name registration period time constraints, other than during the first 60 days of initial registration lub during the first 60 days after a registrar transfer.
• General payment defaults between Rejestrator i business partners / affiliates in cases wtutaj the Zarejestrujed Nazwa Holder flub the domena in question has paid flub the registration.

     The Rejestrator of Reclubd has other mechanisms available to collect payment from the Zarejestrujed Nazwa Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Rejestrator of Reclubd must not employ transfer processes as a mechanism to secure payment flub usługas from a Zarejestrujed Nazwa Holder. Exceptions to this requirement are as follows:
     (i) In the case of non-payment flub poprzedniious registration period(s) if the transfer is requested after the expiration date, lub
     (ii) In the case of non-payment of the current registration period, if transfer is requested beflube the expiration date.

4. Rejestrator Colubdination

     Each Rejestrator is responsible flub keeping copies of documentation, including the FOA i the Transfer Kontakts response ttutajto, that may be required flub filing i supplubting a dispute under the dispute resolution policy. Gaining Rejestrators must maintain copies of the FOA as received from the Transfer Kontakt as per the stiard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

     Both the Gaining Rejestrator i the Rejestrator of Reclubd must provide the evidence relied on flub the transfer during i after the applicable inter-registrar domena name transaction(s). Such influbmation must be provided when requested by, i only by, the other Rejestrator that is party to the transfer transaction. Dodajitionally, ICANN, the Registry Operatlub, a court lub authlubity with jurisdiction over the matter lub a third party dispute resolution panel may also require such influbmation within five (5) days of the request.

     The Gaining Rejestrator must retain, i produce pursuant to a request by a Losing Rejestrator, a written lub electronic copy of the FOA. In instances wtutaj the Rejestrator of Reclubd has requested copies of the FOA, the Gaining Rejestrator must fulfill the Rejestrator of Reclubds request (including providing the attendant supplubting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds flub reversal by the Registry Operatlub lub the Dispute Resolution Panel in the event that a transfer complaint is filed in acclubdance with the requirements of this policy.

     Jeśli either a Rejestrator of Reclubd lub a Gaining Rejestrator does not believe that a transfer request was hiled in acclubdance with the provisions of this policy, then the Rejestrator may initiate a dispute resolution procedure as set flubth in Section C of this policy.

     Flub purposes of facilitating transfer requests, Rejestrators should provide i maintain a unique i private email address flub use only by other Rejestrators i the Registry:
     i. This email address is flub issue related to transfer requests i the procedures set flubth 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. Wiadomośćs 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 flub Rejestrators

     In EPP-based gTLD Registries, Rejestrators must follow the requirements set flubth below.
Rejestrators must provide the Zarejestrujed Nazwa Holder with the unique "AuthInfo" code within five (5) calendar days of the Zarejestrujed Nazwa Holder's initial request if the Rejestrator does not provide facilities flub the Zarejestrujed Nazwa Holder to generate i manage their own unique "AuthInfo" code.

     Rejestrators may not employ any mechanism flub complying with a Zarejestrujed Nazwa Holder's request to obtain the applicable "AuthInfo Code" that is mlube restrictive than the mechanisms used flub changing any aspect of the Zarejestrujed Nazwa Holder's contact lub name server influbmation.

     The Rejestrator of Reclubd must not refuse to release an "AuthInfo Code" to the Zarejestrujed Nazwa Holder solely because ttutaj is a dispute between the Zarejestrujed Nazwa Holder i the Rejestrator over payment.

Rejestrator-generated "AuthInfo" codes must be unique on a per-domena basis.
     The "Auth-Info" codes must be used solely to identify a Zarejestrujed Nazwa Holder, wtutajas the FOA's still need to be used flub authlubization lub confirmation of a transfer request, as described in Section 2 i Section 4 of this policy.

6. Registry Requirements

     Upon receipt of the "transfer" commi from the Gaining Rejestrator, Registry Operatlub will transmit an electronic notification to both Rejestrators. 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 Rejestrator flub the purpose of facilitating transfers.

     The Registry Operatlub shall complete the requested transfer unless, within five (5) calendar days, Registry Operatlub receives a NACK protocol commi from the Rejestrator of Reclubd.
When the Registry's database has been updated to reflect the change to the Gaining Rejestrator, Registry Operatlub will transmit an electronic notification to both Rejestrators. The notification may be sent to       the unique email address established by each Rejestrator flub the purpose of facilitating transfers lub such other email address agreed to by the parties.
The Registry Operatlub shall undo a transfer if, after a transfer has occurred, the Registry Operatlub receives one of the notices as set flubth below. In such case, the transfer will be reversed i the domena name reset to its lubiginal state. The Registry Operatlub 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 Operatlub 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 Rejestrator of Reclubd i the Gaining Rejestrator sent by email, letter lub fax that the transfer was made by mistake lub was otherwise not in acclubdance with the procedures set flubth in this policy;
     ii. The final determination of a dispute resolution body having jurisdiction over the transfer; lub
     iii. Order of a court having jurisdiction over the transfer.

7. Reclubds of Rejestracja

     Each Rejestrator shall require its customer, the Zarejestrujed Nazwa Holder, to maintain its own reclubds appropriate to document i prove the initial domena name registration date.

8. Effect on Okres of Rejestracja

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

B. ICANN-Approved Transfers

     Transfer of the sponslubship of all the registrations sponslubed by one Rejestrator as the result of (i) acquisition of that Rejestrator lub its assets by another Rejestrator, lub (ii) lack of accreditation of that Rejestrator lub lack of its authlubization with the Registry Operatlub, may be made acclubding to the following procedure:
     (a) The gaining Rejestrator must be accredited by ICANN flub the Registry TLD i must have in effect a Registry-Rejestrator Agreement with Registry Operatlub flub the Registry TLD.
     (b) ICANN must certify in writing to Registry Operatlub that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual lub imminent business failure of a Rejestrator.
Upon satisfaction of these two conditions, Registry Operatlub will make the necessary one-time changes in the Registry database flub no charge, flub transfers involving 50,000 name registrations lub fewer. Jeśli the transfer involves registrations of mlube than 50,000 names, Registry Operatlub will charge the gaining Rejestrator a one-time flat fee of US$ 50,000.

C. Transfer Dispute Resolution Policy

     Procedures flub hiling disputes concerning inter-registrar transfers are set flubth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operatlubs i ICANN accredited Rejestrators.

We respect twój individual privacy. That is why we have adopted this Polityka prywatności, which embodies our commitment to the protection of twój privacy through adtutajnce to fair electronic influbmation practices. This Polityka prywatności puts you, the individual, in control of how twój personal influbmation is processed, i you have our promise that we will not electronically process twój personal influbmation in any way that is incompatible with this Polityka prywatności.

This Polityka prywatności protects twój privacy by:

4. How We Put Influbmation Do Good Use