Data Processing Addendum
Last updated: 16 July 2026
This Data Processing Addendum (“DPA”) is entered into between the Controller and the Processor and is incorporated into and governed by the terms of the Agreement. This DPA forms part of, and is automatically incorporated into, the Mailercloud Terms and Conditions; no additional signature is required for it to take effect. If your organisation requires a countersigned copy of this DPA, contact us at [email protected] and we will provide one.
1. Definitions
Any capitalized term not defined in this DPA shall have the meaning given to it in the Agreement.
“Affiliate” means any entity that directly or indirectly controls, is controlled by, or is under common control of a party. “Control”, for purposes of this definition, means direct or indirect ownership or control of more than 50% of the voting interests of a party;
“Agreement” means the agreement between the Controller and the Processor for the provision of the Services;
“Controller” means the Member;
“Customer Data” means all data imported into the Services for the purpose of using the Services or facilitating use of the Services by the Member or its authorized users;
“Data Protection Law” means all laws and regulations, including laws and regulations of the European Union, the European Economic Area, their member states and the United Kingdom, any amendments, replacements or renewals thereof, applicable to the processing of Personal Data, including where applicable the Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2020, the EU GDPR, the UK GDPR, the UK Data Protection Act 2018, the FADP, US State Privacy Laws and any applicable national implementing laws, regulations and secondary legislation relating to the processing of the Personal Data and the privacy of electronic communications, as amended, replaced or updated from time to time, including the Privacy and Electronic Communications Directive (2002/58/EC) and the Privacy and Electronic Communications (EC Directive) Regulations 2003 (SI 2003/2426);
“Data Subject” shall have the same meaning as in Data Protection Law or means a “Consumer” as that term is defined in US State Privacy Laws;
“DPA” means this data processing addendum together with Exhibits A, B and C;
“EEA” means the European Economic Area;
“EU GDPR” means 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);
“FADP” means the Swiss Federal Act on Data Protection of the 1st of September 2023, and as amended from time to time;
“Personal Data” shall have the same meaning as in Data Protection Law;
“Processor” means Luvia Digital Limited (“Mailercloud”), including as applicable any “Service Provider” as that term is defined in US State Privacy Laws;
“Restricted Transfer” means:
(i) where the EU GDPR applies, a transfer of Personal Data via the Services from the EEA either directly or via onward transfer, to any country or recipient outside of the EEA not subject to an adequacy determination by the European Commission; and
(ii) where the UK GDPR applies, a transfer of Personal Data via the Services from the United Kingdom either directly or via onward transfer, to any country or recipient outside of the UK not based on adequacy regulations pursuant to Section 17A of the United Kingdom Data Protection Act 2018; and
(iii) a transfer of Personal Data via the Services from Switzerland either directly or via onward transfer, to any country or recipient outside of the EEA and/or Switzerland not subject to an adequacy determination by the European Commission;
“Services” means all services and software applications and solutions provided to the Controller by the Processor under and as described in the Agreement;
“SCCs” means:
(i) where the EU GDPR applies, the standard contractual clauses annexed to the European Commission’s Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries published at https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32021D0914&from=EN, (“EU SCCs”); and
(ii) where the UK GDPR applies, the international data transfer addendum to the EU SCCs adopted pursuant to Article 46(2)(c) of the UK GDPR and published at https://ico.org.uk/media/for-organisations/documents/4019539/international-data-transfer-addendum.pdf, as may be amended or replaced, (“UK SCCs”); and
(iii) where Personal Data is transferred from Switzerland to outside of Switzerland or the EEA, the EU SCCs as amended in accordance with guidance from the Swiss Data Protection Authority; (“Swiss SCCs”); as may be amended, superseded or replaced from time to time.
“Sub-processor” means any third party (including the Processor’s Affiliates) engaged directly or indirectly by the Processor to process Personal Data under this DPA in the provision of the Services to the Controller;
“Supervisory Authority” means a governmental or government chartered regulatory body having binding legal authority over a party;
“UK GDPR” means the EU GDPR as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018;
“US State Privacy Laws” means the following US state data protection or privacy laws and regulations applicable to the party’s Processing of Personal Data: California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA), Virginia Consumer Data Protection Act (VCDPA), Colorado Privacy Act (CPA), Connecticut Data Privacy Act (CTDPA), and Utah Consumer Privacy Act (UCPA), in each case as may be amended or superseded from time to time.
2. Purpose
2.1 The Processor has agreed to provide the Services to the Controller in accordance with the terms of the Agreement. In providing the Services, the Processor shall process Customer Data on behalf of the Controller. Customer Data may include Personal Data. The Processor will process and protect such Personal Data in accordance with the terms of this DPA.
3. Scope
3.1 In providing the Services to the Controller pursuant to the terms of the Agreement, the Processor shall process Personal Data only to the extent necessary to provide the Services in accordance with the terms of the Agreement, this DPA and the Controller’s instructions documented in the Agreement and this DPA, as updated from time to time.
3.2 The Controller and Processor shall take steps to ensure that any natural person acting under the authority of the Controller or the Processor who has access to Personal Data does not process Personal Data except on the instructions from the Controller, unless required to do so by any Data Protection Law.
4. Processor’s Obligations
4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.
4.2 The Processor confirms that it shall process Personal Data on behalf of the Controller in accordance with the documented instructions of the Controller.
4.3 The Processor shall promptly inform the Controller, if in the Processor’s opinion, any of the instructions regarding the processing of Personal Data provided by the Controller, breach Data Protection Law.
4.4 The Processor shall ensure that all employees, agents, officers and contractors involved in the handling of Personal Data: (i) are aware of the confidential nature of the Personal Data and are contractually bound to keep the Personal Data confidential; (ii) have received appropriate training on their responsibilities as a data processor; and (iii) are bound by the terms of this DPA.
4.5 The Processor shall implement appropriate technical and organisational measures to protect Personal Data, taking into account: (i) the state of the art; (ii) the costs of implementation; (iii) the nature, scope, context and purposes of processing; and (iv) the risk of varying likelihood and severity for the rights and freedoms of natural persons.
4.6 The Processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In assessing the appropriate level of security, account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed.
4.7 The technical and organisational measures detailed in Exhibit B shall at all times be adhered to as a minimum security standard. The Controller accepts and agrees that the technical and organisational measures are subject to development and review and that the Processor may use alternative suitable measures to those detailed in the attachments to this DPA, provided such measures are at least equivalent to the technical and organisational measures set out in Exhibit B and appropriate pursuant to the Processor’s obligations in clauses 4.5 and 4.6 above.
4.8 The Controller acknowledges and agrees that, in the course of providing the Services to the Controller, it may be necessary for the Processor to access the Personal Data to respond to any technical problems or Controller queries and to ensure the proper working of the Services. All such access by the Processor will be limited to those purposes.
4.9 Taking into account the nature of the processing and the information available to the Processor, the Processor shall assist the Controller by having in place appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the Controller’s obligation to respond to requests for exercising the Data Subject’s rights and the Controller’s compliance with the Controller’s data protection obligations in respect of the processing of Personal Data.
4.10 The Processor may not: (i) sell Personal Data; (ii) retain, use, or disclose Personal Data for commercial purposes other than providing the Services under the terms of the Agreement; or (iii) retain, use, or disclose Personal Data outside of the terms of the Agreement.
5. Controller’s Obligations
5.1 The Controller represents and warrants that: (i) it shall comply with this DPA and its obligations under Data Protection Law; (ii) it has obtained any, and all, permissions and authorisations necessary to permit the Processor, its Affiliates and Sub-processors, to execute their rights or perform their obligations under this DPA; and (iii) all Affiliates of the Controller who use the Services shall comply with the obligations of the Controller set out in this DPA.
5.2 The Controller shall implement appropriate technical and organisational measures to protect Personal Data, taking into account: (i) the state of the art; (ii) the costs of implementation; (iii) the nature, scope, context and purposes of processing; and (iv) the risk of varying likelihood and severity for the rights and freedoms of natural persons.
5.3 The Controller shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: (i) the pseudonymisation and encryption of Personal Data; (ii) the ability to ensure the on-going confidentiality, integrity, availability and resilience of processing systems and services; (iii) the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident; (iv) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. In assessing the appropriate level of security account shall be taken in particular of the risks that are presented by processing, in particular from accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data transmitted, stored or otherwise processed.
5.4 The Controller acknowledges and agrees that some instructions from the Controller including the Processor assisting with audits, inspections, DPIAs or providing any assistance under this DPA, may result in additional fees. In such a case the Processor shall notify the Controller of its fees for providing such assistance in advance and shall be entitled to charge the Controller for its reasonable costs and expenses in providing such assistance, unless agreed otherwise in writing.
6. Sub-processors
6.1 The Controller agrees that the Processor may engage Sub-processors in connection with the provision of the Services.
6.2 All Sub-processors who process Personal Data in the provision of the Services to the Controller shall comply with the obligations of the Processor set out in this DPA.
6.3 The Controller authorises the Processor to use the Sub-processors included in the list of Sub-processors published at https://www.mailercloud.com/legal/subprocessors/ (see Exhibit C), to process the Personal Data. During the term of this DPA, the Processor shall provide the Controller with 30 days prior notification, via email, of any changes to the list of Sub-processors before authorising any new or replacement Sub-processor to process Personal Data in connection with provision of the Services.
6.4 The Controller may object to the use of a new or replacement Sub-processor, by notifying the Processor promptly in writing within fifteen (15) days after receipt of the Processor’s notice. If the Controller objects to a new or replacement Sub-processor, the Controller may terminate the Agreement with respect to those Services which cannot be provided by the Processor without the use of the new or replacement Sub-processor. The Processor will refund the Controller any prepaid fees covering the remainder of the term of the Agreement following the effective date of termination with respect to such terminated Services.
6.5 All Sub-processors who process Personal Data shall comply with the obligations of the Processor set out in this DPA. The Processor shall prior to the relevant Sub-processor carrying out any processing activities in respect of the Personal Data: (i) appoint each Sub-processor under a written contract containing materially the same obligations to those of the Processor in this DPA enforceable by the Processor; and (ii) ensure each such Sub-processor complies with all such obligations.
6.6 The Controller agrees that the Processor and its Sub-processors may make Restricted Transfers of Personal Data for the purpose of providing the Services to the Controller in accordance with the Agreement. The Processor confirms that such Sub-processors: (i) are located in a third country or territory recognised by the EU Commission or a Supervisory Authority, as applicable, to have an adequate level of protection; or (ii) have entered into the applicable SCCs with the Processor; or (iii) have other legally recognised appropriate safeguards in place.
7. Restricted Transfers
7.1 The parties agree that, when a transfer of Personal Data occurs between the Controller and the Processor or from the Processor to a Sub-processor which is a Restricted Transfer, it shall be subject to the applicable SCCs.
7.2 The parties agree that the EU SCCs shall apply to Restricted Transfers from the EEA. The EU SCCs shall be deemed entered into (and incorporated into this DPA by reference) and completed as follows:
(i) Module Two (Controller to Processor) shall apply where the Member is a Controller of Personal Data and Mailercloud is processing Personal Data;
(ii) Module Three (Processor to Processor) shall apply where Mailercloud is a Processor of Personal Data and Mailercloud uses a Sub-processor to process the Personal Data;
(iii) Module Four (Processor to Controller) shall apply where Mailercloud is processing Personal Data and the Member is not subject to the EU GDPR or UK GDPR;
(iv) In Clause 7 of the EU SCCs, the optional docking clause shall not apply;
(v) In Clause 9 of the EU SCCs, Option 2 applies, and the time period for giving notice of Sub-processor changes shall be as set out in clause 6.3 of this DPA;
(vi) In Clause 11 of the EU SCCs, the optional language shall not apply;
(vii) In Clause 17 of the EU SCCs, Option 1 applies and the EU SCCs shall be governed by Irish law;
(viii) In Clause 18(b) of the EU SCCs, disputes shall be resolved by the courts of Ireland;
(ix) Annex I of the EU SCCs shall be deemed completed with the information set out in Exhibit A of this DPA;
(x) Annex II of the EU SCCs shall be deemed completed with the information set out in Exhibit B of this DPA.
7.3 The parties agree that the EU SCCs as amended in clause 7.2 above, shall be adjusted as set out below where the FADP applies to any Restricted Transfer:
(i) The Swiss Federal Data Protection and Information Commissioner (“FDPIC”) shall be the sole Supervisory Authority for Restricted Transfers exclusively subject to the FADP;
(ii) Restricted Transfers subject to both the FADP and the EU GDPR, shall be dealt with by the EU Supervisory Authority named in Exhibit A of this DPA;
(iii) The term ‘member state’ must not be interpreted in such a way as to exclude Data Subjects in Switzerland from the possibility of suing for their rights in their place of habitual residence (Switzerland) in accordance with Clause 18(c) of the EU SCCs;
(iv) Where Restricted Transfers are exclusively subject to the FADP, all references to the GDPR in the EU SCCs are to be understood to be references to the FADP;
(v) Where Restricted Transfers are subject to both the FADP and the EU GDPR, all references to the GDPR in the EU SCCs are to be understood to be references to the FADP insofar as the Restricted Transfers are subject to the FADP;
7.4 The parties agree that the UK SCCs shall apply to Restricted Transfers from the UK and the UK SCCs shall be deemed entered into (and incorporated into this DPA by reference), completed as follows:
(i) Table 1 of the UK SCCs shall be deemed completed with the information set out in Exhibit A of this DPA;
(ii) Table 2 of the UK SCCs shall be deemed completed with the information set out in clauses 7.2(i) – (viii) of this DPA;
(iii) Table 3 of the UK SCCs shall be deemed completed with the information set out in Exhibits A and B of this DPA; and
(iv) Either party may end the UK SCCs as set out in clause 19 of the UK SCCs.
7.5 In case of any changes to the EU SCCs or UK SCCs, the parties shall negotiate in good faith necessary amendments to the DPA and the Agreement to ensure compliance with applicable Data Protection Laws.
7.6 In the event that any provision of this DPA contradicts directly or indirectly any SCCs, the provisions of the applicable SCCs shall prevail over the terms of the DPA.
8. Data Subject Access Requests
8.1 The Controller may require correction, deletion, blocking and/or making available the Personal Data during or after termination of the Agreement. The Controller acknowledges and agrees that the Processor will process the request to the extent it is lawful and will reasonably fulfill such request in accordance with its standard operational procedures to the extent possible.
8.2 In the event that the Processor receives a request from a Data Subject in relation to Personal Data, the Processor will refer the Data Subject to the Controller unless otherwise prohibited by law. The Controller shall reimburse the Processor for all costs incurred resulting from providing reasonable assistance in dealing with a Data Subject request. In the event that the Processor is legally required to respond to the Data Subject, the Controller will fully cooperate with the Processor as applicable.
9. Audit
9.1 The Processor shall make available to the Controller all information reasonably necessary to demonstrate compliance with its processing obligations and allow for and contribute to audits and inspections.
9.2 Any audit conducted under this DPA shall consist of examination of the most recent reports, certificates and/or extracts prepared by an independent auditor bound by confidentiality provisions similar to those set out in the Agreement. In the event that provision of the same is not deemed sufficient in the reasonable opinion of the Controller, the Controller may conduct a more extensive audit which shall be: (i) at the Controller’s expense; (ii) limited in scope to matters specific to the Controller and agreed in advance; (iii) carried out during the Processor’s usual business hours and upon reasonable notice which shall be not less than 4 weeks unless an identifiable material issue has arisen; and (iv) conducted in a way which does not interfere with the Processor’s day-to-day business.
9.3 This clause shall not modify or limit the rights of audit of the Controller, instead it is intended to clarify the procedures in respect of any audit undertaken pursuant thereto.
10. Personal Data Breach
10.1 The Processor shall notify the Controller without undue delay after becoming aware of (and in any event within 72 hours of discovering) any breach of security leading to the accidental or unlawful destruction, loss, alteration or unauthorised disclosure or access to any Personal Data (“Personal Data Breach”).
10.2 In the event of a Personal Data Breach, the Processor shall take all commercially reasonable measures to secure the Personal Data, to limit the effects of any Personal Data Breach, and to assist the Controller in meeting the Controller’s obligations under applicable law.
11. Compliance, Cooperation and Response
11.1 The Processor will notify the Controller promptly of any request or complaint regarding the processing of Personal Data, which adversely impacts the Controller, unless such notification is not permitted under applicable law or a relevant court order.
11.2 The Processor may make copies of and/or retain Personal Data in compliance with any legal or regulatory requirement including, but not limited to, retention requirements.
11.3 The Processor shall reasonably assist the Controller in meeting the Controller’s obligation to carry out data protection impact assessments (DPIAs), taking into account the nature of the processing and the information available to the Processor.
11.4 The Controller shall notify the Processor within a reasonable time, of any changes to applicable data protection laws, codes or regulations which may affect the contractual duties of the Processor. The Processor shall respond within a reasonable timeframe in respect of any changes that need to be made to the terms of this DPA or to the technical and organisational measures to maintain compliance. If the Processor is unable to accommodate necessary changes, the Controller may terminate the part or parts of the Services which give rise to the non-compliance. To the extent that other parts of the Services provided are not affected by such changes, the provision of those Services shall remain unaffected.
11.5 The Controller and the Processor and, where applicable, their representatives, shall cooperate, on request, with a Supervisory Authority in the performance of their respective obligations under this DPA and Data Protection Law.
12. Liability
12.1 The limitations on liability set out in the Agreement apply to all claims made pursuant to any breach of the terms of this DPA.
12.2 The parties agree that the Processor shall be liable for any breaches of this DPA caused by the acts and omissions or negligence of its Sub-processors to the same extent the Processor would be liable if performing the services of each Sub-processor directly under the terms of the DPA, subject to any limitations on liability set out in the terms of the Agreement.
12.3 The parties agree that the Controller shall be liable for any breaches of this DPA caused by the acts and omissions or negligence of its Affiliates as if such acts, omissions or negligence had been committed by the Controller itself.
12.4 The Controller shall not be entitled to recover more than once in respect of the same loss.
13. Term and Termination
13.1 The Processor shall only process Personal Data for the term of the DPA. The term of this DPA shall commence on the Effective Date of the Agreement and this DPA shall terminate automatically together with termination or expiry of the Agreement.
14. Deletion and Return of Personal Data
14.1 The Processor shall at the choice of the Controller, upon receipt of a written request received within 30 days of the end of the provision of the Services, delete or return Personal Data to the Controller. The Processor shall in any event delete all copies of Personal Data in its systems within 1 year of the effective date of termination of the Agreement or deactivation of the Controller’s account unless applicable law or regulations require storage of the Personal Data after termination.
15. General
15.1 This DPA sets out the entire understanding of the parties with regards to the subject matter herein.
15.2 Should a provision of this DPA be invalid or become invalid then the legal effect of the other provisions shall be unaffected. A valid provision is deemed to have been agreed which comes closest to what the parties intended commercially and shall replace the invalid provision. The same shall apply to any omissions.
15.3 Subject to any provision of the SCCs to the contrary, this DPA shall be governed by the laws of England and Wales. Any dispute arising under this DPA shall be resolved in accordance with the dispute resolution provisions of the Agreement.
15.4 The parties agree that this DPA is incorporated into and governed by the terms of the Agreement. By entering into the Agreement, the parties are deemed to have executed this DPA, including the SCCs and their Annexes incorporated by reference herein, as of the Effective Date of the Agreement. No further signature is required. A countersigned copy of this DPA is available on written request to [email protected].
15.5 In the event of any conflict or inconsistency between this DPA and the Agreement with respect to the processing of Personal Data or data protection compliance, this DPA shall prevail; in all other respects the Agreement shall prevail. Nothing in this DPA or the Agreement limits the rights of Data Subjects under Data Protection Law.
Exhibit A
List of Parties, Description of Processing and Transfer of Personal Data, Competent Supervisory Authority
A. List of Parties
The Exporter: means the Member.
| Address: | As set out for the Member in the Agreement. |
| Contact person’s name, position and contact details: | As set out for the Member in the Agreement. |
| Activities relevant to the data transferred under the SCCs: | Use of the Services. |
| Signature and date: | By entering into the Agreement, the Exporter is deemed to have signed the SCCs incorporated into this DPA and including their Annexes, as of the Effective Date of the Agreement. |
| Role: | Controller. |
| Name of Representative (if applicable): | Any UK or EU representative named in the Exporter’s privacy policy. |
The Importer: means Luvia Digital Limited
| Address: | 82b High Street, Sawston, Cambridge, England, CB22 3HJ, United Kingdom. |
| Contact person’s name, position and contact details: | Vinoop Thayatt, Director, [email protected] |
| Activities relevant to the data transferred under the SCCs: | The provision of cloud computing solutions to the Exporter under which the Importer processes Personal Data upon the instructions of the Exporter in accordance with the terms of the Agreement. |
| Signature and date: | By entering into the Agreement, the Importer is deemed to have signed the SCCs incorporated into this DPA and including their Annexes, as of the Effective Date of the Agreement. |
| Role: | Processor. |
B. Description of Processing and Transfers
| Categories of Data Subjects: | Controller End Users (Recipients) Description: Individuals who receive emails and other communications sent through your platform. Controller Account Holders Description: Employees or individuals authorized by the controller to access and manage the controller account. |
| Categories of Personal Data: | The Controller may submit Personal Data to the Services, the extent of which is determined and controlled by the Controller. The Personal Data includes but is not limited to: Controller:
End Users:
|
| Sensitive Data: | No sensitive data will be processed or transferred and shall not be contained in the content of, or attachments to, emails. |
| The frequency of the processing and transfer (e.g. whether the data is transferred on a one-off or continuous basis): | Continuous basis for the duration of the Agreement. |
| Nature of the processing: | Processing operations include but are not limited to the provision of email marketing services to the Member. |
| Purpose(s) of the data transfer and further processing: | Personal Data is transferred to sub-contractors who need to process some of the Personal Data in order to provide their services to the Processor as part of the Services provided by the Processor to the Controller. |
| The period for which the Personal Data will be retained, or, if that is not possible, the criteria used to determine that period: For transfers to (Sub-)processors, also specify subject matter, nature and duration of the processing: | Unless agreed otherwise in writing, for the duration of the Agreement, subject to clause 14 of the DPA. The Sub-processor list referenced in Exhibit C sets out the Personal Data processed by each Sub-processor and the services provided by each Sub-processor. |
C. Competent Supervisory Authority
| Identify the competent supervisory authority/ies (e.g. in accordance with Clause 13 of the SCCs) | Where the EU GDPR applies, the Irish Data Protection Authority - Data Protection Commission, (DPC). Where the UK GDPR applies, the UK Information Commissioner’s Office (ICO). Where the FADP applies, the Swiss Federal Data Protection and Information Commissioner, (FDPIC). |
Exhibit B
Technical and Organisational Security Measures
(Including Technical and Organisational Measures to Ensure the Security of Data)
Below is a description of the technical and organisational measures implemented by the Processor (including any relevant certifications) 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.
Where applicable this Exhibit B will serve as Annex II to the SCCs.
| Measure | Description |
|---|---|
| Measures of pseudonymisation and encryption of Personal Data | To ensure data security and compliance, the processor employs various measures: 1. TLS 1.3 Encryption: The processor uses Transport Layer Security (TLS) 1.3 to encrypt network traffic, ensuring that data transmitted between the platform and users is secure and protected from unauthorized access. 2. Private Networks: The processor connects all data sources through private networks, adding an additional layer of security by limiting access to authorized users and devices within the network. 3. Opportunistic TLS v1.2 or Higher for Email Delivery: When delivering emails to recipients, the processor opportunistically uses Transport Layer Security (TLS) version 1.2 or higher. This means that if the recipient’s email server supports TLS, the email transmission will be encrypted, enhancing the security of email communications. |
| Measures for ensuring ongoing confidentiality, integrity, availability and resilience of processing systems and services | Role-Based Access Controls (RBAC) and Least Privilege Principles: The processor uses RBAC and the principle of least privilege to restrict access to sensitive data and systems, ensuring that individuals only access the data required for their roles and specific tasks. Detailed Audit Logs: The processor maintains detailed audit logs of data access, modifications, and system events to detect and investigate unauthorized changes or anomalies. Implemented Redundancy: The processor implements redundancy for all critical databases to ensure data availability and resilience. Daily Data Backups: The processor performs daily backups of critical services and transfers backup data through AES encryption to multiple server locations to ensure data protection and availability. |
| Measures for ensuring the ability to restore the availability and access to Personal Data in a timely manner in the event of a physical or technical incident | The processor has implemented automated, regular daily backups of all critical personal data, with schedules based on data sensitivity and business requirements. The processor stores backups in multiple data centers, maintaining multiple versions of backups to protect against data corruption, ransomware, or accidental deletion. Additionally, the processor has documented a disaster recovery plan that includes step-by-step procedures for data restoration and system recovery, and has developed clear incident response procedures, including roles and responsibilities, communication protocols, and escalation paths. The processor regularly tests the restoration of backups to verify that data can be recovered successfully, implements continuous monitoring of systems to detect issues before they escalate into major incidents, and sets up automated alerts to notify IT staff of any anomalies or failures that could impact data availability. |
| Processes for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures in order to ensure the security of the processing. | The Processor conducts multiple internal audits. The Processor strives to automate audits hence the majority of our monitoring of its infrastructure is automated and running 24/7. The Processor obtains an external security and compliance audit once per calendar year. |
| Measures for user identification and authorisation | Remote access to the data processing systems is only possible through the Processor’s secure VPN tunnel. If the users first authenticate to the secure VPN tunnel, after successful authentication authorisation is executed by providing a unique username and password to a centralized directory service. All access attempts, successful and unsuccessful are logged and monitored. |
| Measures for the protection of data during transmission | Data in transit is protected by Transport Layer Security (“TLS”). |
| Measures for the protection of data during storage | The processor has configured all database servers on private networks. The controller’s data in transit is protected by Transport Layer Security (TLS). |
| Measures for ensuring physical security of locations at which Personal Data are processed | Employees are granted access only through encoded IDs featuring their photos. Visitors must register beforehand, typically at the main entrance, before gaining access. Third-party data centers are continuously monitored by security personnel. Both the physical and operational security standards adhere strictly to the requirements expected of data centers. |
| Measures for ensuring events logging | The processor records system inputs in the form of log files, facilitating retrospective reviews to ascertain whether and by whom Personal Data was entered, altered, or deleted. |
| Measures for ensuring system configuration, including default configuration | The processor has implemented version control for configuration files to track changes and enable rollbacks if necessary. Systems were configured with secure default settings by disabling or removing unnecessary services, applications, and user accounts to minimize vulnerabilities. Furthermore, the processor ensured that all systems and software remained up-to-date with the latest security patches and updates. Patches were thoroughly tested in a staging environment before deployment to production to prevent the introduction of new issues. |
| Measures for internal IT and IT security governance and management | The processor has instructed employees to collect, process, and use Personal Data strictly within the framework and for the purposes of their duties, such as service provision. At a technical level, the multi-client capability includes the separation of functions and appropriate segregation of testing and production systems. Employees, under the processor’s guidance, only have restricted access based on the requirements, ensuring that they can only access data necessary for their roles and responsibilities. The Controller’s Personal Data is stored in a manner that logically separates it from other customer data. |
| Measures for certification/assurance of processes and products | The Processor utilizes third-party data centers that maintain current ISO 27001 and GDPR certifications. The Processor will not utilize third-party data centers that do not maintain the aforementioned certifications and/or attestations, or other substantially similar or equivalent certifications and/or attestations. Upon the Controller’s written request (no more than once in any 12-month period), the Processor shall provide, within a reasonable time, a copy of the most recently completed ISO 27001 and GDPR certification and/or attestation reports (to the extent that to do so does not prejudice the overall security of the Services). Any audit report submitted to the Controller shall be treated as Confidential Information and subject to the confidentiality provisions of the Agreement between the parties. |
| Measures for ensuring data minimisation | To ensure compliance with data minimization principles, the processor has configured the system to require only the email address as mandatory when the controller uploads data for sending emails to end users, while any additional data fields are optional and can be provided based on the controller’s interest or specific needs. The processor implements Role-Based Access Control (RBAC) to ensure that individuals only access the data required for their roles, minimizing exposure to unnecessary data. Additionally, the processor applies the principle of least privilege, granting access only to the data needed for specific tasks. |
| Measures for ensuring data quality | All of the data that the Processor possesses is provided by the Controller. The Processor does not assess the quality of the data provided by the Controller. The Processor provides reporting tools within our product to help the Controller understand and validate the data that is stored. |
| Measures for ensuring limited data retention | The Processor uses a data classification scheme for all data that it stores and our retention policy specifies how each type of data is retained. When a record with Personal Data is deleted then it will be permanently evicted from our active databases. The data is retained in our backups until they are rotated out by more recent backups per the data retention policy. |
| Measures for ensuring accountability | The Processor internally reviews its information security policies semi-annually to ensure that it is still relevant and is being followed. All employees that handle sensitive data must acknowledge the information security policies. These employees are re-trained on information security policies once per year. A disciplinary policy is in place for employees that do not adhere to information security policies. |
| Measures for allowing data portability and ensuring erasure | The Services have built-in tools that allow the Controller to export and permanently erase data. |
| Measures to be taken by the (Sub-) processor to be able to provide assistance to the Controller (and, for transfers from a Processor to a Sub-processor, to the Data Exporter). | The transfer of Personal Data to a third party (e.g. customers, sub-contractors, service providers) is only made if a corresponding contract exists, and only for the specific purposes. If Personal Data is transferred outside the EEA, the Processor provides that an adequate level of data protection exists at the target location or organization in accordance with the European Union’s data protection requirements, e.g. by employing contracts based on the EU SCCs. |
Exhibit C
Authorized Sub-processors
The current list of authorized Sub-processors, including each Sub-processor’s purpose, processing location, transfer mechanism and supplemental measures, is published at:
https://www.mailercloud.com/legal/subprocessors/
The Processor shall provide the Controller with 30 days’ prior notification, via email, of any changes to the list of Sub-processors, in accordance with clause 6.3 of this DPA. To receive notifications of changes to the Sub-processor list, contact [email protected].
Grow with Mailercloud
Try mailercloud for a simplified and empowering email marketing journey.
Already have an account ? Log in