Contact us
Submit TicketLive ChatReport Abuse
Your Cart
Subtotal$0.00
View Cart
USD
U.S. DollarEuroBritish PoundCanadian DollarsAustralian DollarsIndian RupeesChina Yuan RMBMore Info →

Data Processing Addendum

Last Revised: 9/27/2021

This Data Processing Addendum (this “Addendum”) is executed by and between “Processor” Namecheap, Inc. and its Affiliates (“Namecheap”) and you (“Controller”, “Customer”) and is annexed to and supplements our Universal Terms of Service, Privacy Policy and any and all agreements governing Covered Services (collectively, the “Terms of Service”). Unless otherwise defined in this Addendum, all capitalized terms not defined in this Addendum will have the meanings given to them in the Terms of Service.

1. Definitions

  • “Affiliates” means any entity which is controlled by, controls, or is in common control with Namecheap.
  • “Covered Services” means hosted services we offer you that could involve our Processing of Personal Data.
  • “Customer Data” means the Personal Data of any Data Subject Processed by Namecheap within the Namecheap Network on behalf of Customer pursuant to or in connection with the Terms of Service.
  • “Data Controller” means the Customer, as the entity which determines the purposes and means of the Processing of Personal Data.
  • “Data Processor” means Namecheap, as the entity which Processes Personal Data on behalf of the Data Controller.
  • “Data Protection Laws” means the GDPR (as defined below), together with any national implementing laws in any Member State of the European Union or the United Kingdom or, to the extent applicable, in any other country, in each case as amended, repealed, consolidated or replaced from time to time.
  • “Data Subject” means the individual to whom Personal Data relates.
  • “EEA” means the European Economic Area.
  • “GDPR” means the General Data Protection Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data.
  • “Namecheap Network” means Namecheap’s data center facilities, servers, networking equipment, and host software systems (e.g., virtual firewalls) that are within Namecheap’s control and are used to provide the Covered Services.
  • “Personal Data” means any information relating to an identified or identifiable person.
  • “Processing” means any operation or set of operations which is performed upon Personal Data, whether or not by automatic means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
  • “Process”, “processes” and “processed” will be interpreted accordingly. Detail of Processing are set forth in Annex 1.
  • “Security Incident” means either (a) a breach of security of the Namecheap Security Standards leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, any Customer Data; or (b) any unauthorized access to Namecheap equipment or facilities, where in either case such access results in destruction, loss, unauthorized disclosure, or alteration of Customer Data.
  • “Security Standards” means the security standards attached to this Addendum as Annex 2​.
  • “Sensitive Data” means (a) social security number, passport number, driver’s license number, or similar identifier (or any portion thereof); (b) credit or debit card number (other than the truncated (last four digits) of a credit or debit card), financial information, banking account numbers or passwords; (c) employment, financial, genetic, biometric or health information; (d) racial, ethnic, political or religious affiliation, trade union membership, or information about sexual life or sexual orientation; (e) account passwords, mother’s maiden name, or date of birth; (f) criminal history; or (g) any other information or combinations of information that falls within the definition of “special categories of data” under GDPR or any other applicable law or regulation relating to privacy and data protection.
  • “Standard Contractual Clauses” or “SCCs” means the standard data protection clauses for the transfer of personal data from a controller to a processor established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the GDPR and approved by the European Commission decision 2021/914 of 4 June 2021. Module Two (Controller to Processor) Standard Contractual Clauses are in Appendix 1.
  • “Sub-processor” means any Data Processor engaged by Processor to Process data on behalf of Data Controller.
  • “UK Standard Contractual Clauses” or “UK SCCs” means the standard data protection clauses for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, as described in Article 46 of the UK GDPR and approved by the European Commission decision 2010/87/EU.

2. Data Processing

2.1 Scope and Roles.

This Addendum applies when Customer Data is processed by Namecheap. In this context, Namecheap will act as the Data Processor on behalf of the Customer as the Data Controller with respect to Customer Data.

2.2 Details of Data Processing.

