1.Background and purpose
1.1 This Data Processing Addendum and its appendices (“DPA”) are an integral part of the Fidify General Terms and Conditions and the Order Form, or of a separate service agreement, as the case may be (the “Main Agreement”), under which the Processor undertakes to provide SaaS services (the “Service”).
1.2 When used in this DPA, “Processor” refers to the Fidify entity identified as contracting entity in the Main Agreement and “Controller” refers to the commercial customer purchasing the Service. This DPA applies when the Controller purchases or renews a Service. The Processor and the Controller are referred to collectively as the “Parties” and individually as a “Party”.
1.3 In the event of inconsistency between the Main Agreement and this DPA, the Main Agreement generally prevails; however, this DPA prevails with respect to terms and issues relating specifically to the Processing of Personal Data.
1.4 In addition to the remuneration stipulated in the Main Agreement, the Processor is entitled to reasonable and evidenced costs directly attributable to assistance under section 4.12 that goes beyond what is required by Applicable Data Protection Law, or where the Controller imposes higher or additional requirements for handling and control than those stipulated in Applicable Data Protection Law. Such additional remuneration is charged at the professional services rate in the Fidify Price List (Appendix 2 to the Order Form), unless the Main Agreement provides otherwise.
1.5 Where the Controller is established in a jurisdiction covered by a Part of Appendix 2, as identified in the Order Form, that Part applies in addition to this DPA and prevails over the body of this DPA to the extent of any inconsistency.
2.Definitions
2.1 Except as set out below, words and expressions have the meaning given to them in the Main Agreement, unless the context requires otherwise.
“Applicable Data Protection Law”: the legislation protecting the fundamental rights and freedoms of individuals, and in particular their right to privacy with respect to the Processing of Personal Data, applicable in the country in which the Controller is established and/or in the jurisdiction in which the Processor or any Sub-processor is established, including the GDPR and the national laws identified in the applicable Part of Appendix 2;
“DORA”: Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector, as amended or supplemented from time to time;
“EEA”: the European Economic Area;
“GDPR”: Regulation (EU) 2016/679 of the European Parliament and of the Council;
“Personal Data”, “Personal Data Breach”, “Special Categories of Data”, “Process/Processing”, “Controller”, “Processor”, “Data Subject” and “Supervisory Authority” have the same meaning as in the GDPR. The competent Supervisory Authority for the Controller is identified in the applicable Part of Appendix 2 or, failing that, is the authority competent for the Controller under Applicable Data Protection Law;
“Portal”: the Fidify App or Fidify portal to which the Controller has access and through which the Controller may enrol its clients, its own organisation and its business relationships for document sharing and two-way communication;
“Standard Contractual Clauses”: the standard contractual clauses for the transfer of Personal Data to processors established in third countries adopted by the European Commission (Commission Implementing Decision (EU) 2021/914 of 4 June 2021);
“Sub-processor”: any processor (subcontractor) engaged by the Processor who Processes Personal Data on behalf of the Processor in accordance with the instructions provided, the terms of this DPA and the terms of the written subcontract;
“Technical and Organisational Security Measures” or “TOMs”: measures aiming at protecting Personal Data against accidental or unlawful destruction or accidental loss, alteration, unauthorised disclosure or access, in particular where the Processing involves the transmission of data over a network, and against all other unlawful forms of Processing, as published by the Processor at fidifygroup.com/toms-tsd.
3.Controller and Processor
3.1 The Controller determines the purpose and the means of the Processing of Personal Data and is therefore the data controller. The Controller is accordingly obliged to ensure that the Processing of Personal Data under the Main Agreement always rests on a legal basis in accordance with Applicable Data Protection Law.
3.2 As set out in the Main Agreement, the Processor has undertaken to assist the Controller in processing Personal Data and is therefore the data processor.
3.3 Where the Controller instructs the Processor, through the Service, to make Personal Data available to another customer of the Processor, the Processor does so as part of the Controller’s instructions. From the moment the Personal Data is made available, the receiving customer is a separate controller of it, and the Processor processes it on behalf of the receiving customer under that customer’s agreement with the Processor.
4.General obligations of the Processor
4.1 The Processor shall, when Processing Personal Data in the context of the Main Agreement, comply with Applicable Data Protection Law, as amended or replaced from time to time.
4.2 The Processor shall further adhere to the routines and instructions for such Processing communicated in writing by the Controller.
4.3 The Processor shall not Process Personal Data to which it is given access, or which is generated, in the context of the Main Agreement for any purpose other than to perform its obligations under the Main Agreement. The Processor shall not use such Personal Data for its own purposes, except where the Personal Data has first been irrevocably anonymised so that it no longer qualifies as Personal Data.
4.4 Without limiting the foregoing, the Processor may not Process Personal Data in other categories, in any other way, for other purposes or according to other instructions than those that follow from the Main Agreement or are specified in Appendix 1. Should the Processor find that the instructions are insufficient to perform its obligations under this DPA or the Main Agreement, the Processor shall inform the Controller without undue delay. Should performance under the Main Agreement be affected, the Processor shall inform the Controller and await further instructions.
4.5 The Processor shall implement and maintain throughout the term appropriate TOMs to ensure a level of security as required by Article 32 GDPR and Applicable Data Protection Law, to protect the Personal Data against unauthorised or unlawful Processing and against accidental or unlawful destruction or accidental loss, damage, alteration, unauthorised disclosure or access. In considering the appropriateness of the TOMs, the Processor shall take into account the state of the art, the costs of implementation and the nature, scope, context and purposes of Processing, as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons. The TOMs are subject to technical progress and further development; the Processor may implement alternative adequate measures as long as the level of security is maintained. The current TOMs are available on the Processor’s website.
4.6 The Controller warrants that only personnel or contractors who require access to Personal Data to perform their work duties will have access to the Personal Data and that such persons are subject to confidentiality undertakings regarding the Personal Data. The Processor shall only allow access to the Personal Data to personnel on a need-to-know basis and shall ensure that such personnel are bound by adequate confidentiality undertakings and are informed of and aware of Applicable Data Protection Law. The Processor shall also ensure that its personnel only Process Personal Data as instructed by the Controller, unless other Processing is required by law.
4.7 The Controller retains formal control of, and all ownership of and rights to, the Personal Data Processed by the Processor and any Sub-processor under this DPA. The Controller may require to receive the Personal Data at any time, and the Processor shall meet such request without undue delay in a suitable format.
4.8 The Processor shall inform the Controller as soon as possible in the event of attempted or successful unauthorised or unlawful access to, destruction of or change to Personal Data.
4.9 If a Data Subject, a Supervisory Authority or another third party requests information from the Processor regarding Personal Data, the Processor shall promptly refer such party to the Controller. The Processor is not entitled to disclose Personal Data or other information on the Processing without the explicit instruction or approval of the Controller, unless disclosure is required by law.
4.10 The Processor shall inform the Controller without undue delay of any contact with a Supervisory Authority that concerns or may affect the Processor’s Processing of Personal Data attributable to the Controller. The Processor is not entitled to represent or speak on behalf of the Controller in relation to a Supervisory Authority.
4.11 Other than to the extent covered by the Controller’s instructions, the Processor must not disclose Personal Data to third parties, change the purpose or the means of the Processing, take measures such as collecting, recording, changing, blocking, erasing or destroying Personal Data, multiply the data in the Controller’s database, or compile or merge the Personal Data.
4.12 The Data Subject has a right to request through the Controller a record of their Personal Data, data portability, correction, blocking or erasure of the Personal Data covered by this DPA. Once the Controller has, to the extent necessary, confirmed the identity of the Data Subject making a request, the Processor shall assist the Controller to the extent required for such requests to be fulfilled. The Processor shall also assist the Controller in its duties regarding security of Processing, contact with the Supervisory Authority, Personal Data Breaches, data protection impact assessments and prior consultation with the Supervisory Authority, taking into account the nature of the Processing and the information available to the Processor.
4.13 All Processing must be kept confidential, which means that the Processor, its employees and Sub-processors must not disclose any information to third parties without the Controller’s prior consent. The confidentiality undertaking does not apply to information made available to the Processor other than through performance of this DPA, or to information that is publicly known. The confidentiality undertaking survives termination of this DPA. Where the Controller is a regulated or licensed entity subject to statutory professional secrecy, confidentiality or similar obligations under the law applicable to its licence, authorisation or registration - including, without limitation, as a credit institution, professional of the financial sector, management company, alternative investment fund manager, fund administrator, payment institution, electronic money institution, insurance or reinsurance undertaking, or any corresponding status under the law of another jurisdiction - as identified in the Order Form or the applicable Part of Appendix 2, the Processor acknowledges that information relating to the Controller’s clients that the Processor may access in providing the Service may constitute confidential information covered by that obligation, undertakes to treat such information accordingly, shall ensure that any Sub-processor with access to such information is bound by equivalent obligations, and acknowledges that this obligation survives termination of this DPA without time limit to the extent required by the law identified there.
4.14 Upon termination of the Main Agreement, the Processor shall, as instructed by the Controller, either irrevocably anonymise all Personal Data stored or Processed by the Processor under the Main Agreement so that it cannot be recreated, or return or erase all Personal Data. The Processor shall also delete all copies of Personal Data unless applicable law requires that the data is retained. Return of the Personal Data, or confirmation of its deletion, shall be provided to the Controller within ninety (90) days following termination of the Main Agreement, unless extended paid storage of Personal Data has been agreed, in which case this DPA continues to apply. Where section 15 of the Fidify General Terms and Conditions applies, the transition period agreed there runs before this ninety-day period.
5.Use of Sub-processors
5.1 The Controller grants the Processor a general authorisation to engage Sub-processors, provided that the Processor ensures that Articles 28(2) and 28(4) GDPR are met and that the Sub-processors provide adequate guarantees to implement appropriate TOMs to fulfil the requirements of this DPA and Applicable Data Protection Law. The Processor shall ensure that all Sub-processors are bound by written agreements imposing corresponding obligations when Processing Personal Data on behalf of the Controller. The Processor shall maintain an up-to-date list of Sub-processors on its website and remains responsible towards the Controller for any Processing carried out by a Sub-processor.
5.2 The Processor is entitled to engage new Sub-processors and to replace existing Sub-processors. In that case the Processor shall verify the new Sub-processor’s capacity and ability to meet its obligations under Applicable Data Protection Law. The Processor shall inform the Controller (for example by email or within the Service) of its intention to engage or replace a Sub-processor, stating the new Sub-processor, the type of data and categories of Data Subjects concerned, and where the Personal Data will be stored. The Controller is entitled to object in writing within fourteen (14) days of the notice. If the Controller does not object within that period, the new Sub-processor is deemed accepted. If the Controller makes a legitimate objection and the Processor does not accept it, the Processor may, at its discretion, either perform the Service without the intended change or, if performance without the change is unreasonable for the Processor, terminate the Main Agreement including this DPA on thirty (30) days’ written notice from receipt of the objection.
5.3 Upon request, the Processor shall provide the Controller with a correct and up-to-date list of the Sub-processors engaged to Process Personal Data on behalf of the Processor, and the geographic location of the Processing. The Processor may fulfil this obligation by referring the Controller to the list on its website.
5.4 The Processor will impose on Sub-processors data protection terms that provide at least the same level of protection for Personal Data as this DPA, to the extent applicable to the nature of the services provided by the Sub-processor. The Processor remains responsible for each Sub-processor’s compliance with this DPA and for any acts or omissions of a Sub-processor that cause the Processor to breach this DPA or Applicable Data Protection Law.
6.International data transfers
6.1 Where the Processor and/or a Sub-processor transfers Personal Data to a location outside the EEA (or, where the Controller is established outside the EEA, outside the Controller’s jurisdiction as set out in the applicable Part of Appendix 2), the Processor and/or Sub-processor shall ensure that such transfer complies with Applicable Data Protection Law, including Chapter V GDPR where applicable. Such requirements will, where suitable, be fulfilled by entering into the Standard Contractual Clauses or by another transfer mechanism permitted under Article 44 et seq. GDPR or the corresponding provisions of Applicable Data Protection Law. The Processor shall keep the Controller informed of the grounds for transfer.
6.2 The Processor’s affiliate Fidify (Mauritius) Ltd provides support and operational services to the Processor and may access Personal Data hosted in the EEA remotely from Mauritius. This access is covered by the Standard Contractual Clauses between the Processor and its affiliate and by the supplementary measures described in the TOMs.
7.Audits
7.1 The Controller is entitled to verify, itself or through an independent third party (who must not be a competitor of the Processor), that the Processor complies with this DPA, Article 28(3) GDPR and the Controller’s instructions. After thirty (30) days’ prior notice, the Processor shall reasonably assist the Controller and provide the documentation required to carry out such verification. Audits shall be carried out during the Processor’s normal office hours and conducted so that the Processor’s operations are not disturbed. The cost of an audit shall be borne by the Controller. Where the Controller is a regulated financial entity to which section 15 of the Fidify General Terms and Conditions applies, the additional audit rights of the Controller, its auditors and its competent authorities set out there apply in addition to this section 7.
7.2 The Processor may make an inspection conditional upon the signing of a confidentiality agreement to protect the data of other customers, information about the Processor’s TOMs, and the Processor’s business and trade secrets. The Controller shall ensure that its personnel conducting an audit are subject to adequate secrecy obligations.
7.3 If the Parties agree that an audit is to be performed by an external auditor, the auditor is appointed by the Controller and approved by the Processor. Both Parties are entitled to receive a copy of the audit report.
7.4 If an audit reveals non-compliance with this DPA, the Processor shall notify the Controller immediately and remedy the non-compliance without undue delay.
7.5 The Processor shall procure that the Controller is similarly entitled to conduct audits in respect of Sub-processors.
8.Personal Data Breaches
8.1 The Processor shall notify the Controller without undue delay, and in any event within forty-eight (48) hours, after becoming aware of a Personal Data Breach affecting Personal Data Processed under this DPA, unless the Order Form specifies a shorter deadline of twenty-four (24) hours, in which case that shorter deadline applies. The Processor’s own assessment of the likely risk to Data Subjects does not relieve it of this notification obligation; the assessment of whether the Supervisory Authority or Data Subjects must be notified is made by the Controller.
8.2 The notification under section 8.1 must, to the extent relevant and available: (a) describe the Personal Data Breach, including the categories and approximate number of Data Subjects and Personal Data records concerned; (b) state the date and time of the Personal Data Breach and of its discovery; (c) describe the likely consequences and potential risk to Data Subjects; (d) describe the measures proposed or taken to address the breach, including to mitigate its effects and prevent recurrence; and (e) include any other information required for the Controller to comply with Applicable Data Protection Law. Where the information cannot be provided at the same time, it may be provided in phases without undue further delay.
8.3 The Controller is responsible for notifying the competent Supervisory Authority and, where required, Data Subjects, within the time limits imposed by Applicable Data Protection Law. Where the Controller is a regulated financial entity to which section 15 of the Fidify General Terms and Conditions applies, the Processor shall also assist the Controller with ICT-related incident reporting to the Controller’s competent authorities as required under the applicable Outsourcing Rules, including, as applicable, Article 19 DORA or, for Controllers to which DORA does not apply, the equivalent incident-reporting requirements or other applicable outsourcing rules identified in the Order Form.
8.4 The Processor shall document all Personal Data Breaches, including the facts, their effects and the remedial action taken, in a manner that enables the Supervisory Authority to verify compliance with this DPA and Applicable Data Protection Law. The documentation shall only include information necessary for that purpose.
9.Liability and limitation of liability
9.1 Unless otherwise agreed in the Main Agreement, a Party in breach of this DPA is liable for documented and relevant damage suffered by the other Party. Neither Party is liable for indirect or consequential damage. Liability under this DPA for damage not covered by section 10 is limited to the amount paid by the Controller under the Main Agreement during the twelve (12) months preceding the breach. This limitation operates solely between the Parties and does not limit or affect the Controller’s own regulatory responsibilities to its competent authorities.
9.2 The limitation in section 9.1 does not apply where the breach is caused by intent or gross negligence.
10.Liability for damage in connection with the Processing
10.1 Where compensation for damage in connection with the Processing is to be paid to a Data Subject, by judgment or settlement, due to an infringement of this DPA, the Controller’s instructions or Applicable Data Protection Law, Article 82 GDPR (or the corresponding provision of Applicable Data Protection Law identified in Appendix 2) applies.
10.2 Fines under Article 83 GDPR or under Applicable Data Protection Law are borne by the Party named as recipient of the sanction.
10.3 If either Party becomes aware of circumstances that could be detrimental to the other Party, it shall immediately inform the other Party and work actively with it to prevent and minimise the damage or loss.
10.4 Regardless of the content of the Main Agreement, sections 10.1 and 10.2 take precedence over other rules on the allocation of claims between the Parties as far as the Processing is concerned.
11.General notifications
11.1 The Processor shall without undue delay notify the Controller in writing of: (a) any request or complaint from a Data Subject; the Processor shall not respond to that request or complaint unless authorised to do so, responding being the responsibility of the Controller; and (b) any request from a Supervisory Authority or other public authority requiring access to or information regarding the Processor’s or a Sub-processor’s Processing of Personal Data covered by this DPA, including any legally binding request for disclosure of Personal Data by a law enforcement authority, unless notification is prohibited by law.
12.Amendments
12.1 The Parties may amend this DPA to the extent necessary to comply with Applicable Data Protection Law or to enable the Processing. Amendments enter into force thirty (30) days after written notification (email sufficing) to the other Party.
12.2 The Controller shall be notified if the Service is changed in such a way that new functionality is included which may result in other categories of Processing.
13.Term and termination
13.1 This DPA remains in force for as long as the Processor Processes or has access to Personal Data on behalf of the Controller in the context of the Main Agreement.
13.2 Upon expiry or termination, the Processor and any Sub-processors shall, at the choice of the Controller and in accordance with section 4.14, return all Personal Data and copies thereof to the Controller or destroy all Personal Data and certify to the Controller that they have done so, unless legislation applicable to the Processor prevents it from returning or destroying all or part of the Personal Data. In that case the Processor warrants that it will guarantee the confidentiality of the Personal Data and will not actively Process it any further.
14.Governing law and legal venue
14.1 This DPA is governed by the law, and disputes are resolved in the forum, specified for the Main Agreement in the Jurisdiction Schedule to the Fidify General Terms and Conditions, as identified in the Order Form.
14.2 Where the applicable Part of Appendix 2 provides that references to the GDPR are to be read together with, or replaced by, provisions of national law, that Part applies.
15.Regulatory cooperation
15.1 Where the Controller is a regulated financial entity, the Processor’s obligations regarding regulatory information, audit and inspection rights, cooperation with competent authorities, incident reporting, sub-contracting notification, termination rights and exit and transition assistance are set out in section 15 of the Fidify General Terms and Conditions, which applies to the Processing under this DPA as if set out here. In the event of conflict between that section and this DPA in respect of Personal Data, this DPA prevails.
Appendix 1:Instructions on Processing covered by the DPA
| Purpose | Categories of Personal Data | Type of Processing | Legal basis (determined by the Controller) |
|---|---|---|---|
| To provide the Portal and the User Account. | Name; personal identification number; contact details (e.g. address, email and phone number); position at employer or job title; passport and passport photo; facial image for identity verification; CV; other Personal Data contained in documents requested by the Controller. | Creation and provision of the User Account. Requesting, receiving, storing and displaying the Personal Data as part of the Controller’s KYC and AML routines, as determined by the Controller. Biometric comparison of the facial image with the identity document, where the Controller’s onboarding flow requires it. | Performance of the user account agreement for use of the Portal; the Controller’s legal obligations under applicable AML legislation; for Special Categories of Data, a condition under Article 9(2) GDPR established by the Controller (typically explicit consent of the Data Subject). |
| To prevent abuse of the Service and to prevent and investigate crimes against the Processor. | User-generated data (e.g. access and error logs). | Preventing unauthorised use of the Portal; protecting and improving the IT environment against attacks and intrusion. | Compliance with a legal obligation (if any) or legitimate interest in preventing abuse of the Service. |
| To deliver an individually adapted experience of the Portal. | Name; IP address; language settings; user-generated data (e.g. reading history). | Simplification of the use of the Portal (e.g. saving language selection and identifying device type). | Performance of the user account agreement for use of the Portal. |
| To handle customer service issues. | Name; email address. | Handling support requests. | Performance of the user account agreement for use of the Portal. |
| To provide AI-assisted features of the Service (e.g. risk assessment and compliance review support). | The Personal Data listed for the Portal above, to the extent included in documents or fields the Controller submits to the AI-assisted feature. | Automated analysis and summarisation of submitted content to support the Controller’s review. No decision producing legal or similarly significant effects is taken by the Processor. | Performance of the user account agreement for use of the Portal; the Controller’s legitimate interest or legal obligation, as determined by the Controller. |
Categories of Data Subjects: the Controller’s clients and their representatives, beneficial owners and contact persons; the directors, beneficial owners and staff of the Controller’s own organisation; the representatives, beneficial owners and contact persons of the Controller’s investors, counterparties, service providers and other business relationships; the Controller’s authorised users.
Duration of Processing: the term of the Main Agreement and the period set out in section 4.14.
Appendix 2:Jurisdiction-specific terms
The Order Form identifies which Part of this Appendix 2 applies. Where no Part is identified, none applies and the body of this DPA governs.
Part A: European Union and Luxembourg
A.1 Where the Controller is established in the Grand Duchy of Luxembourg, Applicable Data Protection Law includes the GDPR and the Law of 1 August 2018 on the organisation of the Commission nationale pour la protection des données (CNPD) and the general data protection framework, as amended (the “Luxembourg Data Protection Law”). The competent Supervisory Authority is the CNPD. References to the GDPR in this DPA are read together with the Luxembourg Data Protection Law; where the latter imposes additional or more specific requirements, those apply in addition to the GDPR.
A.2 Where the Controller is established in another EU or EEA member state, Applicable Data Protection Law includes the GDPR and the national supplementary legislation of that state, and the competent Supervisory Authority is the authority of that state.
A.3 Where the Controller is subject to statutory professional secrecy, banking secrecy, or an equivalent confidentiality obligation under the law, regulation, or licence conditions applicable to it (including, where the Controller is a credit institution or other professional of the financial sector within the meaning of the Law of 5 April 1993 on the financial sector, as amended, the obligation under Article 41 thereof), the Processor’s confidentiality obligations under this DPA extend to all information covered by that obligation, and the Processor shall treat such information with the same degree of care as the Controller is itself required to apply, as identified in the Order Form, and section 4.13 of this DPA applies accordingly.
A.4 Luxembourg regulatory framework (for information):
| Applicable legal instrument | Luxembourg implementing or supplementary provision |
|---|---|
| GDPR (Regulation (EU) 2016/679) | Law of 1 August 2018 on the organisation of the CNPD and the general data protection framework |
| Directive 2002/58/EC (ePrivacy Directive) | Law of 30 May 2005 on specific provisions for the protection of persons with regard to the processing of personal data in the electronic communications sector, as amended |
| Regulation (EU) 2022/2554 (DORA) | Directly applicable; supplemented by CSSF Circular 22/806 on outsourcing arrangements and applicable CSSF guidance, as amended or replaced |
| Professional secrecy (financial sector) | Article 41 of the Law of 5 April 1993 on the financial sector, as amended (credit institutions and other professionals of the financial sector), as an example of the statutory professional secrecy or equivalent confidentiality obligation referred to in section A.3; the applicable regime for other regulated Controllers (e.g. management companies or alternative investment fund managers) is identified in the Order Form |
| Supervisory authority (data protection) | Commission nationale pour la protection des données (CNPD), cnpd.public.lu |
| Supervisory authority (financial sector) | Commission de Surveillance du Secteur Financier (CSSF) |
Part B: Mauritius
B.1 Where the Controller is established in the Republic of Mauritius, Applicable Data Protection Law includes the Mauritius Data Protection Act 2017 (Act No. 20 of 2017, in force 15 January 2018) (the “Mauritius DPA”) and, where the Controller is also subject to the GDPR, the GDPR. The competent Supervisory Authority is the Data Protection Office (Data Protection Commissioner) of Mauritius.
B.2 Where Mauritian law applies to this DPA, references to Articles of the GDPR in this DPA, or otherwise in the context of the Processor providing the Service to the Controller, are deemed replaced in full by the sections of the Mauritius DPA set out in the table below. Where the Mauritius DPA contains no equivalent to a provision of the GDPR, the GDPR provision does not apply, unless the Controller is independently subject to the GDPR.
B.3 In section 6.1, transfers “outside the EEA” are read as transfers outside Mauritius, and the transfer conditions of section 36 of the Mauritius DPA apply.
B.4 Equivalency table GDPR to Mauritius DPA:
| GDPR Article | Mauritius Data Protection Act 2017 section |
|---|---|
| Article 1 - Subject-matter and objectives | Not applicable - no equivalent |
| Article 2 - Material scope | Section 3 - Application of Act |
| Article 3 - Territorial scope | Section 4 - Territorial application |
| Article 4 - Definitions | Section 2 - Interpretation |
| Article 5 - Principles relating to processing of personal data | Section 21 - General data processing principles |
| Article 6 - Lawfulness of processing | Section 28 - Lawfulness of processing |
| Article 7 - Conditions for consent | Section 24 - Conditions for consent |
| Article 9 - Processing of special categories of personal data | Section 29 - Processing of special categories of personal data |
| Article 15 - Right of access | Section 37 - Right of access |
| Articles 16, 17 and 18 - Rectification, erasure and restriction | Section 39 - Rectification, erasure or restriction of processing |
| Article 20 - Right to data portability | Not applicable - no equivalent |
| Article 21 - Right to object | Section 40 - Right to object |
| Article 22 - Automated individual decision-making | Section 38 - Right to refuse automated processing |
| Article 28 - Processor | Section 31 - Security of processing |
| Article 30 - Records of processing activities | Section 33 - Records of processing activities |
| Article 32 - Security of processing | Section 31 - Security of processing |
| Article 33 - Notification of a personal data breach to the supervisory authority | Section 25 - Notification of data breach |
| Article 34 - Communication of a personal data breach to the data subject | Section 26 - Communication of data breach to the data subject |
| Article 35 - Data protection impact assessment | Section 34 - Data protection impact assessment |
| Chapter V (Articles 44 to 50) - Transfers outside the EEA | Section 36 - Transfer of personal data outside Mauritius |
| Article 82 - Compensation and liability | Not applicable - no equivalent |
| Article 83 - Administrative fines | Not applicable - no equivalent |
Part C: Kenya
C.1 Where the Controller is established in the Republic of Kenya, Applicable Data Protection Law includes the Data Protection Act 2019 and the regulations made under it. The competent Supervisory Authority is the Office of the Data Protection Commissioner (ODPC).
Part D: Zimbabwe
D.1 Where the Controller is established in the Republic of Zimbabwe, Applicable Data Protection Law includes the Cyber and Data Protection Act [Chapter 12:07] (2021) and the regulations made under it. The competent Supervisory Authority is the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ).
Part E: United States
E.1 Where the Controller is established in the United States and requires service-provider or processor terms under applicable state privacy law, the Parties will agree such terms in the Order Form or a separate addendum.