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

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.

2. Definitions

3. Roles of the Parties and Instructions

4. Company Account Data and Company Usage Data

5. Confidentiality and Personnel

6. Sub-processors

7. Security

8. Personal Data Breach

9. Assistance with Individual Requests and Assessments

10. Records, Audit and Demonstrating Compliance

11. Retention, Return and Deletion

12. Processing Locations, Transfers and Government Requests

13. Liability

14. Term, Termination and Survival

15. Order of Precedence and Interpretation

16. Acceptance, Effectiveness and Amendment

17. General

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.

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

2. Roles under European Data Protection Laws

3. Article 28 Terms

4. Company Account Data and Company Usage Data

5. Sub-processors

6. Restricted Transfers

7. Supervisory Authority

8. Liability

9. Termination and Precedence

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

2. Roles

3. Service Provider and Contractor Obligations

4. Consumer Rights

5. Assessments and Automated Decision-Making

6. Demonstrating Compliance

7. Security Breach

8. Deletion

9. Precedence and Liability

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

2. Roles and Accountability

3. Terms Required by Section 18.3 of the Québec Act

4. Individual Rights

5. Anonymization and De-identification

6. Confidentiality Incidents

7. Verification

8. Communication of Personal Information Outside Québec and Canada

9. Retention and Destruction

10. Precedence and Liability

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.