The subject matter of processing of Customer Data by Namecheap is the performance of the Covered Services pursuant to the Terms of Service and product-specific agreements. Namecheap shall only Process Customer Data on behalf of and in accordance with Customer’s documented instructions following purposes: (i) Processing in accordance with the Terms of Service or applicable product-specific agreement; (ii) Processing initiated by end users in their use of the Covered Services; (iii) Processing to comply with other documented, reasonable instructions provided by Customers (ex. via email) where such instructions are consistent with the terms of the Agreement. Namecheap shall not be required to comply with or observe Customer’s instructions if such instructions would violate the GDPR or any other applicable data privacy laws. The duration of the Processing, the nature and purpose of the Processing, the types of personal data and categories of Data Subjects Processed under this Addendum are further specified in Appendix 1 (‘Details of the Processing’) to this Addendum.

For the avoidance of doubt, Customer’s instructions for the Processing of Personal Data shall comply with all applicable data privacy laws. Customer shall have sole responsibility for the accuracy, quality, and legality of Personal Data and the means by which Customer acquired Personal Data. Namecheap shall not be required to comply with or observe Customer’s instructions if such instructions would violate Data Protection Laws. The duration of the Processing, the nature and purpose of the Processing, the types of Personal Data and categories of Data Subjects Processed under this Addendum are further specified in Annex 1 (‘Details of the Processing’) to this Addendum.

3. Confidentiality of Customer Data

Namecheap does not voluntarily provide governments with access to any data about users for surveillance purposes, and Namecheap will not disclose Customer Data to any government or any other third party, except as necessary to comply with the law or a valid and binding order of a law enforcement agency (such as a subpoena or court order). All legal process is carefully reviewed to ensure that it meets or exceeds required legal standards, and Namecheap interprets legal process as narrowly as possible. Namecheap rejects or challenges any requests that have no legal basis or are unclear, overbroad or otherwise inappropriate.

4. Security

4.1 Namecheap has implemented and will maintain the technical and organizational measures for the Namecheap Network as described here in this Section and as further described in SCCs Annex II to this Addendum, Security Standards. In particular, Namecheap has implemented and will maintain the following technical and organizational measures that address the (i) security of the Namecheap Network; (ii) physical security of the facilities; (iii) controls around employee and contractor access to (i) and/or (ii); and (iv) processes for testing, assessing and evaluating the effectiveness of technical and organizational measures implemented by Namecheap.

4.2 Namecheap makes available a number of security features and functionalities that Customer may elect to use in relation to the Covered Services. Customer is responsible for (a) properly configuring the Covered Services, (b) using the controls available in connection with the Covered Services (including the security controls) to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services, (c) using the controls available in connection with the Covered Services (including the security controls) to allow the Customer to restore the availability and access to Customer Data in a timely manner in the event of a physical or technical incident (e.g. backups and routine archiving of Customer Data), and (d) taking such steps as Customer considers adequate to maintain appropriate security, protection, and deletion of Customer Data, which includes use of encryption technology to protect Customer Data from unauthorized access and measures to control access rights to Customer Data.

5. Data Subject Rights

Taking into account the nature of the Covered Services, Namecheap offers Customer certain security standards as described in the “Security” section of this Addendum. Customer may use these stated technical and organizational measures to assist it in connection with its obligations under applicable privacy laws, including its obligations relating to responding to requests from Data Subjects. As commercially reasonable, and to the extent lawfully required or permitted, Namecheap shall promptly notify Customer if Namecheap directly receives a request from a Data Subject to exercise such rights under any applicable data privacy laws (“Data Subject Request”). In addition, where Customer’s use of the Covered Services limits its ability to address a Data Subject Request, Namecheap may, where legally permitted and appropriate and upon Customer’s specific request, provide commercially reasonable assistance in addressing the request, at Customer’s cost (if any). Data Subject Rights are further specified in SCCs incorporated herein.

6. Sub-processing

6.1 Authorized Sub-processors.

Customer agrees that Namecheap may use Sub-processors to fulfill its contractual obligations under its Terms of Service and this Addendum or to provide certain services on its behalf, such as providing support services. Customer hereby consents to Namecheap’s use of Sub-processors as described in this Section. Except as set forth in this Section or as otherwise explicitly authorized by you, Namecheap will not permit any other sub-processing activities.

6.2 Sub-processor Obligations.

Where Namecheap uses any authorized Sub-processor as described in Section 6.1:

  1. Namecheap will restrict the Sub-processor’s access to Customer Data only to what is necessary to maintain the Covered Services or to provide the Covered Services to Customer and any end users in accordance with the Covered Services. Namecheap will prohibit the Sub-processor from accessing Customer Data for any other purpose;
  2. Namecheap will enter into a written agreement with the Sub-processor and, to the extent that the Sub-processor is performing the same data processing services that are being provided by Namecheap under this Addendum, Namecheap will impose on the Sub-processor the same contractual obligations that Namecheap has under this Addendum; and
  3. Namecheap will remain responsible for its compliance with the obligations of this Addendum and for any acts or omissions of the Sub-processor that cause Namecheap to breach any of Namecheap’s obligations under this Addendum.

