icon

Documents

gTDL Registration


Contract for gTLD domain registration

with NetArt Registrar Sp. z o.o.

This Agreement is entered into by and between NetArt Registrar Sp. z o.o. with its registered seat in Cracow, Pana Tadeusza 2, 30-727 Cracow, Poland, entered in the Register of Entrepreneurs of the National Court Register kept by XI Commercial Division of the National Court Register in Cracow under KRS number 0000532637, with share capital in the amount of PLN 650,000 (in words: six hundred and fifty thousand zlotys), fully paid up, REGON: 120764285, NIP: 6751398383, hereinafter referred to as the "Registrar", and the Internet Domain Registrant, represented by an authorised Partner.


I. Definitions


  • Registrant – a natural or legal person, as well as an unincorporated entity that is granted legal capacity by special regulations, who enters into a Domain Registration Agreement with the Registrar in order to register an Internet domain.
  • Partner – an entity authorised by the Registrant to represent it before the Registrar, having at the same time a relevant agreement with the Registrar.
  • ICANN – Internet Corporation for Assigned Names and Numbers, Los Angeles 12025 Waterfront Drive, Suite 300, CA 90094-2536, USA.
  • Registry Operator – an entity that is responsible for, manages and authorises the registration of individual top-level domains (gTLDs) in accordance with the rules established by ICANN and has a relevant agreement with ICANN.
  • Consumer – a natural person entering into a contract not directly related to his or her business or professional activity.
  • Whois Privacy – functionality that allows the protection of Registrant's data in the Whois database by replacing it with the data of a third party, made available to Registrants by the Partner under the terms agreed between the Registrant and the Partner.
  • Whois database – a publicly available database of Internet domain registrants.
  • A gTLD – (generic top-level domain, hereinafter: domain) – a unique sequence of allowed alphanumeric characters, consisting of a name and an extension offered by the Registrar.
  • Domain registration – placement of a domain name with its corresponding nameserver addresses in the Registry Operator's database.
  • Authinfo code – a unique string of characters used to perform operations on the domain, including performing its transfer.
  • Administrative and technical support – a set of activities necessary for the management of a domain, which include, but are not limited to, such activities as managing the data provided by the Registrant, providing access to systems for processing such data, issuing Authinfo Codes, transferring and configuration of the domain.
  • Subscription period – the time for which the domain is registered.
  • UDRP – Uniform Domain Name Dispute Resolution Policy - UDRP.
  • RDRP – Rules for Uniform Domain Name Dispute Resolution Policy – RDRP.
  • Domain reinstatement – renewal of the Subscription Period made within 40 days after the date of expiration of the domain.
  • Domain reactivation – renewal of the Subscription Period made between the 41st and 70th day after the date of expiration of the domain.

II. General Provisions


  • The Registrar is an ICANN-accredited registrar of Internet domains. By using the Registrar's services, the Registrant accepts the terms and conditions of domain registration as set forth in this Agreement, which conforms with the terms and conditions established by ICANN, available at: https://www.icann.org.
  • The present Agreement does not constitute an authorization for the Partner to represent the Registrar before the Registrant.
  • The Domain Registration Agreement between the Registrant and the Registrar is executed by the Registrant submitting and transferring to the Registrar through the Partner:
    1. a statement of approval of the contents of this Agreement,
    2. a domain registration order resulting in its registration using the Partner's ICT system.
  • The Registrant shall perform all obligations of the Registrant under the Domain Registration Agreement signed with the Registrar through the Partner.
  • The Partner shall be responsible for the existence and scope of authorisation to act on behalf of the Registrant.
  • The Registrant acknowledges and agrees that domain registration is done on a first-come, first-served basis, and therefore the Registrar cannot guarantee him the registration of the designated domain.
  • The Registrant acknowledges the paid nature of the domain registration service and agrees to make payments for domain registration even before registration.
  • The Registrant declares that he/she has read the content of this Agreement and approves it in full.
  • The Registrant states that it demands that the domain registration process commence before the expiration of 14 days from the date of a properly placed order on the Partner's website.
  • The Registrant acknowledges that the entity responsible for the domain registration commitment is the Registrar. In consideration of ICANN requirements, the Registrant represents that it will not assert claims against ICANN, the Registry Operators (Verisign Inc., Identity Digital Inc., Public Interest Registry Inc., Registry Services, LLC.), their directors, officers, employees or agents for damages, liabilities, costs and expenses, including legal costs, arising out of or in connection with the domain registration.

III. Partner's duties towards the Registrant


  • The Partner is required to present this Agreement to the Registrant before proceeding with the domain registration process.
  • The Partner is obliged to provide administrative and technical support for the registered domain, and in particular to provide access to an ICT system that allows entering the personal data provided by the Registrant, modifying them, as well as changing the configuration of the domain.
  • The Registrant may pursue complaints for non-performance or improper performance of the Domain Registration Agreement through the Partner. The Partner is obliged to forward the Registrant's complaint to the Registrar, who shall resolve the complaint and relay the response to the Partner.

IV. Domain Registration


  • Domain registration is performed on the basis of:
    1. an accreditation agreement between the Registrar and ICANN,
    2. agreements entered into between the Registrar and the Registry Operators listed below:
      1. Verisign Inc. based in Reston, 12061 Bluemont Way, VA 20190, USA,
      2. VIdentity Digital Inc. headquartered in Bellevue, 10500 NE8th Street Suite 750 Bellevue, WA 98004, USA
      3. Public Interest Registry Inc. of Reston, 11911 Freedom Drive,10th floor, Suite 1000, VA 20190, USA,
      4. Registry Services LLC. based in Tempe, 2155 E GoDaddy Way, AZ 85284, USA,
    3. an agreement between the Registrar, ICANN and NCC Group Software Resilience (NA) LLC. of Manchester, XYZ Building, 2 Hardman Boulevard, Spinningfields, M3 3AQ, United Kingdom
    4. an agreement on representation of the Registrant before the Registrar concluded by the Registrant with the Partner.
  • Administrative and technical services related to domain registration and maintenance shall be performed by the Partner pursuant to an agreement with the Registrant for the representation of the Registrant before the Registrar.
  • The domain shall be registered by placing the domain in the Registry Operator's database at the Registrar's request. Domain registration shall be effected through the Partner.
  • For the purpose of registration, the Registrant undertakes to provide the following data through the Partner:
    1. name and surname, or full name in the case of entities that are not natural persons,
    2. address of residence or registered office,
    3. email address,
    4. d. telephone number and fax number, if any. In the case of entities that are not natural persons, the Registrant additionally undertakes to provide the name of the person authorised to make statements of intent on behalf of the Registrant. Furthermore, the Registrant is entitled to provide the name of the primary and backup DNS name server. The Registrar shall make all arrangements related to administrative and technical service issues with the Partner.
  • The Registrant undertakes to provide true data.
  • Domain Registrant's data may be protected in the Whois database using the Whois Privacy functionality provided by the Partner. Failure by a Registrant who is not an individual to use the Whois Privacy functionality shall be equivalent to the Registrant's consent to the inclusion of the Registrant's data in the Whois database.
  • The Registrant undertakes to update the data referred to in Section IV.4 by notifying the Partner of each change. The Registrant agrees to update this data so that it is true and complete within 7 days after any change during the Subscription Term. In the event if false, incomplete data are provided or in event of deliberate failure to update the data within 7 days after the change, the Registrar has the right to suspend, block or refuse to renew the domain for the next Subscription Period.
  • Due to ICANN requirements, the Registrant acknowledges and accepts the possibility of suspension, transfer, and deletion of the domain in order to correct errors in the domain registration by the Registrar or Registry Operator, as well as in case of necessity or as a result of resolving disputes concerning the registered domain.
  • Due to ICANN requirements, the Registrar reserves the right to delete the domain if the data provided by the Registrant proves to be false, inaccurate or incomplete. The Registrar is also entitled to delete the domain if the Registrant does not respond within 15 calendar days to the Registrar's inquiry regarding the data provided by the Registrant or does not complete the data within this period. At the Registrar's request, within the period specified in the preceding sentence, the Registrant shall provide the Registrar with documents confirming the veracity of the previously provided data.
  • The Registrar shall be liable to the Registrant for exercising due diligence in the domain registration process and providing the service in accordance with the Regulations.
  • The Registrant acknowledges that the domain registration is for a limited period of time, and the Domain Registration Agreement concluded between the Registrar and the Registrant expires on the last day of the subscription period. The Registrant will be notified by the Partner at least twice by email about the upcoming expiration of the domain registration subscription period, in case of expiration - the Registrant will receive at least one additional notification. It is recommended to provide an e-mail address for receiving the aforementioned notifications, established in a domain different from the one in connection with which the Registrar and the Registrant enter into this Agreement.
  • After the expiration of the Domain Registration Agreement, the Registrant has the option to Restore the domain or Reactivate the domain. The subscription period is calculated each time from the date of expiration of the domain. Domain Restoration and Domain Reactivation are chargeable in accordance with the price list available on the Partner's website. Fees for Domain Restoration and Domain Reactivation do not include prices for renewal of the Subscription Period, in accordance with the price list available on the Partner's website.
  • The expiration of the Domain Registration Agreement due to the expiration of the Subscription Term entitles the Registrar to delete the domain or to change the DNS servers to its own for the domain, including redirecting the domain to a page informing about the expiration of the domain and how to renew it, prior to its Restoration in accordance with Section IV.12.
  • Due to ICANN requirements, after the registration of the Registrant's first domain, each time the Registrant's contact information changes, the Registrant changes or the domain is transferred to the Registrar, the Registrar will verify the accuracy of the Registrant's information, in the manner indicated by the Registrar, in particular by the Registrant clicking on the unique code link or the Registrant emailing back the unique code, within 15 days of the Registrant's receipt of a message from the Registrar through the Partner. Receipt by the Registrar of the indicated unique code in response from the Registrant is tantamount to a statement by the Registrant that the contact information provided by him is correct. Verification does not apply to contact information identical to those for which verification was previously successful, subject to provisions of IV.15.
  • In the case of obtaining information that the Registrant’s e-mail address is outdated, it is probable that it is incorrect, does not exist or for any reason the e-mail from the Registrar has not been delivered correctly, the Registrar will be entitled to verify, through the Partner, the Registrant’s data according to section IV.14. or in any other way, especially through telephone contact.
  • In case of failure to confirm the correctness of the data in the manner and within the timeframe indicated by the Registrar through the Partner, the Registrar will be entitled to suspend the domain, including changing the DNS servers of the suspended domain to its own, redirecting the domain to a page informing about the reasons for the suspension of the domain and blocking the possibility of its transfer to another Registrar.
  • The Registrant undertakes to follow the domain registration rules provided by the relevant Registry Operator.

V. Domain Transfer


  • Any domain transfer shall follow ICANN rules available at: https://www.icann.org.
  • Transferring a domain to the Registrar requires:
    1. Placing a transfer order through the Partner,
    2. Registrant's consent to the transfer; if consent is not received within 5 days of the order, the transfer will be canceled.
  • Registrant's consent to the transfer; if consent is not received within 5 days of the order, the transfer will be canceled.
  • The Registrar and its Partner have the right to refuse to execute a domain transfer if:
    1. there is an ongoing dispute over the domain before an arbitration court or a common court, especially if actions are taken under the UDRP,
    2. the transfer is performed within the first 60 days after the domain registration or within the first 60 days after the last transfer is completed,
    3. a relevant court ruling exists prohibiting the execution of the transfer,
    4. there is doubt as to the accuracy of the data of the Registrant data or of the administrative contact,
    5. payment has not been made for domain registration for the previous Subscription Period if the registration has expired or payment has not been made for the current Subscription Period when the domain has not yet expired,
    6. The Registrant expressly objects in writing to the transfer,
    7. a status has been imposed on the domain that prevents the transfer from being executed (ClientTransferProhibited); in order to change the status of the domain and execute the transfer, the Registrant should contact the Partner,
    8. a change of the Registrant, a change of the Registrant's name or a change of the Registrant's e-mail address was effected - within a period of 60 days after the change.
  • The Partner is obliged to inform the Registrant about the rejection of the transfer.
  • In the event of a domain transfer from the Registrar, the Domain Registration Agreement between the Registrant and the Registrar is terminated.

VI. Personal Data Protection


  • The Registrar is entitled to process the Registrant's personal data in the form of:
    1. name and surname,
    2. address of residence,
    3. email address,
    4. telephone number and fax number, if any,
    5. the name of the person authorised to make statements of intent on behalf of the Registrant that is not a natural person.
  • In order to register a domain and to be able to renew the domain for the next Subscription Period in accordance with Section IV.12, it is voluntary, although necessary, to provide the data specified in Section VI.1. This data is provided through the Partner for the purpose of performing the Registrar's obligations under the accreditation agreement with ICANN.
  • The Partner should enable the Registrant to review and correct his data. All activities related to the correction, completion, deletion of personal data can be performed by the Registrant through the Partner.
  • The Registrar may provide the Registrant's personal data for the purpose of performing the provisions of the accreditation agreement with ICANN, to the following entities:
    1. Internet Corporation for Assigned Names and Numbers, with a registered office in Los Angeles 12025 Waterfront Drive, Suite 300, CA 90094-2536, USA.
    2. Verisign Inc. based in Reston, 12061 Bluemont Way, VA 20190, USA,
    3. Identity Digital Inc. headquartered in Bellevue, 10500 NE8th Street Suite 750 Bellevue, WA 98004, USA
    4. Public Interest Registry Inc. of Reston, 11911 Freedom Drive,10th floor, Suite 1000, VA 20190, USA,
    5. Registry Services LLC. based in Tempe, 2155 E GoDaddy Way, AZ 85284, USA,
    6. NCC Group Software Resilience (NA) LLC. of Manchester, XYZ Building, 2 Hardman Boulevard, Spinningfields, M3 3AQ, United Kingdom.
  • TThe Registrant declares that he agrees to the processing of his personal data by the Registrar. The Registrant's consent also includes consent to the processing of data by the entities listed in VI. 4, as well as consent to the inclusion of the data in the Whois database. The Registrant further represents that he has been informed by Partner about:
    1. Registrar's registration data,
    2. the purpose and scope of collection and processing of Registrant data by the Registrar,
    3. The right to inspect and correct his data,
    4. the rights to demand the cessation of data processing and the right to object to the processing.
  • The Registrar undertakes not to process the Registrant's personal data in a manner contrary to the purpose of the processing, as well as contrary to the principles of data processing contained in the regulations on personal data protection.
  • The Registrar undertakes to take reasonable precautions to protect the Registrant's personal data from loss, misuse, unauthorised access or disclosure, alteration or destruction.
  • The Registrar may treat the Registrant's request to cease processing as a breach of this Agreement by the Registrant with the effect of deleting the domain.

VII. Obligation to comply with the law


  • The registrant declares that the registered domain name does not violate the rights of third parties, in particular, the right of protection under trademark registration, under patent protection, the right to a press title, proprietary and personal copyrights, the right to a company name, as well as other exclusive rights afforded to third parties under law or international agreements. The registered domain name must not violate the personal rights of third parties, in particular, contain content considered offensive or restricted by law. The Registrar reserves the right to seek indemnification from the Registrant in the event that third parties assert their claims against the Registrar for registering the domain name in question.
  • If the Registrar acquires knowledge about the Registrant's use of the service in violation of this Agreement or the law, the Registrar shall have the right to process the Registrant's personal data in order to determine the Registrant's liability, and to provide such data to the relevant public authorities.
  • If the Registrar obtains credible knowledge of the unlawful nature of the data provided by the Registrant, the Registrar has the right to prevent access to such data, as well as to block the service provided.
  • Any disputes arising from infringement of third-party rights will be resolved through arbitration in accordance with the UDRP documents adopted by ICANN, as well as the RDRP. These documents, which are annexed to this Agreement, are available at https://www.icann.org. The registrant declares that he has read and accepts those documents.
  • Due to the requirements of ICANN, the Registrant declares that in the event that the domain dispute is resolved in accordance with Section VII.4 in a manner unfavorable to the Registrant, the Registrant accepts the possibility of suspension of the domain, as well as the possibility that the Registrant may lose the right to use the domain and that the right may be transferred to another entity named in the final judgment.
  • In the situation described in Section VII. 5, the Domain Registration Agreement concluded between the Registrant and the Registrar shall be terminated.
  • The above-described settlement of disputes by an arbitration court shall not exclude the jurisdiction of Polish courts for cases arising under this Agreement. Any disputes that may arise from the Agreement between the Registrant and Registrar, which cannot be prevented using the complaint procedure, will be settled by a common court of law with jurisdiction over the seat of Registrar. The above indication of the court's jurisdiction does not apply to Registrants who are Consumers residing in the European Union. The Registrar's registered office shall be deemed as he place of provision of the domain registration service.
  • The Registrant shall be solely responsible for any unlawful use of the domain, which includes responsibility for third parties to whom he makes the domain available for use, unless he discloses the identity and contact information of the aforementioned third parties, within the limits of applicable law, to the person who reports the violation within 7 days of obtaining information about the violation.

