Last Updated: November 20, 2026
SPLITSECURE DATA PROCESSING AGREEMENT
This Data Processing Agreement (this “DPA”) supplements the SplitSecure Services Agreement (the “Agreement”) between SplitSecure Inc. (“Company”) and the customer that accepts or signs this DPA (“Customer”). This DPA sets out the terms on which Company Processes Personal Data on Customer’s behalf in connection with the Services. Capitalized terms not defined in this DPA have the meanings given in the Agreement.
1. Scope and Application
1.1Application. This DPA applies to all Personal Data that Company Processes on Customer’s behalf in connection with the Services, wherever the Personal Data originates and whatever law protects it. The body of this DPA (Sections 1 to 17 and Schedules 1 and 2) applies to all such Personal Data.
1.2Structure. The Addenda to this DPA contain the additional terms required by particular privacy laws. Each Addendum supplements, and does not replace, the body of this DPA. Where an Addendum imposes a higher standard than the body of this DPA in respect of the Personal Data to which that Addendum applies, the higher standard applies to that Personal Data.
1.3Automatic application of Addenda. Each Addendum applies automatically, without any election, notice, selection or separate signature by either party, to the Personal Data described below, from the moment Company begins to Process that Personal Data:
(a)Addendum 1 (EU, UK and Switzerland) applies to Personal Data that is subject to European Data Protection Laws (as defined in Addendum 1);
(b)Addendum 2 (US State Privacy Laws) applies to Personal Data that is subject to US State Privacy Laws (as defined in Addendum 2); and
(c)Addendum 3 (Canada and Québec) applies to Personal Data that is subject to Canadian Privacy Laws (as defined in Addendum 3).
Where the same Personal Data is subject to the laws covered by more than one Addendum, each of those Addenda applies to that Personal Data in respect of the requirements of the laws it covers. Whether an Addendum applies is determined by the law that governs the Personal Data concerned, not by Customer’s place of incorporation or the location from which Customer accesses the Services.
1.4Customer Affiliates. Customer enters into this DPA on behalf of itself and, to the extent required under Applicable Data Protection Laws, in the name and on behalf of its Affiliates that use the Services under the Agreement. Each such Affiliate is bound by this DPA as if it were Customer, and Customer is responsible for its Affiliates’ compliance. Any claim by an Affiliate under this DPA shall be brought by Customer on its behalf.
2. Definitions
(a)“Addendum” means each of Addendum 1, Addendum 2 and Addendum 3 to this DPA, and “Addenda” means all of them.
(b)“Affiliate” means an entity that directly or indirectly controls, is controlled by, or is under common control with a party, where “control” means ownership of more than fifty percent (50%) of the voting equity of the entity, for so long as that control exists.
(c)“Applicable Data Protection Laws” means all laws relating to privacy, data protection or the Processing of Personal Data that apply to a party’s Processing of Personal Data under this DPA, including European Data Protection Laws, US State Privacy Laws and Canadian Privacy Laws.
(d)“Company Account Data” means (i) Personal Data relating to Customer’s personnel and representatives that Company Processes to establish and administer Customer’s account, to authenticate account administrators, to invoice Customer and to manage the contractual relationship between Company and Customer; and (ii) the Personal Data that Company collects from a User, or from an individual who has created an account in the Services but is not yet a User, in order to create, authenticate, secure and administer that person’s own account in the Services and to record the User’s acceptance of Company’s terms, as described in Company’s End User Terms of Service, including the User’s name and business email address, authentication credential identifiers and public keys, device and secure-enclave identifiers, public keys and attestation data, session records, records of acceptance of terms, and error reports and application telemetry collected from the User’s device, in each case whether or not the person is associated with Customer’s organization. Company Account Data does not include the records described in Section 4.2.
(e)“Company Usage Data” has the meaning given in Section 4.
(f)“Customer Personal Data” means Personal Data that Customer or its Users submit to, or that Company collects through, the Services on Customer’s behalf, as described in Schedule 1, and includes activity, audit and event records generated by the operation of the Services in relation to Customer’s Users.
(g)“Deidentified Data” means data that cannot reasonably be used to infer information about, or otherwise be linked to, an identified or identifiable individual, household or device, and in respect of which Company has taken the measures described in Section 4.4.
(h)“Personal Data” means any information relating to an identified or identifiable individual, and includes “personal information”, “personal data” and equivalent terms under Applicable Data Protection Laws.
(i)“Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data Processed by Company or its Sub-processors, and includes any “breach of the security of the system”, “breach of security safeguards”, “confidentiality incident” or equivalent event under Applicable Data Protection Laws.
(j)“Process” and “Processing” mean any operation performed on Personal Data, whether or not by automated means, including collection, recording, organization, structuring, storage, adaptation, retrieval, consultation, use, disclosure, communication, transmission, dissemination, alignment, combination, restriction, anonymization, erasure and destruction.
(k)“Security Measures” means the technical and organizational measures described in Schedule 2, as updated under Section 7.
(l)“Services” means the Service, as defined in the Agreement.
(m)“Sub-processor” means any third party, including any Affiliate of Company, engaged by or on behalf of Company to Process Customer Personal Data in connection with the Services.
(n)“User” has the meaning given in the Agreement.
2.2Terms such as “controller”, “processor”, “business”, “service provider”, “contractor”, “consumer”, “data subject”, “organization” and “service provider for outsourcing purposes” carry the meanings given to them in the Applicable Data Protection Laws to which the relevant Addendum relates. Where this DPA describes a party’s role using one of those terms, the description applies mutatis mutandis under the equivalent concept in each other Applicable Data Protection Law.
3. Roles of the Parties and Instructions
3.1Customer’s role. As between the parties, Customer determines the purposes and means of the Processing of Customer Personal Data and is the controller, business or accountable organization in respect of it. Where Customer Processes Customer Personal Data on behalf of its own clients (including as a Managed Service Provider under the Agreement), Customer acts as a processor or service provider for those clients, Company acts as Customer’s sub-processor, and Customer warrants that it has the authority and the instructions from its clients necessary to appoint Company on the terms of this DPA. References in this DPA to obligations Customer owes as a controller apply in that case to the extent Customer has assumed them under its arrangements with its clients.
3.2Company’s role. Company Processes Customer Personal Data solely as Customer’s processor, service provider or contractor (or, in the case described in the second sentence of Section 3.1, sub-processor) and on Customer’s behalf. Company does not sell, share, rent or otherwise make available Customer Personal Data to any third party for consideration, and does not act as an independent controller, third party or business in respect of Customer Personal Data.
3.3Instructions. Company shall Process Customer Personal Data only (a) to provide, secure, support, operate, maintain and improve the Services in accordance with the Agreement and the Details of Processing in Schedule 1, (b) in accordance with Customer’s documented instructions, including instructions given through the configuration and use of the Services, and (c) as required by law to which Company is subject, in which case Company shall inform Customer of the legal requirement before Processing unless the law prohibits that information on important grounds of public interest. The Agreement, this DPA and Customer’s use of the Services constitute Customer’s complete documented instructions. Additional instructions require the agreement of both parties.
3.4Unlawful instructions. Company shall promptly inform Customer if, in Company’s opinion, an instruction infringes Applicable Data Protection Laws, and may suspend the affected Processing until the instruction is withdrawn or amended. Company is not obliged to review instructions for compliance with law.
3.5Permitted Processing. Nothing in this DPA prevents Company from Processing Customer Personal Data to the extent necessary to detect, prevent and respond to security incidents; to protect against malicious, deceptive, fraudulent or illegal activity; to comply with a legal obligation to which Company is subject; to establish, exercise or defend legal claims; or for any other purpose expressly permitted to a processor, service provider or contractor under Applicable Data Protection Laws.
3.6Customer responsibilities. Customer is responsible for (a) the accuracy, quality and lawfulness of Customer Personal Data and of the means by which Customer acquired it, (b) providing all notices to, and obtaining all consents and authorizations from, individuals that Applicable Data Protection Laws require for the Processing contemplated by the Agreement, (c) the lawfulness of its instructions, and (d) configuring and using the Services in a manner that complies with Applicable Data Protection Laws. Customer shall not submit to the Services any Personal Data that the Agreement prohibits, including personal health data, payment card data and personal financial account data, and (A) “special categories of personal data” within the meaning of Article 9 of the EU GDPR or the UK GDPR and personal data relating to criminal convictions and offences within the meaning of Article 10 of either regulation; (B) “sensitive personal information” within the meaning of the California Consumer Privacy Act (Cal. Civ. Code § 1798.140(ae)) and “sensitive data” or any equivalent category within the meaning of any other US State Privacy Law; (C) “sensitive personal information” within the meaning of section 12 of the Québec Act and information of comparable sensitivity under other Canadian Privacy Laws; and (D) any comparable category of personal information that is subject to heightened protection, consent or security requirements under any other Applicable Data Protection Law (collectively, and as more fully defined in Section 3.5 of the Agreement, “Sensitive Data”, which excludes the Protected Secrets defined in that Section), and represents that the Services are not being used to Process Sensitive Data other than Protected Secrets. Customer shall indemnify Company against claims and losses arising from Customer’s breach of this Section 3.6.
4. Company Account Data and Company Usage Data
4.1Company Account Data. Company Processes Company Account Data as an independent controller and business in its own right, for the purposes of establishing, authenticating, securing and administering Customer’s account and Users’ own accounts and enrolled devices, recording acceptance of Company’s terms, invoicing, managing the contractual relationship, complying with law, and preventing fraud and misuse of the Services, in accordance with Company’s privacy policy and, in respect of Users’ own accounts, Company’s End User Terms of Service. Company Account Data is not Customer Personal Data. Company shall not use Company Account Data to sell or share Personal Data, for advertising purposes, or to build or enhance a profile of any individual for use outside the direct business relationship between Company and Customer.
4.2Usage records are Customer Personal Data. Activity logs, audit records, device and connection identifiers, IP addresses and other records generated by or about Customer’s Users through their use of the Services within Customer’s organization are Customer Personal Data to the extent they relate to an identifiable individual, and Company Processes them on Customer’s behalf under Section 3. Error reports and application telemetry collected from a User’s device, and the credentials, keys and device records that Company collects to create and secure a User’s own account, are Company Account Data under Section 4.1.
4.3Company Usage Data. “Company Usage Data” means Deidentified Data that Company derives from the operation of the Services, including aggregated statistics about service usage, performance, reliability and security. Company may create and use Company Usage Data for any lawful purpose, including to provide, secure, support, operate, improve and upgrade the Services, and to produce aggregate statistics, provided that Company Usage Data shall not identify, and shall not reasonably be capable of being used to identify, Customer or any individual, and Company shall not use Company Usage Data for advertising purposes or to build or enhance a profile of any individual.
4.4Deidentification covenant. In respect of any Deidentified Data, including Company Usage Data, Company shall (a) take reasonable technical and organizational measures to ensure that the data cannot be associated with an individual, household or device; (b) publicly commit to maintain and use the data only in deidentified form and not to attempt to reidentify it, except solely to test whether its deidentification process satisfies Applicable Data Protection Laws; (c) contractually prohibit any recipient of the data from attempting to reidentify it; and (d) where Addendum 3 applies to the source Personal Data, comply with the additional requirements of Section 5 of Addendum 3.
4.5No other controller Processing. Except for Company Account Data under Section 4.1 and Company Usage Data under Section 4.3, Company shall not Process Customer Personal Data for its own purposes.
5. Confidentiality and Personnel
5.1Company shall ensure that each person it authorizes to Process Customer Personal Data is bound by a written or statutory obligation of confidentiality, Processes Customer Personal Data only as necessary to perform Company’s obligations under the Agreement and this DPA, and receives training on the requirements of Applicable Data Protection Laws relevant to that person’s duties on hire and periodically thereafter.
5.2Company shall limit access to Customer Personal Data to those personnel who require access to perform Company’s obligations, and to that part of the Customer Personal Data those personnel require. Company shall take reasonable steps, consistent with applicable law, to verify the reliability of such personnel.
5.3Company may disclose Customer Personal Data to its professional advisers and auditors as reasonably required in connection with the performance of its obligations under this DPA and the Agreement, provided that each recipient is bound by written obligations of confidentiality no less protective than those in the Agreement. Any disclosure that would constitute Processing of Customer Personal Data by a third party on Company’s behalf shall be made only in accordance with Section 6.
6. Sub-processors
6.1General authorization. Customer provides Company with general written authorization to engage Sub-processors, including Company’s Affiliates, to Process Customer Personal Data in connection with the Services, subject to this Section 6.
6.2Sub-processor list and notification. Company shall maintain a current list of its Sub-processors, identifying each Sub-processor, the Processing it performs and the jurisdictions in which it Processes Customer Personal Data, at https://trust.splitsecure.com/ (the “Sub-processor List”). Company shall give notice of each intended addition or replacement of a Sub-processor by email to the privacy contact that Customer has designated under Section 8.5 (or, where none has been designated, to an administrator of Customer’s account) or by notice through the Services, and shall update the Sub-processor List, at least thirty (30) days before authorizing a new Sub-processor to Process Customer Personal Data. Company’s maintenance of the Sub-processor List together with that notice is the means by which Company informs Customer of intended changes concerning the addition or replacement of Sub-processors.
6.3Nature of the notice. Notices under Section 6.2 are service communications required by this DPA and Applicable Data Protection Laws. Customer acknowledges that it is responsible for keeping the contact details of its privacy contact and account administrators current, and that notice is given when Company sends it to the most recent contact details that Customer has provided. Company is not required to permit a Customer contact to opt out of Sub-processor notices while the Agreement remains in effect, but shall permit Customer to change the recipient.
6.4Objection. Customer may object to a new Sub-processor on reasonable grounds relating to the protection of Personal Data by written notice to Company within twenty (20) days after Company’s notice under Section 6.2, stating the grounds. The parties shall then discuss the objection in good faith. Company may, at its option, decline to authorize the Sub-processor, make available an alternative means of providing the affected Services that avoids Processing of Customer Personal Data by the Sub-processor, or notify Customer that no alternative is available. If Company does not resolve the objection within thirty (30) days after receiving it, Customer may terminate the affected Services by written notice given within a further fifteen (15) days, in which case Company shall refund any prepaid fees for the terminated Services for the period after termination. Termination under this Section 6.4 is Customer’s sole remedy for an objection. If Customer does not object within the twenty (20) day period, Customer is deemed to have approved the Sub-processor.
6.5Sub-processor contracts. Company shall enter into a written contract with each Sub-processor that imposes on the Sub-processor data protection obligations no less protective of Customer Personal Data than those imposed on Company under this DPA, including any obligations that an Addendum requires to be flowed down to Sub-processors, and that permits Company to satisfy its obligations under Sections 7 to 11. Company remains fully liable to Customer for the performance of each Sub-processor’s obligations. On Customer’s written request, Company shall provide a copy of the data protection terms of its contract with a Sub-processor, from which Company may redact commercial and other information not relevant to the protection of Personal Data.
6.6Emergency replacement. Where Company must replace a Sub-processor urgently to maintain the security or availability of the Services, Company may do so on shorter notice than that required by Section 6.2, provided it notifies Customer as soon as reasonably practicable and Customer retains its objection right under Section 6.4 from the date of that notice.
6.7Customer-directed disclosures. Where Customer configures the Services to transmit Customer Personal Data to a third-party service that Customer connects to the Services (a “Connected Service”) (for example, identity assertions sent to an application for which the Services act as identity provider, or notifications sent to Customer’s messaging platform), Company transmits that data on Customer’s instruction. The operator of the Connected Service is not a Sub-processor, Section 6 does not apply to it, and Customer is responsible for its agreements with, and the lawfulness of its disclosures to, that operator. A provider may be both a Sub-processor, in respect of the Processing for which Company engages it, and the operator of a Connected Service, in respect of Customer Personal Data that Customer directs the Services to transmit to Customer’s own account with that provider; the Sub-processor List identifies it only in the former capacity.
7. Security
7.1Security Measures. Taking into account the state of the art, the costs of implementation, and the nature, scope, context and purposes of Processing, as well as the risks to individuals, Company shall implement and maintain appropriate technical and organizational measures designed to protect Customer Personal Data against Personal Data Breaches and to ensure a level of security appropriate to the risk, including at least the Security Measures described in Schedule 2.
7.2Updates. Company may update the Security Measures from time to time, provided that no update materially reduces the overall level of protection afforded to Customer Personal Data. Company shall review the Security Measures at least annually and shall update Schedule 2, and make the current version available to Customer, to reflect any material change.
7.3Certifications. Company shall maintain the third-party assurance program described in Schedule 2 and shall obtain a SOC 2 Type II report covering the Security Trust Services Criteria applicable to the Services following the close of the observation period described in Schedule 2, and shall thereafter maintain such a report with recurring annual examinations. Company shall notify Customer if any certification or report described in Schedule 2 is withdrawn or not renewed.
7.4Shared responsibility. Customer is responsible for the secure configuration and use of the Services, including administrator access controls, identity-provider settings, device enrollment decisions and the management of its Users’ credentials and quorum devices, and for the security of systems and networks under its control. Company is not responsible for Customer Personal Data that becomes irretrievable through loss of Customer-controlled devices or keys as described in the Agreement.
8. Personal Data Breach
8.1Notification. Company shall notify Customer without undue delay, and in any event within forty-eight (48) hours, after becoming aware of a Personal Data Breach. Company shall address the notice to Customer’s designated privacy contact under Section 8.5 and to the notice address under the Agreement.
8.2Content of notice. The notice shall describe, to the extent then known to Company: (a) the nature of the Personal Data Breach, including the categories and approximate number of individuals and of records concerned and the sensitivity of the Personal Data involved; (b) the likely consequences; (c) the measures taken or proposed to address the Personal Data Breach and to mitigate its possible adverse effects; and (d) a contact point from whom further information may be obtained. Where all information is not available at the same time, Company shall provide it in phases without undue further delay.
8.3Mitigation and cooperation. Company shall take reasonable measures within its control to contain the Personal Data Breach, to reduce the risk of harm to individuals and to prevent recurrence, and shall provide Customer with the cooperation and assistance reasonably necessary for Customer to meet its own obligations to notify regulators, individuals and other persons and to keep any required record of the incident.
8.4Attempted violations and register. Company shall also inform Customer of any material attempted violation of the confidentiality of Customer Personal Data that Company detects and reasonably believes presents a risk to Customer, and shall maintain a register of Personal Data Breaches affecting Customer Personal Data for the period required by Applicable Data Protection Laws, which Company shall make available to Customer on request.
8.5Privacy contact. Customer shall designate a privacy contact (and, where Addendum 3 applies, its Privacy Officer) and provide that person’s name, title and contact details through the Services or by notice to Company, and shall keep them current. Where no contact has been designated, notices under this Section 8 may be given to Customer’s notice address under the Agreement.
8.6Costs; no admission. Company shall not be required to bear the costs of assistance under Section 8.3 to the extent the Personal Data Breach results from the acts or omissions of Customer or its Users, but Company’s obligation to notify under Section 8.1 applies in all cases. Notification of a Personal Data Breach is not an acknowledgement of fault or liability.
9. Assistance with Individual Requests and Assessments
9.1Requests received by Company. If Company receives a request from an individual to exercise a right under Applicable Data Protection Laws in respect of Customer Personal Data (a “Request”), Company shall, to the extent permitted by law, promptly inform the individual that the Request should be directed to Customer, and shall notify Customer of the Request. Company shall not otherwise respond to the Request except on Customer’s instruction or as required by law.
9.2Customer self-service. Customer is responsible for receiving Requests, verifying the identity of the requester, and determining whether and how to respond. Customer may action Requests for access, correction, deletion, restriction and portability itself, in respect of Customer Personal Data available to it through the Services, using the functionality Company makes available for that purpose.
9.3Company assistance. Where Customer requires assistance that cannot be actioned through that functionality, Customer shall submit a request to Company at legal@splitsecure.com. Company shall acknowledge the request within five (5) business days and shall respond within twenty (20) calendar days, and where Customer notifies Company that a shorter period is necessary for Customer to meet a statutory deadline, Company shall use reasonable efforts to respond within that period. Company shall, on Customer’s documented instruction and without undue delay, correct, delete, restrict, de-index or cease disseminating Customer Personal Data in its possession or control, and shall communicate the instruction to each Sub-processor to which it has disclosed the relevant Customer Personal Data, in each case to the extent required by Applicable Data Protection Laws.
9.4Assessments and regulators. Taking into account the nature of the Processing and the information available to it, Company shall provide Customer with reasonable cooperation and assistance in connection with (a) any data protection impact assessment, privacy impact assessment, risk assessment or cybersecurity audit Customer is required to conduct under Applicable Data Protection Laws in respect of the Processing; (b) any prior consultation with, or inquiry, investigation or request from, a regulator with jurisdiction over the Processing; and (c) Customer’s obligations in respect of automated decision-making, where the Services are used to make decisions producing legal or similarly significant effects on individuals, by providing information about the logic, intended output and role of the relevant functionality, subject to reasonable confidentiality controls and without requiring Company to disclose trade secrets. Company shall notify Customer without undue delay of any complaint, notice or inquiry from a regulator relating to the Processing of Customer Personal Data, except where prohibited by law.
9.5Costs. Assistance under this Section 9 is provided at no additional charge, except that Company may charge its then-current professional services rates, on prior notice to Customer, for assistance that is manifestly excessive, repetitive or unrelated to any requirement of Applicable Data Protection Laws, and Customer is responsible, to the extent legally permitted, for the costs of assistance with assessments under Section 9.4(a) that exceed the provision of information already in Company’s possession.
10. Records, Audit and Demonstrating Compliance
10.1Information and records. Company shall make available to Customer the information reasonably necessary to demonstrate Company’s compliance with this DPA and with its obligations under Applicable Data Protection Laws, and shall maintain records sufficient for that purpose for the term of the Agreement and three (3) years thereafter. On Customer’s reasonable written request, no more than once in any twelve (12) month period and subject to reasonable confidentiality controls, Company shall provide a written description of its use, retention and disclosure of Customer Personal Data sufficient to enable Customer to satisfy itself that they are consistent with this DPA.
10.2Reports and certifications. On Customer’s written request at reasonable intervals and subject to reasonable confidentiality controls, Company shall make available for Customer’s review copies of the certifications and audit reports described in Schedule 2 that demonstrate Company’s compliance with prevailing data security standards applicable to the Processing.
10.3Audit. Where the reports and certifications made available under Section 10.2 are not reasonably sufficient to demonstrate compliance as required by Applicable Data Protection Laws, Company shall allow Customer or an independent third-party representative bound by confidentiality obligations and reasonably acceptable to Company to conduct an audit or inspection of Company’s data security infrastructure and procedures relevant to the Processing of Customer Personal Data, provided that (a) Customer gives at least thirty (30) days’ prior written notice describing the scope; (b) the audit is conducted during business hours, is not unreasonably disruptive to Company’s business and is restricted to data and systems relevant to Customer; (c) audits occur no more than once per calendar year, save where a Personal Data Breach affecting Customer Personal Data has occurred within the preceding twelve (12) months, where there are reasonable and documented indications of Company’s non-compliance with this DPA, or where an audit is required by a regulator or by Applicable Data Protection Laws; and (d) Customer bears the costs of the audit and reimburses Company for time reasonably expended on any on-site component. Customer shall provide Company with a copy of any audit report and shall treat it as Company’s Confidential Information under the Agreement.
10.4Statutory rights not limited. Nothing in this Section 10 limits any right of audit, inspection or verification that Applicable Data Protection Laws or an Addendum grant to Customer and that cannot be limited by contract, but the parties agree that such rights shall be exercised, so far as the law permits, in the manner and on the conditions set out in this Section 10.
11. Retention, Return and Deletion
11.1During the term. Company shall retain Customer Personal Data only for so long as necessary to provide the Services and as instructed by Customer. Customer may delete Customer Personal Data during the term through the self-service functionality of the Services, and Company shall delete Customer Personal Data that cannot be so deleted on Customer’s written request without undue delay.
11.2On exit. Following completion of the Services or the expiry or termination of the Agreement, Company shall, at Customer’s choice made by written notice within thirty (30) days thereafter, return Customer Personal Data to Customer in a commonly used, machine-readable format and delete the remaining copies, or delete all Customer Personal Data, in each case within sixty (60) days after the completion, expiry or termination, and shall certify in writing that it has done so. Where Customer makes no choice, Company shall delete. Company’s export and return obligations are subject to the portability terms of the Agreement. Where the Agreement is reinstated under Section 8.3(i) of the Agreement before return or deletion under this Section 11.2 has been completed, this Section 11.2 ceases to apply to Customer Personal Data that has not yet been returned or deleted, and Company shall continue to Process it under this DPA.
11.3Legal retention. Where applicable law requires Company to retain Customer Personal Data beyond the period in Section 11.2, or return or deletion is not reasonably practicable, Company shall inform Customer, shall block the Customer Personal Data from any Processing other than storage, shall continue to protect it in accordance with this DPA, and shall delete it as soon as the impediment ceases.
11.4Backups and deidentification. Customer Personal Data held in backup systems shall be deleted in accordance with Company’s backup rotation schedule, not exceeding ninety (90) days after the deletion under Section 11.2, and shall not be restored except as necessary to recover the Services and subject to re-deletion. Company may retain Deidentified Data created under Section 4. Company shall not anonymize or deidentify Customer Personal Data otherwise than as permitted by Section 4 and, where Addendum 3 applies, Section 5 of Addendum 3.
12. Processing Locations, Transfers and Government Requests
12.1Locations. Customer acknowledges that Company Processes Customer Personal Data in the United States and that its Sub-processors Process Customer Personal Data in the jurisdictions identified in the Sub-processor List, and that Company personnel located in the jurisdictions identified in Schedule 1 may access Customer Personal Data remotely for the purposes stated there. Company shall not Process, or permit access to, Customer Personal Data on a continuing basis from any other jurisdiction without updating Schedule 1 or the Sub-processor List in accordance with Section 6.2 and, where an Addendum so requires, complying with that Addendum. Short-term and incidental access to Customer Personal Data by Company personnel from another jurisdiction, such as while travelling, is permitted without updating Schedule 1, provided that it is for the purposes stated in Schedule 1, is made over encrypted channels to the US-hosted environments, and does not result in a copy of Customer Personal Data being stored on any personnel device. Such access is not permitted from any country or region that is subject to comprehensive sanctions administered by the US Office of Foreign Assets Control, or from which Company determines that access cannot lawfully or securely be made.
12.2Transfer mechanisms. Where Applicable Data Protection Laws restrict the transfer of Customer Personal Data to a jurisdiction in which Company or a Sub-processor Processes it, the transfer mechanisms and supplementary measures set out in the applicable Addendum apply, and Company shall not transfer Customer Personal Data otherwise than in accordance with them.
12.3Government and legal requests. If Company receives a request or order from a government, law enforcement, regulatory or judicial authority for the disclosure of Customer Personal Data, Company shall (a) not voluntarily disclose Customer Personal Data; (b) unless legally prohibited, notify Customer of the request without undue delay and, where the request permits, before disclosing, so that Customer may seek a protective order or other remedy, and, where Company is permitted to do so, redirect the authority to Customer, for which purpose Company may provide the authority with Customer’s identity and contact details; (c) disclose only the minimum Customer Personal Data required to comply; (d) where there are reasonable grounds to consider the request unlawful or overbroad, challenge it and seek interim measures pending the outcome; and (e) document each request and the response, and make that documentation available to Customer on request, subject to legal restrictions. Where Company is prohibited from notifying Customer, Company shall use reasonable efforts to obtain a waiver of the prohibition.
12.4Statement regarding requests. Company represents that, as of the date Customer accepts this DPA, Company has not received any request from a national security or intelligence authority for access to Customer Personal Data and is not aware of any law or practice in a jurisdiction in which it Processes Customer Personal Data that would prevent it from complying with this DPA. Company shall notify Customer if this statement ceases to be accurate, and the parties shall discuss whether any Processing should be suspended or additional measures adopted. Company maintains a transparency report at https://www.splitsecure.com/privacy.
13. Liability
13.1Each party’s liability arising out of or in connection with this DPA, whether in contract, tort or otherwise, is subject to the exclusions and limitations of liability in the Agreement, which apply in aggregate to claims under the Agreement and this DPA together, except to the extent that Applicable Data Protection Laws do not permit that liability to be excluded or limited, and except as provided in Section 8 of Addendum 1 in respect of the Standard Contractual Clauses.
13.2Customer’s indemnity under Section 3.6 is subject to Section 13.1. Nothing in this DPA limits an individual’s rights against either party under Applicable Data Protection Laws.
14. Term, Termination and Survival
14.1This DPA takes effect on the date determined under Section 16 and remains in force for so long as the Agreement remains in effect or Company or any Sub-processor retains any Customer Personal Data, whichever is later.
14.2A material breach by Company of this DPA is a material breach of the Agreement. If a change in Applicable Data Protection Laws or a decision of a competent authority prevents either party from performing all or part of its obligations under this DPA, the parties shall suspend the affected Processing and negotiate in good faith an amendment that restores compliance; if no amendment is agreed within sixty (60) days, either party may terminate the affected Services on written notice without liability for the termination.
14.3Sections 4, 5, 6.5, 7, 8, 10.1, 11, 12, 13, 15 and 17, and each Addendum to the extent it relates to Customer Personal Data still retained, survive expiry or termination of the Agreement.
15. Order of Precedence and Interpretation
15.1Within the DPA. In the event of conflict or inconsistency, the following order of precedence applies in respect of the Personal Data concerned: (a) any standard contractual clauses or other transfer instrument incorporated by an Addendum, to the extent Applicable Data Protection Laws require them to prevail; (b) the Addendum that applies to that Personal Data under Section 1.3, as to the requirements of the laws that Addendum covers; (c) the body of this DPA and its Schedules; (d) the Agreement; and (e) any other document. Where two or more Addenda apply to the same Personal Data, each prevails as to the requirements of the laws it covers, and where the same term is addressed by more than one Addendum but is not a requirement of the laws either covers, the body of this DPA governs.
15.2Higher standard. Where this DPA, an Addendum and Applicable Data Protection Laws impose different standards on the same Processing and compliance with the more protective standard also satisfies the less protective one, Company shall comply with the more protective standard in respect of the Personal Data to which it applies. Company may, at its option, apply the more protective standard to all Customer Personal Data.
15.3Privacy policy. Company’s privacy policy describes Company’s Processing as a controller and is not incorporated into, and does not form part of, this DPA or the Agreement, except that references in Section 4 to the privacy policy are to the version in effect on the date Customer accepts this DPA, as updated in accordance with its terms without material reduction in protection.
15.4Interpretation. Headings are for convenience only. “Including” means “including without limitation”. References to a law include that law as amended, consolidated or replaced and any regulation or guidance having the force of law made under it. Where this DPA requires a notice or consent to be “written”, electronic communication through the Services or by email suffices.
16. Acceptance, Effectiveness and Amendment
16.1Acceptance. This DPA is entered into and becomes legally binding on the earliest of the following: (a) Customer’s acceptance of the Agreement through the Services, provided that the text of this DPA was presented to Customer, or made available by a conspicuous link, before that acceptance and Customer indicated its assent by checking a box or clicking a button referring to this DPA or to the Agreement into which this DPA is incorporated; (b) Customer’s acceptance of this DPA through the Services by any other means Company makes available; (c) execution of this DPA by both parties, whether by electronic or handwritten signature, in connection with a negotiated Agreement or a written ordering document; or (d) where Customer has been presented with this DPA and has not accepted it by any of the foregoing means, Customer’s submission of Personal Data to the Services. The date on which this DPA becomes binding is its effective date, except that where Company has Processed Customer Personal Data before that date, this DPA applies to that Processing from the date it began.
16.2Authority. The individual accepting this DPA represents that he or she has authority to bind Customer and its Affiliates to this DPA, and Customer represents that it is not a consumer and is entering into this DPA for business purposes.
16.3Standard contractual clauses. Acceptance of this DPA under Section 16.1 constitutes execution by both parties of any standard contractual clauses, addenda and annexes incorporated by an Addendum, including their signature blocks, to the extent Applicable Data Protection Laws permit them to be executed in that manner. Where Applicable Data Protection Laws require a separate written signature for such clauses, the parties shall sign them on request without altering their terms.
16.4Amendment. Company may amend this DPA, including the Addenda and Schedules, by notice to Customer (a) to reflect changes in Applicable Data Protection Laws, in standard contractual clauses or other transfer instruments approved by a competent authority, or in regulatory guidance, or (b) to add an Addendum covering additional privacy laws, provided that no amendment materially reduces the protection afforded to Customer Personal Data. Any other amendment requires the written agreement of both parties. Customer’s continued use of the Services after thirty (30) days’ notice of an amendment under (a) or (b) constitutes acceptance of it.
16.5Precedence over prior instruments. This DPA supersedes any data processing agreement, addendum or standard contractual clauses previously entered into between the parties in respect of the Services, from its effective date.
17. General
17.1Notices under this DPA shall be given in accordance with the Agreement, with a copy to privacy@splitsecure.com in the case of notices to Company and to the privacy contact designated under Section 8.5 in the case of notices to Customer.
17.2If any provision of this DPA is held invalid or unenforceable, the remainder continues in effect and the parties shall replace the provision with a valid one that most closely achieves its purpose. This DPA is governed by the law governing the Agreement, and disputes shall be resolved in the manner provided in the Agreement, except as an Addendum or any incorporated standard contractual clauses otherwise require.
17.3Where this DPA is executed under Section 16.1(c), it may be executed in counterparts and by electronic signature. The following signature block is for use in that case only and is not required for acceptance under Section 16.1(a), (b) or (d).
Customer | SplitSecure Inc. |
Customer legal name: |
|
Signature: | Signature: |
Print name: | Print name: |
Title: | Title: |
Date: | Date: |
SCHEDULE 1 — DETAILS OF PROCESSING
This Schedule 1 describes the Processing of Customer Personal Data under the DPA. It also serves as Annex I.B to the Standard Contractual Clauses under Addendum 1, as the description of business purposes and categories under Addendum 2, and as the description of processing and processing locations under Addendum 3.
Subject matter of the Processing. Provision of the Services, being SplitSecure’s access-governance and secrets-management platform, including its mobile application, web application (Companion Service), browser extensions, coordination services and related support.
Nature of the Processing. Collection, recording, storage, organization, encryption, retrieval, consultation, use, transmission, disclosure to Sub-processors as permitted by the DPA, restriction, erasure and destruction, as necessary to provide the Services. Company does not hold Customer cryptographic key material in plaintext; such material is protected as described in category (g) below and in Schedule 2.
Purposes of the Processing. Company Processes Customer Personal Data solely for the following purposes: (a) providing, operating and making available the Services to Customer in accordance with the Agreement; (b) authenticating Users and administering their access to the Services; (c) storing, hosting and transmitting Customer Personal Data at Customer’s direction; (d) providing technical support and troubleshooting at Customer’s request; (e) detecting and responding to security incidents and protecting against malicious, deceptive, fraudulent or illegal activity affecting the Services; (f) verifying or maintaining the quality or safety of, or improving or upgrading, the Services, to the extent permitted by Section 4 of the DPA; and (g) complying with law and Customer’s documented instructions.
Categories of individuals. Customer’s employees, contractors, consultants and agents who are Users or administrators of the Services; individuals whose Personal Data Customer or its Users include in free-text fields, justifications or vault names; and, where Customer is a Managed Service Provider, the corresponding individuals of Customer’s clients.
Categories of Personal Data.
(a)Organization membership and identity data: the User’s name, business email address, job title and username as recorded in Customer’s organization; identity-provider subject identifiers and attributes synchronized by Customer via SAML 2.0 or SCIM (including external ID, username and group membership); and the User’s roles, team memberships and permissions within Customer’s organization. (Records of acceptance of Company’s terms, and the data Company collects to create and secure a User’s own account, are Company Account Data.)
(b)Device enrollment and authentication records within Customer’s organization: identifiers of the credentials and devices a User has enrolled for use within Customer’s organization (including WebAuthn credential identifiers and device and enclave identifiers and public keys); device names and serial numbers; IP addresses; device model; and session and step-up authentication records. (Device attestation material and the credentials, keys and device records that Company collects to create and secure a User’s own account are Company Account Data.)
(c)Usage and audit data: records of actions taken in the Services, including the identity of the person who proposed, approved or executed an operation, timestamps, device identifiers and any free-text justification or identifier a User supplies.
(d)Communications data: the content of transactional email notifications, mobile push notification tokens and content, and support correspondence.
(e)Billing contact data: organization name and billing contact name and email address transmitted to Company’s payment processor; Company itself retains only an opaque billing identifier, the payment method type, the last four digits of the card number and records of transactions, as described in Company’s End User App Privacy Policy. (Billing contact data of Customer’s administrators is Company Account Data.)
(f)Diagnostic data: server-side trace logs and error records generated by Users’ use of the Services within Customer’s organization, which may incidentally contain identifiers; trace logs are retained for no more than fifteen (15) days and error records for no more than ninety (90) days. (Error reports and application telemetry collected from a User’s device are Company Account Data under Section 4.2.)
(g)Protected Secrets: the private keys, passwords, passkeys, certificates and other secret values that Customer or its Users store in a vault in the Services for protection (as defined in Section 3.5 of the Agreement), which may relate to identifiable individuals (for example, an individual’s account log-in credentials). In a threshold vault, a Protected Secret exists only as shares held on Users’ enrolled devices and is reconstituted solely inside an attested execution environment permitted by Customer’s policies, for the duration of an approved operation. Company personnel cannot access Protected Secrets in plaintext. Record names, usernames, site addresses and other metadata stored with a Protected Secret are not Protected Secrets, and are Customer Personal Data to the extent that they relate to an identifiable individual.
(h)Identity assertions and notifications: where Customer configures the Services to act as an identity provider for, or to forward audit events to, a Connected Service (as defined in Section 6.7 of the DPA), (1) in signed SAML assertions, a name identifier in the format and with the value that Customer’s administrator configures (which may be the requesting User’s email address or session name) and the attributes that the administrator defines for that application (which may include the User’s email address, name, username, role and group); these values are set by the administrator and are not drawn from a directory; and (2) in forwarded audit events, the proposal identifier, the Users who requested, voted on or executed the operation, the justification and the other details shown to voters, the result, and the name and fingerprint of the devices involved. No Protected Secret or key material is included in an assertion or a forwarded event.
(i)Session recordings: where Customer enables session recording for a target system, the session and target identifiers, the User who authenticated, the username used on the target system, the target address, the start time and exit codes; the output that the target system returns during the session, with timestamps, which ordinarily includes the commands the User types (because the terminal echoes them) and may include Personal Data that the target system displays; the command strings of non-interactive executions; and terminal settings and channel events. Keystrokes are not recorded. Recordings are stored as Customer Personal Data in encrypted form, can be opened only through the approvals that Customer has configured in the Services, and cannot be accessed by Company personnel. Customer is responsible under the Agreement for deciding which sessions are recorded and for not recording sessions in which Sensitive Data is displayed.
(j)Digital asset data: where Customer uses the Services’ wallet features, wallet addresses and records of the transactions that Users propose, approve and sign. Transactions that are broadcast become part of the public record of the relevant blockchain network.
Sensitive Data. None, other than Protected Secrets (category (g) above), which may include individuals’ account log-in credentials and which Company Processes only as described there and in Schedule 2. Customer is otherwise prohibited by Section 3.6 of the DPA and the Agreement from submitting Sensitive Data, and the Services are not designed to receive it.
Frequency of the transfer. Continuous, for the duration of the Agreement.
Duration of the Processing. For the term of the Agreement and thereafter until Customer Personal Data is returned or deleted in accordance with Section 11 of the DPA, or for such longer period as applicable law requires. Audit records and other activity records relating to Customer’s organization are retained for the term of the Agreement and are deleted in accordance with Section 11 of the DPA, or earlier at Customer’s written request under Section 11.1. As a feature of the Services, audit records remain available to Customer in the Services for at least seven (7) years after their creation during the term of the Agreement.
Company Processing locations. Customer Personal Data is Processed and stored by Company in the United States, in Amazon Web Services facilities. Company operates no Processing or storage location outside the United States. Two kinds of Processing take place elsewhere at Customer’s direction and are not Company Processing locations: where Customer’s policy designates Users’ enrolled devices as the execution environment, the relevant cryptographic operations are performed on those devices, wherever they are located; and where Customer uses the Services’ wallet features, the transactions that Customer’s Users approve are broadcast to the relevant public blockchain networks. Static web-application assets containing no Personal Data are distributed through Amazon CloudFront’s global edge network. Company personnel located in the United States and Canada may access Customer Personal Data remotely from those jurisdictions for the purposes of support, security monitoring, incident response and operation of the Services, over encrypted channels to the US-hosted environments; no copy of Customer Personal Data is stored on personnel devices. Company does not permit personnel or contractors located in any other jurisdiction to access Customer Personal Data on a continuing basis. Short-term and incidental access by Company personnel from another jurisdiction, such as while travelling, is permitted for the same purposes without updating this paragraph, provided that it is made over encrypted channels to the US-hosted environments and no copy of Customer Personal Data is stored on any personnel device. Such access is not permitted from any country or region that is subject to comprehensive sanctions administered by the US Office of Foreign Assets Control, or from which Company determines that access cannot lawfully or securely be made. Company shall update this paragraph in accordance with Section 12.1 of the DPA before permitting access on a continuing basis from any additional jurisdiction.
Sub-processors and their locations. The current Sub-processor List, identifying each Sub-processor, the Processing it performs and the jurisdictions in which it Processes Customer Personal Data, is maintained at https://trust.splitsecure.com/ in accordance with Section 6 of the DPA. A dated copy of the Sub-processor List as at the effective date of the DPA is deemed incorporated in this Schedule.
Competent supervisory authority (Addendum 1). Determined in accordance with Section 7 of Addendum 1.
SCHEDULE 2 — SECURITY MEASURES
This Schedule 2 describes the technical and organizational measures Company maintains to protect Customer Personal Data. It also serves as Annex II to the Standard Contractual Clauses under Addendum 1, as the description of reasonable security procedures under Addendum 2, and as the description of confidentiality and security measures for the purposes of section 18.3 of the Québec Act under Addendum 3. Company may update this Schedule in accordance with Section 7 of the DPA.
Pseudonymization and encryption. All data is encrypted in transit using TLS 1.2 or higher with industry-recommended cipher suites. Data at rest is encrypted using AES-256 through AWS storage-level encryption, and sensitive records are additionally protected with application-layer envelope encryption (AES-256-GCM) using key-encryption keys wrapped by AWS Key Management Service. Sensitive cryptographic operations are performed exclusively inside attested, hardware-isolated execution environments: AWS Nitro Enclaves operated by Company, whose images are cryptographically measured and signed, or, where Customer’s policy so provides, the secure enclaves of Users’ enrolled devices. Customer cryptographic key material in a threshold vault is protected by a threshold secret-sharing scheme such that complete key material is never assembled outside such an execution environment. Company personnel cannot access that material in plaintext.
Confidentiality, integrity, availability and resilience. Company personnel are bound by confidentiality obligations, and Company requires every Sub-processor to accept data protection and confidentiality obligations no less protective than those in the DPA. The Services run on AWS managed services replicated across multiple availability zones. Cryptographic processing is isolated from general-purpose infrastructure through hardware-enforced enclave boundaries, and staging and production environments run in separate AWS accounts.
Restoration of availability. Production datastores use AWS-managed continuous backups with point-in-time recovery and are replicated across multiple availability zones. Backup restoration procedures are periodically tested to validate backup integrity and Company’s ability to recover production systems within its recovery objectives.
Testing, assessment and evaluation. Company has completed a SOC 2 Type I examination covering the Security Trust Services Criteria. Company’s first SOC 2 Type II examination covers an observation period that ended on September 30, 2026, and Company undergoes SOC 2 Type II examinations annually thereafter. Automated static analysis, linting and dependency vulnerability monitoring are integrated into Company’s development and release pipeline, and Company performs continuous vulnerability scanning of production infrastructure. Identified vulnerabilities are risk-assessed, prioritized and remediated in accordance with Company’s security policies.
User identification and authorization. End users authenticate using one of the methods enabled by Customer: email-based login with one-time links, phishing-resistant WebAuthn/passkey credentials, or single sign-on through Customer’s identity provider, in which case authentication requirements (including multi-factor requirements) are governed by Customer’s identity-provider policies. End-user devices are enrolled through pairing flows backed by hardware attestation (Apple App Attest and Android Key Attestation) where supported by the platform. All API requests are authenticated and authorized against the requesting User’s organization and team membership. Company personnel access corporate and production systems through single sign-on with multi-factor authentication from company-managed devices, and production access is restricted to authorized personnel on a least-privilege basis.
Protection of data in transmission and storage. All traffic over public networks is encrypted using TLS 1.2 or higher. Certain sensitive payloads are additionally encrypted at the application layer such that they can be decrypted only inside the attested execution environment permitted by Customer’s policy. Data at rest is encrypted with AES-256 using keys held in AWS KMS; sensitive records are additionally envelope-encrypted, and the associated key-encryption keys can be released only to enclave environments that pass cryptographic attestation. Customer secrets and key material are never stored in plaintext outside an attested execution environment. Session recordings are encrypted so that they can be opened only through the approvals that Customer has configured in the Services, and Company personnel cannot access them.
Physical security. All Company Processing occurs in physical data centers operated by AWS, whose physical security controls are described at https://aws.amazon.com/compliance/data-center/controls/.
Event logging. Infrastructure and application logs are centrally collected and monitored by Company’s engineering team, and log activity is investigated and escalated as appropriate. Security-relevant customer-facing actions are recorded in a cryptographically signed, tamper-evident audit log available to Customer, and Customer may forward audit events to its own logging and SIEM systems. Application trace logs reference Users by a pseudonymous identifier and are retained for fifteen (15) days.
System configuration and change management. All changes to production systems are made through version-controlled code subject to mandatory peer review and deployed through automated CI/CD pipelines. Enclave images are built through a controlled release process, cryptographically measured and release-signed; production key material is accessible only to enclave images whose measurements match signed releases.
Governance and personnel. Company maintains a risk-based information security program with administrative, organizational, technical and physical safeguards. Company personnel receive security and privacy awareness training on hire and periodically thereafter, acknowledge Company’s information security policies, and are subject to reasonable reliability checks consistent with applicable law. Company formally assigns roles and responsibilities for information security and data privacy.
Incident response. Company maintains documented incident response procedures covering identification, containment, investigation, remediation and post-incident review, including procedures for notifying Customer and its designated privacy contact in accordance with Section 8 of the DPA, and maintains a register of Personal Data Breaches.
Data minimization and retention. Company operates on a shared-responsibility model: Customer determines the Personal Data it submits to the Services. The Services are designed so that Personal Data is incidental to their operation, and Company limits collection to the information necessary to provide, secure and operate the Services, including protocol-required device attestation data. Audit records reference individuals by identifier, with display information resolved at read time. When a User’s account is deleted, Company retains for Customer a record of that User’s name, email address, role, sign-in method and join and leave dates so that Customer’s audit log remains complete, and replaces that record with a “Forgotten User” marker on Customer’s instruction, so that the individual’s Personal Data is removed from historical audit views. Customer Personal Data is deleted in accordance with Section 11 of the DPA.
Data quality. Company’s APIs are defined schema-first using Protocol Buffers, with strongly typed generated clients and servers enforcing a strict contract. Data is validated server-side before persistence, and automated unit and integration test suites executed in continuous integration cover the logic that Processes Personal Data.
Portability and erasure. Customer Personal Data may be deleted by Customer through self-service functionality or at Customer’s request, and Company will respond to data-porting requests in accordance with Section 9 of the DPA and the portability terms of the Agreement.
Sub-processors. Company enters into written agreements with its Sub-processors imposing data protection obligations no less protective than those in the DPA, and assesses each Sub-processor’s security posture before engagement and periodically thereafter.
ADDENDUM 1 — EUROPEAN UNION, UNITED KINGDOM AND SWITZERLAND
This Addendum 1 applies automatically under Section 1.3 of the DPA to Customer Personal Data that is subject to European Data Protection Laws (“European Personal Data”). It supplements the DPA and applies only to European Personal Data. Terms defined in the DPA have the same meaning here.
1. Definitions
(a)“European Data Protection Laws” means (i) Regulation (EU) 2016/679 (the “EU GDPR”); (ii) the EU GDPR as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the European Union (Withdrawal) Act 2018, and the Data Protection Act 2018 (together, the “UK GDPR”); (iii) the Swiss Federal Act on Data Protection of 25 September 2020 and its ordinances (the “FADP”); (iv) Directive 2002/58/EC and national laws implementing it, and the Privacy and Electronic Communications (EC Directive) Regulations 2003; and (v) any law of a member state of the European Union or European Economic Area, of the United Kingdom or of Switzerland supplementing any of them; in each case as amended or replaced from time to time. “GDPR” means the EU GDPR and the UK GDPR.
(b)“EU SCCs” means the standard contractual clauses for the transfer of personal data to third countries annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, as amended or replaced from time to time.
(c)“UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses (version B1.0) issued by the Information Commissioner and laid before Parliament under section 119A of the Data Protection Act 2018 on 2 February 2022, as revised from time to time under section 18 of its Mandatory Clauses.
(d)“Standard Contractual Clauses” means the EU SCCs, the EU SCCs as amended by the UK Addendum, and the EU SCCs as modified by Section 6.4 of this Addendum for Switzerland, in each case as incorporated by Section 6.
(e)“Restricted Transfer” means a transfer of European Personal Data from Customer (or its Affiliate) to Company, or an onward transfer from Company to a Sub-processor, to a country that is not the subject of an adequacy decision or regulations by the European Commission, the UK Secretary of State or the Swiss Federal Council, as applicable, where the transfer would be prohibited by European Data Protection Laws in the absence of the Standard Contractual Clauses or another appropriate safeguard.
(f)“Supervisory Authority”, “Data Subject”, “Personal Data Breach”, “controller” and “processor” have the meanings given in the GDPR, and references to the GDPR include the FADP as applicable.
2. Roles under European Data Protection Laws
2.1In respect of European Personal Data, Customer is the controller and Company is the processor, except where Customer acts as a processor for its own clients as described in Section 3.1 of the DPA, in which case Customer is a processor, Company is a sub-processor, and the obligations that Article 28 of the GDPR imposes on the controller are owed by Customer’s clients and passed to Company through Customer.
2.2Where Customer is a processor, (a) Customer warrants that its clients have authorized the engagement of Company on the terms of the DPA and this Addendum; (b) Company’s obligations under Sections 9.4 and 10 of the DPA to assist with data protection impact assessments and prior consultations, and under Section 8 of the DPA to assist with notifications to Supervisory Authorities and Data Subjects, are owed to Customer for the benefit of Customer’s clients; and (c) references in the DPA to Customer’s obligations as controller are read as references to the corresponding obligations of Customer’s clients.
3. Article 28 Terms
3.1In addition to the DPA, and as required by Article 28(3) of the GDPR, Company shall in respect of European Personal Data:
(a)Process the European Personal Data only on documented instructions from Customer, including with regard to transfers of Personal Data to a third country or an international organization, unless required to do so by European Union or member state law, or the law of the United Kingdom or Switzerland, to which Company is subject, in which case Company shall inform Customer of that legal requirement before Processing unless that law prohibits such information on important grounds of public interest (Section 3.3 of the DPA constitutes those documented instructions);
(b)ensure that persons authorized to Process the European Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality (Section 5 of the DPA);
(c)take all measures required pursuant to Article 32 of the GDPR (Section 7 of the DPA and Schedule 2);
(d)respect the conditions referred to in Article 28(2) and (4) of the GDPR for engaging another processor (Section 6 of the DPA), and impose on each Sub-processor, by way of contract, the same data protection obligations as are set out in the DPA and this Addendum, in particular providing sufficient guarantees to implement appropriate technical and organizational measures;
(e)taking into account the nature of the Processing, assist Customer by appropriate technical and organizational measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to requests for exercising the Data Subject’s rights under Chapter III of the GDPR, including the rights of access, rectification, erasure, restriction, data portability, objection, and not to be subject to a decision based solely on automated processing (Section 9 of the DPA);
(f)assist Customer in ensuring compliance with the obligations pursuant to Articles 32 to 36 of the GDPR, taking into account the nature of the Processing and the information available to Company (Sections 7, 8 and 9.4 of the DPA);
(g)at the choice of Customer, delete or return all the European Personal Data to Customer after the end of the provision of the Services, and delete existing copies unless European Union, member state, United Kingdom or Swiss law requires storage of the Personal Data (Section 11 of the DPA);
(h)make available to Customer all information necessary to demonstrate compliance with the obligations laid down in Article 28 of the GDPR and allow for and contribute to audits, including inspections, conducted by Customer or another auditor mandated by Customer (Section 10 of the DPA, which the parties agree sets out the manner in which those audits are conducted); and
(i)immediately inform Customer if, in Company’s opinion, an instruction infringes the GDPR or other European Data Protection Laws (Section 3.4 of the DPA).
3.2Company shall notify Customer of a Personal Data Breach affecting European Personal Data without undue delay, and in any event within the period stated in Section 8.1 of the DPA, after Company becomes aware of it; the outer time limit in Section 8.1 of the DPA does not extend the meaning of “without undue delay”. The parties acknowledge that Customer’s obligation under Article 33(1) of the GDPR to notify the competent supervisory authority within 72 hours runs from the time Customer becomes aware of the Personal Data Breach, which, where Company is the source of Customer’s knowledge, is the time of Company’s notice under this Section 3.2. Company’s notification period under Section 8.1 of the DPA is a separate obligation of Company and is not part of, and does not reduce, that 72-hour period.
3.3Company shall maintain the records required by Article 30(2) of the GDPR in respect of Processing carried out on Customer’s behalf and make them available to Customer or a Supervisory Authority on request.
3.4Customer, as controller, is responsible for maintaining a lawful basis under Article 6 of the GDPR for the Processing, for providing the information required by Articles 13 and 14 to Data Subjects, and for ensuring that no special categories of personal data within Article 9 or data within Article 10 of the GDPR are submitted to the Services, consistent with Section 3.6 of the DPA.
4. Company Account Data and Company Usage Data
4.1Where Company creates Deidentified Data under Section 4 of the DPA from European Personal Data, Company shall apply anonymization techniques such that the resulting data is no longer personal data within the meaning of Recital 26 of the GDPR, taking into account all the means reasonably likely to be used to identify an individual, and the deidentification covenant in Section 4.4 of the DPA applies. Company is an independent controller of Company Account Data and shall comply with European Data Protection Laws in that capacity.
5. Sub-processors
5.1Section 6 of the DPA sets out the general written authorization for the purposes of Article 28(2) of the GDPR and Clause 9(a) (Option 2) of the EU SCCs, and the thirty (30) day period in Section 6.2 of the DPA is the minimum prior notice period for that Clause. Customer’s right to object under Section 6.4 of the DPA satisfies Clause 9(a). Company’s obligations under Section 6.5 of the DPA satisfy Clause 9(b) to (e), and copies of Sub-processor agreements provided under Clause 9(c) may be redacted as provided in Section 6.5 of the DPA.
6. Restricted Transfers
6.1Transfers permitted. Customer authorizes Company and its Sub-processors to make Restricted Transfers of European Personal Data as necessary to provide the Services, and acknowledges that Company’s primary Processing operations take place in the United States, subject to this Section 6.
6.2EU SCCs. In respect of Restricted Transfers subject to the EU GDPR, the parties are deemed to have entered into the EU SCCs, which are incorporated into this Addendum by reference and completed as follows:
(a)Module Two (controller to processor) applies where Customer is a controller; Module Three (processor to processor) applies where Customer is a processor under Section 2.1 of this Addendum;
(b)Customer (or, where applicable, its Affiliate) is the “data exporter” and Company is the “data importer”, and the parties’ details for Annex I.A are those in the Agreement or the account records of the Services;
(c)in Clause 7, the optional docking clause does not apply;
(d)in Clause 9, Option 2 applies with the notice period in Section 5.1 of this Addendum;
(e)in Clause 11, the optional language does not apply;
(f)in Clause 13, the Supervisory Authority is determined under Section 7 of this Addendum;
(g)in Clause 17, Option 1 applies and the EU SCCs are governed by the law of Ireland; in Clause 18(b), disputes shall be resolved before the courts of Ireland;
(h)Annex I.A and I.B are completed by this Section 6.2(b) and Schedule 1 to the DPA; Annex I.C is completed by Section 7 of this Addendum; Annex II is completed by Schedule 2 to the DPA; and Annex III (list of sub-processors) is completed by the Sub-processor List as at the effective date of the DPA, as updated under Section 6 of the DPA; and
(i)the certification of deletion under Clause 8.5 and the audits under Clause 8.9 are carried out in accordance with Sections 11 and 10 of the DPA respectively, without limiting Customer’s rights under those Clauses.
6.3UK transfers. In respect of Restricted Transfers subject to the UK GDPR, the parties are deemed to have entered into the EU SCCs as completed under Section 6.2, as amended by the UK Addendum, which is incorporated by reference and completed as follows: Table 1 (Parties): the parties and key contacts are as described in Section 6.2(b), and the start date is the effective date of the DPA; Table 2 (Selected SCCs, Modules and Selected Clauses): the EU SCCs as completed under Section 6.2; Table 3 (Appendix Information): Annex 1A as in Section 6.2(b), Annex 1B as in Schedule 1, Annex II as in Schedule 2, and Annex III as in Section 6.2(h); Table 4 (Ending this Addendum when the Approved Addendum changes): Importer and Exporter. Part 2 (Mandatory Clauses) of the UK Addendum applies as issued by the Information Commissioner and revised from time to time. For the purposes of Clause 17 and 18 as amended by the UK Addendum, the governing law and courts are those of England and Wales.
6.4Swiss transfers. In respect of Restricted Transfers subject to the FADP, the EU SCCs as completed under Section 6.2 apply with the following modifications: (a) references to the GDPR are read as references to the FADP insofar as the transfer is subject to the FADP; (b) the term “member state” is not interpreted so as to exclude Data Subjects in Switzerland from suing for their rights in their place of habitual residence under Clause 18(c); (c) the competent Supervisory Authority under Clause 13 and Annex I.C is the Swiss Federal Data Protection and Information Commissioner insofar as the transfer is subject to the FADP; (d) references to personal data include information relating to legal entities until the FADP no longer protects such information; and (e) the EU SCCs also protect the data of Data Subjects in Switzerland.
6.5Onward transfers. Company shall make Restricted Transfers to Sub-processors only under the Standard Contractual Clauses, an adequacy decision or regulations, or another transfer mechanism recognized by European Data Protection Laws, and shall carry out and document a transfer risk assessment where required.
6.6Supplementary measures. In addition to Sections 12.3 and 12.4 of the DPA, (a) Company shall, on Customer’s request, provide the information reasonably necessary for Customer to complete a transfer impact assessment, including the information in Schedule A to Addendum 3 regarding the legal framework of the United States, which Company represents is accurate as at the effective date of the DPA; (b) the parties shall, as needed and at least on any material change in the law or practice of a destination country, review whether the Standard Contractual Clauses and the Security Measures continue to provide protection essentially equivalent to that guaranteed in the EEA, the United Kingdom or Switzerland, and whether additional measures are required; and (c) if Company can no longer comply with the Standard Contractual Clauses, it shall notify Customer promptly and the parties shall follow the procedure in Clause 14(f) and 16 of the EU SCCs.
6.7Alternative mechanisms. If the Standard Contractual Clauses cease to be a valid mechanism for any Restricted Transfer, or a competent authority requires transfers under them to be suspended, Company may by notice to Customer adopt an alternative transfer mechanism recognized by European Data Protection Laws with effect from the date in the notice, and Section 16.4 of the DPA applies. Where European Data Protection Laws require the Standard Contractual Clauses to be executed as a separate instrument, Section 16.3 of the DPA applies.
6.8Precedence. In the event of conflict between the Standard Contractual Clauses and the DPA or this Addendum in respect of a Restricted Transfer, the Standard Contractual Clauses prevail, in accordance with Clause 5 of the EU SCCs and Section 15.1(a) of the DPA. Nothing in the DPA or this Addendum is intended to modify the Standard Contractual Clauses or to reduce the protection they afford to Data Subjects.
7. Supervisory Authority
7.1For the purposes of Clause 13 and Annex I.C of the EU SCCs, the competent Supervisory Authority is (a) where Customer is established in an EEA member state, the Supervisory Authority of that member state; (b) where Customer is not established in the EEA but has appointed a representative under Article 27 of the EU GDPR, the Supervisory Authority of the member state in which the representative is established; and (c) otherwise, the Supervisory Authority of the member state in which the Data Subjects whose Personal Data is transferred are located. For the UK Addendum, the Supervisory Authority is the Information Commissioner. For transfers subject to the FADP, Section 6.4(c) applies.
8. Liability
8.1Nothing in the DPA or the Agreement excludes or limits either party’s liability under Clause 12 of the Standard Contractual Clauses, whether to a Data Subject or as between the parties, or any liability that cannot be excluded or limited under European Data Protection Laws. Subject to that, Section 13 of the DPA applies.
9. Termination and Precedence
9.1This Addendum 1 applies for so long as Company Processes European Personal Data, and thereafter to the extent Company or a Sub-processor retains any. Section 14 of the DPA applies.
9.2In respect of European Personal Data, the order of precedence is that set out in Section 15.1 of the DPA, with the Standard Contractual Clauses ranking first.
ADDENDUM 2 — UNITED STATES STATE PRIVACY LAWS
This Addendum 2 applies automatically under Section 1.3 of the DPA to Customer Personal Data that is subject to US State Privacy Laws (“US Personal Information”). It supplements the DPA and applies only to US Personal Information. Terms defined in the DPA have the same meaning here.
1. Definitions
(a)“CCPA” means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020, together with its implementing regulations, as amended or replaced from time to time.
(b)“US State Privacy Laws” means all laws of any state of the United States relating to privacy or the protection, processing, sale or sharing of personal information that apply to the Processing under the DPA, as amended or replaced from time to time, including the CCPA, the Virginia Consumer Data Protection Act, the Colorado Privacy Act, the Connecticut Data Privacy Act, the Utah Consumer Privacy Act, the Texas Data Privacy and Security Act, the Oregon Consumer Privacy Act and comparable comprehensive state privacy statutes.
(c)The terms “business”, “business purpose”, “commercial purpose”, “consumer”, “contractor”, “cross-context behavioral advertising”, “deidentified”, “personal information”, “processing”, “profiling”, “sale”, “sell”, “sensitive personal information”, “service provider”, “share”, “targeted advertising” and “third party” have the meanings given in the CCPA, and where an equivalent concept exists under another US State Privacy Law, the corresponding term under that law applies to Processing subject to it.
(d)“Expressly Permitted” means, in respect of US Personal Information subject to the CCPA, expressly permitted by the CCPA, and in respect of US Personal Information subject to another US State Privacy Law and not the CCPA, expressly permitted by that law.
2. Roles
2.1In respect of US Personal Information, Customer is the business or controller and Company is a service provider, contractor or processor, except where Customer itself acts as a service provider, contractor or processor for its own clients as described in Section 3.1 of the DPA, in which case Company Processes US Personal Information as Customer’s subcontractor on the same terms. Company does not act as a third party in respect of US Personal Information.
2.2Customer discloses US Personal Information to Company solely for the limited and specified business purposes set out in Schedule 1 to the DPA, and for no other purpose. The categories of personal information and of consumers are those described in Schedule 1.
3. Service Provider and Contractor Obligations
3.1In addition to the DPA, Company shall in respect of US Personal Information:
(a)not sell or share the US Personal Information;
(b)not retain, use or disclose the US Personal Information for any purpose, including any commercial purpose, other than the business purposes specified in Schedule 1 or as otherwise permitted by the DPA, except where Expressly Permitted;
(c)not retain, use or disclose the US Personal Information outside the direct business relationship between Company and Customer, except where Expressly Permitted;
(d)not combine the US Personal Information with personal information that Company receives from or on behalf of another person, or collects from its own interaction with a consumer, except where Expressly Permitted;
(e)not use the US Personal Information for cross-context behavioral advertising or targeted advertising, or to build or enhance a profile of a consumer for use outside the direct business relationship between Company and Customer;
(f)comply with all obligations applicable to a service provider, contractor or processor under US State Privacy Laws, and provide the same level of privacy protection to the US Personal Information as US State Privacy Laws require of Customer;
(g)notify Customer promptly, and in any event within five (5) business days, after determining that it can no longer meet its obligations under US State Privacy Laws in respect of the US Personal Information;
(h)grant Customer the right, on reasonable notice, to take reasonable and appropriate steps to stop and remediate any unauthorized use of the US Personal Information by Company, and cooperate with Customer in doing so; and
(i)ensure that each Sub-processor that Processes US Personal Information is bound by a written contract meeting the requirements of US State Privacy Laws for a service provider’s or contractor’s engagement of another person, in accordance with Section 6.5 of the DPA.
3.2Certification. Company certifies that it understands the restrictions in Section 3.1 and will comply with them.
3.3Company Account Data and Company Usage Data. Company Processes Company Account Data as a business in its own right under Section 4 of the DPA. Company shall not sell or share such data, shall not use it for cross-context behavioral advertising or targeted advertising, and shall not use it to build or enhance a profile of a consumer for use outside the direct business relationship between Company and Customer. Company Usage Data is deidentified information, and Section 4.4 of the DPA constitutes Company’s compliance with the requirements of the CCPA for deidentified information, including the public commitment and contractual flow-down requirements of California Civil Code section 1798.140(m).
4. Consumer Rights
4.1Section 9 of the DPA applies to requests by consumers to know, access, correct, delete, or limit the use and disclosure of sensitive personal information, to opt out of the sale or sharing of personal information or of targeted advertising or profiling, and to exercise any equivalent right under US State Privacy Laws.
4.2Where Customer instructs Company to delete or correct US Personal Information, or notifies Company that a consumer has opted out of the sale or sharing of personal information or of targeted advertising, Company shall comply and shall notify each Sub-processor to which it has disclosed the relevant US Personal Information of the instruction, directing the Sub-processor to comply and to forward the instruction to its own recipients, in each case to the extent required by US State Privacy Laws.
4.3Company is not responsible for verifying the identity of a consumer, except where Customer instructs it to do so and Company is reasonably able to. Company shall not be required to comply with a consumer request that it receives directly other than as provided in Section 9.1 of the DPA.
5. Assessments and Automated Decision-Making
5.1Section 9.4 of the DPA applies to any data protection assessment, risk assessment or cybersecurity audit that Customer is required to conduct or obtain under US State Privacy Laws in respect of the Processing, and to Customer’s obligations in respect of automated decision-making technology and profiling.
5.2Where the Services involve automated decision-making technology used by Customer to make a significant decision concerning a consumer, Company shall provide Customer with the information about the logic, intended output and role of that technology that Customer reasonably requires to meet its obligations under US State Privacy Laws, subject to reasonable confidentiality controls and without disclosing trade secrets.
6. Demonstrating Compliance
6.1Section 10 of the DPA sets out the manner in which Customer may take reasonable and appropriate steps to ensure that Company uses US Personal Information in a manner consistent with Customer’s obligations under US State Privacy Laws, including through the written description under Section 10.1 of the DPA, the reports and certifications under Section 10.2 and the audit right under Section 10.3, and constitutes the parties’ agreement on the assessment measures contemplated by the CCPA and its regulations.
7. Security Breach
7.1Section 8 of the DPA applies to any breach of the security of US Personal Information. Company’s cooperation under Section 8.3 of the DPA includes the cooperation reasonably necessary for Customer to meet its obligations under US State Privacy Laws and applicable state breach notification laws, including the provision of information required for notices to consumers, attorneys general and other regulators.
8. Deletion
8.1Section 11 of the DPA applies to the return and deletion of US Personal Information. Where Company suppresses rather than deletes US Personal Information as permitted by US State Privacy Laws, Company shall apply controls that prevent the suppressed data from being used for any purpose other than those Expressly Permitted, and shall disclose that practice in the written description under Section 10.1 of the DPA.
9. Precedence and Liability
9.1In respect of US Personal Information, this Addendum 2 prevails over the body of the DPA and the Agreement as to the requirements of US State Privacy Laws, in accordance with Section 15.1 of the DPA. Section 13 of the DPA applies, save to the extent any limitation of liability is not permitted by US State Privacy Laws.
ADDENDUM 3 — CANADA AND QUÉBEC
This Addendum 3 applies automatically under Section 1.3 of the DPA to Customer Personal Data that is subject to Canadian Privacy Laws (“Canadian Personal Information”). It supplements the DPA and applies only to Canadian Personal Information. Terms defined in the DPA have the same meaning here.
1. Definitions
(a)“PIPEDA” means the Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5, and its regulations.
(b)“Québec Act” means the Act respecting the protection of personal information in the private sector, CQLR c. P-39.1, as amended by An Act to modernize legislative provisions as regards the protection of personal information (Law 25), and its regulations, including the Regulation respecting the anonymization of personal information.
(c)“Canadian Privacy Laws” means all laws of Canada or of any province or territory of Canada relating to privacy or the protection of personal information that apply to the Processing under the DPA, including PIPEDA, the Québec Act, the Personal Information Protection Act, S.A. 2003, c. P-6.5 (“Alberta PIPA”) and the Personal Information Protection Act, S.B.C. 2003, c. 63 (“BC PIPA”), in each case as amended or replaced from time to time.
(d)“Confidentiality Incident” means any access to, use of or communication of Canadian Personal Information that is not authorized by law, any loss of Canadian Personal Information, and any other breach of the protection of Canadian Personal Information, including a breach of security safeguards under PIPEDA and a confidentiality incident under section 3.6 of the Québec Act. A Confidentiality Incident is a Personal Data Breach for the purposes of the DPA.
(e)“Privacy Officer” means the person in charge of the protection of personal information within Customer’s organization, including any person designated under section 3.1 of the Québec Act or Principle 4.1 of Schedule 1 to PIPEDA, designated under Section 8.5 of the DPA.
2. Roles and Accountability
2.1In respect of Canadian Personal Information, Customer is the organization that determines the purposes for which and the means by which the information is Processed and remains accountable for it, including under Principle 4.1.3 of Schedule 1 to PIPEDA, section 5(1) of Alberta PIPA and section 4(2) of BC PIPA. Company Processes Canadian Personal Information solely as Customer’s service provider, for the purpose of carrying out a mandate or performing a contract of enterprise or for services on Customer’s behalf within the meaning of section 18.3 of the Québec Act. Where Customer itself acts for its own clients as described in Section 3.1 of the DPA, Company Processes Canadian Personal Information as Customer’s subcontractor on the same terms.
2.2Customer is responsible for identifying the purposes of collection, for obtaining and managing any consent that Canadian Privacy Laws require, for complying with the openness and transparency requirements of Canadian Privacy Laws, including informing individuals that their information may be communicated outside Québec and Canada, and for the lawfulness of its instructions.
3. Terms Required by Section 18.3 of the Québec Act
3.1The parties intend the DPA and this Addendum to constitute the written contract required by section 18.3 of the Québec Act before Canadian Personal Information is communicated to Company, and by Principle 4.1.3 of Schedule 1 to PIPEDA. Without limiting the DPA, Company shall in respect of Canadian Personal Information:
(a)take the measures described in Section 7 of the DPA and Schedule 2 to ensure the confidentiality of the Canadian Personal Information, and provide a level of protection comparable to that which Canadian Privacy Laws require of Customer;
(b)use the Canadian Personal Information only for the purpose of providing the Services to Customer under the Agreement and Customer’s documented instructions, and not for any purpose of its own;
(c)not retain the Canadian Personal Information after the expiry of the Agreement, other than as permitted by Section 11 of the DPA and Section 5 of this Addendum;
(d)notify the Privacy Officer without delay of any violation or attempted violation by any person of any obligation concerning the confidentiality of the Canadian Personal Information, in accordance with Section 6 of this Addendum; and
(e)allow the Privacy Officer to conduct any verification relating to the confidentiality requirements of this Addendum, in accordance with Section 7 of this Addendum.
3.2Company shall not communicate Canadian Personal Information to any third party except to a Sub-processor in accordance with Section 6 of the DPA, or as required by law in accordance with Section 12.3 of the DPA and Section 8 of this Addendum. Company shall ensure that each Sub-processor that Processes Canadian Personal Information is bound by a written contract containing the terms required by section 18.3 of the Québec Act, in accordance with Section 6.5 of the DPA.
4. Individual Rights
4.1Section 9 of the DPA applies to requests by individuals to exercise their rights under Canadian Privacy Laws, including rights of access, correction or rectification, withdrawal of consent, portability of computerized personal information under section 27 of the Québec Act, cessation of dissemination, re-indexation or de-indexation under section 28.1 of the Québec Act, and the rights concerning decisions based exclusively on automated processing under section 12.1 of the Québec Act. Company shall provide the assistance described in Section 9.3 of the DPA so as to enable Customer to respond within the time limits of Canadian Privacy Laws, including thirty (30) days under PIPEDA and the Québec Act and forty-five (45) days under Alberta PIPA.
4.2Where the Services are used by Customer to render a decision based exclusively on automated processing of Canadian Personal Information, Company shall provide Customer, on request, with the information about the personal information used, the reasons and principal factors and parameters that led to the decision, and the means of correction, that Customer requires to comply with section 12.1 of the Québec Act, subject to reasonable confidentiality controls and without disclosing trade secrets.
5. Anonymization and De-identification
5.1Company shall not anonymize Canadian Personal Information except (a) on Customer’s documented instruction, or (b) as provided in Section 5.2, and in either case only in accordance with section 23 of the Québec Act and the Regulation respecting the anonymization of personal information, including the requirement that the anonymization be carried out according to generally accepted best practices and the criteria and terms set out in that Regulation, and shall not attempt to identify an individual from information that has been anonymized or de-identified.
5.2Customer hereby instructs Company to anonymize Canadian Personal Information for the purpose of creating Company Usage Data under Section 4.3 of the DPA, and authorizes Company to use Canadian Personal Information, once de-identified within the meaning of section 12 of the Québec Act, for the purposes of study, research or the production of statistics concerning the operation, performance and security of the Services, provided that Company (a) complies with Section 4.4 of the DPA and with Section 5.1 of this Addendum, (b) conducts and documents the anonymization process and its periodic re-assessment as the Regulation requires, and (c) provides Customer on request with a description of the anonymization process sufficient for Customer to record it in its register of anonymization.
6. Confidentiality Incidents
6.1Section 8 of the DPA applies to Confidentiality Incidents. In addition, Company shall notify the Privacy Officer without delay after becoming aware of a Confidentiality Incident and of any violation or attempted violation of the confidentiality of Canadian Personal Information, and the notice shall include the sensitivity of the information concerned and Company’s assessment of the risk of serious injury to the individuals concerned.
6.2Company shall provide the cooperation and assistance reasonably necessary for Customer to comply with its obligations in respect of the Confidentiality Incident, including any obligation to notify the Office of the Privacy Commissioner of Canada, the Commission d’accès à l’information du Québec, any provincial privacy commissioner and the individuals concerned, and to maintain a register of Confidentiality Incidents under section 3.8 of the Québec Act and section 10.3 of PIPEDA. The register maintained by Company under Section 8.4 of the DPA shall be retained for at least five (5) years after the date Company becomes aware of each Confidentiality Incident.
7. Verification
7.1Company shall allow Customer and its Privacy Officer to conduct any verification relating to the confidentiality requirements of this Addendum, as required by section 18.3 of the Québec Act. The parties agree that verifications shall, so far as the Québec Act permits, be conducted in the manner and on the conditions set out in Section 10 of the DPA, and that the reports and certifications made available under Section 10.2 of the DPA are the primary means of verification. Nothing in Section 10 of the DPA limits a verification that Customer is entitled to conduct under section 18.3 of the Québec Act and that cannot be limited by contract.
7.2Section 9.4 of the DPA applies to any privacy impact assessment Customer is required to conduct under Canadian Privacy Laws, including under sections 3.3 and 17 of the Québec Act, and to any inquiry, investigation or consultation involving the Office of the Privacy Commissioner of Canada, the Commission d’accès à l’information du Québec or a provincial privacy commissioner.
8. Communication of Personal Information Outside Québec and Canada
8.1Customer acknowledges that Company and its Sub-processors Process Canadian Personal Information outside Québec and outside Canada, in the jurisdictions and for the purposes described in Schedule 1 to the DPA and the Sub-processor List.
8.2The parties intend the DPA, this Addendum and Schedule A to this Addendum to constitute the written agreement required by section 17 of the Québec Act in respect of the communication of Canadian Personal Information outside Québec. Company has provided in Schedule A the information regarding the legal framework of the destination jurisdictions that Customer requires to complete its privacy impact assessment under section 17, represents that Schedule A is accurate as at the effective date of the DPA, and shall provide such further information as Customer reasonably requests for that purpose. Where Customer’s assessment identifies risks that require additional terms, the parties shall record them in writing.
8.3Company shall provide Customer with the information Customer reasonably requires to comply with its openness obligations in respect of foreign Processing, including under Principle 4.8 of Schedule 1 to PIPEDA and sections 6(2) and 13.1 of Alberta PIPA, being the countries outside Canada in which Canadian Personal Information may be Processed, the purposes for which service providers outside Canada are authorized to Process it, and the fact that it may be accessible to the courts, law enforcement and national security authorities of those jurisdictions.
8.4Section 12.3 of the DPA applies to any request from a government, law enforcement, regulatory or judicial authority outside Canada for the disclosure of Canadian Personal Information. Before permitting access to Canadian Personal Information on a continuing basis from any jurisdiction not described in Schedule 1 to the DPA, Company shall update Schedule A to describe the legal framework of that jurisdiction and give Customer notice under Section 12.1 of the DPA.
9. Retention and Destruction
9.1Section 11 of the DPA applies to the return and destruction of Canadian Personal Information. For the purposes of section 23 of the Québec Act, Company shall destroy Canadian Personal Information when the purposes for which it was collected or used are accomplished, subject to any retention period required by law, or shall anonymize it in accordance with Section 5.
10. Precedence and Liability
10.1In respect of Canadian Personal Information, this Addendum 3 prevails over the body of the DPA and the Agreement as to the requirements of Canadian Privacy Laws, in accordance with Section 15.1 of the DPA. Section 13 of the DPA applies, save to the extent any limitation of liability is not permitted by Canadian Privacy Laws. This Addendum 3 remains in force for so long as Company or a Sub-processor retains any Canadian Personal Information.
SCHEDULE A TO ADDENDUM 3 — LEGAL FRAMEWORK OF DESTINATION JURISDICTIONS
This Schedule A is provided to support Customer’s privacy impact assessment under section 17 of the Québec Act, Customer’s notification obligations under sections 6(2) and 13.1 of Alberta PIPA, and, where Addendum 1 applies, Customer’s transfer impact assessment under Section 6.6 of Addendum 1. Company shall update it in accordance with Section 8.4 of Addendum 3 and shall notify Customer of any material change. The description of the legal framework in this Schedule A relates to the United States, where Customer Personal Data is stored and Processed; incidental access by Company personnel while travelling under Section 12.1 of the DPA does not involve storage or Processing of Customer Personal Data in the country concerned. A current version and Company’s transparency report are maintained at https://www.splitsecure.com/privacy.
Destination jurisdiction. United States of America. Canadian Personal Information is Processed and stored in Amazon Web Services facilities in the United States and may be accessed remotely by Company personnel from the jurisdictions stated in Schedule 1 to the DPA. Sub-processors Process Canadian Personal Information in the jurisdictions stated in the Sub-processor List.
General legal framework. The United States has no single comprehensive federal privacy statute. Protection derives from sectoral federal laws, comprehensive privacy legislation in a growing number of states, and enforcement by the Federal Trade Commission under section 5 of the FTC Act against unfair or deceptive practices, which makes Company’s public and contractual privacy commitments enforceable against it.
Public-authority access. US law enforcement may compel disclosure of stored data under the Electronic Communications Privacy Act, generally requiring a judicial warrant for content, and the CLOUD Act extends that reach to data in a US provider’s possession, custody or control wherever located. National security authorities may compel disclosure under section 702 of the Foreign Intelligence Surveillance Act, which is directed at non-US persons reasonably believed to be located outside the United States and applies to electronic communication service providers, and may collect data in transit outside the United States under Executive Order 12333. National security letters under 18 U.S.C. § 2709 may compel non-content subscriber information and may carry non-disclosure obligations. Executive Order 14086 imposes necessity and proportionality limits on US signals-intelligence activities and establishes an independent Data Protection Review Court.
Remedies for individuals. Judicial remedies available to individuals who are not US persons are limited. The Privacy Act of 1974 extends to US citizens and lawful permanent residents. The Judicial Redress Act of 2015 and the redress mechanism established under Executive Order 14086 are available only to residents of countries designated by the US Attorney General; as at the date of this Schedule, Canada is not among the countries so designated. Standing requirements established in Clapper v. Amnesty International USA and TransUnion LLC v. Ramirez present a practical barrier to challenges to surveillance authorities.
Mitigating measures. Company assesses the residual risk to Canadian Personal Information as low for the following reasons. Cryptographic key material and the most sensitive data fields are encrypted such that Company cannot produce them in plaintext in response to legal process: enclave-held data decrypts only under a cryptographically attested enclave image, and identity-provider secrets and OAuth tokens are encrypted at the field level. The Canadian Personal Information Processed by the Services consists principally of business contact and authentication data and records of administrative actions, which are unlikely to be of intelligence interest. Company has not to date received any national security order or request for Canadian Personal Information. Company’s policy, set out in Section 12.3 of the DPA, is to require valid legal process, to challenge orders that are overbroad or unlawful, to disclose only the minimum required and to notify Customer unless legally prohibited.