7. Security Incident

7.1 Security Incident.

If Namecheap becomes aware of a Security Incident, Namecheap will without undue delay: (a) notify Customer of the Security Incident; and (b) take reasonable steps to mitigate the effects and to minimize any damage resulting from the Security Incident.

7.2 Namecheap Assistance.

To assist Customer in relation to any personal data breach notifications Customer is required to make under any applicable privacy laws, Namecheap will include in the notification under section 8.1 such information about the Security Incident as Namecheap is reasonably able to disclose to Customer, taking into account the nature of the Covered Services, the information available to Namecheap, and any restrictions on disclosing the information, such as confidentiality.

7.3 Failed Security Incidents.

Customer agrees that:

  1. A failed Security Incident will not be subject to the terms of this Addendum. A failed Security Incident is one that results in no unauthorized access to Customer Data or to any of Namecheap’s Network, equipment, or facilities storing Customer Data, and may include, without limitation, pings and other broadcast attacks on firewalls or edge servers, port scans, unsuccessful log-on attempts, denial of service attacks, packet sniffing (or other unauthorized access to traffic data that does not result in access beyond headers) or similar incidents; and
  2. Namecheap’s obligation to report or respond to a Security Incident under this Section is not and will not be construed as an acknowledgment by Namecheap of any fault or liability of Namecheap with respect to the Security Incident.

7.4 Communication.

Notification(s) of Security Incidents, if any, will be delivered to one or more of Customer’s administrators by any means Namecheap selects, including via email. It is Customer’s sole responsibility to ensure Customer’s administrators maintain accurate contact information on the Namecheap account panel and secure transmission at all times.

8. Customer Rights

8.1 Independent Determination.

Customer is responsible for reviewing the information made available by Namecheap relating to data security and its Security Standards and making an independent determination as to whether the Covered Services meets Customer’s requirements and legal obligations as well as Customer’s obligations under this Addendum. The information made available is intended to assist Customer in complying with Customer’s obligations under applicable privacy laws, including the GDPR, in respect of data protection impact assessments and prior consultation.

8.2 Customer Audit Rights.

Customer has the right to confirm Namecheap’s compliance with this Addendum as applicable to the Covered Services, including specifically Namecheap’s compliance with its Security Standards. Customer may do so by exercising a reasonable right to conduct an audit or inspection, including under the Standard Contractual Clauses if they apply. If Namecheap declines to follow any instruction requested by Customer regarding a properly requested and scoped audit or inspection, Customer is entitled to terminate this Addendum and the Terms of Service. If the Standard Contractual Clauses apply, nothing in this Section varies or modifies the Standard Contractual Clauses nor affects any supervisory authority’s or data subject’s rights under the Standard Contractual Clauses. This Section will also apply insofar as Namecheap carries out the control of Sub-processors on behalf of the Customer.

9. Transfers of Personal Data

9.1 U.S. Based Processing. Customer agrees that, except where specifically noted in the Terms of Service, Namecheap may transfer Customer Data to the United States for processing. Transfers will be made in accordance with legally enforceable transfer mechanisms where required by applicable Data Protection Laws.

9.2 Application of Standard Contractual Clauses. The Standard Contractual Clauses will apply to Customer Data that is transferred outside the EEA, either directly or via onward transfer, to any country not recognized by the European Commission as providing an adequate level of protection for personal data (as described in the GDPR). The Standard Contractual Clauses will not apply to Customer Data that is not transferred, either directly or via onward transfer, outside the EEA. Notwithstanding the foregoing, the Standard Contractual Clauses will not apply where the data is transferred in accordance with a recognized compliance standard for the lawful transfer of Personal Data outside the EEA, such as when necessary for the performance of Covered Services pursuant to the Terms of Service or with your consent. Additional information relating to EEA-US transfers of personal data can be found here.