VIII. Complaint procedure


  • A complaint must be made in writing under pain of nullity, by submitting through the Partner a statement with a handwritten signature, using a qualified electronic signature or in the form of a regular e-mail sent from the contact email address in the Partner's ICT system. The complaint should specify:
    1. the Registrant's data enabling contact with the him/her, including data enabling identification of the person making the complaint as the Registrant,
    2. the name of the domain to which it applies,
    3. Registrant's allegations,
    4. the circumstances justifying the complaint,
    5. the requested remedy, if any, for the alleged violation.
  • The Registrar is obliged to respond to the complaint in the form of an email, within 14 days from the date of its receipt from the Partner, indicating whether it recognises the complaint and how it intends to resolve it, or informing about the lack of grounds for recognizing the complaint with the reasons for its position. If it is necessary to clarify additional circumstances related to services provided to the Registrar by entities for which the Registrar is not responsible, the Registrar shall send to the Partner, within 7 days, notification of the need to clarify such circumstances. The response to the complaint shall be sent to the Partner, who shall be required to deliver such response to the Registrant, in accordance with the complaint procedure under the agreement between the Partner and the Registrant.

IX. Modifications of the Agreement


  • The Registrar reserves the right to modify this Agreement as may be necessary in order to comply with: the provisions of the agreements with ICANN, the provisions of the agreements with Registry Operators, the provisions of the Annexes and other documents applicable to the Registrar. The Registrar shall inform the Registrant about any modification of the Agreement by e-mail to the Registrant's e-mail address or administrative address or through the Partner. In the event of a modification of this Agreement, a Registrant who is a Consumer residing in the territory of the European Union shall have the right to object within 14 days after the Registrar or its Partner informs the Registrant of the modification of the Agreement. This period for a Registrant that is not a Consumer is 7 days. Failure to file an objection will mean that the Registrant accepts the amended content of the Agreement in its entirety.
  • The Registrant shall provide the notice referred to in Section IX.1 in writing under pain of nullity by submitting the notice with a handwritten signature or using a qualified electronic signature. A Registrant who is a consumer residing in the territory of the European Union may also make this statement in the form of an ordinary email sent from the contact email address in the Partner's ICT system.
  • If the Registrant files an objection, the Registrar has the right to treat the objection as an offer to terminate the Domain Registration Agreement before its term. The objection should be filed through the Partner and it should include all the Registrant's data, as well as the name of the Internet domain.

X. Final Provisions


  • The relationship between the Registrar and the Registrant is governed exclusively by the provisions of the substantive law of the Republic of Poland. The above provision shall not limit the rights acquired under the law by a consumer residing in the territory of the European Union.
  • Any termination, expiration or invalidity of the contract between the Partner and the Registrant necessitates the conclusion of a new contract between the Registrant and the Partner selected by the Registrant until the end of the Subscription Period. If such an agreement is not concluded before the end of this period, the Registrar has the right to refuse to renew the domain. In the event of termination, expiration or invalidity of the contract between the Partner and the Registrant, the Registrar will not provide administrative and technical support for the Registrant's domain on its own.
  • A Registrant who is a Consumer residing in the territory of the European Union has the right to withdraw from the Domain Registration Agreement without giving reasons within 14 days from the date of its conclusion. This withdrawal shall be effected by submitting a statement to the Partner, who is obliged to relay such a statement to the Registrar.
  • Any and all matters related to registration of a domain, its administrative and technical support, transfer and deletion of the domain shall be handled by the Registrar through the Partner. The Registrant shall not contact the Registrar, Registry Operators or ICANN directly for this purpose.
  • The Registrant agrees not to disseminate ICANN's and Registry Operators' contact information, in the form of telephone number, fax number or email address, in particular by including such information in the Whois database.
  • The Registrar, subject to due diligence, shall not be responsible for the failure of the domain registration and changes in the data for which the domain has been registered, for reasons beyond its control including those of the cooperating Registry Operators or Partners.
  • The registrar is not responsible for a domain being blocked or deleted for reasons beyond its control.
  • The Registrar's liability shall be limited to the value of the domain registration fees paid by the Registrant. The Registrar shall not be liable for the Registrant's lost benefits.
  • The Registrar shall not be liable for the consequences of unlawful actions of the Registrant and for the consequences of the steps taken to remedy any unlawful behavior of the Registrant.
  • The Registrar shall not be liable for the Partner's acts or omissions arising in connection with the contract between the Partner and the Registrant.
  • The Partner shall be responsible for all acts and omissions of the Registrant resulting from this Agreement.
  • The provisions of this Agreement contained in Section II.10 and Section X.8 shall not be binding with respect to a Registrant who is a Consumer residing in the European Union.
  • In matters not regulated herein, generally applicable laws shall apply, and the provisions of this Agreement shall not exclude the application of mandatory laws.
  • This Agreement is binding upon the Registrant from the moment the Registrant places a domain registration order through the Partner.
  • Should any provisions of the Agreement be found to be legally invalid or ineffective, this circumstance will not affect the validity and effectiveness of the remaining provisions, unless it is clear from the circumstance that, without the invalid or ineffective provision, the contract between the Registrar and the Registrant would not have been concluded.
  • The Model Agreement for domain registration with NetArt Registrar Sp. z o.o. is effective as of 07.12.2023.

Uniform Domain Name Dispute Resolution Policy



Policy Adopted: August 26, 1999
Implementation Documents Approved: October 24, 1999


Notes:

1. This policy is now in effect. See www.icann.org/udrp/udrp-schedule.htm for the implementation schedule.

2. This policy has been adopted by all accredited domain-name registrars for domain names ending in .com, .net, and .org. It has also been adopted by certain managers of country-code top-level domains (e.g., .nu, .tv, .ws).

3. The policy is between the registrar (or other registration authority in the case of a country-code top-level domain) and its customer (the domain-name holder or registrant). Thus, the policy uses "we" and "our" to refer to the registrar and it uses "you" and "your" to refer to the domain-name holder.



Uniform Domain Name Dispute Resolution Policy


(As Approved by ICANN on October 24, 1999)


1. Purpose


This Uniform Domain Name Dispute Resolution Policy (the "Policy") has been adopted by the Internet Corporation for Assigned Names and Numbers ("ICANN"), is incorporated by reference into your Registration Agreement, and sets forth the terms and conditions in connection with a dispute between you and any party other than us (the registrar) over the registration and use of an Internet domain name registered by you. Proceedings under Paragraph 4 of this Policy will be conducted according to the Rules for Uniform Domain Name Dispute Resolution Policy (the "Rules of Procedure"), which are available at www.icann.org/udrp/udrp-rules-24oct99.htm, and the selected administrative-dispute-resolution service provider's supplemental rules.


2. Your Representations


By applying to register a domain name, or by asking us to maintain or renew a domain name registration, you hereby represent and warrant to us that (a) the statements that you made in your Registration Agreement are complete and accurate; (b) to your knowledge, the registration of the domain name will not infringe upon or otherwise violate the rights of any third party; (c) you are not registering the domain name for an unlawful purpose; and (d) you will not knowingly use the domain name in violation of any applicable laws or regulations. It is your responsibility to determine whether your domain name registration infringes or violates someone else's rights.

3. Cancellations, Transfers, and Changes

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

a. subject to the provisions of Paragraph 8, our receipt of written or appropriate electronic instructions from you or your authorized agent to take such action;

b. our receipt of an order from a court or arbitral tribunal, in each case of competent jurisdiction, requiring such action; and/or

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

We may also cancel, transfer or otherwise make changes to a domain name registration in accordance with the terms of your Registration Agreement or other legal requirements.



4. Mandatory Administrative Proceeding


This Paragraph sets forth the type of disputes for which you are required to submit to a mandatory administrative proceeding. These proceedings will be conducted before one of the administrative-dispute-resolution service providers listed at www.icann.org/en/dndr/udrp/approved-providers.htm (each, a "Provider").

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

(i) your domain name is identical or confusingly similar to a trademark or service mark in which the complainant has rights; and

(ii) you have no rights or legitimate interests in respect of the domain name; and

(iii) your domain name has been registered and is being used in bad faith.

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

b. Evidence of Registration and Use in Bad Faith. For 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 and use of a domain name in bad faith:

(i) circumstances indicating that you have registered or you have acquired the domain name primarily for the purpose of selling, renting, or otherwise transferring the domain name registration to the complainant who is the owner of the trademark or service mark or to a competitor of that complainant, for valuable consideration in excess of your documented out-of-pocket costs directly related to the domain name; or

(ii) you have registered the domain name in order to prevent the owner of the trademark or service mark from reflecting the mark in a corresponding domain name, provided that you have engaged in a pattern of such conduct; or

(iii) you have registered the domain name primarily for the purpose of disrupting the business of a competitor; or

(iv) by using the domain name, you have intentionally attempted to attract, for commercial gain, Internet users to your web site or other on-line location, by creating a likelihood of confusion with the complainant's mark as to the source, sponsorship, affiliation, or endorsement of your web site or location or of a product or service on your web site or location.

c. How to Demonstrate Your Rights to and Legitimate Interests in the Domain Name in Responding to a Complaint. When you receive a complaint, you should refer to Paragraph 5 of the Rules of Procedure in determining how your 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 your rights or legitimate interests to the domain name for purposes of Paragraph 4(a)(ii):

(i) before any notice to you of the dispute, your use of, or demonstrable preparations to use, the domain name or a name corresponding to the domain name in connection with a bona fide offering of goods or services; or

(ii) you (as an individual, business, or other organization) have been commonly known by the domain name, even if you have acquired no trademark or service mark rights; or

(iii) you are making a legitimate noncommercial or fair use of the domain name, without intent for commercial gain to misleadingly divert consumers or to tarnish the trademark or service mark at issue.

d. 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).

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

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

g. Fees. All fees charged by a Provider in connection with any dispute before an Administrative Panel pursuant to this Policy shall be paid by the complainant, except in cases where you elect to expand 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 and the complainant.

h. Our Involvement in Administrative Proceedings. We do not, and will not, participate in the administration or conduct of any proceeding before an Administrative Panel. In addition, we will not be liable as a result of any decisions rendered by the Administrative Panel.

i. Remedies. The remedies available to a complainant pursuant to any proceeding before an Administrative Panel shall be limited to requiring the cancellation of your domain name or the transfer of your domain name registration to the complainant.

j. Notification and Publication. The Provider shall notify us of any decision made by an Administrative Panel with respect to a domain name you have registered with us. All decisions under this Policy will be published in full over the Internet, except when an Administrative Panel determines in an exceptional case to redact portions of its decision.

k. Availability of Court Proceedings. The mandatory administrative proceeding requirements set forth in Paragraph 4 shall not prevent either you or the complainant from submitting the dispute to a court of competent jurisdiction for independent resolution before such mandatory administrative proceeding is commenced or after such proceeding is concluded. If an Administrative Panel decides that your domain name registration should be canceled or transferred, we will wait ten (10) business days (as observed in the location of our principal office) after we are informed by the applicable Provider of the Administrative Panel's decision before 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 or of your address as shown in our Whois database. See Paragraphs 1 and 3(b)(xiii) of the Rules of Procedure for details.) If we receive such documentation within the ten (10) business day period, we will not implement the Administrative Panel's decision, and we will take no further action, until we receive (i) evidence satisfactory to us of a resolution between the parties; (ii) evidence satisfactory to us that your lawsuit has been dismissed or withdrawn; or (iii) a copy of an order from such court dismissing your lawsuit or ordering that you do not have the right to continue to use your domain name.


5. All Other Disputes and Litigation


All other disputes between you and any party other than us regarding your domain name registration that are not brought pursuant to the mandatory administrative proceeding provisions of Paragraph 4 shall be resolved between you and such other party through any court, arbitration or other proceeding that may be available.


6. Our Involvement in Disputes


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


7. Maintaining the Status Quo


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


8. Transfers During a Dispute


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

b. Changing Registrars. You may not transfer your domain name registration to another registrar during a pending administrative proceeding brought pursuant to Paragraph 4 or for 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 your domain name registration to another registrar during a pending court action or arbitration, provided that the domain name you have registered with us shall continue to be subject to the proceedings commenced against you in accordance with the terms of this Policy. In the event that you transfer a domain name registration to us during the pendency of a court action or arbitration, such dispute shall remain subject to the domain name dispute policy of the registrar from which the domain name registration was transferred.


9. Maintaining the Status Quo


We reserve the right to modify this Policy at any time with the permission of ICANN. We will post our revised Policy at least thirty (30) calendar days before 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 domain name registration dispute, whether the dispute arose before, on or after the effective date of our change. In the event that you object to a change in this Policy, your sole remedy is to cancel your domain 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 your domain name registration.

Rules for Uniform Domain Name Dispute Resolution Policy



Rules for Uniform Domain Name Dispute Resolution Policy (the "Rules")


These Rules are in effect for all UDRP proceedings in which a complaint is submitted to a provider on or after 31 July 2015. The prior version of the Rules, applicable to all proceedings in which a complaint was submitted to a Provider on or before 30 July 2015, is at https://www.icann.org/resources/pages/rules-be-2012-02-25-en. UDRP Providers may elect to adopt the notice procedures set forth in these Rules prior to 31 July 2015.


Administrative proceedings for the resolution of disputes under the Uniform Dispute Resolution Policy adopted by ICANN shall be governed by these Rules and also the Supplemental Rules of the Provider administering the proceedings, as posted on its web site. To the extent that the Supplemental Rules of any Provider conflict with these Rules, these Rules supersede.


1. Definitions

In these Rules:

Complainant means the party initiating a complaint concerning a domain-name registration.

ICANN refers to the Internet Corporation for Assigned Names and Numbers.

Lock means a set of measures that a registrar applies to a domain name, which prevents at a minimum any modification to the registrant and registrar information by the Respondent, but does not affect the resolution of the domain name or the renewal of the domain name.

Mutual Jurisdiction means a court jurisdiction at the location of either (a) the principal office of the Registrar (provided the domain-name holder has submitted in its Registration Agreement to that jurisdiction for court adjudication of disputes concerning or arising from the use of the domain name) or (b) the domain-name holder's address as shown for the registration of the domain name in Registrar's Whois database at the time the complaint is submitted to the Provider.

Panel means an administrative panel appointed by a Provider to decide a complaint concerning a domain-name registration.

Panelist means an individual appointed by a Provider to be a member of a Panel.

Party means a Complainant or a Respondent.

Pendency means the time period from the moment a UDRP complaint has been submitted by the Complainant to the UDRP Provider to the time the UDRP decision has been implemented or the UDRP complaint has been terminated.

Policy means the Uniform Domain Name Dispute Resolution Policy that is incorporated by reference and made a part of the Registration Agreement.

Provider means a dispute-resolution service provider approved by ICANN. A list of such Providers appears at www.icann.org/udrp/approved-providers.htm.

Registrar means the entity with which the Respondent has registered a domain name that is the subject of a complaint.

Registration Agreement means the agreement between a Registrar and a domain-name holder.

Respondent means the holder of a domain-name registration against which a complaint is initiated.

Reverse Domain Name Hijacking means using the Policy in bad faith to attempt to deprive a registered domain-name holder of a domain name.

Supplemental Rules means the rules adopted by the Provider administering a proceeding to supplement these Rules. Supplemental Rules shall not be inconsistent with the Policy or these Rules and shall cover such topics as fees, word and page limits and guidelines, the means for communicating with the Provider and the Panel, and the form of cover sheets.


2. Communications


(a) When forwarding a complaint to the Respondent, it shall be the Provider's responsibility to employ reasonably available means calculated to achieve actual notice to Respondent. Achieving actual notice, or employing the following measures to do so, shall discharge this responsibility:

(i) sending the complaint to all postal-mail and facsimile addresses (A) shown in the domain name's registration data in Registrar's Whois database for the registered domain-name holder, the technical contact, and the administrative contact and (B) supplied by Registrar to the Provider for the registration's billing contact; and

(ii) sending the complaint in electronic form (including annexes to the extent available in that form) by e-mail to:

(A) the e-mail addresses for those technical, administrative, and billing contacts;

(B) postmaster@<the contested domain name>; and

(C) if the domain name (or "www." followed by the domain name) resolves to an active web page (other than a generic page the Provider concludes is maintained by a registrar or ISP for parking domain-names registered by multiple domain-name holders), any e-mail address shown or e-mail links on that web page; and

(iii) sending the complaint to any address the Respondent has notified the Provider it prefers and, to the extent practicable, to all other addresses provided to the Provider by Complainant under Paragraph 3(b)(v).

(b) Except as provided in Paragraph 2(a), any written communication to Complainant or Respondent provided for under these Rules shall be made by the preferred means stated by the Complainant or Respondent, respectively (see Paragraphs 3(b)(iii) and 5(c)(iii)), or in the absence of such specification

