Back to Privacy & Legal Center

Data Processing Agreement (“DPA”)

Last update: January, 2026

v.1.0

This Personal Data Processing Agreement (hereinafter "DPA") is entered into between RegDoor (“Processor”) and the Client (“Controller”), as defined in the Agreement that the Client signed with RegDoor (RegDoor and Client each a “Party”, and collectively, the “Parties”).

The DPA applies to the processing of personal data carried out by RegDoor for the Client, in the context of the Client's use of the RegDoor application. 

The Parties seek to implement this DPA to comply with the requirements of EU GDPR (defined hereunder) in relation to Processor’s processing of Personal Data (as defined under the EU GDPR) as part of its obligations under the Agreement.

Except as modified below, the terms of the Agreement shall remain in full force and effect.  

  1. Definitions

Terms not otherwise defined herein shall have the meaning given to them in the EU GDPR or the Agreement. The following terms shall have the corresponding meanings assigned to them below: 

1.1. "Data Transfer" means a transfer of the Personal Data from the Controller to the Processor, or between two establishments of the Processor, or with a Sub-processor by the Processor.

1.2. “EU GDPR” means the 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 and repealing Directive 95/46/EC (General Data Protection Regulation).

1.3. “Standard Contractual Clauses” means the contractual clauses attached hereto as Schedule 1 pursuant to the European Commission’s Implementing Decision (EU) 2021/914 of 4 June 2021 on Standard Contractual Clauses for the transfer of Personal Data to processors established in third countries which do not ensure an adequate level of data protection.

1.4. “Controller” means the natural or legal person, public authority, agency, or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law.

1.5. “Processor” means a natural or legal person, public authority, agency, or other body which processes personal data on behalf of the controller.

1.6. “Sub-processor” means a processor/ sub-contractor appointed by the Processor for the provision of all or parts of the Services and Processes the Personal Data as provided by the Controller.

  1.  Purpose of this Agreement

This DPA sets out various obligations of the Processor in relation to the Processing of Personal Data and shall be limited to the Processor’s obligations under the Agreement. If there is a conflict between the provisions of the Agreement and this DPA, the provisions of this DPA shall prevail.

  1. Categories of Personal Data and Data Subjects 

The Controller authorizes permission to the Processor to process the Personal Data to the extent of which is determined and regulated by the Controller. 

  1. Purpose of Processing 

The objective of Processing of Personal Data by the Processor shall be limited to the Processor’s provision of the Services to the Controller and or its Client, pursuant to the Agreement. 

  1. Duration of Processing 

The Processor will Process Personal Data for the duration of the Agreement, unless otherwise agreed upon in writing by the Controller.

  1. Data Controller’s Obligations

    6.1 The Data Controller shall warrant that it has all necessary rights to provide the Personal Data to the Data Processor for the Processing to be performed in relation to the agreed services. To the extent required by Data Privacy Laws, Data Controller is responsible for ensuring that it provides such Personal Data to Data Processor based on an appropriate legal basis allowing lawful processing activities, including any necessary Data Subject consents to this Processing are obtained, and for ensuring that a record of such consents is maintained. Should such consent be revoked by the Data Subject, the Data Controller is responsible for communicating the fact of such revocation to the Data Processor. 

    6.2 The Data Controller shall immediately advise the Data Processor in writing if it receives or learns of any: 

    6.2.1. Complaint or allegation indicating a violation of Data Privacy Laws regarding Personal Data;

    6.2.2. Request from one or more individuals seeking to access, correct, or delete Personal Data; 

    6.2.3. Inquiry or complaint from one or more individuals relating to the collection, processing, use, or transfer of Personal Data; and 

    6.2.4. Any regulatory request, search warrant, or other legal, regulatory, administrative, or governmental process seeking Personal Data


  2. Data Processor’s Obligations

    7.1 The Processor will Process Personal Data solely to the extent necessary to provide the services described in this Agreement and in accordance with the written and documented instructions received from the Controller, including by email, when the Controller determines that such Processing is necessary, whether directly or through its affiliates, agents, or authorized personnel. (each, an “Instruction”).

    7.2 At the Data Controller’s request, the Data Processor will provide reasonable assistance to the Data Controller in responding to/ complying with requests/ directions by Data Subject in exercising their rights or of the applicable regulatory authorities regarding Data Processor’s Processing of Personal Data. 

    7.3 The processor shall inform the controller if, in its opinion, a processing instruction infringes applicable legislation or regulation.

    7.4 As A Data Processor, taking into account the nature of the processing and the information available to the Data Processor, the Data Processor may assist, if needed, the data controller in conducting any necessary Data Protection Impact Assessments (DPIAs), as required under GDPR.


  3. Audit Rights

    8.1. Upon Controller’s reasonable request, the Processor will make available to the Controller, information as is reasonably necessary to demonstrate Processor’s compliance with its obligations under the EU GDPR or other applicable laws in respect of its Processing of the Personal Data.

    8.2. When the Controller wishes to conduct the audit (by itself or through a representative) at Processor’s site, it shall provide at least thirty (30) days’ prior written notice to the Processor; the Processor will provide reasonable cooperation and assistance in relation to audits, including inspections, conducted by the Controller or its representative. 

    8.3. The Controller shall bear the expense of such an audit.


  4. Mechanism of Data Transfers 