9.3 With respect to Customer Data transferred from the United Kingdom for which United Kingdom law (and not the law in any EEA jurisdiction) governs the international nature of the transfer, and such law permits use of the UK SCCs but not use of the SCCs, the UK SCCs form part of this DPA and take precedence over the rest of this DPA, as set forth in the UK SCCs, until such time that the United Kingdom adopts new Standard Contractual Clauses, in which case new, Standard Contractual Clauses will control. For purposes of the UK SCCs, they shall be deemed completed as follows:

  1. The “exporters” and “importers” are the Parties and their Affiliates to the extent any of them is involved in such transfer, including those set forth in Annex I.A of the SCCs.
  2. Clause 9 of the UK SCCs specifies that United Kingdom law will govern the UK SCCs.
  3. The content of Appendix 1 of the UK SCCs is set forth in Annex I of the SCCs herein.
  4. The content of Appendix 2 of the UK SCCs is set forth in Annex II of the SCCs herein.

The UK Standard Contractual Clauses will not apply to Customer Data that is not transferred, either directly or via onward transfer, outside the United Kingdom. Notwithstanding the foregoing, the UK Standard Contractual Clauses will not apply where the data is transferred in accordance with a recognized compliance standard for the lawful transfer of Customer Data outside the United Kingdom, such as when necessary for the performance of Covered Services pursuant to the Terms of Service or with your consent.

9.4 With respect to Personal Data transferred from the European Economic Area, the SCCs incorporated herein shall apply and form part of this DPA. In the event of a conflict between any provision of the SCCs and any provision of this DPA, the SCCs will control to the extent of conflicts.

10. Termination of the Addendum

This Addendum will continue in force until the termination of our processing in accordance with the Terms of Service (the “Termination Date”).

11. Return or Deletion of Customer Data

Any deletion of Customer Data will be governed by the terms of the particular Covered Services and Universal Terms of Service.

12. Limitations of Liability

The liability of each party under this Addendum will be subject to the exclusions and limitations of liability set out in the Terms of Service and the SCCs. Customer agrees that any regulatory penalties incurred by Namecheap in relation to the Customer Data that arise as a result of, or in connection with, Customer’s failure to comply with its obligations under this Addendum and any applicable privacy laws will count towards and reduce Namecheap’s liability under the Terms of Service as if it were liability to the Customer under the Terms of Service.

13. Entire Terms of Service; Conflict

This Addendum supersedes and replaces all prior or contemporaneous representations, understandings, agreements, or communications between Customer and Namecheap, whether written or verbal, regarding the subject matter of this Addendum, including any data processing addenda entered into between Namecheap and Customer with regard to the processing of personal data and on the free movement of such data. Except as amended by this Addendum, the Terms of Service will remain in full force and effect. If there is a conflict between any other agreement between the parties including the Terms of Service and this Addendum, the terms of this Addendum will control. In the event of a conflict between any provision of the SCCs and any provision of this DPA, the SCCs will control to the extent of conflicts.

[​See Section 9.2 of the Addendum for the applicability of these SCCs​]

Appendix 1

STANDARD CONTRACTUAL CLAUSES

SECTION I

Clause 1

Purpose and scope

a. The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)1 for the transfer of personal data to a third country.

b. The Parties:

I. the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”), and

II. the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data importer”) have agreed to these standard contractual clauses (hereinafter: “Clauses”).

c. These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.

d. The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2

Effect and invariability of the Clauses

  1. These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided, that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
  2. These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3

Third-party beneficiaries

a. Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

  1. Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
  2. Clause 8 - Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c), (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g); Module Four: Clause 8.1 (b) and Clause 8.3(b);
  3. Clause 9 - Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);
  4. Clause 12 - Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);
  5. Clause 13;
  6. Clause 15.1(c), (d) and (e);
  7. Clause 16(e);
  8. Clause 18 - Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.

b. Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4

Interpretation

  1. Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
  2. These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
  3. These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5

Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6

Description of the transfers

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7

Docking clause

  1. An entity that is not a Party to these Clauses may, with the agreement of the Partie, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
  2. Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
  3. The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II - OBLIGATIONS OF THE PARTIES

Clause 8

Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1 Instructions

  1. The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
  2. The data importer shall immediately inform the data exporter if it is unable to follow those instructions.

8.2 Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.

8.3 Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.

8.4 Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.

8.5 Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

8.6 Security of processing

  1. The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter “personal data breach”). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
  2. The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
  3. In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
  4. The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

8.7 Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter “Sensitive Data”), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