(i) by telecopy or facsimile transmission, with a confirmation of transmission; or

(ii) by postal or courier service, postage pre-paid and return receipt requested; or

(iii) electronically via the Internet, provided a record of its transmission is available.

(c) Any communication to the Provider or the Panel shall be made by the means and in the manner (including number of copies) stated in the Provider's Supplemental Rules.

(d) Communications shall be made in the language prescribed in Paragraph 11. E-mail communications should, if practicable, be sent in plaintext.

(e) Either Party may update its contact details by notifying the Provider and the Registrar.

(f) Except as otherwise provided in these Rules, or decided by a Panel, all communications provided for under these Rules shall be deemed to have been made:

(i) if delivered by telecopy or facsimile transmission, on the date shown on the confirmation of transmission; or

(ii) if by postal or courier service, on the date marked on the receipt; or

(iii) if via the Internet, on the date that the communication was transmitted, provided that the date of transmission is verifiable.

(g) Except as otherwise provided in these Rules, all time periods calculated under these Rules to begin when a communication is made shall begin to run on the earliest date that the communication is deemed to have been made in accordance with Paragraph 2(f).

(h) Any communication by

(i) a Panel to any Party shall be copied to the Provider and to the other Party;

(ii) the Provider to any Party shall be copied to the other Party; and

(iii) a Party shall be copied to the other Party, the Panel and the Provider, as the case may be.

(i) It shall be the responsibility of the sender to retain records of the fact and circumstances of sending, which shall be available for inspection by affected parties and for reporting purposes.

(j) In the event a Party sending a communication receives notification of non-delivery of the communication, the Party shall promptly notify the Panel (or, if no Panel is yet appointed, the Provider) of the circumstances of the notification. Further proceedings concerning the communication and any response shall be as directed by the Panel (or the Provider).


3. The Complaint

