Caseware Legal
The Caseware Legal page provides centralized access to Caseware’s legal policies, agreements, and compliance resources. Explore important information related to privacy, security, AI, accessibility, and product usage in one place.

Data Processing Agreement
Caseware Data Processing Agreement
Version: 5.0
Last Updated: November 2026
RECITALS
(A) Customer is the controller of the Personal Data processed under this DPA and is responsible for ensuring that the processing is carried out in accordance with applicable Data Protection Laws.
(B) Caseware is the processor of the Personal Data under this DPA and shall process Personal Data only in accordance with Customer’s documented instructions and the terms of this DPA.
(C) The Parties wish to set out in this DPA the terms and conditions under which Caseware will process Personal Data on behalf of Customer.
1. Introduction & Scope
This Data Processing Agreement (“DPA”) is incorporated by reference into the Master Product and Services Agreement (“MPSA”) entered into by Caseware International Inc.
or the Affiliate of Caseware International Inc. identified in the applicable Order Form (collectively “Caseware” or the “Processor”) and the customer identified therein (the “Customer” or “Controller”).
Caseware may update this DPA from time to time. As the Processor may have access to Personal Data in providing Services (defined below), the Customer (as the Controller) and Caseware (as the Processor) require a contractual agreement concerning the collection, processing and use of Personal Data accessed by the Processor to help ensure the Personal Data receives protection substantially equivalent to that afforded by the Controller. This DPA governs the duration of the processing, the nature and purpose of the processing, the type of Personal Data being processed, the categories of Data Subjects and the rights and obligations of the Controller and of the Processor.
Customer and Caseware are separately referred to as “Party” and collectively as “Parties”.
2. Definitions
Capitalized terms not defined in this DPA shall have the meaning given to them in the MPSA.
“CCPA” means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020 (Cal. Civ. Code §§ 1798.100 et seq.), together with its implementing regulations.
“Customer Information” means business contact and account information relating to Customer’s personnel, including names, work email addresses, work telephone numbers, job titles and account details, that Caseware processes for account administration, contracting, billing, relationship management or direct communications with Customer’s personnel. To the extent Caseware determines the purposes and means of such processing, Caseware processes Customer Information as an independent controller in accordance with Caseware’s Privacy Statement, as updated from time to time (https://www.caseware.com/legal/privacy-statement).
“Data Protection Laws” shall mean all data protection and privacy laws applicable to the processing of Personal Data according to the territorial origin of the Personal Data.
“Data Subject” shall mean an identified or identifiable natural person related to the Personal Data. Data Subject shall be equivalent to “Consumer” (as defined pursuant to the CCPA).
“GDPR” shall mean 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). Terms used but not otherwise defined in this DPA that are defined in the GDPR shall have the meaning given to them in the GDPR.
“Personal Data” or “personal data” means any information relating to an identified or identifiable natural person. For the purposes of this DPA, Personal Data means Personal Data processed by Caseware on behalf of Customer in connection with the Caseware Offerings. This DPA does not apply to Customer Information.
“Restricted Transfer” shall mean (i) a transfer of Personal Data from Customer to Caseware; or (ii) an onward transfer of Personal Data from Caseware to a Sub-Processor, or (iii) an onward transfer between two establishments of Caseware or a Sub-Processor; in each case, where such transfer would be prohibited by Data Protection Laws (or by the terms of data transfer agreements put in place to address the data transfer restrictions of Data Protection Laws), authorisation mechanisms will be applied as required by applicable Data Protection Laws.
“Services” means, for purposes of this DPA, the Caseware Offerings as defined in the MPSA.
“Standard Contractual Clauses” shall mean the standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council approved by decision of the European Commission on June 4, 2021.
“Sub-Processor” shall mean any person or entity appointed by or on behalf of Caseware to process Personal Data on behalf of Caseware in connection with the Services and shall include any Sub-Processor rightfully appointed by a Sub-Processor (a Sub-Sub-Processor) to process Personal Data on behalf of Caseware in connection with the Services but shall not include any individual employee of Caseware or a Sub-Processor.
3. Type of Data
The following types/categories of data that may be collected, processed and/or used by Caseware include:
· Personal Data (e.g., last name, first name, address and date of birth);
· Communication data (e.g., telephone number, fax, email);
· Contract data (e.g., billing and payment details);
· IT usage data (e.g., user ID, passwords and roles);
· Bank data (e.g., bank account details and credit card number); and/or
· Any other categories of Personal Data that the Customer, in its capacity as controller, chooses to process using the Caseware Offerings.
4. Data Subjects
Data Subjects which may be affected by using their Personal Data include:
· The Customer’s clients/service recipients;
· The Customer’s employees or contractors;
· The Customer’s suppliers/service providers and/or;
· Any other categories of Data Subjects whose Personal Data the Customer, in its capacity as controller, processes using the Caseware Offerings.
5. Place of Data Processing
Caseware uses third-party hosting and infrastructure providers, including Amazon Web Services (AWS), to provide the Caseware Offerings. The primary hosting location applicable and / or available to a Customer is determined by the relevant Caseware Offering, the Customer's location and the applicable Order Form or product documentation. Caseware currently operates primary cloud hosting environments in Australia, Canada, Ireland and the United States.
Certain support, security, document-processing and AI-enabled functionality may involve the processing of Personal Data outside the Customer's primary hosting region. Where such processing constitutes an international or Restricted Transfer, Caseware will use reasonable efforts to make sure that the transfer is made in accordance with applicable Data Protection Laws and is subject to an appropriate transfer mechanism and supplementary safeguards where required. These measures may include an applicable adequacy decision, the Standard Contractual Clauses, the UK Addendum, a transfer impact assessment and appropriate contractual, technical and organizational safeguards.
Where a Customer’s data hosted in Canada uses AI-enabled features, including Caseware Verity, model inference requests (the prompt and the generated response) may be processed in AWS regions in Canada or the United States through Amazon Bedrock cross-region inference. This does not change the Customer's primary hosting region, where Customer Data is stored. Current processing locations for each Sub-Processor are set out in Attachment 2.
6. Instructions
Caseware shall process Personal Data for the purposes of: (i) processing as required by Customers in their use of the Services; (ii) processing in accordance with the MPSA, this DPA and any other agreements between the Parties; (iii) processing to comply with other reasonable instructions provided by Customer where such instructions are consistent with the terms of the MPSA, applicable laws and DPA. Caseware will inform Customer if, in Caseware’s opinion, the Customer’s instructions or requests are contrary to Data Protection Laws, with reasons therefore by email.
7. Confidentiality Commitment by Caseware
Caseware shall use reasonable efforts to make sure (a) the reliability of all individuals who could potentially access the Personal Data through appropriate screening measures, including background checks where permitted by applicable law and proportionate to the individual’s role; (b) that all such individuals are subject to confidentiality undertakings at least as restrictive as those set forth in the MPSA and will treat the Personal Data as Confidential Information; and (c) that all such individuals have undergone training in the care, protection, and handling of Personal Data.
Where Customer is a professional subject to statutory professional secrecy obligations under §203 StGB (Berufsgeheimnisträger), including Wirtschaftsprüfer, Steuerberater and Rechtsanwälte, the parties shall supplement this DPA with the applicable §203 StGB addendum. Where required, all Caseware personnel and Sub-Processors with access to protected data shall be bound by substantially equivalent confidentiality obligations.
Caseware shall not use Customer Data, Input or Outputs to train or fine-tune AI Models without Customer’s prior written authorization. The Parties agree that Customer discloses Personal Data to Caseware only for these limited and specified Business Purposes.
8. Technical & Organizational Measures
Caseware shall implement the necessary technical and organizational measures (“TOMs”) to ensure a level of security appropriate to the risk. These may include, as appropriate:
- the pseudonymization and encryption of Personal Data;
- availability and resilience of processing systems and services;
- the ability to restore the availability of and access to Personal Data in a timely manner in the event of a physical or technical incident; and
- a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing and maintaining these measures for the duration of the contract.
Caseware will implement appropriate technical and organizational measures to protect Customer’s Personal Data against unauthorized or unlawful processing and against accidental loss, destruction, damage, alteration or disclosure. When implementing and updating such technical and organizational measures ensuring a level of security appropriate to the risk, Caseware will have regard to 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. Without limiting the generality of the foregoing, Caseware has carried out the technical and organizational measures (“TOMs”) specified in Attachment 1 to this DPA.
Caseware engages approved Sub-Processors to provide parts of the Services. The TOMs therefore depend partially on these Sub-Processors, as also described in Attachment 1, provided that Caseware remains responsible for its compliance with the TOMs regardless of its reliance on Sub-Processors. Caseware may decide on commercially reasonable improvements of the TOMs and provide the Customer on request with an updated Attachment 1.
9. Global Data Protection Officer
Caseware has appointed a Global Data Protection Officer (DPO) pursuant to Article 37 GDPR. The DPO can be contacted at:
· Anouschka van de Graaf, Global Data Protection Officer;
· Caseware International Inc.;
Current DPO contact details are also accessible on Caseware’s website at www.caseware.com/legal.
10. Sub-Processors
Customer acknowledges and agrees that Caseware may engage Sub-Processors in the provision of Services, subject to the terms and conditions of this DPA, and that (i) a Caseware Affiliate may be retained as a Sub-Processor; and (ii) Caseware or a Caseware Affiliate may engage third-party Sub-Processors.
This DPA applies under Module 2 (Controller to Processor) where Customer acts as controller of the Personal Data. Where Customer acts as processor for its own clients (for example, accounting firms, trust and administration service providers), and engages Caseware as sub-processor, Customer warrants that it has obtained the necessary authorizations and/or consents from its own clients. The parties acknowledge that Module 3 (Processor to Processor) Standard Contractual Clauses may be required in such cases and will be made available upon written request.
Where Caseware engages a Sub-Processor in the provision of Services, a data processing agreement will be entered into with the Sub-Processor. A list of Caseware’s current Sub-Processors is available in Attachment 2.
Caseware will notify Customer of any intended addition or replacement of a Sub-Processor by updating the Sub-Processor List at trust.caseware.com/subprocessors. Customers may subscribe to receive notifications of updates via the Trust Center. Customer may object in writing within a reasonable period after notification where Customer reasonably believes that the intended appointment would violate applicable Data Protection Laws or present a material data protection risk. In the event of a reasonable objection, the Parties will endeavour to resolve the matter without undue delay. Caseware will use reasonable efforts to make available to Customer a change in Services to avoid processing of Customer Information or Personal Data by the objected-to Sub-Processor without unreasonably burdening Customer. If Customer objects to a new Sub-Processor that is necessary for the provision of the Services, Customer may terminate the affected subscription without penalty by providing written notice before the end of the notice period.
If use of a Sub-Processor involves a Restricted Transfer, Caseware shall ensure that the authorisation required under applicable law is incorporated into an agreement between Caseware and the Sub-Processor; and between the Sub-Processor and any Sub-Sub-Processor.
11. Data Subject Requests
Caseware shall reasonably support the Customer in the case of Data Subject access, rectification or erasure requests, insofar as Customer cannot fulfill such a request on its own, to the extent legally permitted and technically possible. Customers shall pay Caseware’s costs for such support, to the extent legally permitted. If a Data Subject request is received by Caseware that relates to Personal Data transferred by the Customer, Caseware will refer the request to the Customer. Unless required by law, Caseware will not respond to such a request but shall instead support Customer as provided in this Section.
12. Data Breach Notification
Caseware shall inform Customer promptly and in any event within 72 hours after becoming aware of a breach of the Personal Data (meaning a breach of security leading to destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise processed), including a breach at a Sub-Processor, and shall provide the necessary information to allow Customer to inform authorities and Data Subjects. Where not all information is available at the time of notification, Caseware may provide information in phases as it becomes available. Caseware shall take reasonable efforts to remediate the cause of such data breach and mitigate (potential) damage resulting from the breach.
The notification to Customer will include at least a) the nature of the breach, b) the impacted data categories, c) the identified and potential consequences of the breach and d) the measures Caseware takes to mitigate the consequences of the breach. At the request of Customer, Caseware shall assist Customer in notifying the breach to a Supervisory Authority and/or the Data Subjects concerned.
13. Data Protection Impact Assessment (DPIA)
Upon request by Customer, Caseware shall provide reasonable assistance to Customer in conducting a DPIA, solely in relation to Caseware’s processing of Customer’s Personal Data and taking into account the nature of the processing and information available to Caseware and Sub-Processors. Customers shall pay Caseware’s costs for such support, to the extent legally permitted.
14. Deletion or Returning Personal Data
Upon termination or expiry of the MPSA, Caseware will make Customer’s Personal Data available for export or return in accordance with the offboarding provisions of Section 11.6 of the MPSA. Following the applicable offboarding period, Caseware will delete or destroy the remaining Personal Data, except to the extent retained in accordance with Caseware’s standard backup, archival or legal retention practices or as otherwise required by applicable law. Personal Data retained in backups or archives will remain subject to the protections of this DPA and will not be processed for any other purpose, except as required by applicable law, until deleted in accordance with Caseware’s applicable retention practices.
15. Information & Audit Rights
Customers may obtain information on existing Caseware security certifications at Caseware’s Trust Center (trust.caseware.com). Upon Customer’s request, Caseware shall make available to Customer, or a third-party auditor instructed by Customer, once a year, information regarding Caseware’s compliance with this DPA and Data Protection Laws. Caseware may satisfy such requests by providing copies of its then-current third-party audit reports or certifications; if Customer reasonably demonstrates that such reports are insufficient onsite audits may be conducted. Any audit may include Caseware submitting its data processing facilities, data files and documentation needed for processing Personal Data (and/or those of its agents, affiliates and Sub-Processors) to reviewing, auditing and/or certifying by Customer (or any independent or impartial inspection agents or auditors selected by Customer and not reasonably objected to by Caseware), with reasonable notice and during regular business hours. Customer shall bear the costs of any audit and shall ensure that all audit findings are treated as Caseware’s Confidential Information. Before any information or audit is provided, the Parties shall mutually agree on the scope, timing, and duration of such audit.
16. Restricted Transfers from the EU, Switzerland and the UK
Any transfer of Personal Data from the EU, Switzerland, the UK or the EEA to a country outside such areas that does not ensure an adequate level of protection as determined by decision of the EU Commission, or UK or Swiss regulatory authorities, will be subject to the applicable Standard Contractual Clauses (or applicable equivalent promulgated by the UK or Swiss regulatory authorities), at Attachment 3 and any transfer of Personal Data from the UK or Switzerland to a country that does not ensure an adequate level of protection as determined by decision of the EU, UK, or Swiss regulatory authorities, will be subject to the applicable equivalent to the SCCs used at the time, including the UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, at Attachment 4.
Customers transferring Personal Data from the EU, Switzerland, the EEA or the UK to Caseware will be considered a “Data Exporter”, and Caseware will be considered a “Data Importer” (both terms as defined in the Standard Contractual Clauses). Customer (as "data exporter") and Caseware (as "data importer") hereby enter into the Standard Contractual Clauses or the UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, as applicable, in respect of any Restricted Transfer from Customer to Caseware.
The Standard Contractual Clauses or the equivalent Swiss or UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, as applicable, shall come into effect upon execution of the MPSA.
17. California Specific Provisions
To the extent that Caseware processes any Personal Data relating to individuals who are California residents, Caseware shall comply with the requirements of the CCPA, including any amendments and implementing regulations that become effective on or after the effective date of this DPA, and shall provide the same level of privacy protection as is required by the CCPA. Capitalized terms used but not defined in this Section 17 shall have the same meaning as in the CCPA. For the purposes of the CCPA, the parties agree that Caseware is a “Service Provider” in the performance of its obligations, and that Customer is a “Business,” and that the transfer of Personal Data to Caseware shall not be considered a “Sale” or “Sharing.” To the extent required by the CCPA, Caseware shall (a) grant Customer the right to take reasonable and appropriate steps to help ensure that Caseware uses Personal Data in a manner consistent with Customer’s obligations under the CCPA; (b) notify Customer if Caseware determines that it can no longer meet its obligations under the CCPA; and (c) grant Customer the right, upon reasonable notice, to take reasonable and appropriate steps to stop and remediate any unauthorised use of Personal Data. To the extent required by the CCPA, Customer shall
inform Caseware of any consumer requests made pursuant to the CCPA with which it must comply, and shall provide all information necessary for Caseware to comply with such request.
Caseware shall Process Personal Data only for the “Business Purposes” specified in the MPSA and this DPA, including but not limited to (a) providing, operating, evaluating, monitoring, supporting, maintaining, securing, developing and improving the Services; (b) auditing Customer’s use of the Services; (c) helping to ensure security and integrity; (d) debugging to identify and repair errors that impair existing intended functionality; (e) short-term, transient use; and (f) undertaking internal research for technological development and demonstration, in each case solely to the extent permitted by applicable law and reasonably necessary and proportionate for those Business Purposes. Caseware shall not use Customer Data, Input or Outputs to train or fine-tune AI Models without Customer’s prior written authorization. The Parties agree that Customer discloses Personal Data to Caseware only for these limited and specified Business Purposes.
As a Service Provider, Caseware shall not:
- Sell or Share Personal Data;
- retain, use, or disclose Personal Data for any purpose other than for the Business Purposes specified in the MPSA and this DPA, including retaining, using, or disclosing Personal Data for a commercial purpose other than the Business Purposes specified in the MPSA and this DPA, or as otherwise permitted by the CCPA;
- retain, use, or disclose Personal Data outside of the direct business relationship between Caseware and Customer; or
- combine Personal Data that Caseware receives from, or on behalf of, Customer with personal information that it receives from, or on behalf of, another person or persons, or collects from its own interaction with the consumer, provided that Caseware may combine personal information to perform any Business Purpose as defined in the regulations adopted pursuant to paragraph (10) of subdivision (a) of Cal. Civ. Code § 1798.185, except as provided for in paragraph (6) of subdivision (e) of Cal. Civ. Code § 1798.140 and in regulations adopted by the California Privacy Protection Agency.
18. Other U.S. Data Protection Laws
To the extent that Caseware Processes any Personal Data relating to individuals who are “Consumers” as that term is defined in the Colorado Privacy Act, Colo. Rev. Stat. §§ 6-1-1301 et seq. (“CPA”), the Connecticut Data Privacy Act, Public Act No. 22-15 (“CTDPA”), the Utah Consumer Privacy Act, Utah Code Ann. §§ 13-61-101 et seq. (“UCPA”), and the Virginia Consumer Data Protection Act, Va. Code Ann. §§59.1575 et seq. (“VCDPA”) (collectively, the “Consumer Privacy Laws” or “CPL”), respectively, and upon the respective effective dates of the CPL, Caseware shall comply with the CPL’s requirements, including any amendments and implementing regulations that become effective on or after the effective date of this DPA.
19. Liability
The liability of the Parties under this DPA shall be subject to the liability provisions of the MPSA.
20. Term & Termination
This DPA becomes effective upon agreement with the MPSA and shall remain in force as long as Caseware processes Personal Data or throughout the term of the MPSA, whichever is longer.
21. Miscellaneous
In case of a conflict, between this DPA or any other agreement between the parties and the Standard Contractual Clauses, the Standard Contractual Clauses shall take precedence. In case of a conflict, between the provisions of this DPA and any other agreement between the Parties, this DPA shall take precedence. Should individual provisions of this DPA be or become invalid, this shall not affect the validity of the remaining conditions of this DPA. Without prejudice to Clause 17 (Governing Law) and Clause 18 (Forum and Jurisdiction) of the Standard Contractual Clauses, the Parties submit to the choice of jurisdiction and venue stipulated in the MPSA.
Attachment 1:
Technical and Organizational Measures (“TOMs”)
Attachment 2:
The following Sub-Processors are listed in alphabetical order. Not all Sub-Processors are engaged for all Caseware Offerings — the service description indicates the relevant products and contexts. Caseware ensures that each Sub-Processor is bound by data protection obligations no less protective than those set out in this DPA. The current live Sub-Processor list is available at trust.caseware.com/subprocessors.
Attachment 3:
Standard Contractual Clauses
See attached.
STANDARD CONTRACTUAL CLAUSES SECTION I Clause 1 Purpose and scope
The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.
The Parties:
the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”), and
the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data importer”) have agreed to these standard contractual clauses (hereinafter: “Clauses”).
These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.
The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.
Clause 2 Effect and invariability of the Clauses
These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.
Clause 3 Third-party beneficiaries
(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:
Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;
Clause 8 - Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c), (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g); Module Four: Clause 8.1 (b) and Clause 8.3(b);
Clause 9 - Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);
Clause 12 - Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);
Clause 13;
Clause 15.1(c), (d) and (e);
Clause 16(e);
Clause 18 - Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.
(b) Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.
Clause 4 Interpretation
Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.
These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.
These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.
Clause 5 Hierarchy
In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 6 Description of the transfer(s)
The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.
Clause 7 - Docking clause
An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.
Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.
The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.
SECTION II – OBLIGATIONS OF THE PARTIES Clause 8 Data protection safeguards
The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.
8.1 Instructions
The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.
The data importer shall immediately inform the data exporter if it is unable to follow those instructions.
Purpose limitation
The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.
Transparency
On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.
Accuracy
If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.
Duration of processing and erasure or return of data
Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).
Security of processing
The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter “personal data breach”). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.
The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.
Sensitive data
Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter “sensitive data”), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.
Onward transfers
The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter “onward transfer”) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:
the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;
the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;
the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or
the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.
Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.
8.9 Documentation and compliance
The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.
The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.
The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.
The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.
The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.
Clause 9 Use of sub-processors
The data importer has the data exporter’s general authorisation for the engagement of subprocessor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors […]. The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.
Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfills its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.
The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.
The data importer shall remain fully responsible to the data exporter for the performance of the subprocessor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.
The data importer shall agree a third-party beneficiary clause with the sub-processor whereby - in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent - the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
Clause 10 Data subject rights
The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.
The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.
In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.
Clause 11 Redress
The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.
The data importer agrees that data subjects may also lodge a complaint with an independent dispute resolution body at no cost to the data subject. It shall inform the data subjects, in the manner set out in paragraph (a), of such redress mechanism and that they are not required to use it, or follow a particular sequence in seeking redress.
In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.
Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:
lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;
refer the dispute to the competent courts within the meaning of Clause 18.
The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.
The data importer shall abide by a decision that is binding under the applicable EU or Member State law.
The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.
Clause 12 Liability
Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.
Each Party shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages that the Party causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter under Regulation (EU) 2016/679.
Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.
The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its / their responsibility for the damage.
The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.
Clause 13 Supervision
Where the data exporter is established in an EU Member State: The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.
Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679: The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.
Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679: The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.
The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.
SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES Clause 14 Local laws and practices affecting compliance with the Clauses
The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.
The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:
the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;
the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;
any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.
The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.
The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.
The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).
Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation [for Module Three: , if appropriate in consultation with the controller]. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by [for Module Three: the controller or] the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.
Clause 15 Obligations of the data importer in case of access by public authorities
15.1 Notification
(a) The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary, with the help of the data exporter) if it:
receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or
becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.
If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.
Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).
The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.
Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.
15.2 Review of legality and data minimization.
The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).
The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request. [For Module Three: The data exporter shall make the assessment available to the controller.]
The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.
SECTION IV – FINAL PROVISIONS Clause 16 Non-compliance with the Clauses and termination
The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.
In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).
The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:
the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;
the data importer is in substantial or persistent breach of these Clauses; or
the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.
In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.
Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.
Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.
Clause 17 Governing law
These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.
Clause 18 Choice of forum and jurisdiction
Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.
The Parties agree that those shall be the courts of Ireland.
A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.
The Parties agree to submit themselves to the jurisdiction of such courts.
ANNEX I
Defined terms used in this Annex 1 shall have the meaning given to them in the MPSA between Caseware and Customer, and/or the DPA.
A. LIST OF PARTIES
Data exporter(s):
1. Name: The Customer (the legal entity entering into the MPSA with Caseware). Address: As specified in the applicable Order Form. Contact person: As specified in the applicable Order Form.
Activities relevant to the data transferred under these Clauses: Transfer of Customer's Personal Data to Caseware for processing in connection with the Services. Role (controller/processor): Controller
Data importer(s):
1. Name: Caseware International Inc. or the Affiliate of Caseware International Inc. identified in the applicable Order Form. Address: As applicable per the relevant entity; see Section 1 of the DPA. Contact person: Global Data Protection Officer; privacy@caseware.com.
Activities relevant to the data transferred under these Clauses: Processing of Customer's Personal Data in connection with the provision of the Services as described in the MPSA. Role (controller/processor): Processor
B. DESCRIPTION OF TRANSFER
Categories of data subjects whose personal data is transferred:
Please see the DPA, which describes the Categories of personal data transferred:
Please see the DPA, which describes the categories of data.
Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialized training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.
The parties do not anticipate the transfer of special categories of data.
The frequency of the transfer (e.g., whether the data is transferred on a one-off or continuous basis).
Please see the DPA
Nature of the processing
Please see the DPA
Purpose(s) of the data transfer and further processing
Please see the DPA
The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period
Please see the DPA
For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing
Please see the DPA
C. COMPETENT SUPERVISORY AUTHORITY
Identify the competent supervisory authority/ies in accordance with Clause 13
● The competent supervisory authority that shall apply will be the competent supervisory authority of the country in which the Customer’s client’s data originates
ANNEX II TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA
See Attachment 1 of the DPA, which describes the technical and organizational security measures implemented by Caseware.
ANNEX III
LIST OF SUB-PROCESSORS
See Attachment 2 of the DPA, which lists Caseware's current Sub-Processors.
Attachment 4:
UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses
See attached.
This Addendum has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.
○ Part 1: Tables
■ Table 1: Parties
■ Table 2: Selected SCCs, Modules and Selected Clauses
■ Table 3: Appendix Information
“Appendix Information” means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:
Annex 1A: List of Parties:
Annex 1B: Description of Transfer:
Annex II: Technical and organisational measures including technical and organisational measures to ensure the security of the data:
Annex III: List of Sub processors (Modules 2 and 3 only):
■ Table 4: Ending this Addendum when the Approved Addendum Changes
○ Part 2: Mandatory Clauses
■ Entering into this Addendum
Each Party agrees to be bound by the terms and conditions set out in this Addendum, in exchange for the other Party also agreeing to be bound by this Addendum.
Although Annex 1A and Clause 7 of the Approved EU SCCs require signature by the Parties, for the purpose of making Restricted Transfers, the Parties may enter into this Addendum in any way that makes them legally binding on the Parties and allows data subjects to enforce their rights as set out in this Addendum. Entering into this Addendum will have the same effect as signing the Approved EU SCCs and any part of the Approved EU SCCs.
■ Interpretation of this Addendum
Where this Addendum uses terms that are defined in the Approved EU SCCs, those terms shall have the same meaning as in the Approved EU SCCs. In addition, the following terms have the following meanings:
This Addendum must always be interpreted in a manner that is consistent with UK Data Protection Laws and so that it fulfils the Parties’ obligation to provide the Appropriate Safeguards.
If the provisions included in the Addendum EU SCCs amend the Approved SCCs in any way which is not permitted under the Approved EU SCCs or the Approved Addendum, such amendment(s) will not be incorporated in this Addendum and the equivalent provision of the Approved EU SCCs will take their place.
If there is any inconsistency or conflict between UK Data Protection Laws and this Addendum, UK Data Protection Laws applies.
If the meaning of this Addendum is unclear or there is more than one meaning, the meaning which most closely aligns with UK Data Protection Laws applies.
Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this Addendum has been entered into.
■ Hierarchy
Although Clause 5 of the Approved EU SCCs sets out that the Approved EU SCCs prevail over all related agreements between the parties, the parties agree that, for Restricted Transfers, the hierarchy in Section 10 will prevail.
Where there is any inconsistency or conflict between the Approved Addendum and the Addendum
EU SCCs (as applicable), the Approved Addendum overrides the Addendum EU SCCs, except where (and in so far as) the inconsistent or conflicting terms of the Addendum EU SCCs provides greater protection for data subjects, in which case those terms will override the Approved Addendum.
Where this Addendum incorporates Addendum EU SCCs which have been entered into to protect
transfers subject to the General Data Protection Regulation (EU) 2016/679 then the Parties acknowledge that nothing in this Addendum impacts those Addendum EU SCCs.
■ Incorporation of and changes to the EU SCCs
This Addendum incorporates the Addendum EU SCCs which are amended to the extent necessary so that:
together they operate for data transfers made by the data exporter to the data importer, to the extent that UK Data Protection Laws apply to the data exporter’s processing when making that data transfer, and they provide Appropriate Safeguards for those data transfers;
Sections 9 to 11 override Clause 5 (Hierarchy) of the Addendum EU SCCs; and
this Addendum (including the Addendum EU SCCs incorporated into it) is (1) governed by the laws of England and Wales and (2) any dispute arising from it is resolved by the courts of England and Wales, in each case unless the laws and/or courts of Scotland or Northern Ireland have been expressly selected by the Parties.
Unless the Parties have agreed alternative amendments which meet the requirements of Section 12, the provisions of Section 15 will apply.
No amendments to the Approved EU SCCs other than to meet the requirements of Section 12 may be made.
The following amendments to the Addendum EU SCCs (for the purpose of Section 12) are made:
a. References to the “Clauses” means this Addendum, incorporating the Addendum EU SCCs; b. In Clause 2, delete the words:
“and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679”;
Clause 6 (Description of the transfer(s)) is replaced with:
“The details of the transfer(s) and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred are those specified in Annex I.B where UK Data Protection Laws apply to the data exporter’s processing when making that transfer.”;
Clause 8.7(i) of Module 1 is replaced with:
“it is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer”;
Clause 8.8(i) of Modules 2 and 3 is replaced with:
“the onward transfer is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer;”
References to “Regulation (EU) 2016/679”, “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)” and “that Regulation” are all replaced by “UK Data Protection Laws”. References to specific Article(s) of “Regulation (EU) 2016/679” are replaced with the equivalent Article or Section of UK Data Protection Laws;
References to Regulation (EU) 2018/1725 are removed;
References to the “European Union”, “Union”, “EU”, “EU Member State”, “Member State” and “EU or Member State” are all replaced with the “UK”;
The reference to “Clause 12(c)(i)” at Clause 10(b)(i) of Module one, is replaced with “Clause 11(c)(i)”;
Clause 13(a) and Part C of Annex I are not used;
The “competent supervisory authority” and “supervisory authority” are both replaced with the “Information Commissioner”;
In Clause 16(e), subsection (i) is replaced with:
“the Secretary of State makes regulations pursuant to Section 17A of the Data Protection Act 2018 that cover the transfer of personal data to which these clauses apply;”; m. Clause 17 is replaced with:
“These Clauses are governed by the laws of England and Wales.”;
Clause 18 is replaced with:
“Any dispute arising from these Clauses shall be resolved by the courts of England and Wales. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of any country in the UK. The Parties agree to submit themselves to the jurisdiction of such courts.”; and
The footnotes to the Approved EU SCCs do not form part of the Addendum, except for footnotes 8, 9, 10 and 11.
■ Amendments to this Addendum
The Parties may agree to change Clauses 17 and/or 18 of the Addendum EU SCCs to refer to the laws and/or courts of Scotland or Northern Ireland.
If the Parties wish to change the format of the information included in Part 1: Tables of the Approved Addendum, they may do so by agreeing to the change in writing, provided that the change does not reduce the Appropriate Safeguards.
From time to time, the ICO may issue a revised Approved Addendum which:
makes reasonable and proportionate changes to the Approved Addendum, including correcting errors in the Approved Addendum; and/or
reflects changes to UK Data Protection Laws;
The revised Approved Addendum will specify the start date from which the changes to the Approved Addendum are effective and whether the Parties need to review this Addendum including the Appendix Information. This Addendum is automatically amended as set out in the revised Approved Addendum from the start date specified.
If the ICO issues a revised Approved Addendum under Section 18, if any Party selected in Table 4 “Ending the Addendum when the Approved Addendum changes”, will as a direct result of the changes in the Approved Addendum have a substantial, disproportionate and demonstrable increase in:
its direct costs of performing its obligations under the Addendum; and/or
its risk under the Addendum,
and in either case it has first taken reasonable steps to reduce those costs or risks so that it is not substantial and disproportionate, then that Party may end this Addendum at the end of a reasonable notice period, by providing written notice for that period to the other Party before the start date of the revised Approved Addendum.
The Parties do not need the consent of any third party to make changes to this Addendum, but any changes must be made in accordance with its terms.
- Alternative Part 2 Mandatory Clauses:
Application and Interface Security
Our Software Development Life Cycle (SDLC) ensures that our applications and programming interfaces (APIs) are designed, deployed, and tested in accordance with leading industry standards – such as OWASP, ISO, and SOC – and adhere to legal, statutory, or regulatory compliance obligations.
You will be onboarded once all agreements and policies are accepted for usage of the service. You are responsible for ensuring your usage of Caseware Cloud is in compliance with applicable laws and regulations.
Legal specifics can be found in the Cloud Services Agreement here.
Our policies and procedures have been established and are maintained in support of data security to include confidentiality, integrity, and availability across multiple system interfaces, jurisdictions, and business functions to prevent improper disclosure, alteration, or destruction.
Audit Assurance and Compliance
Independent audits are conducted by registered 3rd parties as part of our compliance program for ISO 27001 and SOC 2 for our Cloud services. We also have an internal audit program, external penetration testing and regularly scheduled internal vulnerability testing. Vulnerability test results are shared with customers as outlined in the Client Initiated Testing Policy. The results of these processes are tracked through our improvements process. The methodology and tools used to conduct penetration testing is tailored to each assessment for specific targets and attacker profiles. SOC 2 reports are provided under NDA to clients. Our SOC 3 Report is available in PDF format here.
Production data is stored on Amazon Web Services (AWS). The application handles logical separation of client data through database isolation. Data that is transferred to and from our service (including backups) is 100% encrypted over an SSL connection (AES-256-bit – the same strength used in online banking). Data transmission occurs between client and server, and databases. Controls are in place for secure and encrypted bulk data transfers. There are no email transmissions. For more information on security, see: https://www.casewarecloud.com/security.html. Our legal team monitors our regulatory obligations. Please refer to our Cloud Services agreement for legal requirements here.
Business Continuity Management and Operational Resilience
Caseware has a consistent unified framework for business continuity planning and has established, documented, and adopted this to ensure all business continuity plans are consistent in addressing priorities for testing, maintenance, and information security requirements.
Requirements for business continuity plans include the following:
- Defined purpose and scope, aligned with relevant dependencies
- Accessible to and understood by those who will use them
- Owned by a named person(s) who is responsible for their review, update, and approval
- Defined lines of communication, roles, and responsibilities
- Detailed recovery procedures, manual work-around, and reference information
- Method for plan invocation
Our business continuity and security incident response plans are tested at planned intervals or upon significant organizational or environmental changes. Incident response plans involve impacted customers (tenant) and other business relationships that represent critical intra-supply chain business process dependencies.
Our service is hosted on Amazon’s AWS and utilities services and environmental conditions (for example, water, power, temperature and humidity controls, telecommunications, and internet connectivity) are secured, monitored, maintained, and tested for continual effectiveness at planned intervals to ensure protection from unauthorized interception or damage, and are designed with automated failover or other redundancies in the event of planned or unplanned disruptions.
Our cloud service is completely virtual and hosted on Amazon Web Services (AWS). Amazon is also ISO and SOC2 compliant and responsible for restricting access to facilities housing the productions systems to authorized individuals. AWS is also responsible for environmental protection and preventative maintenance over production systems. AWS has published further details here: https://aws.amazon.com/compliance/data-center/controls. These certifications address physical security, system availability, network and IP backbone access, customer provisioning and problem management. Physical access and environmental controls are managed and controlled by AWS. AWS physical protection assurance information can be found at: https://aws.amazon.com/compliance.
Caseware has aligned our security program to ISO 27001 and we have business continuity processes in place to address disruptions to critical services. We monitor all cloud instances for performance and availability and incorporate the following:
- Identify critical products and services
- Identify all dependencies, including processes, applications, business partners, and third party service providers
- Understand threats to critical products and services
- Determine impacts resulting from planned or unplanned disruptions and how these vary over time
- Establish the maximum tolerable period for disruption
- Establish priorities for recovery
- Establish recovery time objectives for resumption of critical products and services within their maximum tolerable period of disruption
- Estimate the resources required for resumption
Customers can see our real-time operational status at our status page here: https://caseware.statuspage.io/.
We maintain a central system for documentation and train all staff on processes. Procedures include change management, security processes, roles and responsibilities of internal users. Our procedures are updated on an as needed basis and revision histories are logged. Additionally, policies and procedures shall include defined roles and responsibilities supported by regular workforce training.
Caseware maintains a records and retention policy for Cloud services. The retention policy is not client-specific. Backup and recovery procedures are documented and automated alerts are sent daily to operations staff. Backup and recovery measures have been incorporated into business continuity planning and tested accordingly for effectiveness. See the retention policy for each category of records below.
System transaction logs
Description: Database journals and other logs used for database recovery.
Retention period: 30 days.
Reason for retention: Based on backup and recovery strategy.
Allowable storage media: Electronic.
Audit logs
Description: Security logs, for example, records of logon/logoff and permission changes.
Retention period: 30 days.
Reason for retention: Maximum period of delay before forensic investigation.
Allowable storage media: Electronic.
Operational procedures
Description: Records associated with the completion of operational procedures.
Retention period: 2 years.
Reason for retention: Maximum period elapsed regarding dispute.
Allowable storage media: Electronic.
Customer
Description: Customer backups.
Retention period: 90 days.
Reason for retention: Data protection requirement.
Allowable storage media: Electronic.
Change Control and Configuration Management
Change management controls have been established for any new development and/or acquisition of new data, physical or virtual applications, infrastructure network and systems components, or any corporate, operations and/or data center facilities have been pre-authorized by the organization’s business leadership or other accountable business role or function. Our SDLC has a defined quality change control and testing process with established baselines, testing, and release standards which focus on system availability, confidentiality and integrity of systems and services.
Policies and procedures have been established, and supporting business processes and technical measures implemented, to restrict the installation of unauthorized software on organizationally-owned or managed user end-point devices and IT infrastructure network and systems components within the production cloud environment. Our change management policies and procedures include managing the risks associated with applying changes to business-critical or customer impacting applications and system-system interface (API) designs and configurations. Technical measures have also been implemented to provide assurance that all changes directly correspond to a registered change request, business-critical or customer, and/or authorization by, the customer as per agreement prior to deployment.
Data Security and Information Lifecycle Management
Caseware has policies and procedures and supporting business processes and technical measures in place to inventory and maintain data flows within the SaaS network and systems for each geographic location. Controls are in place to ensure that data is placed in the geographic area determined by the client. Subscriber data within the production cloud environment resides on two-tier architecture and is not directly accessible from the internet.
Our security policy defines four levels of data classification: confidential, restricted, operational, and public. All data stored within the production cloud infrastructure is considered confidential, which is our highest level of security and only authorized staff have access to this environment. Logical access to the production cloud environment is restricted to the operations team alone.
All subscriber data is stored in the production cloud environment. Use of customer data in non-production environments is controlled through secure data-handling processes, which require explicitly documented approval from the customers whose data is affected, and must comply with legal and regulatory requirements for scrubbing of sensitive data elements.
There is a designated operations team responsible for all operational functions regarding the infrastructure and storage with assigned responsibilities that have been defined, documented, and communicated.
Caseware Cloud is hosted on Amazon web servers around the world. Upon subscribing to the Caseware Cloud Services, CWC informs clients of the jurisdiction in which the server that has been allocated to host your Subscriber Data and Personal Information is located. You may consent to such allocation, or refuse a server so allocated.
For performance reasons, we’ll typically set you up in:
- United States/North Virginia if you’re located in the United States or South America
- Canada/Montreal if you’re located in Canada
- Australia/New South Wales if you’re located in the Asia-Pacific region
- Ireland/Leinster if you’re located in any other region
Data center Security
The production infrastructure is completely hosted within Amazon’s AWS. AWS is responsible for restricting access to facilities housing the production systems to authorized individuals. AWS is also responsible for environmental protection and preventative maintenance over production systems. Physical access is controlled by AWS at the perimeter and at building ingress points. Full details can be found here: https://aws.amazon.com/whitepapers/#security. AWS has published further details here: https://aws.amazon.com/compliance/data-center/controls/.
Our production infrastructure is completely hosted within Amazon’s AWS. AWS has SOC 2 reports, which are reviewed annually. AWS governance processes can be found here: https://aws.amazon.com/compliance/.
Encryption and Key Management
Our cryptography policies and procedures are designed to support business process. Technical measures have been implemented based on business requirements for protection of data at rest and data in transit as per applicable legal, statutory, and regulatory compliance obligations.
Our cryptography policy requires all encryption keys to have identifiable owners within the organization. The cryptographic key lifecycle management ensures access controls are in place for secure key generation, exchange and storage, including segregation of keys used for encrypted data or sessions.
Data stored at the server level (data-at-rest) is encrypted using the industry standard AES-256 algorithm. Data that is transferred to and from our service (data-in-transit) is encrypted via TLS with ephemeral key exchange and use industry-accepted strong cipher suites. Certificates use a minimum of 2048-bit key strength with SHA-2 or stronger signature algorithm. Private keys are generated and stored in our secrets management systems. They are deployed and used on production systems as needed via our change control process. Certificates are obtained through a reputable vendor and follow the built-in and industry standard renewal/rotation process based on expiry or revocation as needed.
Governance and Risk Management
Security risk assessments are completed at least annually and consider the following:
- Awareness of where sensitive data is stored and transmitted across applications, databases, servers, and network infrastructure
- Compliance with defined retention periods
- Data classification and protection from unauthorized use, access, loss, destruction, and falsification
We have implemented an Information Security Management System based on ISO 27001 and SOC 2 controls. Our ISMS includes the following areas insofar as they relate to the characteristics of the business:
- Information Security Policy (this document)
- Access Control Policy
- Availability Management
- Clean Desk Policy
- Cryptography Policy
- IS Supplier Management Policy
- Logging and Monitoring Policy
- Mobile Device Policy
- Network Security Policy
- Password Management Policy
- Patch Management Policy
- Software Policy
- Technical Vulnerability Management Policy
- Risk Assessment Methodology
- Malware, Email and ISMS Policy
- Internet Acceptable Use Policy
- Penetration Testing Policy
- Teleworking Policy
- Records Retention and Protection
Department managers are responsible for maintaining awareness of, and complying with, security policies, procedures, and standards that are relevant to their area of responsibility.
Risk acceptance levels have been defined within the risk management methodology and all risks are mitigated to an acceptable level with reasonable resolution time frames and stakeholder approval.
Our information security policies and procedures are posted and available for review by all impacted staff and external business relationships. The Information Security Steering Committee is responsible for developing, maintaining, and enforcing our service’s information security policies. The information security policy is reviewed annually and approved by the Information Security Steering Committee. Executive and line management provide support for information security through clearly documented direction and commitment, and shall ensure action has been assigned. There is a senior member of management who is responsible for information security governance and operations, including protection of customer data – this role reports to the CFO.
Policy reviews are conducted annually by the Information Security Steering Committee or as a result of changes to the organization to ensure its continuing alignment with the security strategy, effectiveness, accuracy, relevance, and applicability to legal, statutory, or regulatory compliance obligations.
Formal risk assessments are performed annually and in conjunction with any changes to information systems to determine the likelihood and impact of all identified risks. The likelihood and impact associated with inherent and residual risk is determined independently, considering all risk categories based on audit results, threat and vulnerability analysis, and regulatory compliance. Risk assessment results can include updates to security policies, procedures, standards, and controls to ensure that they remain relevant and effective. The results of risk assessments are:
- Reported to senior management who then partake in a risk treatment process
- Updated in a risk register
- Prioritized based on possible impact to production systems
Our HR has a defined screening process for all staff. Reference checks are obtained with respect to all employees at time of hiring, with criminal and credit background checks for those who perform operational roles with the product cloud environment. All staff are required to sign a confidentiality agreement prior to employment to ensure protection of client information for the protection of data. Information security awareness training is provided during employee onboarding. Specific training is provided for developers on secure coding practices. Formal records are maintained for completion of internal staff training. Employee terminations and position changes are initiated by department managers. Our HR team reviews these requests and submits the request through our ticketing system for de-provisioning and provisioning requirements. Our HR team has an employee departure process to ensure all equipment is returned and accounts terminated to ensure that access to production environments is removed.
A security awareness training program has been established for all contractors, third-party users, and employees and is mandated. All individuals with access to confidential and restricted data receive appropriate awareness training and regular updates in organizational procedures, processes, and policies relating to their job function relative to the organization. Roles and responsibilities of contractors, employees, and third-party users are documented as they relate to information assets and security.
User responsibilities are defined within job descriptions for all staff and they are made aware of their roles and responsibilities for:
- Maintaining awareness and compliance with established policies and procedures and applicable legal, statutory, or regulatory compliance obligations
- Maintaining a safe and secure working environment
- Report any suspicious activity if detected
We have a clear screen policy which requires that unattended workspaces do not have openly visible sensitive documents and user computing sessions had been disabled after an established period of inactivity.
We have an Access Control policy in place that specifies how to manage access control to all system components and sensitive information in the organization. Policies governing acceptable use or access to subscriber data and metadata is included in the Caseware privacy policy (https://www.caseware.com/privacy-statement/). Caseware collects, uses and discloses information only for the following purposes:
- To verify your identity
- To provide you with the Caseware Cloud Services
- To contact you for the purposes of product information, service updates, billing notifications, or notifications relating to the Caseware Cloud Services
- To monitor and/or improve system usage, server and software performance
- To assist with technical support issues
- To comply with any laws, regulations, court orders, subpoenas or other legal process of investigation and to protect CWC, its Affiliates and other individuals from harm
- To improve and enhance CWC Service offerings
Identity and Access Management
Policies and procedures have been established to store and manage identity information about every person who accesses the production cloud infrastructure and to determine their level of access. Access control policies and procedures have been established, and supporting business processes and technical measures implemented, for restricting user access as per defined segregation of duties to address business risks associated with a user-role conflict of interest. The access control repository is managed by the provider. We use a privileged identity manager and password management system.
Access to, and use of, audit tools that interact with production cloud environment is segmented and restricted to prevent compromise and misuse of log data. User access to diagnostic and configuration ports are restricted to authorized individuals and applications.
Controls are in place to ensure only approved software is installed within the production cloud infrastructure.
Access to the organization’s own developed applications, program, or object source code, or any other form of intellectual property (IP), and use of proprietary software is controlled following the rule of least privilege based on job function as per established user access policies and procedures.
Caseware Cloud Service requires password authentication to access the base system. Once in the system, users must be assigned security roles to perform additional operations and access certain content. With security roles, you can control who has access to what content. Your organization is responsible for developing appropriate security policies around passwords and security roles using the security features provided in Caseware Cloud. Caseware provides access to clients, who then control their own users and administrative accounts, including provisioning and de-provisioning. Two-factor authentication is employed. User access is authorized and revalidated quarterly, to ensure the rule of least privilege based on job function. For identified access violations, remediation activities are followed based on the established user access policies and procedures. Timely de-provisioning (revocation or modification) of user access to data or managed applications, infrastructure systems, and network components, has been implemented as per established policies and procedures and based on user’s change in status such as termination of employment or other business relationship, job change, or transfer. The provider manages service account provisioning and de-provisioning. Service account authentication utilizes multi-factor authentication.
Infrastructure and Virtualization Security
Caseware Cloud deploys a SaaS-based endpoint detection and response security endpoint to all hosts within our infrastructure. All user, process, and network activity is collected and stored in the tamper-proof central location and analyzed in near real-time for suspicious behaviors as well as for manual forensics. Protection, retention, and lifecycle management of audit logs, adhere to applicable legal, statutory, or regulatory compliance obligations and provide unique user access accountability to detect potentially suspicious network behaviors and/or file integrity anomalies, that are required to support forensic investigative capabilities in the event of a security breach. Our tools have the capability to detect/prevent unauthorized or anomalous behavior based on network traffic or host activity. All authentication events, successful and failed, are logged.
Our production and non-production environments are separated to prevent unauthorized access or changes to information assets. Separation of the environments include logical separation and segregation of duties for personnel accessing these environments as part of their job duties.
Our production system and network environment is protected by centrally managed firewalls and ensures separation of production and non-production environments. Our production environment is designed, developed, deployed, and configured to ensure our operations team and clients user access is appropriately segmented from other client users, based on the following considerations:
- Established policies and procedures
- Isolation of business critical assets and/or sensitive user data and sessions that mandate stronger internal controls and high levels of assurance
- Compliance with legal, statutory, and regulatory compliance obligations
The production cloud infrastructure has a reliable and mutually agreed upon external time source that is used to synchronize the system clocks of all relevant information processing systems to facilitate tracing and reconstitution of activity timelines.
Supply Chain Management, Transparency, and Accountability
Policies and procedures have been implemented to ensure the consistent review of service agreements between providers and customers across the relevant supply chain. Reviews performed at least annually and identify non-conformance to established agreements. Any non-conformances are identified as actions to address service-level conflicts or inconsistencies.
Threat and Vulnerability Management
Policies and procedures have been established, and supporting business processes and technical measures implemented, to prevent the execution of malware within the production cloud environment or end user devices and IT infrastructure network and system components. Policies and procedures have been established, and supporting processes and technical measures implemented, for timely detection of vulnerabilities within organizationally-owned or managed applications, infrastructure network and system components. We also perform ongoing application and code vulnerability evaluations of our products and have dual peer reviews of all code changes to ensure the efficiency of implemented security controls. Our risk management methodology is used for prioritizing remediation of identified vulnerabilities. Changes are managed through our defined change management process for all vendor-supplied patches, configuration changes, or changes to our applications. Our anti-malware solution is centrally managed and runs on all systems. The anti-malware solution includes mechanisms for detecting or preventing phishing. Malware signature updates are deployed within 1 day of release.