8.8 Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union2 (in the same country as the data importer or in another third country, hereinafter “onward transfer”) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

  1. the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
  2. the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
  3. the onward transfer is necessary for the establishment, exercise or defense of legal claims in the context of specific administrative, regulatory or judicial proceedings; or (iv) the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.
  4. Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9 Documentation and compliance

  1. The data importer shall promptly and adequately deal with inquiries from the data exporter that relate to the processing under these Clauses.
  2. The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
  3. The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into
  4. The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
  5. The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.

Clause 9

Use of sub-processors

  1. GENERAL WRITTEN AUTHORISATION: The data importer has the data exporter’s general authorization for the engagement of sub-processor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors at least 10 days in advance, thereby giving the data exporter sufficient time to be able to object to such changes prior to the engagement of the sub-processor(s). The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
  2. Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects.3 The Parties agree that, by complying with this Clause, the data importer fulfills its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
  3. The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
  4. The data importer shall remain fully responsible to the data exporter for the performance of the sub-processor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
  5. The data importer shall agree a third-party beneficiary clause with the sub-processor whereby - in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent - the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

Clause 10

Data subject rights

  1. The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorized to do so by the data exporter.
  2. The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organizational measures, taking into account the nature of the processing by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
  3. In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.

Clause 11

Redress

  1. The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorized to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
  2. In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
  3. Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to: lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work or the competent supervisory authority pursuant to Clause 13; refer the dispute to the competent courts within the meaning of Clause 18.
  4. The Parties accept that the data subject may be represented by a not-for-profit body, organization or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
  5. The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
  6. The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Clause 12

Liability

  1. Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
  2. The data importer shall be liable to the data subject, and the data subject shall be entitled to receive compensation for any material or non-material damages the data importer or its sub- processor causes the data subject by breaching the third-party beneficiary rights under these Clauses.
  3. Notwithstanding paragraph (b), the data exporter shall be liable to the data subject, and the data subject shall be entitled to receive compensation for any material or non-material damages the data exporter or the data importer (or its sub-processor) causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter and, where the data exporter is a processor acting on behalf of a controller, to the liability of the controller under Regulation (EU) 2016/679 or Regulation (EU) 2018/1725, as applicable.
  4. The Parties agree that if the data exporter is held liable under paragraph (c) for damages caused by the data importer (or its sub-processor), it shall be entitled to claim back from the data importer that part of the compensation corresponding to the data importer’s responsibility for the damage.
  5. Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable, and the data subject is entitled to bring an action in court against any of these Parties.
  6. The Parties agree that if one Party is held liable under paragraph (e), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its / their responsibility for the damage.
  7. The data importer may not invoke the conduct of a sub-processor to avoid its own liability.

Clause 13

Supervision

  1. The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.
  2. The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to inquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

SECTION III - LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES

Clause 14

Local laws and practices affecting compliance with the Clauses

  1. The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
  2. The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
  3. The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
  4. The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
  5. The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
  6. Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfill its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organizational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured or if instructed by the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15

Obligations of the data importer in case of access by public authorities

15.1 Notification

  1. The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary with the help of the data exporter) if it: I. receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or, II. becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
  2. If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
  3. Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
  4. The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
  5. Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2 Review of legality and data minimisation

  1. The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
  2. The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.
  3. The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV - FINAL PROVISIONS

Clause 16

Non-compliance with the Clauses and termination

  1. The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
  2. In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
  3. The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

I. the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

II. the data importer is in substantial or persistent breach of these Clauses; or

III.the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

d. Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data.The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

e. Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17

Governing law

These Clauses shall be governed by the law of one of the EU Member States, provided such law allows for third-party beneficiary rights. The Parties agree that this shall be the law of Belgium.

Clause 18

Choice of forum and jurisdiction

  1. Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
  2. The Parties agree that those shall be the courts of Belgium.
  3. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
  4. The Parties agree to submit themselves to the jurisdiction of such courts.

ANNEX I

A. LIST OF PARTIES

Data exporter(s): The Data Exporter is the entity identified as “Customer” in the Addendum that has entered the Terms of Service with Namecheap, and their contact details are as provided by them while subscribing to the Terms of Service.

Signature and date: As of the date of Data Exporter’s acceptance of Data Importer’s Terms of Service, Data Exporter is deemed to have signed the Data Protection Addendum, including these Standard Contractual Clauses in their entirety.

Role: Controller

Data importer(s): Namecheap, Inc.

Contact details: Office of the Data Protection Officer – dpo@namecheap.com