(a) Any person or entity may initiate an administrative proceeding by submitting a complaint in accordance with the Policy and these Rules to any Provider approved by ICANN. (Due to capacity constraints or for other reasons, a Provider's ability to accept complaints may be suspended at times. In that event, the Provider shall refuse the submission. The person or entity may submit the complaint to another Provider.)

(b) The complaint shall be submitted in hard copy and (except to the extent not available for annexes) in electronic form and shall:

(i) Request that the complaint be submitted for decision in accordance with the Policy and these Rules;

(ii) Provide the name, postal and e-mail addresses, and the telephone and telefax numbers of the Complainant and of any representative authorized to act for the Complainant in the administrative proceeding;

(iii) Specify a preferred method for communications directed to the Complainant in the administrative proceeding (including person to be contacted, medium, and address information) for each of (A) electronic-only material and (B) material including hard copy;

(iv) Designate whether Complainant elects to have the dispute decided by a single-member or a three-member Panel and, in the event Complainant elects a three-member Panel, provide the names and contact details of three candidates to serve as one of the Panelists (these candidates may be drawn from any ICANN-approved Provider's list of panelists);

(v) Provide the name of the Respondent (domain-name holder) and all information (including any postal and e-mail addresses and telephone and telefax numbers) known to Complainant regarding how to contact Respondent or any representative of Respondent, including contact information based on pre-complaint dealings, in sufficient detail to allow the Provider to send the complaint as described in Paragraph 2(a);

(vi) Specify the domain name(s) that is/are the subject of the complaint;

(vii) Identify the Registrar(s) with whom the domain name(s) is/are registered at the time the complaint is filed;

(viii) Specify the trademark(s) or service mark(s) on which the complaint is based and, for each mark, describe the goods or services, if any, with which the mark is used (Complainant may also separately describe other goods and services with which it intends, at the time the complaint is submitted, to use the mark in the future.);

(ix) Describe, in accordance with the Policy, the grounds on which the complaint is made including, in particular,

(1) the manner in which the domain name(s) is/are identical or confusingly similar to a trademark or service mark in which the Complainant has rights; and

(2) why the Respondent (domain-name holder) should be considered as having no rights or legitimate interests in respect of the domain name(s) that is/are the subject of the complaint; and

(3) why the domain name(s) should be considered as having been registered and being used in bad faith

(The description should, for elements (2) and (3), discuss any aspects of Paragraphs 4(b) and 4(c) of the Policy that are applicable. The description shall comply with any word or page limit set forth in the Provider's Supplemental Rules.);

(x) Specify, in accordance with the Policy, the remedies sought;

(xi) Identify any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the complaint;

(xii) State that Complainant will submit, with respect to any challenges to a decision in the administrative proceeding canceling or transferring the domain name, to the jurisdiction of the courts in at least one specified Mutual Jurisdiction;

(xiii) Conclude with the following statement followed by the signature of the Complainant or its authorized representative:

"Complainant agrees that its claims and remedies concerning the registration of the domain name, the dispute, or the dispute's resolution shall be solely against the domain-name holder and waives all such claims and remedies against (a) the dispute-resolution provider and panelists, except in the case of deliberate wrongdoing, (b) the registrar, (c) the registry administrator, and (d) the Internet Corporation for Assigned Names and Numbers, as well as their directors, officers, employees, and agents."

"Complainant certifies that the information contained in this Complaint is to the best of Complainant's knowledge complete and accurate, that this Complaint is not being presented for any improper purpose, such as to harass, and that the assertions in this Complaint are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument."; and

(xiv) Annex any documentary or other evidence, including a copy of the Policy applicable to the domain name(s) in dispute and any trademark or service mark registration upon which the complaint relies, together with a schedule indexing such evidence.

(c) The complaint may relate to more than one domain name, provided that the domain names are registered by the same domain-name holder.


4. Notification of Complaint


(a) The Provider shall submit a verification request to the Registrar. The verification request will include a request to Lock the domain name.

(b) Within two (2) business days of receiving the Provider’s verification request, the Registrar shall provide the information requested in the verification request and confirm that a Lock of the domain name has been applied. The Registrar shall not notify the Respondent of the proceeding until the Lock status has been applied. The Lock shall remain in place through the remaining Pendency of the UDRP proceeding. Any updates to the Respondent’s data, such as through the result of a request by a privacy or proxy provider to reveal the underlying customer data, must be made before the two (2) business day period concludes or before the Registrar verifies the information requested and confirms the Lock to the UDRP Provider, whichever occurs first. Any modification(s) of the Respondent’s data following the two (2) business day period may be addressed by the Panel in its decision.

(c) The Provider shall review the complaint for administrative compliance with the Policy and these Rules and, if in compliance, shall forward the complaint (together with the explanatory cover sheet prescribed by the Provider's Supplemental Rules) to the Respondent, in the manner prescribed by Paragraph 2(a), within three (3) calendar days following receipt of the fees to be paid by the Complainant in accordance with Paragraph 19.

(d) If the Provider finds the complaint to be administratively deficient, it shall promptly notify the Complainant and the Respondent of the nature of the deficiencies identified. The Complainant shall have five (5) calendar days within which to correct any such deficiencies, after which the administrative proceeding will be deemed withdrawn without prejudice to submission of a different complaint by Complainant.

e) If the Provider dismisses the complaint due to an administrative deficiency, or the Complainant voluntarily withdraws its complaint, the Provider shall inform the Registrar that the proceedings have been withdrawn, and the Registrar shall release the Lock within one (1) business day of receiving the dismissal or withdrawal notice from the Provider.

(f) The date of commencement of the administrative proceeding shall be the date on which the Provider completes its responsibilities under Paragraph 2(a) in connection with forwarding the Complaint to the Respondent.

(g) The Provider shall immediately notify the Complainant, the Respondent, the concerned Registrar(s), and ICANN of the date of commencement of the administrative proceeding. The Provider shall inform the Respondent that any corrections to the Respondent’s contact information during the remaining Pendency of the UDRP proceedings shall be communicated to the Provider further to Rule 5(c)(ii) and 5(c)(iii).


5. The Response


(a) Within twenty (20) days of the date of commencement of the administrative proceeding the Respondent shall submit a response to the Provider.

(b) The Respondent may expressly request an additional four (4) calendar days in which to respond to the complaint, and the Provider shall automatically grant the extension and notify the Parties thereof. This extension does not preclude any additional extensions that may be given further to 5(d) of the Rules.

(c) The response shall be submitted in hard copy and (except to the extent not available for annexes) in electronic form and shall:

(i) Respond specifically to the statements and allegations contained in the complaint and include any and all bases for the Respondent (domain-name holder) to retain registration and use of the disputed domain name (This portion of the response shall comply with any word or page limit set forth in the Provider's Supplemental Rules.);

(ii) Provide the name, postal and e-mail addresses, and the telephone and telefax numbers of the Respondent (domain-name holder) and of any representative authorized to act for the Respondent in the administrative proceeding;

(iii) Specify a preferred method for communications directed to the Respondent in the administrative proceeding (including person to be contacted, medium, and address information) for each of (A) electronic-only material and (B) material including hard copy;

(iv) If Complainant has elected a single-member panel in the Complaint (see Paragraph 3(b)(iv)), state whether Respondent elects instead to have the dispute decided by a three-member panel;

(v) If either Complainant or Respondent elects a three-member Panel, provide the names and contact details of three candidates to serve as one of the Panelists (these candidates may be drawn from any ICANN-approved Provider's list of panelists);

(vi) Identify any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the complaint;

(vii) State that a copy of the response has been sent or transmitted to the Complainant, in accordance with Paragraph 2(b); and

(viii) Conclude with the following statement followed by the signature of the Respondent or its authorized representative:

"Respondent certifies that the information contained in this Response is to the best of Respondent's knowledge complete and accurate, that this Response is not being presented for any improper purpose, such as to harass, and that the assertions in this Response are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument."; and

(ix) Annex any documentary or other evidence upon which the Respondent relies, together with a schedule indexing such documents.

(d) If Complainant has elected to have the dispute decided by a single-member Panel and Respondent elects a three-member Panel, Respondent shall be required to pay one-half of the applicable fee for a three-member Panel as set forth in the Provider's Supplemental Rules. This payment shall be made together with the submission of the response to the Provider. In the event that the required payment is not made, the dispute shall be decided by a single-member Panel.

(e) At the request of the Respondent, the Provider may, in exceptional cases, extend the period of time for the filing of the response. The period may also be extended by written stipulation between the Parties, provided the stipulation is approved by the Provider.

(f) If a Respondent does not submit a response, in the absence of exceptional circumstances, the Panel shall decide the dispute based upon the complaint.


6. Appointment of the Panel and Timing of Decision


(a) Each Provider shall maintain and publish a publicly available list of panelists and their qualifications.

(b) If neither the Complainant nor the Respondent has elected a three-member Panel (Paragraphs 3(b)(iv) and 5(c)(iv)), the Provider shall appoint, within five (5) calendar days following receipt of the response by the Provider, or the lapse of the time period for the submission thereof, a single Panelist from its list of panelists. The fees for a single-member Panel shall be paid entirely by the Complainant.

(c) If either the Complainant or the Respondent elects to have the dispute decided by a three-member Panel, the Provider shall appoint three Panelists in accordance with the procedures identified in Paragraph 6(e). The fees for a three-member Panel shall be paid in their entirety by the Complainant, except where the election for a three-member Panel was made by the Respondent, in which case the applicable fees shall be shared equally between the Parties.

(d) Unless it has already elected a three-member Panel, the Complainant shall submit to the Provider, within five (5) calendar days of communication of a response in which the Respondent elects a three-member Panel, the names and contact details of three candidates to serve as one of the Panelists. These candidates may be drawn from any ICANN-approved Provider's list of panelists.

(e) In the event that either the Complainant or the Respondent elects a three-member Panel, the Provider shall endeavor to appoint one Panelist from the list of candidates provided by each of the Complainant and the Respondent. In the event the Provider is unable within five (5) calendar days to secure the appointment of a Panelist on its customary terms from either Party's list of candidates, the Provider shall make that appointment from its list of panelists. The third Panelist shall be appointed by the Provider from a list of five candidates submitted by the Provider to the Parties, the Provider's selection from among the five being made in a manner that reasonably balances the preferences of both Parties, as they may specify to the Provider within five (5) calendar days of the Provider's submission of the five-candidate list to the Parties.

(f) Once the entire Panel is appointed, the Provider shall notify the Parties of the Panelists appointed and the date by which, absent exceptional circumstances, the Panel shall forward its decision on the complaint to the Provider.


7. Impartiality and Independence


A Panelist shall be impartial and independent and shall have, before accepting appointment, disclosed to the Provider any circumstances giving rise to justifiable doubt as to the Panelist's impartiality or independence. If, at any stage during the administrative proceeding, new circumstances arise that could give rise to justifiable doubt as to the impartiality or independence of the Panelist, that Panelist shall promptly disclose such circumstances to the Provider. In such event, the Provider shall have the discretion to appoint a substitute Panelist.


8. Communication Between Parties and the Panel


No Party or anyone acting on its behalf may have any unilateral communication with the Panel. All communications between a Party and the Panel or the Provider shall be made to a case administrator appointed by the Provider in the manner prescribed in the Provider's Supplemental Rules.


9. Transmission of the File to the Panel


The Provider shall forward the file to the Panel as soon as the Panelist is appointed in the case of a Panel consisting of a single member, or as soon as the last Panelist is appointed in the case of a three-member Panel.


10. General Powers of the Panel


(a) The Panel shall conduct the administrative proceeding in such manner as it considers appropriate in accordance with the Policy and these Rules.

(b) In all cases, the Panel shall ensure that the Parties are treated with equality and that each Party is given a fair opportunity to present its case.

(c) The Panel shall ensure that the administrative proceeding takes place with due expedition. It may, at the request of a Party or on its own motion, extend, in exceptional cases, a period of time fixed by these Rules or by the Panel.

(d) The Panel shall determine the admissibility, relevance, materiality and weight of the evidence.

(e) A Panel shall decide a request by a Party to consolidate multiple domain name disputes in accordance with the Policy and these Rules.


11. Language of Proceedings


(a) Unless otherwise agreed by the Parties, or specified otherwise in the Registration Agreement, the language of the administrative proceeding shall be the language of the Registration Agreement, subject to the authority of the Panel to determine otherwise, having regard to the circumstances of the administrative proceeding.

(b) The Panel may order that any documents submitted in languages other than the language of the administrative proceeding be accompanied by a translation in whole or in part into the language of the administrative proceeding.


12. Further Statements


In addition to the complaint and the response, the Panel may request, in its sole discretion, further statements or documents from either of the Parties.


13. In-Person Hearings


There shall be no in-person hearings (including hearings by teleconference, videoconference, and web conference), unless the Panel determines, in its sole discretion and as an exceptional matter, that such a hearing is necessary for deciding the complaint.


14. Default


(a) In the event that a Party, in the absence of exceptional circumstances, does not comply with any of the time periods established by these Rules or the Panel, the Panel shall proceed to a decision on the complaint.

(b) If a Party, in the absence of exceptional circumstances, does not comply with any provision of, or requirement under, these Rules or any request from the Panel, the Panel shall draw such inferences therefrom as it considers appropriate.


15. Panel Decisions


(a) A Panel shall decide a complaint on the basis of the statements and documents submitted and in accordance with the Policy, these Rules and any rules and principles of law that it deems applicable.

(b) In the absence of exceptional circumstances, the Panel shall forward its decision on the complaint to the Provider within fourteen (14) days of its appointment pursuant to Paragraph 6.

(c) In the case of a three-member Panel, the Panel's decision shall be made by a majority.

(d) The Panel's decision shall be in writing, provide the reasons on which it is based, indicate the date on which it was rendered and identify the name(s) of the Panelist(s).

(e) Panel decisions and dissenting opinions shall normally comply with the guidelines as to length set forth in the Provider's Supplemental Rules. Any dissenting opinion shall accompany the majority decision. If the Panel concludes that the dispute is not within the scope of Paragraph 4(a) of the Policy, it shall so state. If after considering the submissions the Panel finds that the complaint was brought in bad faith, for example in an attempt at Reverse Domain Name Hijacking or was brought primarily to harass the domain-name holder, the Panel shall declare in its decision that the complaint was brought in bad faith and constitutes an abuse of the administrative proceeding.


16. Communication of Decision to Parties


(a) Within three (3) business days after receiving the decision from the Panel, the Provider shall communicate the full text of the decision to each Party, the concerned Registrar(s), and ICANN. The concerned Registrar(s) shall within three (3) business days of receiving the decision from the Provider communicate to each Party, the Provider, and ICANN the date for the implementation of the decision in accordance with the Policy.

(b) Except if the Panel determines otherwise (see Paragraph 4(j) of the Policy), the Provider shall publish the full decision and the date of its implementation on a publicly accessible web site. In any event, the portion of any decision determining a complaint to have been brought in bad faith (see Paragraph 15(e) of these Rules) shall be published.


17. Settlement or Other Grounds for Termination


(a) If, before the Panel's decision, the Parties agree on a settlement, the Panel shall terminate the administrative proceeding. A settlement shall follow steps 17(a)(i)17(a)(vii):

(i) The Parties provide written notice of a request to suspend the proceedings because the parties are discussing settlement to the Provider.

(ii) The Provider acknowledges receipt of the request for suspension and informs the Registrar of the suspension request and the expected duration of the suspension.

(iii) The Parties reach a settlement and provide a standard settlement form to the Provider further to the Provider's supplemental rules and settlement form. The standard settlement form is not intended to be an agreement itself, but only to summarize the essential terms of the Parties' separate settlement agreement. The Provider shall not disclose the completed standard settlement form to any third party.

(iv) The Provider shall confirm to the Registrar, copying the Parties, the outcome of the settlement as it relates to actions that need to be taken by the Registrar.

(v) Upon receiving notice from the Provider further to 17(a)(iv), the Registrar shall remove the Lock within two (2) business days.

(vi) The Complainant shall confirm to the Provider that the settlement as it relates to the domain name(s) has been implemented further to the Provider’s supplemental rules.

(vii) The Provider will dismiss the proceedings without prejudice unless otherwise stipulated in the settlement.

(b) If, before the Panel's decision is made, it becomes unnecessary or impossible to continue the administrative proceeding for any reason, the Panel shall terminate the administrative proceeding, unless a Party raises justifiable grounds for objection within a period of time to be determined by the Panel.


18. Effect of Court Proceedings


(a) In the event of any legal proceedings initiated prior to or during an administrative proceeding in respect of a domain-name dispute that is the subject of the complaint, the Panel shall have the discretion to decide whether to suspend or terminate the administrative proceeding, or to proceed to a decision.

(b) In the event that a Party initiates any legal proceedings during the Pendency of an administrative proceeding in respect of a domain-name dispute that is the subject of the complaint, it shall promptly notify the Panel and the Provider. See Paragraph 8 above.


19. Fees


(a) The Complainant shall pay to the Provider an initial fixed fee, in accordance with the Provider's Supplemental Rules, within the time and in the amount required. A Respondent electing under Paragraph 5(c)(iv) to have the dispute decided by a three-member Panel, rather than the single-member Panel elected by the Complainant, shall pay the Provider one-half the fixed fee for a three-member Panel. See Paragraph 5(d). In all other cases, the Complainant shall bear all of the Provider's fees, except as prescribed under Paragraph 19(d). Upon appointment of the Panel, the Provider shall refund the appropriate portion, if any, of the initial fee to the Complainant, as specified in the Provider's Supplemental Rules.

(b) No action shall be taken by the Provider on a complaint until it has received from Complainant the initial fee in accordance with Paragraph 19(a).

(c) If the Provider has not received the fee within ten (10) calendar days of receiving the complaint, the complaint shall be deemed withdrawn and the administrative proceeding terminated.

(d) In exceptional circumstances, for example in the event an in-person hearing is held, the Provider shall request the Parties for the payment of additional fees, which shall be established in agreement with the Parties and the Panel.


20. Exclusion of Liability


Except in the case of deliberate wrongdoing, neither the Provider nor a Panelist shall be liable to a Party for any act or omission in connection with any administrative proceeding under these Rules.

21. Amendments

The version of these Rules in effect at the time of the submission of the complaint to the Provider shall apply to the administrative proceeding commenced thereby. These Rules may not be amended without the express written approval of ICANN.

Transfer Policy


I. Inter-Registrar Transfer


A. Holder-Authorized Transfers


1. Registrar Requirements


Registered Name Holders must be able to transfer their domain name registrations between Registrars provided that the Gaining Registrar's transfer process meets the minimum standards of this policy and that such transfer is not prohibited by ICANN or Registry policies. Inter-Registrar domain name transfer processes must be clear and concise in order to avoid confusion. Further, Registrars should make reasonable efforts to inform Registered Name Holders of, and provide access to, the published documentation of the specific transfer process employed by the Registrars.

1.1 Transfer Authorities

The Administrative Contact and the Registered Name Holder, as listed in the Losing Registrar's or applicable Registry's (where available) publicly accessible WHOIS service are the only parties that have the authority to approve or deny a transfer request to the Gaining Registrar. In the event of a dispute, the Registered Name Holder's authority supersedes that of the Administrative Contact.

Registrars may use Whois data from either the Registrar of Record or the relevant Registry for the purpose of verifying the authenticity of a transfer request; or from another data source as determined by a consensus policy.


2. Gaining Registrar Requirements


For each instance where a Registered Name Holder requests to transfer a domain name registration to a different Registrar, the Gaining Registrar shall:

2.1 Obtain express authorization from either the Registered Name Holder or the Administrative Contact (hereafter, "Transfer Contact"). Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Transfer Contact.

2.1.1 The authorization must be made via a valid Standardized Form of Authorization (FOA). There are two different FOAs available at the ICANN website. The FOA labeled "Initial Authorization for Registrar Transfer" must be used by the Gaining Registrar to request an authorization for a registrar transfer from the Transfer Contact. The FOA labeled "Confirmation of Registrar Transfer Request" must be used by the Registrar of Record to request confirmation of the transfer from the Transfer Contact.

The FOA shall be communicated in English, and any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Transfer Contact in additional languages. However, Registrars choosing to exercise such option are responsible for the accuracy and completeness of the translation into such additional non-English version of the FOA.

2.1.2 In the event that the Gaining Registrar relies on a physical process to obtain this authorization, a paper copy of the FOA will suffice insofar as it has been signed by the Transfer Contact and further that it is accompanied by a physical copy of the Registrar of Record's Whois output for the domain name in question.

2.1.2.1 If the Gaining Registrar relies on a physical authorization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Transfer Contact and maintaining appropriate records proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden for ensuring that the entity making the request is indeed authorized to do so. The acceptable forms of physical identity are:

a. Notarized statement,

b. Valid Drivers license,

c. Passport,

d. Article of Incorporation,

e. Military ID,

f. State/government issued ID,

g. Birth certificate.

g. Birth certificate.

2.1.3.1 In the event that the Gaining Registrar relies on an electronic process to obtain this authorization the acceptable forms of identity would include:

a. Electronic signature in conformance with national legislation, in the location of the Gaining Registrar (if such legislation exists).

b. Consent from an individual or entity that has an email address or phone number matching the Transfer Contact email address or phone number.

2.1.3.2 The Registrar of Record may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set forth above.

2.1.3.3 A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received and authenticated the transfer request made by a Transfer Contact.

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

2.2.1 Transmission of a "transfer" command constitutes a representation on the part of the Gaining Registrar that the requisite authorization has been obtained from the Transfer Contact listed in the authoritative Whois database.

2.2.2 The Gaining Registrar is responsible for validating the Registered Name Holder requests to transfer domain names between Registrars. However, the Registrar of Record must still transmit an FOA in accordance with Section I.A.3 ("Obligations of the Registrar of Record") of this policy.

2.2.3 The FOA labeled "Initial Authorization for Registrar Transfer" shall expire under the following circumstances:

2.2.3.1 a period of sixty (60) days has passed since the FOA was issued by the Gaining Registrar, unless the Gaining Registrar allows automatic renewal of the FOA and the Registered Name Holder has expressly opted in to the automatic renewal;

2.2.3.2 the domain name expires before the inter-registrar transfer is completed;

2.2.3.3 a Change of Registrant is completed further to Section II.C;

2.2.3.4 the inter-registrar transfer is completed.

2.2.4 If the FOA expires pursuant to one of the aforementioned circumstances described in I.A.2.2.3.1 – I.A.2.2.3.4, prior to submitting the "transfer" request to the registry, in order to proceed with the transfer, the Gaining Registrar must re-authorize the transfer request via a new FOA.


3. Obligations of the Registrar of Record


3.1 A Registrar of Record shall confirm the intent of the Registered Name Holder when a notice of a pending transfer is received from the Registry by notifying the Registered Name Holder of the transfer. The Registrar of Record must do so in a manner consistent with the standards set forth in this policy.

3.2 In order to ensure that the form of the request employed by the Registrar of Record is substantially administrative and informative in nature and clearly provided to the Transfer Contact for the purpose of verifying the intent of the Transfer Contact, the Registrar of Record must use the FOA.

3.3 The FOA shall be communicated in English, and any dispute arising out of a transfer request, shall be conducted in the English language. Registrars may choose to communicate with the Transfer Contact in additional languages. However, the Registrar choosing to exercise such option is responsible for the accuracy and completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes and procedures set forth in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional information to the FOA used to obtain the consent of the Transfer Contact in the case of a transfer request.

In the event the Registered Name Holder preapproves a transfer, the Registrar of Record has the option of sending a modified version of the FOA, which informs the Registered Name Holder that the preapproved transfer has been initiated.

This requirement does not preclude the Registrar of Record from marketing to its existing customers through separate communications.

3.4 The FOA should be sent by the Registrar of Record to the Registered Name Holder as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operator.

3.5 Failure by the Registrar of Record 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.

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

3.7 Upon denying a transfer request for any of the following reasons, the Registrar of Record must provide the Registered Name Holder and the potential Gaining Registrar with the reason for denial. The Registrar of Record may deny a transfer request only in the following specific instances:

3.7.1 Evidence of fraud.

3.7.2 Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact.

3.7.3 No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.

3.7.4 Express objection to the transfer by the authorized Transfer Contact. Objection could take the form of specific request (either by paper or electronic means) by the authorized Transfer Contact to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the authorized Transfer Contact on an opt-in basis and upon request by the authorized Transfer Contact, the Registrar must remove the lock or provide a reasonably accessible method for the authorized Transfer Contact to remove the lock within five (5) calendar days.

3.7.5 The transfer was requested within 60 days of the creation date as shown in the registry Whois record for the domain name.

3.7.6 A domain name is within 60 days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs). "Transferred" shall only mean that an inter-registrar transfer has occurred in accordance with the procedures of this policy.

3.8 The Registrar of Record must deny a transfer request in the following circumstances:

3.8.1 A pending UDRP proceeding that the Registrar has been informed of;

3.8.2 Court order by a court of competent jurisdiction;

3.8.3 Pending dispute related to a previous transfer pursuant to the Transfer Dispute Resolution Policy;

3.8.4 URS proceeding or URS suspension that the Registrar has been informed of;

3.8.5 The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request.

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

3.9.1 Nonpayment for a pending or future registration period;

3.9.2 No response from the Registered Name Holder or Administrative Contact;

3.9.3 Domain name in Registrar Lock Status, unless the Registered Name Holder is provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request;

3.9.4 Domain name registration period time constraints, other than during the first 60 days of initial registration, during the first 60 days after a registrar transfer, or during the 60-day lock following a Change of Registrant pursuant to Section II.C.2;

3.9.5 General payment defaults between Registrar and business partners / affiliates in cases where the Registered Name Holder for the domain in question has paid for the registration.

3.10 The Registrar of Record has other mechanisms available to collect payment from the Registered Name Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Record must not employ transfer processes as a mechanism to secure payment for services from a Registered Name Holder. Exceptions to this requirement are as follows:

3.10.1 In the case of non-payment for previous registration period(s) if the transfer is requested after the expiration date, or

3.10.2 In the case of non-payment of the current registration period, if transfer is requested before the expiration date.


4. Registrar Coordination


4.1 Each Registrar is responsible for keeping copies of documentation, including the FOA and the Transfer Contacts response thereto, that may be required for filing and supporting a dispute under the dispute resolution policy. Gaining Registrars must maintain copies of the FOA as received from the Transfer Contact as per the standard document retention policies of the contracts. Copies of the reliable evidence of identity must be kept with the FOA.

4.2 Both the Gaining Registrar and the Registrar of Record must provide the evidence relied on for the transfer during and after the applicable inter-registrar domain name transaction(s). Such information must be provided when requested by, and only by, the other Registrar that is party to the transfer transaction. Additionally, ICANN, the Registry Operator, a court or authority with jurisdiction over the matter or a third party dispute resolution panel may also require such information within five (5) days of the request.

4.3 The Gaining Registrar must retain, and produce pursuant to a request by a Losing Registrar, a written or electronic copy of the FOA. In instances where the Registrar of Record has requested copies of the FOA, the Gaining Registrar must fulfill the Registrar of Record's request (including providing the attendant supporting documentation) within five (5) calendar days. Failure to provide this documentation within the time period specified is grounds for reversal by the Registry Operator or the Dispute Resolution Panel in the event that a transfer complaint is filed in accordance with the requirements of this policy.

4.4 If either a Registrar of Record or a Gaining Registrar does not believe that a transfer request was handled in accordance with the provisions of this policy, then the Registrar may initiate a dispute resolution procedure as set forth in Section I.C of this policy.

4.5.1 This email address is for issues related to transfer requests and the procedures set forth in this policy only;

4.5.2 The email address should be managed to ensure messages are received by someone who can respond to the transfer issue;

4.5.3 Messages received at such email address must be responded to within a commercial reasonable timeframe not to exceed seven (7) calendar days.

4.6 Transfer Emergency Action Contact

4.6.1 Registrars will establish a Transfer Emergency Action Contact ("TEAC") for urgent communications relating to transfers. The goal of the TEAC is to quickly establish a real-time conversation between registrars (in a language that both parties can understand) in an emergency. Further actions can then be taken towards a resolution, including initiating existing (or future) transfer dispute or undo processes.

4.6.2 Communications to TEACs will be reserved for use by ICANN-Accredited Registrars, gTLD Registry Operators and ICANN Staff. The TEAC point of contact may be designated as a telephone number or some other real-time communication channel and will be recorded in, and protected by, the ICANN registrar portal. Communications to a TEAC must be initiated in a timely manner, within a reasonable period of time following the alleged unauthorized loss of a domain.

4.6.3 Messages sent via the TEAC communication channel must generate a non-automated response by a human representative of the Gaining Registrar. The person or team responding must be capable and authorized to investigate and address urgent transfer issues. Responses are required within 4 hours of the initial request, although final resolution of the incident may take longer.

4.6.4 The Losing Registrar will report failures to respond to a TEAC communication to ICANN Compliance and the registry operator. Failure to respond to a TEAC communication may result in a transfer-undo in accordance with Section I.A.6.4 of this policy and may also result in further action by ICANN, up to and including non-renewal or termination of accreditation.

4.6.5 Both parties will retain correspondence in written or electronic form of any TEAC communication and responses, and share copies of this documentation with ICANN and the registry operator upon request. This documentation will be retained in accordance with Section 3.4 of the Registrar Accreditation Agreement (RAA). Users of the TEAC communication channel should report non-responsive Registrars to ICANN. Additionally, ICANN may conduct periodic tests of the Registrar TEAC communication channel in situations and a manner deemed appropriate to ensure that registrars are indeed responding to TEAC messages.


5. Requirements for the “ClientTransferProhibited” Status and “AuthInfo” Codes


5.1 Subject to ICANN specifications or policies and any applicable laws or regulations, Registrars must follow the requirements set forth below.

Registrars may only set a domain name in "ClientTransferProhibited" status upon registration or subsequent request by the Registered Name Holder, provided, however, that the Registrar includes in its registration agreement (obtaining the express consent of the Registered Name Holder) the terms and conditions upon which it prohibits transfer of the domain name. Further, the Registrar must remove the "ClientTransferProhibited" status within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to remove the "ClientTransferProhibited" status.

5.2 Registrars must provide the Registered Name Holder with the unique "AuthInfo" code and remove the "ClientTransferProhibited" within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to generate and manage their own unique "AuthInfo" code and to remove the "ClientTransferProhibited" status.

5.3 Registrars may not employ any mechanism for complying with a Registered Name Holder's request to remove the "ClientTransferProhibited" status or obtain the applicable "AuthInfo Code" that is more restrictive than the mechanisms used for changing any aspect of the Registered Name Holder's contact or name server information.

5.4 The Registrar of Record must not refuse to remove the "ClientTransferProhibited" status or release an "AuthInfo Code" to the Registered Name Holder solely because there is a dispute between the Registered Name Holder and the Registrar over payment.

5.5 Registrar-generated "AuthInfo" codes must be unique on a per-domain basis.

5.6 The "AuthInfo" codes must be used solely to identify a Registered Name Holder, whereas the FOAs still need to be used for authorization or confirmation of a transfer request, as described in Section I.A.2 and Section I.A.4 of this policy.


6. Registry Requirements


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

6.2 The Registry Operator shall complete the requested transfer unless, within five (5) calendar days, Registry Operator receives a NACK protocol command from the Registrar of Record.

6.3 When the Registry's database has been updated to reflect the change to the Gaining Registrar, Registry Operator will transmit an electronic notification to both Registrars. The notification may be sent to the unique email address established by each Registrar for the purpose of facilitating transfers or such other email address agreed to by the parties.

6.4 The Registry Operator shall undo a transfer if, after a transfer has occurred, the Registry Operator receives one of the notices as set forth below. In such case, the transfer will be reversed and the Registrar of Record field reset to its original state. The Registry Operator 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 Operator must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:

6.4.1 Agreement of the Registrar of Record and the Gaining Registrar sent by email, letter or fax that the transfer was made by mistake or was otherwise not in accordance with the procedures set forth in this policy;

6.4.2 The final determination of a dispute resolution body having jurisdiction over the transfer; or

6.4.3 Order of a court having jurisdiction over the transfer;

6.4.4 Documentation provided by the Registrar of Record prior to transfer that the Gaining Registrar has not responded to a message via the TEAC within the timeframe specified in Section I.A.4.6.


7. Records of Registration


Each Registrar shall require its customer, the Registered Name Holder, to maintain its own records appropriate to document and prove the initial domain name registration date.


8. Effect on Term of Registration


The completion by Registry Operator of a holder-authorized transfer under Section I.A shall result in a one-year extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years.


B. ICANN-Approved Transfers


1. Transfer of the sponsorship of all the registrations sponsored by one Registrar as the result of (i) acquisition of that Registrar or its assets by another Registrar, or (ii) lack of accreditation of that Registrar or lack of its authorization with the Registry Operator, may be made according to the following procedure:

1.1 The gaining Registrar must be accredited by ICANN for the Registry TLD and must have in effect a Registry-Registrar Agreement with Registry Operator for the Registry TLD.

1.2 ICANN must certify in writing to Registry Operator that the transfer would promote the community interest, such as the interest in stability that may be threatened by the actual or imminent business failure of a Registrar.

2. Upon satisfaction of these two conditions, Registry Operator will make the necessary one-time changes in the Registry database for no charge, for transfers involving 50,000 name registrations or fewer. If the transfer involves registrations of more than 50,000 names, Registry Operator will charge the gaining Registrar a one-time flat fee of US$ 50,000.


C. Transfer Dispute Resolution Policy


Procedures for handling disputes concerning inter-registrar transfers are set forth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operators and ICANN accredited Registrars.


II. Inter-Registrant Transfer (Change of Registrant)


A. Definitions

1. This policy uses the following terms:

1.1 "Change of Registrant" means a Material Change to any of the following:

1.1.1 Prior Registrant name

1.1.2 Prior Registrant organization

1.1.3 Prior Registrant email address

1.1.4 Administrative Contact email address, if there is no Prior Registrant email address.

1.2 "Designated Agent" means an individual or entity that the Prior Registrant or New Registrant explicitly authorizes to approve a Change of Registrant on its behalf.

1.3 "Material Change" means a change which is not a typographical correction. The following will be considered material changes:

1.3.1 A change to the Registered Name Holder's name or organization that does not appear to be merely a typographical correction;

1.3.2 Any change to the Registered Name Holder's name or organization that is accompanied by a change of address or phone number;

1.3.3 Any change to the Registered Name Holder's email address.

1.4 "Prior Registrant" means the Registered Name Holder at the time a Change of Registrant is initiated.

1.5 "New Registrant" means the entity or person to whom the Prior Registrant proposes to transfer its domain name registration.


B. Availability of Change of Registrant


1. In general, registrants must be permitted to update their registration/Whois data and transfer their registration rights to other registrants freely.

2. A Registrar must deny a Change of Registrant request under the following circumstances:

2.1 The domain name registration agreement has expired, and the Registered Name Holder no longer has the right to renew or transfer the domain name to another registrar, as provided for in Section 2.2.5 of the Expired Registration Recovery Policy;

2.2 The Change of Registrant was not properly authorized by the Prior Registrant and the New Registrant, further to Section II.C below;

2.3 The domain name is subject to a domain name related dispute, including but not limited to:

2.3.1 A pending UDRP proceeding that the Registrar has been informed of;

2.3.2 A pending URS proceeding that the Registrar has been informed of;

2.3.3 A pending TDRP proceeding;

2.3.4 A court order by a court of competent jurisdiction, prohibiting a Change of Registrant, that the Registrar has been informed of.

3. In the following circumstances, the Change of Registrant process described in Section II.C below does not apply:

3.1 the registration agreement expires;

3.2 the registration agreement is terminated by the Registrar;

3.3 the Registrar or Registry Operator updates the Prior Registrant's information pursuant to a court order;

3.4 the Registrar updates the Prior Registrant's information in the implementation of a UDRP decision;

3.5 the Registrar updates the Prior Registrant's information in accordance with the Expired Domain Deletion Policy;

3.6 the Registrar updates the Prior Registrant's information in response to an abuse complaint.


C. Change of Registrant Process


1. To process a Change of Registrant from the Prior Registrant to a New Registrant, the Registrar must do all of the following:

1.1 Confirm the domain name is eligible for Change of Registrant further to Section II.B;

1.2 Obtain confirmation of the Change of Registrant request from the New Registrant, or a Designated Agent of the New Registrant. The Registrar must use a secure mechanism to confirm that the New Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the New Registrant or its Designated Agent, if applicable, that the New Registrant must enter into a registration agreement with the Registrar (a link to the registration agreement itself can be provided). The Registrar must also inform the New Registrant or Designated Agent, if applicable, that the request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days;

1.3 Inform the Prior Registrant or its Designated Agent that if its final goal is to transfer the domain name to a different registrar, the Prior Registrant is advised to request the inter-registrar transfer before the Change of Registrant to avoid triggering the 60-day lock described in Section II.C.2 (unless the Registrar gave the Prior Registrant the option to opt out of the 60-day lock, and the Prior Registrant opted out the 60-day lock);

1.4 Upon or after informing the Prior Registrant or its Designated Agent, if applicable, as described in II.C.1.3 above, obtain confirmation of the Change of Registrant request from the Prior Registrant, or the Designated Agent of the Prior Registrant. The Registrar must use a secure mechanism to confirm that the Prior Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the Prior Registrant or Designated Agent, if applicable, that the Change of Registrant request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days;

1.5 Process the Change of Registrant within one (1) day of obtaining the confirmations described above;

1.6 Notify the Prior Registrant and New Registrant before or within one day of the completion of the Change of Registrant. The notification must:

1.6.1 always be sent to both the New Registrant and Prior Registrant before or within one day of the Change of Registrant being performed;

1.6.2 explain the request that was received and list the domain(s) in question;

1.6.3. include contact information for questions;

1.6.4. advise the Prior Registrant and New Registrant of the 60-day inter-registrar transfer lock as described in Section II.C.2 or advise the Prior Registrant that it previously opted out of the 60-day inter-registrar transfer lock as described in Section II.C.2.

2. The Registrar must impose a 60-day inter-registrar transfer lock following a Change of Registrant, provided, however, that the Registrar may allow the Registered Name Holder to opt out of the 60-day inter-registrar transfer lock prior to any Change of Registrant request.


Registrar Transfer Dispute Resolution Policy



In any dispute relating to Inter-Registrar domain name transfers, Registrars are encouraged to first of all attempt to resolve the problem among the Registrars involved in the dispute. In cases where this is unsuccessful and where a registrar elects to file a dispute, the following procedures apply. It is very important for Registrars to familiarize themselves with the Transfer Dispute Resolution Policy (TDRP) as described in this document before filing a dispute. Transfer dispute resolution fees can be substantial. It is critical that Registrars fully understand the fees that must be paid, which party is responsible for paying those fees and when and how those fees must be paid.

This version of the TDRP and corresponding procedures will apply to all Complaints filed on or after 1 December 2016.


1. Definitions


1.1 Complainant

A party bringing a Complaint under the TDRP. A Complainant may be either a Losing Registrar (in the case of an alleged fraudulent transfer) or a Gaining Registrar (in the case of an improper NACK) under this Policy.

1.2 Complaint

The initial document in a TDRP proceeding that provides the allegations and claims brought by the Complainant against the Respondent.

1.3 Dispute Resolution Panel

The Dispute Resolution Panel shall mean an administrative panel appointed by a Dispute Resolution Provider ("Provider") to decide a Complaint concerning a dispute under the TDRP.

1.4 Dispute Resolution Provider

The Dispute Resolution Provider must be an independent and neutral third party that is neither associated nor affiliated with the Respondent, Complainant, or the Registry Operator under which the disputed domain name is registered. ICANN shall have the authority to accredit one or more independent and neutral Dispute Resolution Providers according to criteria developed in accordance with the TDRP.

1.5 Form of Authorization – FOA

The standardized form of consent that the Gaining Registrar and Losing Registrar are required to use to obtain authorization from the Registrant or Administrative Contact in order to properly process the transfer of domain name sponsorship from one Registrar to another.

1.6 Gaining Registrar

The registrar who seeks to become the Registrar of Record by submitting a transfer request.

1.7 Invalid Transfer

A transfer that is found non-compliant with the Transfer Policy.

1.8 Losing Registrar

The registrar who was the Registrar of Record at the time a request for the transfer of domain is submitted.

1.9 NACK

A denial of a request for transfer by the Losing Registrar.

1.10 Registrant

The individual, organization, or entity that holds the right to use a specific domain name for a specified period of time.

1.11 Registrar of Record

The Registrar who sponsors a domain name at the registry.

1.12 Registry (Registry Operator)

The organization authorized by ICANN to provide registration services for a given TLD to ICANN-accredited Registrars.

1.13 Respondent

A party against whom a Complaint is brought. Under the TDRP, the Respondent can be a Losing Registrar in the case of an improper (NACK), a Gaining Registrar in the case of an alleged fraudulent transfer, or the Registrar of Record.

1.14 Supplemental Rules

The Supplemental Rules shall mean those rules adopted by the Provider administering a proceeding to supplement the TDRP. Supplemental Rules shall be consistent with the TDRP and shall cover topics such as fees, word and page limits and guidelines, the means for communicating with the Provider, and the form of cover sheets.

1.15 Transfer Policy

The ICANN Consensus Policy governing the transfer of sponsorship of registrations between registrars as referenced in the Registry-Registrar Agreement executed between a Registrar and the Registry, as well as the Registrar Accreditation Agreement which is executed between ICANN and all ICANN - accredited registrars.


2. Dispute Resolution Process


2.1 Filing a Complaint

The Complainant may file a Complaint with a Dispute Resolution Provider. The decision of the Dispute Resolution Panel is final, except as it may be appealed to a court of competent jurisdiction in accordance with Section 3.4 of the TDRP.

2.2 Statute of Limitations

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



3. Dispute Procedures


3.1 Registrar files a Request for Enforcement with a Dispute Resolution Provider

3.1.1 Either the Gaining Registrar or Losing Registrar may submit a Complaint. This must be done in accordance with the Supplemental Rules adopted by the applicable Dispute Resolution Provider.

3.1.2 The Complaint shall be submitted to the Dispute Resolution Provider and to the Respondent in electronic form and shall:

(i) Request that the Complaint be submitted for decision in accordance with the TDRP and the applicable Supplemental Rules;

(ii) Provide the name, postal and e-mail addresses, and the telephone and fax numbers of the Complainant and those representatives authorized by the Complainant to act on behalf of the Complainant in the administrative proceeding;

(iii) Provide the name of the Respondent and all information (including any postal and e-mail addresses and telephone and fax numbers) known to  Complainant regarding how to contact Respondent or any representative of Respondent, including contact information based on pre-complaint dealings;

(iv) Specify the domain name(s) that is/are the subject of the Complaint;

(v) Specify the incident(s) that gave rise to the dispute;

(vi) Describe, in accordance with the Transfer Policy, the grounds on which the Complaint is based;

(vii) State the specific remedy being sought (either approval or denial of the transfer);

(viii) Identify any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the Complaint;

(ix) Certify that a copy of the Complaint, together with the cover sheet as prescribed by the Provider's Supplemental Rules, has been sent or transmitted to the Respondent; and

(x) Conclude with the following statement followed by the signature of the Complainant or its authorized representative:

"<insert name of  Complainant> agrees that its claims and remedies concerning the registration of the domain name, the dispute, or the dispute's resolution shall be solely against the Respondent and waives all such claims and remedies against the Dispute Resolution Provider as well as its directors, officers, employees, and agents, except in the case of deliberate wrongdoing or gross negligence."

"<insert name of Complainant> certifies that the information contained in this Complaint is to the best of  Complainant's knowledge complete and accurate, that this Complaint is not being presented for any improper purpose, such as to harass, and that the assertions in this Complaint are warranted under the TDRP and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument."

3.1.3 The Complaint may relate to more than one domain name, provided that the domain names involve the same Complainant and Respondent and that the claims arise out of the same or similar factual circumstances.

3.1.4 The Complaint shall annex the following documentary evidence (as applicable and available) in electronic form if possible, together with a schedule indexing such evidence:

(i) For the Gaining Registrar:

a. Completed Form of Authorization ("FOA"),

b. Copy of the Whois output for the date transfer was initiated, which was used to identify the authorized Transfer Contacts,

c. Copy of evidence of identity used,

d. Copy of a bilateral agreement, final determination of a dispute resolution body or court order in cases when the Registrant of Record is being changed simultaneously with a Registrar Transfer,

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

(ii) For the Losing Registrar:

a. Completed FOA from the Losing Registrar,

b. Copy of the Whois output for the date the transfer was initiated,

c. Relevant history of Whois modifications made to the applicable registration,

d. Evidence of one of the following if a transfer was denied:

  • fraud;
  • Pending UDRP proceeding that the Registrar has been informed of;
  • URS proceeding or URS Suspension that the Registrar has been informed of;
  • Pending dispute under the Transfer Dispute Resolution Policy;
  • court order by a court of competent jurisdiction;
  • Registrant or administrative contact identity dispute in accordance with Section 4 of the Transfer Policy [Registrar of Record Requirements];
  • applicable payment dispute along with evidence that the registration was put on HOLD status;
  • express written objection from the Registered Name Holder or Administrative Contact;
  • LOCK status along with proof of a reasonable means for the registrant to remove LOCK status as per Section __of Exhibit __ to this Agreement;
  • The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request.
  • domain name within 60 days of initial registration; or
  • domain name within 60 days of a prior transfer.

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

3.2 Respondent shall have seven (7) calendar days from receipt of the Complaint to prepare a Response to the Complaint ("Response").

3.2.1 The Response shall be submitted in electronic form to both the Dispute Resolution Provider and Complainant and shall:

(i) Respond specifically to the statements and allegations contained in the Complaint (This portion of the response shall comply with any word or page limit set forth in the Dispute Resolution Provider's Supplemental Rules.);

(ii) Provide the name, postal and e-mail addresses, and the telephone and fax numbers of the Respondent (non-filing Registrar);

(iii) Identify any other legal proceedings that have been commenced or terminated in connection with or relating to any of the domain name(s) that are the subject of the Complaint;

(iv) State that a copy of the Response has been sent or transmitted to the Complainant;

(v) Conclude with the following statement followed by the signature of the Respondent or its authorized representative:

"Respondent certifies that the information contained in this Response is to the best of Respondent's knowledge complete and accurate, that this Response is not being presented for any improper purpose, such as to harass, and that the assertions in this Response are warranted under these Rules and under applicable law, as it now exists or as it may be extended by a good-faith and reasonable argument."; and

(vi) Annex any documentary or other evidence upon which the Respondent relies, together with a schedule indexing such documents.

3.2.2 At the request of the Respondent, the Dispute Resolution Provider may, in exceptional cases, extend the period of time for the filing of the response, but in no case may the extension be more 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 Dispute Resolution Provider.

3.2.3 If a Respondent does not submit a response, in the absence of exceptional circumstances, the Dispute Resolution Panel appointed by the Dispute Resolution Provider shall decide the dispute based upon the Complaint.

3.2.4 The Dispute Resolution Panel appointed by the Dispute Resolution Provider must review all applicable documentation and compare registrant/contact data with that contained within the authoritative Whois database and reach a conclusion not later than thirty (30) days after receipt of Response from the Respondent.

(i) If the registrant/contact data does not match the data listed in authoritative Whois, the Dispute Resolution Panel should contact each Registrar and require additional documentation.

(ii) If the Gaining Registrar is unable to provide a complete FOA with data matching that contained within the authoritative Whois database at the time of the transfer request, then the Dispute Resolution Panel shall find that the transfer should be reversed. In the case of a thick Registry, if the Registrar of Record's Whois is not accessible or invalid, the applicable Registry Operator's Whois should be used. In the case of a thin Registry, if the Registrar of Record's Whois is not accessible or is invalid, the Dispute Resolution Provider may place the dispute on hold until such time as the problem is resolved.

(iii) In the case where a Losing Registrar NACKs a transfer, the Losing Registrar must provide evidence of one of the factors for which it is allowed to NACK as set forth in Section 3.1.4 (ii)(d) of the TDRP. If the Losing Registrar cannot provide evidence that demonstrates any of the factors, and the Gaining Registrar provides to the Dispute Resolution Provider a complete FOA with data matching that contained within the authoritative Whois database at the time of the transfer request, then the transfer should be approved.

(iv) The Dispute Resolution Panel may not issue a finding of "no decision." It must weigh the applicable evidence in light of the Transfer Policy and determine, based on a preponderance of the evidence, which Registrar should prevail in the dispute and what resolution to the Complaint will appropriately redress the issues set forth in the Complaint.

(v) Resolution options for the Dispute Resolution Panel are limited to the following:

a. Approve Transfer,

b. Deny the Transfer (This could include ordering the domain name
be returned to the Losing Registrar in cases where a Transfer has already occurred.)

(vi) Transfers from a Gaining Registrar to a third registrar, and all other subsequent transfers, are invalid if the Gaining Registrar acquired sponsorship of the domain name(s) at issue through an Invalid Transfer, as determined through the dispute resolution process set forth in this Transfer Dispute Resolution Policy.

(vii) In the event the Dispute Resolution Panel determines that an Invalid Transfer occurred, the domain shall be transferred back to the registrar that was Registrar of Record immediately prior to the Invalid Transfer.

3.3 Fees for Dispute Resolution Service

3.3.1 The applicable Dispute Resolution Provider shall determine the applicable filing fee ("Filing Fees"). The specific fees along with the terms and conditions governing the actual payment of such fees shall be included in the Dispute Resolution Provider’s Supplemental Rules.

3.3.2 In the event that the Complainant does not prevail in a dispute, the Filing Fees shall be retained by the Dispute Resolution Provider.

3.3.3 In the event that the Complainant prevails in a dispute, the Respondent, 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 Complainant, whichever applicable, the Filing Fees, no later than fourteen (14) calendar days after it receives the Filing Fees from the Respondent. Such fees must be paid regardless of whether a court proceeding is commenced in accordance with Section 3.4 below. Failure to pay Filing Fees to the Dispute Resolution Provider may result in the loss of accreditation by ICANN.

3.4 Availability of Court Proceedings

The procedures set forth above shall not prevent a Registrar from submitting a dispute to a court of competent jurisdiction for independent resolution before such administrative proceeding is commenced or after such proceeding is concluded. If a Dispute Resolution Panel decides a domain name registration should be transferred (either to the Gaining Registrar, or alternatively, back from the Gaining Registrar to the Losing Registrar), such Registrar will wait fourteen (14) calendar days after it is informed of the decision before 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 domain name(s). If 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 or withdrawn; or (iii) a copy of an order from such court dismissing the lawsuit or ordering certain actions with respect to the domain name.

3.5 Decision Publication

3.5.1. The relevant Dispute Resolution Provider shall publish any decision made with respect to a transfer dispute initiated under the TDRP. All decisions under this Policy will be published in full over the Internet except when the Panel, convened by the Dispute Resolution Provider, in an exceptional case, determines to redact portions of its decision. In any event, the portion of any decision determining a complaint to have been brought in bad faith shall be published.

3.5.2. Decision reports shall include, at a minimum:

(i) The domain name under dispute;

(ii) The names of parties involved in the dispute;

(iii) The full decision of the case;

(iv) The date of the implementation of the decision.

3.5.3 If the Dispute Resolution Provider believes a decision should not be published, the Dispute Resolution Provider should confer with ICANN and publish the decision if so directed.

3.5.4. Publication does not apply to TDRP Complaints filed prior to 1 December 2016.

Domain Name Registrants' Rights

These materials are available in English only.

.eu Domain Name Registration Agreemen (Polish version)


Umowa dotycząca rejestracji domeny .eu

w NetArt Registrar Sp. z o.o.

Niniejsza Umowa zawierana jest między NetArt Registrar Sp. z o.o. z siedzibą w Krakowie, ul. Pana Tadeusza 2, 30-727 Kraków, Polska, wpisaną do Rejestru Przedsiębiorców Krajowego Rejestru Sądowego prowadzonego przez Sąd Rejonowy dla Krakowa - Śródmieścia w Krakowie XI Wydział Gospodarczy KRS pod numerem 0000532637 z kapitałem zakładowym w wysokości 650.000 PLN (słownie: sześćset pięćdziesiąt tysięcy złotych), w całości wpłaconym, REGON: 120764285, NIP: 6751398383, zwaną w dalszej części Umowy "Rejestratorem", a Abonentem domeny internetowej reprezentowanym przez upoważnionego Partnera.


    I. Definicje


    1. Abonent - osoba fizyczna lub prawna, a także podmiot nieposiadający osobowości prawnej, któremu szczególne przepisy przyznają zdolność do czynności prawnych, który w celu rejestracji domeny internetowej zawiera z Rejestratorem niniejszą Umowę.
    2. Partner - podmiot upoważniony przez Abonenta do reprezentowania go przed Rejestratorem, posiadający jednocześnie stosowne porozumienie z Rejestratorem.
    3. Operator Rejestru - European Registry for Internet Domains vzw / asbl, Diamant Building, A. Reyerslaan 80, 1030 Brussels, Belgium, podmiot odpowiedzialny, zarządzający i zezwalający na rejestrację domen .eu.
    4. Konsument - osoba fizyczna zawierająca umowę niezwiązaną bezpośrednio z prowadzoną przez nią działalnością gospodarczą lub zawodową.
    5. WHOIS - ogólnodostępna baza danych Abonentów domen .eu.
    6. Domena internetowa (domena) - unikalny ciąg dozwolonych znaków alfanumerycznych, składający się z nazwy oraz rozszerzenia .eu
    7. Rejestracja domeny - umieszczenie nazwy domeny wraz z odpowiadającymi jej adresami serwerów nazw w bazie Operatora Rejestru.
    8. Kod AuthInfo - unikalny ciąg znaków, służący do dokonywania operacji na domenie, w tym do dokonywania jej transferu.
    9. Obsługa administracyjna i techniczna - zespół czynności niezbędnych do zarządzania domeną, które obejmują między innymi takie czynności jak: zarządzanie danymi przekazanymi przez Abonenta, udostępnienie systemów przetwarzania tych danych, wydawanie kodów AuthInfo, transfer oraz konfiguracja domeny.
    10. Okres abonamentowy - czas na jaki rejestrowana jest domena.
    11. ADR - ang. Alternative Dispute Resolution, tłum. Alternatywne Rozstrzyganie Sporów.

II. Postanowienia Ogólne


  1. NetArt Registrar Sp. z o.o. jest akredytowanym przez EURid Rejestratorem domen .eu. Korzystając z usług firmy NetArt Registrar Sp. z o.o. Abonent akceptuje warunki rejestracji domeny przedstawione w niniejszej Umowie, która jest zgodna z zasadami i warunkami ustalonymi przez EURid, dostępnymi pod adresem: https://eurid.eu/pl/strona-glowna/ tj. Warunkami rejestracji nazw domen .eu oraz Polityką rejestracyjną nazwa domen .eu oraz innymi dokumentami, do których one odsyłają (dalej „Warunki” i „Polityka”).
  2. Niniejsza Umowa nie stanowi upoważnienia dla Partnera do reprezentowania Rejestratora przed Abonentem.
  3. Zawarcie pomiędzy Abonentem a Rejestratorem niniejszej Umowy, następuje poprzez złożenie przez Abonenta i przekazanie Rejestratorowi za pośrednictwem Partnera:

    1. oświadczenia o akceptacji treści niniejszej Umowy,
    2. zamówienia rejestracji domeny skutkującego zarejestrowaniem jej przy użyciu systemu teleinformatycznego Partnera.
  4. Wszelkie obowiązki Abonenta wynikające z zawartej z Rejestratorem Umowy, Abonent wykonuje za pośrednictwem Partnera.
  5. Partner ponosi odpowiedzialność za istnienie i zakres umocowania do działania w imieniu Abonenta.
  6. Abonent przyjmuje do wiadomości i zgadza się, że rejestracja domeny odbywa się na zasadzie pierwszeństwa, w związku z czym Rejestrator nie może mu zagwarantować rejestracji wskazanej domeny.
  7. Abonent przyjmuje do wiadomości odpłatny charakter usługi rejestracji domeny i wyraża zgodę na dokonywanie płatności z tytułu rejestracji domeny, jeszcze przed jej zarejestrowaniem.
  8. Abonent oświadcza, iż zapoznał się z treścią niniejszej Umowy i ją w całości akceptuje.
  9. Abonent oświadcza, że żąda  rozpoczęcia procesu rejestracji domeny przed upływem 14 dni od daty prawidłowo złożonego zamówienia na stronie Partnera.
  10. Abonent przyjmuje do wiadomości, że podmiotem odpowiedzialnym za zobowiązanie do rejestracji domeny jest Rejestrator.

III. Obowiązki Partnera wobec Abonenta


  1. Partner zobowiązany jest przedstawić niniejszą Umowę Abonentowi przed przystąpieniem do procesu rejestracji domeny.
  2. Partner jest zobowiązany zapewnić obsługę administracyjną i techniczną rejestrowanej domeny, a w szczególności zapewnić dostęp do systemu teleinformatycznego umożliwiającego wprowadzanie danych osobowych podanych przez Abonenta, ich zmianę, a także zmianę konfiguracji domeny.
  3. Abonent ma możliwość dochodzenia roszczeń reklamacyjnych za niewykonanie lub niewłaściwe wykonanie Umowy o rejestrację domeny za pośrednictwem Partnera. Partner zobowiązany jest do przekazania reklamacji Abonenta Rejestratorowi, który rozstrzyga reklamację i przekazuje odpowiedź Partnerowi.

IV. Rejestracja Domeny


  1. Rejestracja domeny.eu odbywa się na podstawie:

    1. umowy akredytacyjnej zawartej pomiędzy Rejestratorem a European Registry for Internet Domains vzw / asbl, Diamant Building, A. Reyerslaan 80, 1030 Brussels, Belgium,
    2. umowy o reprezentację Abonenta przed Rejestratorem zawartej przez Abonenta z Partnerem.

  2. Obsługę administracyjną i techniczną dotyczącą rejestracji i utrzymania domeny wykonuje Partner na podstawie zawartej z Abonentem umowy o reprezentację Abonenta przed Rejestratorem.
  3. Rejestracja domeny następuje poprzez umieszczenie domeny w bazie Operatora Rejestru na wniosek Rejestratora. Rejestracja domeny odbywa się za pośrednictwem Partnera.
  4. W celu dokonania rejestracji Abonent zobowiązuje się podać za pośrednictwem Partnera następujące dane:

    1. imię i nazwisko albo pełną nazwę w przypadku podmiotów nie będących osobami fizycznymi,
    2. adres zamieszkania albo siedziby,
    3. numer PESEL albo inny numer ewidencyjny w sposób jednoznaczny identyfikujący Abonenta,
    4. adres poczty elektronicznej,
    5. numer telefonu oraz numer faksu o ile występuje.

  5. Abonent zobowiązuje się do podania prawdziwych danych oraz wyraża zgodę na ujawnienie ich w ogólnodostępnej bazie WHOIS w zakresie wskazanym w Warunkach i Polityce. Abonent przyjmuje do wiadomości, że Operator Rejestru ma prawo odrzucenia wniosku o rejestrację domeny lub wycofania nazwy domeny, dla której Abonent przedstawił dane niekompletne lub niedokładne.
  6. Abonent zobowiązuje się do dokonywania aktualizacji danych, o których mowa w pkt. IV.4 poprzez zawiadomienie o każdorazowej ich zmianie Partnera. Abonent zobowiązuje się do uaktualniania tych danych tak, aby były prawdziwe i kompletne
  7. Abonent przyjmuje do wiadomości i akceptuje możliwość umieszczenia w kwarantannie domeny lub anulowania domeny w przypadku naruszenia przez Abonenta Warunków lub Polityki.
  8. Rejestrator ponosi odpowiedzialność wobec Abonenta za zachowanie należytej staranności w procesie rejestracji domeny.
  9. Abonent przyjmuje do wiadomości, że rejestracja domeny następuje na czas określony, a zawarta pomiędzy Rejestratorem a Abonentem Umowa o rejestrację domeny wygasa z upływem ostatniego dnia Okresu abonamentowego. Abonent zostanie powiadomiony przez Partnera co najmniej dwukrotnie za pomocą poczty elektronicznej o zbliżającym się terminie upływu Okresu abonamentowego rejestracji domeny, w przypadku jej wygaśnięcia - Abonent otrzyma co najmniej jedno dodatkowe powiadomienie. Abonent gwarantuje, że podany przez niego adres e-mail jest adresem poprawnie działającym.
  10. Po wygaśnięciu Umowy o rejestrację domeny przez okres 40 dni Abonent posiada możliwość rejestracji domeny na kolejny Okres abonamentowy liczony każdorazowo od daty wygaśnięcia domeny (dalej: przywrócenie domeny). Przywrócenie takie jest odpłatne zgodnie z cennikiem dostępnym na stronie Partnera. Po upływie wyżej wskazanego terminu domena zostanie usunięta z bazy Rejestratora i bazy Operatora Rejestru.
  11. Abonent zobowiązuje się nie rejestrować domeny w złej wierze ani do celów niezgodnych z prawem.

V. Transfer Domeny


  1. Transfer domeny przebiega zgodnie z zasadami określonymi w Polityce.
  2. Transfer domeny do Rejestratora wymaga:

    1. złożenia zamówienia transferu za pośrednictwem Partnera,
    2. przekazania kodu AuthInfo kolejno: przez innego akredytowanego rejestratora Abonentowi, przez Abonenta Rejestratorowi za pośrednictwem Partnera i przez Rejestratora do Operatora Rejestru.

  3. Abonent ma możliwość zmiany podmiotu świadczącego usługę rejestracji domeny z Rejestratora na inny wybrany podmiot. W tym celu Abonent zwraca się do Rejestratora za pośrednictwem Partnera o wydanie kodu AuthInfo.
  4. Partner jest zobowiązany poinformować Abonenta o odrzuceniu transferu.
  5. W przypadku przeniesienia domeny od Rejestratora rozwiązaniu ulega niniejsza Umowa pomiędzy Abonentem a Rejestratorem.

VI. Ochrona Danych Osobowych


  1. Rejestrator ma prawo do przetwarzania danych osobowych Abonenta w postaci:

    1. imienia i nazwiska,
    2. adresu zamieszkania,
    3. numeru PESEL lub innego numeru ewidencyjnego jednoznacznie identyfikującego Abonenta,
    4. adresu poczty elektronicznej,
    5. numeru telefonu oraz numeru faksu o ile występuje,
    6. imienia i nazwiska osoby upoważnionej do składania oświadczeń woli w imieniu Abonenta niebędącego osobą fizyczną.

  2. W celu rejestracji domeny, oraz możliwości rejestracji domeny na kolejny Okres abonamentowy zgodnie z punktem IV.9, dobrowolne, aczkolwiek konieczne jest podanie danych określonych w pkt. VI.1. Dane te przekazywane są za pośrednictwem Partnera na potrzeby wykonania obowiązków Rejestratora wynikających z umowy akredytacyjnej z EURid
  3. Partner powinien zapewnić Abonentowi możliwość wglądu do jego danych i możliwość ich poprawiania. Wszelkie czynności związane z poprawianiem, uzupełnianiem, usunięciem danych osobowych Abonent może wykonywać za pośrednictwem Partnera.
  4. Rejestrator może przekazać dane osobowe Abonenta w celu wykonania postanowień umowy akredytacyjnej z EURid następującym podmiotom:
    1. European Registry for Internet Domains vzw / asbl, Diamant Building, A. Reyerslaan 80, 1030 Brussels, Belgium
  5. Abonent oświadcza, iż wyraża zgodę na przetwarzanie jego danych osobowych przez Rejestratora. Zgoda Abonenta obejmuje także zgodę na przetwarzanie danych przez podmiot wymieniony w pkt. VI. 4, a także zgodę na umieszczenie danych w bazie WHOIS. Abonent oświadcza ponadto, iż został poinformowany przez Partnera o:

    1. danych rejestrowych Rejestratora,
    2. celu i zakresie zbierania i przetwarzania danych Abonenta przez Rejestratora,
    3. prawie wglądu do swoich danych i ich poprawiania,
    4. uprawnieniach do żądania zaprzestania przetwarzania danych oraz prawie wniesienia sprzeciwu wobec przetwarzania danych, wynikających z art. 32 ust. 1 pkt 7 i 8 ustawy o ochronie danych osobowych (Dz. U. z 2015 r., poz. 2135).

  6. Rejestrator zobowiązuje się nie przetwarzać danych osobowych Abonenta w sposób sprzeczny z celem przetwarzania, a także sprzeczny z zasadami przetwarzania danych zawartymi w ustawie o ochronie danych osobowych.
  7. Rejestrator zobowiązuje się przedsięwziąć uzasadnione środki ostrożności mające na celu ochronę danych osobowych Abonenta przed utratą, niewłaściwym użyciem, nieupoważnionym dostępem lub ujawnieniem, zmianą lub zniszczeniem.
  8. Żądanie zaprzestania przetwarzania danych przez Abonenta, Rejestrator może traktować jako naruszenie przez Abonenta niniejszej Umowy ze skutkiem w postaci wyrejestrowania domeny.

VIII. Obowiązek Przestrzegania Prawa


  1. Abonent oświadcza, iż rejestrowana nazwa domeny nie narusza praw osób trzecich, w szczególności prawa ochronnego z tytułu rejestracji znaku towarowego, z tytułu ochrony patentowej, prawa do tytułu prasowego, praw autorskich majątkowych oraz osobistych, prawa do firmy, a także innych praw wyłącznych przyznanych przez przepisy prawa lub umowy międzynarodowe osobom trzecim. Rejestrowana nazwa domeny nie może naruszać dóbr osobistych osób trzecich, w szczególności zawierać treści uznawanych za obraźliwe, czy też zastrzeżonych na mocy przepisów prawa. Rejestrator zastrzega sobie prawo dochodzenia odszkodowania od Abonenta w przypadku gdyby osoby trzecie dochodziły swoich roszczeń względem Rejestratora z tytułu zarejestrowania danej nazwy domeny.
  2. W przypadku uzyskania przez Rejestratora informacji o korzystaniu z usługi przez Abonenta niezgodnie z niniejszą Umową lub z przepisami prawa, Rejestrator ma prawo przetwarzać dane osobowe Abonenta w celu ustalenia jego odpowiedzialności, a także przekazać te dane odpowiednim organom władzy publicznej.
  3. W przypadku uzyskania wiarygodnej wiadomości o bezprawnym charakterze danych dostarczonych przez Abonenta, Rejestrator ma prawo uniemożliwić dostęp do tych danych, a także zablokować świadczoną usługę.
  4. Spory wynikłe na tle naruszenia praw osób trzecich w przypadku wyboru procedury alternatywnego rozstrzygania sporów rozpatrywane będą przed jednym z dostawców usług wymienionych na stronie internetowej EURid (postępowanie ADR).
  5. Abonent przyjmuje do wiadomości, że ma obowiązek uczestniczyć w postępowaniu ADR w przypadkach określonych w Warunkach rejestracji nazw domen .eu dostępnych na stronie EURid.
  6. Abonent oświadcza, iż w przypadku rozpatrzenia sporu o domenę zgodnie z pkt. VII.4 w sposób dla niego niekorzystny, Abonent akceptuje możliwość zawieszenia domeny, a także możliwość utraty prawa do korzystania z domeny i przekazania go innemu podmiotowi wskazanemu w orzeczeniu kończącym postępowanie.
  7. W sytuacji opisanej w pkt. VII. 6 Umowa o rejestrację domeny zawarta pomiędzy Abonentem a Rejestratorem ulega rozwiązaniu.
  8. Opisane powyżej rozstrzyganie sporów przez sąd polubowny nie wyłącza właściwości sądów polskich dla spraw wynikłych na tle obowiązywania niniejszej Umowy. Wszelkie spory mogące wyniknąć z Umowy pomiędzy Abonentem a Rejestratorem, którym nie uda się zapobiec w drodze postępowania reklamacyjnego, rozstrzygane będą przez sąd powszechny, właściwy dla siedziby Rejestratora, z tym że w przypadku sporów z Abonentami będącymi konsumentami, sądem właściwym będzie sąd właściwy dla miejsca zamieszkania (siedziby) strony pozwanej. Strony zgodnie ustalają, iż miejscem świadczenia usługi rejestracji domeny jest siedziba Rejestratora.

VIII. Postępowanie Reklamacyjne


  1. Reklamacja Abonenta w związku z niewykonaniem lub nienależytym wykonaniem usług winna zostać przekazana Rejestratorowi za pośrednictwem Partnera w formie pisemnej i określać:
    1. dane Abonenta umożliwiające kontakt z nim,
    2. nazwę domeny, której dotyczy,
    3. zarzuty Abonenta,
    4. okoliczności uzasadniające reklamację,
    5. ewentualny żądany sposób usunięcia zarzucanego naruszenia.
  2. Rejestrator zobowiązany jest udzielić pisemnej odpowiedzi na reklamację, w terminie 14 dni od daty jej otrzymania od Partnera, wskazując, czy uznaje reklamację oraz w jaki sposób zamierza ją rozstrzygnąć lub informując o braku podstaw do uznania reklamacji wraz z uzasadnieniem swojego stanowiska. W przypadku konieczności wyjaśnienia dodatkowych okoliczności związanych z usługami świadczonymi na rzecz Rejestratora przez podmioty, za które Rejestrator nie ponosi odpowiedzialności, przesyła on Partnerowi w terminie 7 dni informację o potrzebie wyjaśnienia tych okoliczności. Odpowiedź na reklamację przekazywana jest Partnerowi, który zobowiązany jest dostarczyć taką odpowiedź Abonentowi, zgodnie z procedurą reklamacyjną wynikającą z umowy między Partnerem a Abonentem.

IX. Zmiana Umowy


  1. Rejestrator zastrzega sobie prawo zmiany niniejszej Umowy w sposób konieczny dla spełnienia postanowień umowy z EURid lub postanowień innych obowiązujących Rejestratora dokumentów określonych umową z EURid. O zmianie Umowy Rejestrator poinformuje Abonenta drogą elektroniczną na adres poczty e-mail Abonenta lub adres administracyjny lub też za pośrednictwem Partnera. W przypadku zmiany niniejszej Umowy, Abonent będący konsumentem ma prawo do wniesienia sprzeciwu w terminie 14 dni od chwili poinformowania Abonenta przez Rejestratora lub jego Partnera o zmianie Umowy. Termin ten dla Abonenta nie będącego Konsumentem wynosi 7 dni. Brak wniesienia sprzeciwu będzie oznaczał zaakceptowanie przez Abonenta zmienionej treści Umowy w całości.
  2. W przypadku wniesienia przez Abonenta sprzeciwu, Rejestrator ma prawo do potraktowania sprzeciwu jako oferty wcześniejszego rozwiązania Umowy o rejestrację domeny. Sprzeciw powinien być wniesiony w formie pisemnej za pośrednictwem Partnera oraz zawierać wszystkie dane Abonenta, a także nazwę domeny internetowej.

X. Postanowienia Końcowe

  1. Dla wykonywania niniejszej Umowy właściwe jest prawo polskie.
  2. Rozwiązanie, wygaśnięcie lub nieważność umowy między Partnerem a Abonentem powoduje konieczność zawarcia nowej umowy między Abonentem a wybranym przez niego Partnerem do końca Okresu abonamentowego. Jeżeli taka umowa nie zostanie zawarta przed końcem tego okresu, Rejestrator ma prawo odmówić ponownej rejestracji domeny. W przypadku rozwiązania, wygaśnięcia lub nieważności umowy między Partnerem a Abonentem, Rejestrator nie będzie zapewniał we własnym zakresie obsługi administracyjnej i technicznej dla domeny Abonenta.
  3. Abonent będący Konsumentem ma prawo odstąpienia od Umowy o rejestrację domeny bez podania przyczyn w terminie 14 dni od daty jej zawarcia. Odstąpienie to wykonuje się poprzez złożenie oświadczenia Partnerowi, który zobowiązany jest takie oświadczenie przekazać Rejestratorowi.
  4. Wszelkie sprawy związane z rejestracją domeny, jej obsługą administracyjną i techniczną, anulowaniem rejestracji, usunięciem domeny lub jej transferem będą rozpatrywane przez Rejestratora za pośrednictwem Partnera. Abonent nie będzie w tym celu kontaktował się bezpośrednio z Rejestratorem.
  5. Rejestrator, pod warunkiem zachowania należytej staranności, nie ponosi odpowiedzialności za niepowodzenie w rejestracji domeny oraz zmian danych, na które została zarejestrowana domena, z przyczyn od siebie niezależnych w tym z przyczyn leżących po stronie współpracujących Operatorów Rejestru lub Partnerów.
  6. Rejestrator nie ponosi odpowiedzialności za zablokowanie lub usunięcie domeny z przyczyn od siebie niezależnych.
  7. Odpowiedzialność Rejestratora ograniczona jest do wartości wniesionych przez Abonenta opłat z tytułu rejestracji domeny. Rejestrator nie ponosi odpowiedzialności za utracone przez Abonenta korzyści.
  8. Rejestrator nie ponosi odpowiedzialności za skutki bezprawnych działań Abonenta oraz za skutki kroków podjętych w celu likwidacji bezprawnych zachowań Abonenta.
  9. Rejestrator nie ponosi odpowiedzialności za działania lub zaniechania Partnera wynikłe na tle obowiązywania umowy między Partnerem a Abonentem.
  10. Partner będzie odpowiedzialny za wszelkie działania oraz zaniechania Abonenta wynikające z niniejszej Umowy.
  11. Postanowienia niniejszej Umowy zawarte w pkt. X.7 nie są wiążące względem Abonenta będącego konsumentem w rozumieniu Ustawy z dnia 23.04.1964 Kodeks Cywilny (Dz. U Nr 16, poz. 93) z późniejszymi zmianami.
  12. Postanowienia niniejszej Umowy nie wyłączają stosowania przepisów powszechnie obowiązującego prawa.
  13. Niniejsza Umowa obowiązuje Abonenta od chwili złożenia przez niego za pośrednictwem Partnera zamówienia rejestracji domeny.
  14. Wzór Umowy o rejestrację domeny .eu w NetArt Registrar Sp. z o.o. obowiązuje od dnia 16.05.2016 r.

Privacy Policy


This document describes the rules for the operation of the website (hereinafter: "the Website") provided by NetArt Registrar sp. z o.o. (hereinafter: "the Company"), with regard to cookies, pixel tags and other IT data (hereinafter collectively: "cookies"). The addressees of this document are primarily the users of the Website. If you would like to learn more about the processing of personal data within the framework of the Company's services, we encourage you to visit http://www.netart-registrar.com/RODO, where you can find information dedicated for the users of the Company's services.


Identity and contact details of the controller


The controller of the personal data processed within the service is NetArt Registrar sp. z o.o. with its registered office in Cracow (KRS number: 0001000590).

Contact with the controller is possible using:

  • traditional mail to the address ul. Pana Tadeusza 2, 30-727 Cracow;
  • email to info@netart-registrar.com.

Data Protection Officer


Please be advised that we have appointed a Data Protection Officer. The function of the Company's Data Protection Officer is performed by Daniel Trędkiewicz.

Contact with the Company's Data Protection Officer regarding data protection matters is possible via email iod@netart-registrar.com.


What are cookies?


Cookies are small text files that are stored in the browser or memory of a website user's device (computer, laptop, phone, etc.) They are commonly used to make websites work better, increase their performance, target personalised marketing communications, and to provide information to website administrators for analytical purposes.

Cookies can be read by the ICT system of the website administrator (own cookies) or by the ICT systems of third parties cooperating with the website administrator (third party cookies).

Some cookies are deleted after the end of the browser session (session cookies), and some, when the user visits the website again, will allow the website to recognise the end user's device and adapt the website to the user's preferences (permanent cookies).

As a rule, cookies do not allow the identification of a website user, however, in certain situations, in combination with other information, cookies may constitute personal data.


Purposes, legal basis and period of processing of information contained in cookies


As part the website, cookies that are not necessary for the proper operation of the website remain disabled until the user agrees to their use. Consent, which is the legal basis for the processing of personal data through non-essential cookies, is obtained via a cookie management tool (Article 6(1)(a) of the RODO in conjunction with Articles 173 and 174 of the Telecommunications Law of 16 July, 2004).

As part of the website, we may use the following cookies, depending on the consent you have given:

Necessary cookies. They are essential to the operation of the website and must always be active. They are used in response to actions taken on the website, such as, for example, completing forms, logging into the Client Panel, providing information on consent or objection to certain cookies. If these are changed via your browser settings, certain elements of the website may be disabled. They are always active and it is not possible to disable them through the cookie management tool. They can be disabled by your browser settings, but this may prevent the service from functioning properly.

Functional cookies. Their role is to collect information to improve the efficiency of the activities that are carried out on the website. These cookies allow us to customise the operation of the website according to the needs and preferences of visitors, for example by remembering the choices made on our website.

Analytical cookies. They are responsible for collecting information about how the website is used. They allow us to better understand the operation of our site and obtain information on which of its subpages are most popular and how users navigate the website. These cookies allow us to better tailor the website to users' expectations, count visits and receive information about the sources of traffic on our site.

Marketing cookies. They are responsible for the proper operation and optimisation of systems related to advertising activities. Information from these files may be shared with advertisers so that advertisements published on their websites are appropriately tailored to the user's expectations. They allow for better personalisation of the communication carried out.

Community cookies. They allow you to share content prepared by us via external social media, as well as to link accounts on such media to our site and its functionalities. They are also responsible for recording a user's activities, and the information they acquire can be used for advertising activities on individual social media.

As part of the use of cookies, we may acquire information such as (1) individual user ID, (2) IP address, (3) information about the operating system and web browser, (4) information about the subpages viewed, (5) information about the source of the user – the source of entry to the Company's website, (6) information about the approximate location of the user limited to their locality, (7) information about the language in which the user displays the website, (8) information about the time spent on the website, and (9) other information about the user's use of the website and the subpages viewed.

Settings of cookies other than session cookies are saved for a period of one year after consent has been given. After this time, the cookie settings need to be re-selected using the cookie management tool. You can change your cookie settings at any time using the tool linked at the bottom of the privacy policy.


Third-party vendor tools – data recipients


As part of the website, for the purposes listed above, we may use the following tools provided by third-party vendors who are also recipients of information from website users' cookies:

Google Analytics, provided by Google Ireland Limited (Google Building Gordon House, 4 Barrow St, Grand Canal Dock, Dublin 4, D04 V4X7, Ireland). Google Analytics is an online tool for analyzing Web site statistics. Here you can learn more about how Google uses the data it collects when you use its partners' sites and applications.

Google Ads, provided by Google Ireland Limited (Google Building Gordon House, 4 Barrow St, Grand Canal Dock, Dublin 4, D04 V4X7, Ireland). Google Ads is Google's advertising service that allows sponsored links to be displayed in Google's search results and on Google AdSense partner websites, sold under the CPC and CPM model. Here you can learn more about how Google uses the data it collects when you use its partners' sites and applications.

Meta Ads, provided by Meta Platforms Ireland Limited (Block J, Serpentine Avenue, Dublin 4 Ireland). Meta Ads is an advertising system that allows you to advertise simultaneously on the Meta platform (Facebook), Instagram, Messenger and Audience Network. Here you can learn more about how Meta uses the data it collects when you use its partners' sites and apps.

Adform, provided by Adform A/S (Silkegade 3B, ST. & 1., 1113 Copenhagen, Denmark). Adform is a tool that allows digital ads to be displayed on devices connected to the Internet. Here you can learn more about how Adform uses the data it collects when you use its partners' sites and applications.

Microsoft Ads, provided by Microsoft Ireland Operations Limited (One Microsoft Place, South County Business Park, Leopardstown, Dublin, Ireland 18, D18 P521). Microsoft Ads is an advertising tool that provides pay-per-click ads on search engines, as well as on other sites, mobile apps and videos. Here you can learn more about how Microsoft uses the data it collects when you use its partners' sites and applications.

LinkedIn Ads, whose provider is Linkedin Ireland Unlimited Company (Wilton Place, Dublin 2, Ireland). Linkedin Ads is a tool allowing targeting ads to Linkedin users. Here you can learn more about how LinkedIn uses the data it collects when you use its partners' sites and applications.

In addition, your personal data may be transferred to the following categories of entities: marketing service providers, advertising service providers, social network providers, analytics service providers, entities providing other services necessary for the Company to provide electronic services.


Transfer of personal data outside the European Economic Area


As part of the use of cookies, some of the information may be transferred to service providers or their subcontractors who are based outside the European Economic Area, i.e. in the United States. On 10 July 2023, the European Commission adopted a new decision finding an adequate level of protection for personal data provided by the so-called 'EU-US Data Privacy Framework'. Under this decision, the European Commission concluded that the changes made by the United States of America to its legislation provide an adequate degree of protection for personal data transferred by private and public entities from the territory of the European Economic Area to organisations in the US that ensure compliance with the new "EU-US Data Protection Framework." A list of these organisations has been published by the US Department of Commerce (Data Privacy Framework Program). The transfer of data to these organisations is possible without the need for additional permits or legal instruments such as standard contractual clauses.

With respect to US entities that are not enrolled in the Data Privacy Framework Program, the legal basis for the transfer will be the obligation of the entity to which your personal data will be disclosed to apply the provisions of the standard data protection clauses issued under European Commission Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries under Regulation (EU) 2016/679 of the European Parliament and of the Council. The content of these clauses is publicly available on the Internet in the EUR-lex electronic database of European Union legislation. Under these clauses, additional safeguards related to the transfer of data outside the European Economic Area have been introduced. If you would like more information, please feel free to contact the Client Service Department.


Rights in connection with the processing of personal data


In connection with the processing of your personal data by the Company, you have the following rights:

  • The right of access to personal data – entitles you to access your personal data and obtain information about the rules for its processing
  • The right to obtain a copy of your personal data – entitles you to request a copy of your personal data under processing
  • The right to rectification of personal data  – entitles you to request the rectification of inaccurate personal data or the completion of personal data
  • The right to erasure of personal data – entitles you to request the erasure of your personal data undergoing processing
  • The right to restrict the processing of personal data – entitles you to request the restriction of the processing of your personal data to storage activities, excluding undertaking other operations on your personal data
  • The right to data portability – entitles you to receive your personal data in a structured, commonly used machine-readable format and send it to another entity
  • The right to object to the processing of personal data – entitles you to request the cessation of the processing of your personal data for specific purposes
  • The right to withdraw consent to the processing of personal data – entitles you to withdraw at any time your consent to the processing of your personal data for specific purposes, which does not affect the lawfulness of processing activities prior to the withdrawal of consent
  • The right to lodge a complaint with a supervisory authority – entitles you to lodge a complaint with the President of the UODO (Personal Data Protection Office) about the processing of your personal data by the controller.
  • To exercise the above rights, please contact the Company's Customer Service Department. You can raise any objections to the way your request is handled directly with the Data Protection Officer.


Setting the conditions for storing and accessing cookies


The conditions for storing and accessing cookies can also be specified using the settings of the software installed on the device used. Please refer to the instructions for the most popular web browsers.


Other information


With the exception of essential cookies, activation of all other cookies is completely voluntary.

As part of the use of cookies, we may process data in an automated manner, by evaluating selected factors about the users of the website so that we can analyse their behaviour, which allows us to better tailor the displayed content to the individual preferences and interests of the users.

Information on the rules governing the processing of personal data at the Company is reviewed on an ongoing basis and updated as necessary. You can read up-to-date information in this regard on the website. If you have further questions, the Customer Service Department and the Data Protection Officer are at your service.



Information as of 07.12.2023.

RODO



Identity and contact details of the controller


The Controller of your personal data is NetArt Registrar sp. z o.o. with its registered office in Cracow (KRS number: 0000532637).

Contact with NetArt Registrar is possible using:

  • traditional mail to the address ul. Pana Tadeusza 2, 30-727 Cracow
  • email to info@netart-registrar.com

Data Protection Officer


Please be advised that we have appointed a Data Protection Officer. The function of the NetArt Registrar's Data Protection Officer is performed by Daniel Trędkiewicz.

Contact with the NetArt Registrar's Data Protection Officer regarding data protection matters is possible via email iod@netart-registrar.com


Purposes, legal basis and duration of personal data processing


The purposes, legal basis and duration of the processing of your personal data depend on the nature of the relationship between you and the company. Read the information for:

Registrants

As part of your relationship with NetArt Registrar, your personal data may be processed for the following purposes:

Conducting correspondence. The legal basis for the processing of your personal data will be the realisation of the legitimate interest of NetArt Registrar, which is to conduct correspondence within the framework of its business activities (Article 6(1)(f) of the GDPR). Your personal data will be processed for the duration of the correspondence and thereafter until the expiry of the statute of limitations for any claims related to the correspondence (as a rule, the statute of limitations expires at the end of the calendar year after the expiry of three or six years from the due date of the claim) or the statute of limitations for the possibility of imposing an administrative fine.

Publication of Registrants' data in the Whois database. Under the requirements imposed by ICANN, NetArt Registrar, as an accredited registrar of global Internet domains, is required to maintain a database of domains and their Registrants (Whois). Once a global domain is registered, the details of its Registrant may be published in the Whois database. It is freely available to all Internet users. The data of Registrants with the status of a natural person are protected by default by replacing them in the Whois database with the designation "REDACTED FOR PRIVACY" or equivalent. This does not apply only to the country and province (voivodship) of the Registrant. On the other hand, Registrants with the legal status of a company can protect their data in the Whois database using the Whois Privacy functionality offered by the Partner. If you opt out of Whois database data protection and decide to disclose your data, the legal basis for its processing will be your voluntary consent (Article 6(1)(a) of the GDPR) expressed through the Partner at the stage of managing the Registrant's Whois data protection status. Your personal data will be processed until such time as you lose your rights to the domain or until Registrant data protection is activated in the Whois database.

Complaint processing. The legal basis for the processing of your personal data will be the realisation of the legitimate interest of NetArt Registrar which is the processing of complaints and defence against claims (Article 6(1)(f) of the GDPR). Your personal data will be processed for the time necessary to process your complaint, and thereafter documents relating to the complaint procedure will be stored until the expiry of the limitation period for claims (as a rule, the statute of limitations expires at the end of a calendar year after the expiry of three or six years from the due date of the claim).

Providing the services offered by NetArt Registrar by electronic means (domain registration services). The legal basis for the processing of your personal data will be the performance of the contract to which you are a party (Article 6(1)(b) of the GDPR in conjunction with Article 18(1) and (2) of the Act of July 18, 2002 on the provision of electronic services in connection with the gTLD Domain Registration Agreement or the .eu Domain Registration Agreement). Your personal data will be processed for the duration of the provision of services.

Provision of data at the request of entitled authorities. The legal basis for the processing of your personal data will be the performance of obligations provided by law (Article 6(1)(c) of the GDPR in conjunction with Article 18(6) of the Act of 18 July 2002 on the provision of electronic services in conjunction with the provision of national law governing the procedure of entitled authorities, such as Article 15 of the Act of 6 June 1997 Code of Criminal Procedure or Article 248 of the Act of 17 November 1964 Code of Civil Procedure). Your personal data will be processed until the expiry of the statute of limitations for claims - as a rule, this will occur on the last day of the calendar year after the expiry of three or six years from the due date of the claim (note that this period may be interrupted by law, which may result in an extension of the processing period) - or the statute of limitations for the possibility of imposing an administrative fine.

Establishment, exercise or defense of claims. The legal basis for the processing of your personal data will be the realisation of the legitimate interest of NetArt Registrar, which is to protect the interest of NetArt Registrar against claims and to assert claims (Article 6(1)(f) of the GDPR).Your personal data will be processed until the expiry of the statute of limitations for claims - as a rule, this will occur on the last day of the calendar year after the expiry of three or six years from the due date of the claim (note that this period may be interrupted by law, which may result in an extension of the processing period) - or the statute of limitations for the possibility of imposing an administrative fine.

Ensuring the security of services, the network, including preventing unauthorised access to electronic communications networks and preventing damage to computer systems. The legal basis for the processing of your personal data will be the realisation of the legitimate interest of NetArt Registrar, which is to ensure adequate security of the services provided and the business conducted (Article 6(1)(f) of the GDPR). Your personal data will be processed for a period of time that ensures the security of the services, network and information. Representatives of the Registrant If you are a representative of a Registrant, we will process your personal data for the following purpose:

Conducting correspondence. The legal basis for the processing of your personal data will be the realisation of the legitimate interest of NetArt Registrar, which is to conduct correspondence within the framework of its business activities (Article 6(1)(f) of the GDPR). Your personal data will be processed for the duration of the correspondence and thereafter until the expiry of the statute of limitations for any claims related to the correspondence (as a rule, the statute of limitations expires at the end of the calendar year after the expiry of three or six years from the due date of the claim) or the statute of limitations for the possibility of imposing an administrative fine.

Recipients of personal data and the source and categories of personal data The type of recipients and the source and categories of your personal data depend on the nature of the relationship between you and NetArt Registrar. Read the information specific to:

Registrants

If we provide you with a web domain registration and maintenance service, the type of recipients and the source and categories of your personal data will depend on the type of domain you register.

.eu domains. are registered by NetArt Registrar pursuant to an agreement with a Partner enabling Registrants to order domain registration services. The Partner provides NetArt Registrar with access to the Registrant's within the scope of the domain name, identification data, address data, contact data, as well as nationality (due to the availability of .eu domains for persons having citizenship or residence in one of the member states of the European Union, Norway, Iceland or Liechtenstein). After obtaining this data from the Partner, NetArt Registrar makes such data available to the European Registry for Internet Domains (EURid) (Telecomlaan 9, 1831 Diegem, Belgium), which is the operator of the .eu domain registry.

.Global domains .com, .net, .org, .info and .biz. are registered by NetArt Registrar on the basis of an agreement with the Partner enabling Registrants to order domain registration services. The Partner provides NetArt Registrar with the Registrant's data in the scope of domain name, identification data, address data, contact data. After obtaining this data from the Partner, NetArt Registrar makes this data available to the following entities, depending on the type of domain:

  • Internet Corporation for Assigned Names and Numbers (ICANN) Los Angeles 12025 Waterfront Drive, Suite 300, CA 90094-2536, USA;
  • NCC Group Software Resilience (NA) LLC XYZ Building, 2 Hardman Boulevard, Spinningfields, Manchester, M3 3AQ, United Kingdom (Data Depository);
  • Verisign Inc. Reston, 12061 Bluemont Way, VA 20190, USA (Registry Operator for .com and .net domains);
  • Identity Digital Inc.  10500 NE 8th Street, Suite 750, Bellevue, WA 98004, USA (Registry Operator for .info domains);
  • Public Interest Registry  Reston, 11911 Freedom Drive, 10th Floor, Suite 1000, VA 20190, USA (Registry operator for .org domains).
  • Registry Services, LLC   2155 E GoDaddy Way, Tempe, AZ 85284, USA (Registry Operator for .biz domains).

In addition, your personal data may be transferred to the following categories of entities: entities providing legal services and data protection consulting, entities providing correspondence services, entities providing other services necessary for NetArt Registrar to provide services electronically, authorised entities and authorities.

Representatives of the Registrant

If you are a representative of the Registrant, NetArt Registrar will obtain your personal information directly from you when you choose to contact NetArt Registrar on matters related to the service provided to the Registrant. The scope of the data to be obtained will depend on what data will be included in the content of the correspondence (e.g., identification data, contact data, content of the correspondence).

Your personal data may be transferred to the following categories of entities: entities providing legal services and data protection consulting, entities providing correspondence services, entities providing other services necessary for NetArt Registrar to provide services electronically, authorised entities and authorities.

Recipients of personal data outside the European Economic Area

Registrants

In the case of European domains, Registrants' data is generally not transferred outside the European Economic Area. However, due to the nature of the domain registration service, which allows the public presentation of content on the Internet, it is likely that the Registrant's data (which also applies to global domain Registrants) in terms of the content collected on the website (e.g. the domain name containing the Registrant's name, photographs on the website, entries on the website containing personal data, etc.) will be publicly accessible from anywhere in the world. The extent of the data made available on the Registrant's website is completely independent of NetArt Registrar and is administered solely by the Registrant. NetArt Registrar's role is limited to providing the Registrant's data obtained from the Partner for the purpose of EURid domain registration (in the case of European domains). It is also important to note that EURid maintains a public Whois registry in which domain data, including the personal data of Registrants, can be published - we recommend reading EURid's detailed rules for maintaining this registry.

In the case of global domains, on the other hand, there is a transfer of personal data outside the European Economic Area, due to the fact that Registry Operators, ICANN and Data Depositories are based outside the European Economic Area (generally in the United States). Therefore, the transfer of data outside the European Economic Area is necessary to register the domain. On the factual side, NetArt Registrar, as an ICANN-accredited registrar, shares the personal data of Registrants with the relevant Registry Operator, Data Depository and ICANN. Global domain registration is also linked to keeping a public Whois registry, where domain data, including Registrants' data, may be published - we recommend reading the detailed rules for the maintenance of these registries by ICANN, the relevant Registry Operator and Registrar.

The legal basis for the transfer of personal data outside the European Economic Area to the United States may be the European Commission's decision of 13 July 2023 finding an adequate level of protection for personal data provided by the so-called "EU-US Data Privacy Framework". Under this decision, the European Commission concluded that the changes made by the United States of America to its legislation provide an adequate degree of protection for personal data transferred by private and public entities from the territory of the European Economic Area to organisations in the US that ensure compliance with the new "EU-US Data Protection Framework." A list of these organisations has been published by the US Department of Commerce (Data Privacy Framework Program). The transfer of data to these organisations is possible without the need for additional permits or legal instruments such as standard contractual clauses.

With respect to entities from countries for which the European Commission has not issued a decision on the adequacy level of data protection or with respect to entities from the United States that are not enrolled in the Data Privacy Framework Program, the legal basis for data transfer may be the obligation of the entity to which your personal data will be disclosed to apply the provisions of the standard data protection clauses issued under European Commission Implementing Decision 2021/914 of 4 June 2021. on standard contractual clauses for the transfer of personal data to third countries under Regulation (EU) 2016/679 of the European Parliament and of the Council. The content of these clauses is publicly available on the Internet in the EUR-lex electronic database of European Union legislation. Under these clauses, additional safeguards related to the transfer of data outside the European Economic Area have been introduced.

For more information about NetArt Registrar's safeguards in connection with the transfer of personal data outside the European Economic Area, please contact NetArt Registrar's Data Protection Officer.

Representatives of the Registrant

Personal data of Registrant's representatives are not transferred outside the European Economic Area.


Rights in connection with the processing of personal data


In connection with the processing of your personal data by NetArt Registrar, you have the following rights:

  • The right of access to personal data – entitles you to access your personal data and obtain information about the rules for its processing
  • The right to obtain a copy of your personal data – entitles you to request a copy of your personal data under processing
  • The right to rectification of personal data – entitles you to request the rectification of inaccurate personal data or the completion of personal data
  • The right to erasure of personal data – entitles you to request the erasure of your personal data undergoing processing
  • The right to restrict the processing of personal data – entitles you to request the restriction of the processing of your personal data to storage activities, excluding undertaking other operations on your personal data
  • The right to data portability – entitles you to receive your personal data in a structured, commonly used machine-readable format and send it to another entity
  • The right to object to the processing of personal data – entitles you to request the cessation of the processing of your personal data for specific purposes
  • The right to withdraw consent to the processing of personal data – entitles you to withdraw at any time your consent to the processing of your personal data for specific purposes, which does not affect the lawfulness of processing activities prior to the withdrawal of consent
  • The right to lodge a complaint with a supervisory authority – entitles you to lodge a complaint with the President of the UODO (Personal Data Protection Office) about the processing of your personal data by the controller

Rights in connection with the processing of personal data


In connection with the processing of your personal data by the Company, you have the following rights:

  • The right of access to personal data – entitles you to access your personal data and obtain information about the rules for its processing
  • The right to obtain a copy of your personal data – entitles you to request a copy of your personal data under processing
  • The right to rectification of personal data  – entitles you to request the rectification of inaccurate personal data or the completion of personal data
  • The right to erasure of personal data – entitles you to request the erasure of your personal data undergoing processing
  • The right to restrict the processing of personal data – entitles you to request the restriction of the processing of your personal data to storage activities, excluding undertaking other operations on your personal data
  • The right to data portability – entitles you to receive your personal data in a structured, commonly used machine-readable format and send it to another entity
  • The right to object to the processing of personal data – entitles you to request the cessation of the processing of your personal data for specific purposes
  • The right to withdraw consent to the processing of personal data – entitles you to withdraw at any time your consent to the processing of your personal data for specific purposes, which does not affect the lawfulness of processing activities prior to the withdrawal of consent
  • The right to lodge a complaint with a supervisory authority – entitles you to lodge a complaint with the President of the UODO (Personal Data Protection Office) about the processing of your personal data by the controller.
  • To exercise the above rights, please contact the Company's Customer Service Department. You can raise any objections to the way your request is handled directly with the Data Protection Officer.

TTo exercise the above rights, please contact the NetArt Registrar's Customer Service Department. You can raise any objections to the way your request is handled directly with the Data Protection Officer.


Other information


Providing personal data is a precondition for domain registration and use of NetArt Registrar's services. When placing an order for domain registration, you are required to provide correct data. The provision of personal data in certain cases is a statutory requirement (e.g. due to regulations governing tax and accounting obligations). Therefore, without the provision of personal data, the provision of services and the implementation of other purposes for which we process your personal data will not be possible.

The implementation of submitted requests - both in the field of personal data protection and related to the services provided - is always preceded by appropriate authorisation of the person submitting the request. Remember that if there is any doubt about your identity, NetArt Registrar has the right to perform additional verification of the identity of the person making the request. This is to prevent the execution of instructions submitted by unauthorised persons.

Your personal data will not be subject to profiling.

We would further like to inform you that NetArt Registrar uses cookies on its website. For more information on the use of cookies, please see our Privacy Policy available on NetArt Registrar.

Information on the rules governing the processing of personal data at NetArt Registrar is reviewed on an ongoing basis and updated as necessary. You can read up-to-date information in this regard at netart-registrar.com/rodo. If you have further questions, the Customer Service Department and the Data Protection Officer are at your service.


Information as of 07.12.2023.

More than 10 years of strategic
partnership with ICANN

icon

5 000 000+

domains

icon

500 000+

hosting services

icon

1 000 000+

SSL Certificates