Any transfer of Personal Data outside the European Economic Area shall occur only in accordance with the Standard Contractual Clauses and applicable Data Protection Laws.

Processor shall implement supplementary measures and conduct transfer impact assessments where required.

  1. Sub-processors

10.1. The Controller acknowledges and agrees that the Processor may engage a third-party Sub-processor(s) in connection with the performance of the Services, provided such Sub-processor(s) take technical and organizational measures to ensure confidentiality of Personal Data shared with them; The current Sub-processors engaged by the Processors and approved by the Controller are listed in Annex II of Schedule 1 hereto. The processor shall notify the controller at least thirty (30) calendar days in advance of any intended changes or additions to its Sub-processors listed in Annex II by emailing notice of the intended change to Customer. In accordance with Article 28(4) of the GDPR, the Processor shall remain liable to Controller for any failure on behalf of a Sub-processor to fulfil its data protection obligations under the DPA in connection with the performance of the Services.

10.2. If the Controller has a concern that the Sub-processor(s) Processing of Personal Data is reasonably likely to cause the Controller to breach its data protection obligations under the GDPR, the Controller may object to Processor’s use of such Sub-processor and the Processor and Controller shall confer in good faith to address such concern. 

  1. Personal Data Breach Notification

11.1. The Processor shall maintain defined procedures in case of a Personal Data Breach (as defined under the GDPR) and shall without undue delay notify Controller if it becomes aware of any Personal Data Breach unless such Data Breach is unlikely to result in a risk to the rights and freedoms of natural persons. 

11.2. The Processor shall provide the Controller with all reasonable assistance to comply with the notification of Personal Data Breach to Supervisory Authority and/or the Data Subject, to identify the cause of such Data Breach and take such commercially reasonable steps as reasonably required to mitigate and remedy such Data Breach. 

11.3. No Acknowledgement of Fault by Processor. Processor’s notification of or response to a Personal Data Breach under this DPA will not be construed as an acknowledgement by Processor of any fault or liability with respect to the data incident.

  1. Return and Deletion of Personal Data

12.1 The Processor shall at least thirty (30) days from the end of the Agreement or cessation of the Processor’s Services under the Agreement, whichever occurs earlier, shall return to the Controller all the Personal Data, or if the Controller so instructs, the Processor shall have the Personal Data deleted. The Processor shall return such Personal Data in a commonly used format or in the current format in which it was stored at discretion of the Controller, soon as reasonably practicable following receipt of Controller’s notification.


SCHEDULE 1

ANNEX I

TECHNICAL AND ORGANISATIONAL MEASURES INCLUDING TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