Activities relevant to the data transferred under these Clauses: Providing the Services to Data Exporter.

Signature and date: As of the date of Data Exporter’s acceptance of Data Importer’s Terms of Service, Data Importer is deemed to have signed the Data Protection Addendum, including these Standard Contractual Clauses in their entirety.

Role: Processor

В. DESCRIPTION OF TRANSFER

1. Categories of data subjects whose personal data is transferred

Customer may upload Personal Data in the course of its use of the Covered Services, the extent to which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to Personal Data relating to the following categories of Data Subjects:

  • Prospects, customers, business partners and vendors of Customer (who are natural persons)
  • Employees or contact persons of Customer’s prospects, customers, business partners and vendors
  • Employees, agents, advisors, freelancers of Customer (who are natural persons)
  • Customer’s Users authorized by Customer to use the Covered Services

2. Categories of personal data transferred

Customer may upload Personal Data in the course of its use of the Covered Services, the type of and extent to which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to the following categories of Personal Data of Data Subjects:

  • Name
  • Address
  • Telephone number
  • Date of birth
  • Email address
  • Other data collected that could directly or indirectly identify you.

3. Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance, strict purpose limitation, access restrictions (including access only for staff having followed specialized training), keeping a record of access to the data, restrictions for onward transfers or additional security measures

Namecheap does not intentionally collect special categories of data, but the data exporter, at its own discretion, may collect such data. These categories may include racial or ethnic origin, political opinions, philosophical beliefs, trade union membership, health or sex data. Data exporter is solely responsible for meeting all obligations regarding the collection, use, and transfer of such data.

4. The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis) Data is transferred on a continuous basis,

Data is transferred on a continuous basis, for the length of the Agreement between the parties.

5. Nature of the processing

Namecheap will Process Personal Data as necessary to perform the Covered Services pursuant to the Terms of Services, product-specific agreements, and as further instructed by Customer throughout its use of the Covered Services.

6. Purpose(s) of the data transfer and further processing

Namecheap’s Terms of Services, product-specific agreements, and as further instructed by Customer throughout its use of the Covered Services.

7. The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period

Personal data shall be retained for the length of time necessary to provide the Covered Services under the Terms of Service, or as otherwise required by applicable law.

8. For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing

Namecheap’s sub-processors will process personal data to assist Namecheap in providing the Covered Services pursuant to the Agreement, for as long as needed for Namecheap to provide the Covered Services.

C. COMPETENT SUPERVISORY AUTHORITY

1. Identify the competent supervisory authority/ies in accordance with Clause 13

With respect to the SCCs, the parties agree that the competent supervisory authority is the Belgian Data Protection Authority. With respect to the UK SCCs, the competent supervisory authority means the UK Information Commissioner’s Office.

ANNEX II - TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

Security Standards

We are, as always, committed to the protection of our customer’s information. To provide the best level of security, we consider a number of factors such as best practices, cost to execute, details and circumstances of processing, severity and risk of data breach occurrence and its potential impact on a customer. We also regularly test, assess and evaluate the effectiveness of our procedures. Below are technical and organizational standards that we’ve implemented across our core, US based operations to ensure the ongoing confidentiality, integrity, availability and resilience of our processing systems and services. Rest assured, we are continually adding to the ways in which your data is safe with us.

Data Privacy Program

Our Data Privacy Program is established to maintain a global data governance throughout its lifecycle. This program is overseen by our Data Protection Officer.

I. Confidentiality​

Below are the practices we use to protect the confidentiality of our customer’s personal data.

Physical Security
We have physical access controls in place, as well as surveillance systems (including alarms, and CCTV monitoring where appropriate). We also implement clean desk policies (locking of unattended computers, locked cabinets, etc.), visitor access management and shredding of documents/destruction disks.

Access Control & Prevention of Unauthorized Access
New access to systems is reviewed and approved by management prior to being granted. We perform regular reviews of user accounts and assigned permissions for key systems. We also limit the personnel who may grant, alter or cancel authorized access to data and resources. We use 2FA (2-factor authentication) for mission critical services. All services are connected via Microsoft Active Directory solution (ADFS) with security practices enabled on and RBAC privilege assignment to have secure Single-Sign on in our internal services. Encryption & Pseudonymization
We provide encryption of external and internal communication via strong cryptographic protocols, and remote access to the company networks made via VPN with strong encryption and 2FA. We also have implemented and use pseudonymization, where appropriate.

Data Minimization
Data minimization is accomplished by PII/SPI minimization, segregation of data stored by function (test, staging, live), logical segregation of data by role based access rights and system/product based defined data retention periods for personal data.

Security Testing
We perform regular network and vulnerability scans throughout our system and have an external bounty program to receive vulnerability findings of independent security researchers and implement a fix further on.

II. Integrity of Data

We focus on a number of ways to ensure the integrity of customer data.

Change & Release Management
Namecheap has a change and release management process in place, as well as role and function access provisioning on production environments. We require encrypted connections to our services interfaces between Customer and Namecheap at all times. We also use industry standard encryption mechanisms for data in transit.

Logging & Monitoring
Namecheap collects logs. Logs may include access ID, time, diagnostic data, and other relevant activity. Logs are used (i) for providing, securing, managing, measuring and improving the Namecheap services, (ii) as directed or instructed by Customer and its Users, and/or (iii) for compliance with Namecheap policies, applicable law, regulation, or governmental request. This may include monitoring the performance, stability, usage and security of the Namecheap services.

III. Availability

We implement appropriate continuity and security measures to maintain the availability of our service, the personal data residing within those services and the ability to timely restore such data, including the following:

  • Extensive performance/availability monitoring and reporting for critical systems
  • Incident response programme
  • Critical data either replicated or backed up (Cloud Backups/Hard Disks/Database replication etc.)
  • Planned software, infrastructure and security maintenance in place (Software updates, security patches etc.)
  • Redundant and resilient systems (server clusters, mirrored DBs with geographically remote mirror, high availability setups etc.) located on off-site and/or geographically separated locations. Use of uninterruptible power supplies, fail redundant hardware and network systems
  • Alarm, security systems in place
  • Physical Protection measures in place for critical sites (surge protection, raised floors, cooling systems, fire and/or smoke detectors, fire suppression systems etc.)
  • DDOS protection to maintain availability
  • Failover Protection measures in place, including mechanisms designed to address loss of availability of data, including storing copies of data in a different place from where the primary computer equipment processing is located.

IV. Data Processing Instructions

We have established internal privacy policies and agreements to ensure personal data is processed in accordance with customers’ preferences and instructions.

[1] Where the data exporter is a processor subject to Regulation (EU) 2016/679 acting on behalf of a Union institution or body as controller, reliance on these Clauses when engaging another processor (sub-processing) not subject to Regulation (EU) 2016/679 also ensures compliance with Article 29(4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC (OJ L 295 of 21.11.2018, p. 39), to the extent these Clauses and the data protection obligations as set out in the contract or other legal act between the controller and the processor pursuant to Article 29(3) of Regulation (EU) 2018/1725 are aligned. This will in particular be the case where the controller and processor rely on the standard contractual clauses included in Decision 2021/915.

[2] The Agreement on the European Economic Area (EEA Agreement) provides for the extension of the European Union's internal market to the three EEA States Iceland, Liechtenstein and Norway. The Union data protection legislation, including Regulation (EU) 2016/679, is covered by the EEA Agreement and has been incorporated into Annex XI thereto. Therefore, any disclosure by the data importer to a third party located in the EEA does not qualify as an onward transfer for the purpose of these Clauses.

[3] This requirement may be satisfied by the sub-processor acceding to these Clauses under the appropriate Module, in accordance with Clause 7.

[4] As regards the impact of such laws and practices on compliance with these Clauses, different elements may be considered as part of an overall assessment. Such elements may include relevant and documented practical experience with prior instances of requests for disclosure from public authorities, or the absence of such requests, covering a sufficiently representative time-frame. This refers in particular to internal records or other documentation, drawn up on a continuous basis in accordance with due diligence and certified at senior management level, provided that this information can be lawfully shared with third parties. Where this practical experience is relied upon to conclude that the data importer will not be prevented from complying with these Clauses, it needs to be supported by other relevant, objective elements, and it is for the Parties to consider carefully whether these elements together carry sufficient weight, in terms of their reliability and representativeness, to support this conclusion. In particular, the Parties have to take into account whether their practical experience is corroborated and not contradicted by publicly available or otherwise accessible, reliable information on the existence or absence of requests within the same sector and/or the application of the law in practice, such as case law and reports by independent oversight bodies.

Need help? We're always here for you.

Go to Live Chat page
notmyip