Description of the  technical and organisational security measures implemented by Regdoor as the data processor/data importer to ensure an appropriate level of security, taking into account the nature, scope, context, and purpose of the processing, and the risks for the rights and freedoms of natural persons.

  • Security

  • Security Management System.

    • Organization. RegDoor designates qualified security personnel whose responsibilities include development, implementation, and ongoing maintenance of the Information Security Program.

    • Policies. Management reviews and supports all security related policies to ensure the security, availability, integrity and confidentiality of Customer Personal Data.  These policies are updated at least once annually.

    • Assessments. RegDoor engages a reputable independent third-party to perform risk assessments of all systems containing Customer Personal Data at least once annually.

    • Risk Treatment. RegDoor maintains a formal and effective risk treatment program that includes penetration testing, vulnerability management and patch management to identify and protect against potential threats to the security, integrity or confidentiality of Customer Personal Data.

    • Vendor Management. RegDoor maintains an effective vendor management program

    • Incident Management. RegDoor reviews security incidents regularly, including effective determination of root cause and corrective action.

    • Standards. RegDoor adopts key applicable organizational and technical security measures, as example the ISO Standards of the 27000 family. 

  • Personnel Security.

    • RegDoor personnel are required to conduct themselves in a manner consistent with the company’s guidelines regarding confidentiality, business ethics, appropriate usage, and professional standards. RegDoor conducts reasonably appropriate background checks on any employees who will have access to client data under this Agreement, including in relation to employment history and criminal records, to the extent legally permissible and in accordance with applicable local labor law, customary practice and statutory regulations.

    • Personnel are required to execute a confidentiality agreement in writing at the time of hire and to protect Customer Personal Data at all times. Personnel must acknowledge receipt of, and compliance with, RegDoor’s confidentiality, privacy and security policies. Personnel are provided with privacy and security training on how to implement and comply with the Information Security Program. Personnel handling Customer Personal Data are required to complete additional requirements appropriate to their role (e.g., certifications). RegDoor’s personnel will not process Customer Personal Data without authorization.

  • Access Controls

  • Access Management. RegDoor maintains a formal access management process for the request, review, approval and provisioning of all personnel with access to Customer Personal Data to limit access to Customer Personal Data and systems storing, accessing or transmitting Customer Personal Data to properly authorized persons having a need for such access. Access reviews are conducted periodically to ensure that only those personnel with access to Customer Personal Data still require it.

  • Infrastructure Security Personnel. RegDoor has, and maintains, a security policy for its personnel, and requires security training as part of the training package for its personnel. RegDoor’s infrastructure security personnel are responsible for the ongoing monitoring of RegDoor’s security infrastructure, the review of the Services, and for responding to security incidents.

  • Access Control and Privilege Management. RegDoor’s and Customer’s administrators and end users must authenticate themselves via a Multi-Factor authentication system or via a single sign on system in order to use the Services

  • Internal Data Access Processes and Policies – Access Policy. RegDoor’s internal data access processes and policies are designed to protect against unauthorized access, use, disclosure, alteration or destruction of Customer Personal Data. RegDoor designs its systems to only allow authorized persons to access data they are authorized to access based on principles of “least privileged” and “need to know”, and to prevent others who should not have access from obtaining access.  RegDoor requires the use of unique user IDs, strong passwords, two factor authentication and carefully monitored access lists to minimize the potential for unauthorized account use. The granting or modification of access rights is based on: the authorized personnel’s job responsibilities; job duty requirements necessary to perform authorized tasks; a need to know basis; and must be in accordance with RegDoor’s internal data access policies and training. Approvals are managed by workflow tools that maintain audit records of all changes. Access to systems is logged to create an audit trail for accountability. Where passwords are employed for authentication (e.g., login to workstations), password policies follow industry standard practices. These standards include password complexity, password expiry, password lockout, restrictions on password reuse and re-prompt for password after a period of inactivity

  • Data Center and Network Security

  • Data Centers.

    • Infrastructure. RegDoor has AWS as its data center.

    • Resiliency. Multi Availability Zones are enabled on AWS and RegDoor conducts Backup Restoration Testing on regular basis to ensure resiliency.

    • Server Operating Systems. RegDoor’s servers are customized for the application environment and the servers have been hardened for the security of the Services. RegDoor employs a code review process to increase the security of the code used to provide the Services and enhance the security products in production environments.

    • Disaster Recovery. RegDoor replicates data over multiple systems to help to protect against accidental destruction or loss. RegDoor has designed and regularly plans and tests its disaster recovery programs.

    • Security Logs. RegDoor’s systems have logging enabled to their respective system log facility in order to support the security audits, and monitor and detect actual and attempted attacks on, or intrusions into, RegDoor’s systems.

    • Vulnerability Management. RegDoor performs regular vulnerability scans on all infrastructure components of its production and development environment.  Vulnerabilities are remediated on a risk basis, with Critical, High and Medium security patches for all components installed as soon as commercially possible.

  • Networks and Transmission.

    • Data Transmission. Transmissions on production environment are transmitted via Internet standard protocols.

    • External Attack Surface. AWS Security Group which is equivalent to virtual firewall is in place for Production environment on AWS.

    • Incident Response. RegDoor maintains incident management policies and procedures, including detailed security incident escalation procedures. RegDoor monitors a variety of communication channels for security incidents, and RegDoor’s security personnel will react promptly to suspected or known incidents, mitigate harmful effects of such security incidents, and document such security incidents and their outcomes.

    • Encryption Technologies. RegDoor makes HTTPS encryption (also referred to as SSL or TLS) available for data in transit.

  • Data Storage, Isolation, Authentication, and Destruction. RegDoor stores data in a multi-tenant environment on AWS servers. Data, the Services database and file system architecture are replicated between multiple availability zones on AWS. RegDoor logically isolates the data of different customers. A central authentication system is used across all Services to increase uniform security of data. RegDoor ensures secure disposal of Client Data through the use of a series of data destruction processes.

ANNEX II

LIST OF SUB-PROCESSORS

The controller has authorized the use of the following sub-processors:

Name of Sub- Processor

Description of Processing

Location of Other Processor

Amazon Web Services

Hosting the Production Environment

Ireland