Snapshot 123366
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Data Processing Addendum Reviewed by ContraForce team · Effective and last updated August 2026 Effective and last updated August 2026 This Data Processing Addendum (“DPA”) forms part of, and is incorporated by reference into, the ContraForce Cloud Services Agreement available at https://www.contraforce.com/cloud-services-agreement, or such other written or electronic customer agreement, between ContraForce Group, Inc., a Delaware corporation, d/b/a ContraForce (“ContraForce,” “Provider,” “we,” or “us”) and the customer entity that agrees to those terms (“Customer” or “you”) governing Customer’s access to and use of the Cloud Services (the “Agreement”). This DPA applies to the extent ContraForce Processes Customer Personal Data on Customer’s behalf in connection with the Cloud Services. Where ContraForce acts as a Controller in its own right, that Processing is described in the ContraForce Privacy Policy available at https://www.contraforce.com/privacy-policy (the “Privacy Policy”) and is governed by Section 2.3 of this DPA rather than by Sections 3 through 14. This DPA is published at https://www.contraforce.com/dpa. Superseded editions are archived and remain available at that address. 1. Definitions and Interpretation 1.1 Capitalized terms used but not defined in this DPA have the meanings given in the Agreement. 1.2 Where this DPA and the Privacy Policy use the same term, that term carries the same meaning in both documents. The Privacy Policy describes ContraForce’s Processing as a Controller. This DPA governs ContraForce’s Processing as a Processor or Sub-processor. The two documents are intended to be read together and neither limits the other except as expressly provided in Section 17.3. 1.3 In this DPA: “Account Data” means Personal Data relating to Customer’s relationship with ContraForce, including the names and business contact information of Authorized Users and of individuals authorized to administer Customer’s account, billing and payment contact information, and support and communication records. “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 interests of that entity. “Applicable Data Protection Law” means all laws and regulations applicable to a party’s Processing of Personal Data under this DPA, including the EU GDPR, the UK GDPR, the Swiss FADP, and the US State Privacy Laws, in each case as amended, replaced, or superseded from time to time. “Controller,” “Processor,” “Data Subject,” “Personal Data,” “Personal Data Breach,” “Process” (and “Processing”), “Special Category Data,” and “Supervisory Authority” have the meanings given in the EU GDPR. Where the US State Privacy Laws apply, the corresponding terms in those laws (including “business,” “service provider,” “contractor,” “processor,” “consumer,” “personal information,” and “sensitive personal information”) carry their statutory meanings and are addressed in Section 14. “Customer Personal Data” means Personal Data contained within Customer Data, including End Customer Data, that ContraForce Processes on behalf of Customer under the Agreement. Customer Personal Data does not include Account Data, Usage Data, or Aggregated Statistics. “Deployment Model” means either the BYOC Model or the ContraForce Cloud Model, as described in Section 4 and as identified in the applicable Order. “End Customer” means a customer or client of Customer to whom Customer provides managed security or other services using or supported by the Cloud Services. “EU GDPR” means Regulation (EU) 2016/679. “EU SCCs” means the standard contractual clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021. “Restricted Transfer” means a transfer of Customer Personal Data from the European Economic Area, the United Kingdom, or Switzerland to a country that has not been the subject of an adequacy decision applicable to that transfer. “Security Telemetry” means logs, alerts, incidents, signals, detections, entity records, configuration data, and related records generated by, ingested from, or produced in the monitoring of Customer’s or an End Customer’s information technology environment. “Sub-processor” means any third party engaged by ContraForce to Process Customer Personal Data. “Swiss FADP” means the Swiss Federal Act on Data Protection of 25 September 2020, as amended. “UK Addendum” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, version B1.0. “UK GDPR” has the meaning given in section 3(10) of the Data Protection Act 2018. “Usage Data” means Personal Data relating to the operation, performance, and use of the Cloud Services, including access logs, feature usage records, and diagnostic data, in each case relating to Authorized Users. “US State Privacy Laws” means the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act, and each other statute of general application enacted by a State of the United States that governs the processing of personal data and is in effect at the relevant time, in each case together with any implementing regulations. 1.4 References to Sections and Annexes are to Sections and Annexes of this DPA. The Annexes form part of this DPA. 2. Roles of the Parties 2.1 ContraForce as Processor. In respect of Customer Personal Data, Customer acts as Controller, or as Processor on behalf of a third-party Controller, and ContraForce acts as Processor or, where Customer acts as Processor, as Sub-processor. ContraForce Processes Customer Personal Data only as described in this DPA and Annex 1. 2.2 Managed service chain. Customer may use the Cloud Services to deliver services to End Customers. Where an End Customer is the Controller of Customer Personal Data and Customer acts as that End Customer’s Processor, ContraForce acts as a Sub-processor. Customer represents and warrants that it has, and will maintain throughout the term, all authority, authorizations, and instructions necessary from each relevant End Customer to appoint ContraForce as a Sub-processor, to give the instructions set out in this DPA on that End Customer’s behalf, and to consent to the Sub-processors and transfers contemplated by this DPA. ContraForce owes the obligations in this DPA to Customer alone. ContraForce is not required to enter into a separate agreement with, accept instructions from, or respond directly to any End Customer, and will refer any such approach to Customer. 2.3 ContraForce as Controller. ContraForce acts as a Controller in respect of Account Data and Usage Data. ContraForce Processes that data for account administration, provisioning, billing and collections, support, service communications, securing and monitoring the integrity of the Cloud Services, detecting and preventing fraud and abuse, improving and developing the Cloud Services, and complying with legal obligations. That Processing is described in the Privacy Policy, and Sections 3 through 14 of this DPA do not apply to it. ContraForce will Process Account Data and Usage Data in accordance with Applicable Data Protection Law and the Privacy Policy. 2.4 Aggregated Statistics. As set out in the Agreement, including Section 2(e) of the ContraForce Cloud Services Agreement, ContraForce may compile Aggregated Statistics. Before any Customer Personal Data is incorporated into Aggregated Statistics, ContraForce will apply de-identification and aggregation such that the resulting data cannot reasonably be used to identify any Data Subject, Customer, or End Customer. ContraForce will not attempt to reidentify such data, will maintain the de-identification, and will contractually obligate any recipient to the same restrictions. Aggregated Statistics so processed are not Customer Personal Data. 2.5 No sale, share, or secondary use. ContraForce will not sell or share Customer Personal Data, will not Process it for cross-context behavioral advertising or targeted advertising, will not Process it for any purpose other than the purposes set out in Annex 1, and will not retain, use, or disclose it outside the direct business relationship between the parties, except as permitted by Applicable Data Protection Law. 3. Processing Instructions 3.1 Documented instructions. ContraForce will Process Customer Personal Data only on Customer’s documented instructions. The following constitute Customer’s complete documented instructions: (a) the Agreement, including each Order; (b) this DPA, including Annex 1; (c) Customer’s configuration of the Cloud Services, including connectors, tenant onboarding, Gamebooks and other standard operating procedures, response policies, agent scope, and retention settings; and (d) any further written instructions agreed by the parties. 3.2 Configuration as instruction. A configuration change, provisioning action, or response action initiated through Customer’s authenticated account, or through an automation Customer has enabled, is Customer’s documented instruction to Process accordingly. No separate written notice is required. 3.3 Legally required Processing. ContraForce may Process Customer Personal Data where required by law to which ContraForce is subject. In that case ContraForce will inform Customer of the legal requirement before Processing, unless the law prohibits that notification on important grounds of public interest. 3.4 Unlawful instructions. ContraForce will inform Customer if, in ContraForce’s opinion, an instruction infringes Applicable Data Protection Law. ContraForce may suspend performance of the affected instruction until it is amended, confirmed, or withdrawn. 3.5 Instructions beyond scope. Where Customer instructs Processing outside the scope described in Annex 1, the parties will discuss the instruction in good faith. ContraForce may condition performance on agreement of reasonable additional fees and, where required, amended terms. 4. Deployment Models, Data Location, and Retention 4.1 BYOC Model. Where Customer deploys the Cloud Services into infrastructure operated under Customer’s own cloud subscription (the “BYOC Model”), Security Telemetry and the Customer Personal Data it contains reside in and are Processed within Customer’s own tenant and infrastructure, under Customer’s control and subject to Customer’s own retention and residency configuration. ContraForce does not create or retain a persistent copy of that Security Telemetry outside Customer’s tenant, other than the operational metadata identified in Annex 1. 4.2 ContraForce Cloud Model. Where Customer subscribes to a ContraForce-hosted offering (the “ContraForce Cloud Model”), ContraForce hosts the Cloud Services on cloud infrastructure operated by ContraForce or its Sub-processors. The hosting region is as set out in the applicable Order or as configured by Customer where the Cloud Services offer region selection. 4.3 Retention. ContraForce retains Customer Personal Data only for as long as necessary to provide the Cloud Services, in accordance with the retention settings Customer configures and the retention periods stated in Annex 1, and thereafter in accordance with Section 11. 4.4 Minimization. ContraForce will Process the minimum Customer Personal Data necessary to provide the Cloud Services and to perform its obligations under the Agreement. 5. Confidentiality ContraForce will ensure that each person it authorizes to Process Customer Personal Data is subject to a binding written obligation of confidentiality or an appropriate statutory or professional duty of confidentiality, has received appropriate training in the protection of Personal Data, and Processes Customer Personal Data only as necessary to perform ContraForce’s obligations under the Agreement. 6. Security 6.1 Measures. ContraForce will implement and maintain the technical and organizational measures set out in Annex 2, designed to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, the nature, scope, context, and purposes of Processing, and the risk to Data Subjects. 6.2 No material reduction. ContraForce may update the measures in Annex 2 provided that the updates do not materially reduce the overall level of security of the Cloud Services. 6.3 Attestation. ContraForce maintains a SOC 2 Type II examination covering the Cloud Services and will make the current report available to Customer under Section 12. 6.4 Customer responsibilities. Customer is responsible for its own configuration of the Cloud Services, including access controls, role assignments, retention settings, connector scope, and the security of its own systems and credentials, and for assessing whether the measures in Annex 2 meet Customer’s requirements and those of its End Customers. 7. Sub-processors 7.1 General authorization. Customer grants ContraForce general authorization to engage Sub-processors to Process Customer Personal Data. The current list of Sub-processors engaged by ContraForce is maintained at https://trust.contraforce.com/subprocessors (the “Sub-processor List”). The Sub-processor List is incorporated into this DPA by reference and completes Annex 3. 7.2 Notice of changes. ContraForce will give Customer at least thirty (30) days’ notice before a new Sub-processor begins Processing Customer Personal Data, by updating the Sub-processor List and issuing a notification through the update subscription available at that address. Customer is responsible for subscribing to those notifications. Where a change is required urgently to maintain the security or continuity of the Cloud Services, ContraForce will give notice as soon as reasonably practicable. 7.3 Objection. Customer may object to a new Sub-processor on reasonable data protection grounds by written notice within the notice period. The parties will discuss the objection in good faith. If ContraForce is unable to make a change that reasonably addresses the objection within thirty (30) days, Customer may terminate the affected Cloud Services on written notice and will receive a pro-rata refund of prepaid fees for the terminated Cloud Services covering the period after the effective date of termination. This is Customer’s sole remedy for an unresolved objection. 7.4 Flow-down and liability. ContraForce will impose on each Sub-processor data protection obligations no less protective than those in this DPA and will remain fully liable to Customer for the performance of each Sub-processor’s obligations. 8. Data Subject Requests 8.1 Self-service. The Cloud Services provide functionality that enables Customer to access, correct, delete, restrict, and export Customer Personal Data. Customer will use that functionality to respond to Data Subject requests where it is sufficient to do so. 8.2 Referral. If ContraForce receives a request from a Data Subject relating to Customer Personal Data, ContraForce will not respond to the substance of the request except to confirm that the request should be directed to Customer, and will notify Customer promptly, unless prohibited by law. 8.3 Assistance. Taking into account the nature of the Processing, ContraForce will assist Customer by appropriate technical and organizational measures, insofar as possible, in fulfilling Customer’s obligations to respond to Data Subject requests. Where the functionality in Section 8.1 is not sufficient and assistance requires material ContraForce effort, ContraForce may charge a reasonable fee, notified in advance. 9. Assistance with Compliance Obligations Taking into account the nature of Processing and the information available to ContraForce, ContraForce will provide reasonable assistance to Customer in relation to Customer’s obligations concerning security of Processing, notification of Personal Data Breaches to Supervisory Authorities and Data Subjects, data protection impact assessments, and prior consultation with Supervisory Authorities. Where assistance requires material ContraForce effort beyond providing existing documentation and standard responses, ContraForce may charge a reasonable fee, notified in advance. 10. Personal Data Breach 10.1 Notification. ContraForce will notify Customer without undue delay, and in any event within seventy-two (72) hours, after ContraForce becomes aware of a Personal Data Breach affecting Customer Personal Data. 10.2 Content. The notification will describe, to the extent known at the time and supplemented as further information becomes available: the nature of the Personal Data Breach; the categories and approximate number of Data Subjects and records concerned; the likely consequences; the measures taken or proposed to address the Personal Data Breach and mitigate its effects; and a contact point for further information. 10.3 Cooperation. ContraForce will take reasonable steps to contain, investigate, and mitigate the Personal Data Breach, will preserve relevant records, and will cooperate with Customer and provide the information Customer reasonably requires to meet its own notification obligations. 10.4 No admission. ContraForce’s notification or response under this Section is not an acknowledgement of fault or liability. 10.5 External communications. ContraForce will not notify any third party of a Personal Data Breach affecting Customer Personal Data identifying Customer without Customer’s prior consent, except where required by law or where notification is directed to a Supervisory Authority or law enforcement. 11. Deletion and Return 11.1 During the term. Customer may access and export Customer Personal Data at any time during the term using the functionality of the Cloud Services. 11.2 On termination. Following expiry or termination of the Agreement, Customer may export Customer Personal Data for thirty (30) days. After that period, ContraForce will delete Customer Personal Data in its possession or control within a further thirty (30) days, unless required by law to retain it. At Customer’s written request made during the export period, ContraForce will instead return Customer Personal Data in a commonly used format before deleting it. 11.3 Backups. Customer Personal Data contained in routine backup media is deleted in accordance with ContraForce’s backup cycle and is protected from further active Processing until deleted. 11.4 BYOC Model. Under the BYOC Model, Customer Personal Data residing in Customer’s own tenant remains under Customer’s control and is not deleted by ContraForce. Section 11.2 applies only to operational metadata held by ContraForce. 11.5 Legally required retention. Where ContraForce is required by law to retain Customer Personal Data, ContraForce will retain it only for the period and purpose required, will continue to protect it in accordance with this DPA, and will put it beyond further active use. 12. Audits and Information 12.1 Documentation first. ContraForce will make available to Customer the information necessary to demonstrate compliance with this DPA, including its current SOC 2 Type II report, a summary of penetration test results, and responses to a reasonable security questionnaire, in each case no more than once in any twelve (12) month period and subject to confidentiality obligations. 12.2 Audit. Where the information provided under Section 12.1 is not sufficient to demonstrate compliance and an audit is required by Applicable Data Protection Law, Customer or an independent auditor appointed by Customer and not reasonably objected to by ContraForce may conduct an audit of ContraForce’s Processing of Customer Personal Data, on at least thirty (30) days’ written notice, no more than once in any twelve (12) month period, during normal business hours, for a scope and duration agreed in advance, and subject to the auditor executing a confidentiality agreement. Customer bears its own and ContraForce’s reasonable costs of the audit. 12.3 Limits. An audit will not extend to Personal Data or Confidential Information of any other ContraForce customer, to any component of ContraForce’s multi-tenant infrastructure where access would compromise the security or confidentiality of another customer’s data, or to ContraForce’s internal pricing, cost, or commercial information. ContraForce may satisfy an audit request in whole or in part by procuring a report from a qualified independent auditor. 12.4 Regulators. Nothing in this Section limits any audit or inspection right of a Supervisory Authority exercised under Applicable Data Protection Law. 13. International Transfers 13.1 Certification and authorization. ContraForce is certified under the EU-U.S. Data Privacy Framework and the UK Extension to the EU-U.S. Data Privacy Framework, and adheres to the applicable Data Privacy Framework Principles in respect of Personal Data received from the European Economic Area and the United Kingdom. ContraForce remains liable under those Principles for the onward transfer of such Personal Data to its Sub-processors. Customer authorizes ContraForce to transfer Customer Personal Data to the United States and to any other country in which ContraForce or a Sub-processor Processes Customer Personal Data as necessary to provide the Cloud Services, subject to this Section. 13.2 Transfer mechanism. In respect of any Restricted Transfer, the parties agree that the following applies, in the order stated, to the extent valid and applicable to the transfer: (a) in respect of transfers from the European Economic Area and from the United Kingdom, the EU-U.S. Data Privacy Framework and the UK Extension to the EU-U.S. Data Privacy Framework, for so long as ContraForce maintains an active certification on the Data Privacy Framework List and the relevant framework remains recognized as providing an adequate level of protection for the transfer; (b) where the framework in clause (a) does not apply to the transfer, ceases to be available, or is invalidated, the EU SCCs, which are incorporated into this DPA by reference and completed as set out in Annex 4; (c) in respect of transfers subject to the UK GDPR, the EU SCCs as amended by the UK Addendum, completed as set out in Annex 5; and (d) in respect of transfers subject to the Swiss FADP, the EU SCCs with the amendments in Section 13.4. ContraForce does not currently certify under the Swiss-U.S. Data Privacy Framework, and transfers subject to the Swiss FADP are made under the EU SCCs. 13.3 EU SCC elections. Where the EU SCCs apply: Module Two (Controller to Processor) applies where Customer is a Controller of the transferred Customer Personal Data, and Module Three (Processor to Processor) applies where Customer is a Processor. The optional docking clause in Clause 7 applies. Under Clause 9, Option 2 (general written authorization) applies, with the notice period in Section 7.2. The optional language in Clause 11(a) does not apply. The governing law under Clause 17 is the law of Ireland. The forum under Clause 18(b) is the courts of Ireland. Annex I, Annex II, and Annex III of the EU SCCs are completed by Annex 1, Annex 2, and Annex 3 of this DPA respectively. 13.4 Swiss amendments. Where the Swiss FADP applies, references in the EU SCCs to the GDPR are to the Swiss FADP, the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner, the term “member state” does not operate to prevent Data Subjects in Switzerland from bringing proceedings in Switzerland, and the EU SCCs also protect the data of legal entities until the Swiss FADP is amended to remove that protection. 13.5 Conflict. If the EU SCCs or the UK Addendum apply and conflict with any other provision of this DPA or the Agreement, the EU SCCs or the UK Addendum prevail in respect of the Restricted Transfer. 14. US State Privacy Laws 14.1 Roles. Where the US State Privacy Laws apply to Customer Personal Data, Customer is the business or controller and ContraForce is the service provider, contractor, or processor, as those terms are defined in the applicable statute. 14.2 Restrictions. ContraForce will not: (a) sell or share Customer Personal Data; (b) retain, use, or disclose Customer Personal Data for any purpose other than performing the services specified in the Agreement and Annex 1, or as otherwise permitted by the US State Privacy Laws; (c) retain, use, or disclose Customer Personal Data outside the direct business relationship between ContraForce and Customer; or (d) combine Customer Personal Data with personal information ContraForce receives from or on behalf of another person, or collects from its own interaction with a consumer, except as permitted by the US State Privacy Laws. 14.3 Certification. ContraForce certifies that it understands the restrictions in Section 14.2 and will comply with them. 14.4 Compliance and remediation. ContraForce will comply with the obligations applicable to it under the US State Privacy Laws and provide the level of privacy protection those laws require. Customer may take reasonable and appropriate steps to ensure that ContraForce uses Customer Personal Data consistently with Customer’s obligations, and, on notice, to stop and remediate unauthorized use. ContraForce will notify Customer promptly if it determines that it can no longer meet its obligations under the US State Privacy Laws. 14.5 Deidentified data. Where ContraForce Processes deidentified data, ContraForce will take reasonable measures to ensure the data cannot be associated with a consumer or household, will publicly commit to maintaining the data in deidentified form and not to attempt reidentification, and will contractually obligate recipients to the same. 15. Customer Obligations and Warranties 15.1 Customer warrants that: (a) it has established and will maintain a valid legal basis for the Processing of Customer Personal Data contemplated by the Agreement; (b) it has provided all notices and obtained all consents, authorizations, and permissions required under Applicable Data Protection Law to enable ContraForce and its Sub-processors to Process Customer Personal Data as contemplated by this DPA, including from End Customers and their personnel and users; and (c) its instructions to ContraForce comply with Applicable Data Protection Law. 15.2 Customer acknowledges that the Cloud Services are designed to Process Security Telemetry, that Personal Data appears in Security Telemetry incidentally and is not selected or structured by ContraForce, and that ContraForce has no practical means of determining in advance what categories of Personal Data a given environment will generate. 15.3 Customer will not intentionally submit to the Cloud Services, and will not configure a connector or data source with the primary purpose of transmitting, Special Category Data, protected health information subject to the Health Insurance Portability and Accountability Act, payment card data subject to the Payment Card Industry Data Security Standard, government-issued identification numbers, or biometric or genetic data, except as agreed in writing in an Order or a separate instrument executed by both parties. This Section does not apply to such data appearing incidentally within Security Telemetry. 16. Liability 16.1 Each party’s liability arising out of or related to this DPA is subject to the exclusions and limitations of liability set out in the Agreement, and any reference in the Agreement to the liability of a party means the aggregate liability of that party under the Agreement and this DPA together. 16.2 Section 16.1 does not limit any liability of either party to a Data Subject under the third-party beneficiary provisions of the EU SCCs or the UK Addendum, and does not limit either party’s liability for its own breach of Applicable Data Protection Law where such limitation is not permitted by that law. 17. General 17.1 Term. This DPA takes effect on the effective date of the Agreement, or on the date Customer accepts it if later, and continues until ContraForce has ceased all Processing of Customer Personal Data. Provisions that by their nature should survive, including Sections 5, 11, 12, 13, 16, and 17, survive termination or expiry of the Agreement. 17.2 Updates. ContraForce may update this DPA to reflect changes in Applicable Data Protection Law, transfer mechanisms, Sub-processors, or the Cloud Services. ContraForce will give Customer at least thirty (30) days’ notice of any update that materially reduces ContraForce’s obligations or Customer’s rights, and Customer may object in writing within that period. If the parties do not resolve the objection in good faith within thirty (30) days, Customer may terminate the affected Cloud Services without further cost or penalty and will receive a pro-rata refund of prepaid fees covering the period after the effective date of termination. Updates required to comply with Applicable Data Protection Law take effect on notice. Where Customer has executed a countersigned copy of this DPA, an update takes effect only on the parties’ written agreement, except for updates to Annex 3 and updates required by Applicable Data Protection Law. 17.3 Precedence. In the event of conflict, the following order applies: (a) the EU SCCs or the UK Addendum, in respect of a Restricted Transfer; (b) this DPA, in respect of ContraForce’s Processing of Customer Personal Data as Processor or Sub-processor; (c) the Agreement; and (d) the Privacy Policy. The Privacy Policy governs ContraForce’s Processing as a Controller under Section 2.3, and this DPA does not limit or modify it in that respect. 17.4 Governing law. This DPA is governed by the law governing the Agreement, except that the EU SCCs and the UK Addendum are governed as provided in those instruments. 17.5 Execution. This DPA is incorporated into the Agreement by reference and no signature is required for it to take effect. Where Customer’s internal requirements call for an executed instrument, ContraForce will provide a signature page on request, and the copy executed by both parties governs as between those parties. 17.6 Third parties. Except as expressly provided in the EU SCCs and the UK Addendum, this DPA does not confer any right on any person who is not a party to it, including any End Customer or Authorized User. 17.7 Severability. If any provision of this DPA is held invalid or unenforceable, the remaining provisions remain in full force and the invalid provision is modified to the minimum extent necessary to make it valid and enforceable. 17.8 Contact. Data protection enquiries under this DPA may be sent to privacy@contraforce.com or to ContraForce Group, Inc., 5 Cowboys Way, Suite 300, Frisco, Texas 75034, United States. Annex 1 — Details of Processing This Annex completes Annex I of the EU SCCs. Part A — Parties Data exporter. Customer, as identified in the Agreement. Role: Controller, or Processor on behalf of one or more End Customer Controllers. Activities relevant to the transfer: procurement and use of the Cloud Services for security monitoring, investigation, and response, including delivery of managed security services to End Customers. Contact details and signature: as set out in the Agreement or in an executed signature page. Data importer. ContraForce Group, Inc., a Delaware corporation, d/b/a ContraForce, 5 Cowboys Way, Suite 300, Frisco, Texas 75034, United States. Contact: privacy@contraforce.com. Role: Processor, or Sub-processor where Customer acts as Processor. Activities relevant to the transfer: provision of the Cloud Services as described below. Part B — Description of Processing Categories of Data Subjects. Authorized Users and other personnel, contractors, and representatives of Customer. Personnel, contractors, and representatives of End Customers. Users of, and individuals whose activity is recorded in, the information technology environments monitored using the Cloud Services. Individuals identified in Security Telemetry as the subject of, or a participant in, a security event, alert, or investigation, including external individuals such as senders of inbound email. Categories of Personal Data. Identifiers and account data, including names, usernames, user principal names, business email addresses, business telephone numbers, employee and account identifiers, and directory group membership. Device and network data, including IP addresses, device names and identifiers, MAC addresses, hostnames, operating system and configuration details, and geolocation inferred from IP address. Authentication and access data, including sign-in records, authentication method, session data, multi-factor authentication events, and access and permission records. Activity data contained in Security Telemetry, including process execution records, file and object names and paths, command line data, URLs and domains accessed, email metadata such as sender, recipient, subject line, and attachment names, and cloud and application audit records. Investigation records, including alert and incident records, case notes, analyst and agent actions, dispositions, and response actions taken. Free-text content, to the extent an individual’s Personal Data appears within log content, alert payloads, ticket notes, or artifacts captured during an investigation. Special Category Data. Not intentionally Processed. Special Category Data may appear incidentally within Security Telemetry, including within file names, URLs, email subject lines, or free-text content, where the monitored environment generates it. ContraForce does not select, structure, index, or Process such data for any purpose beyond the provision of the Cloud Services. Restrictions on Customer’s intentional submission of such data are set out in Section 15.3. Applicable additional safeguards: the measures in Annex 2, role-based access control limiting access to Authorized Persons with a need to know, encryption in transit and at rest, and retention limits. Frequency of transfer. Continuous, for the duration of the Agreement. Nature and purpose of Processing. Provision of the Cloud Services, being an AI-assisted security delivery platform. Specifically: ingestion and normalization of Security Telemetry from Customer-connected data sources; automated and agent-assisted triage, enrichment, correlation, and investigation of security alerts and incidents; execution of response and remediation actions configured by Customer; case management, reporting, and analytics on security operations; provision of support, troubleshooting, and service maintenance; and securing the Cloud Services and preventing fraud and abuse. Duration of Processing. The term of the Agreement, plus the retention and deletion periods in Section 11. Retention. Under the BYOC Model, Security Telemetry is retained in Customer’s own tenant subject to Customer’s configuration, and ContraForce retains only the operational metadata described below. Under the ContraForce Cloud Model, Customer Personal Data is retained in accordance with the retention period configured by Customer in the Cloud Services or, where Customer has made no such configuration, the retention period stated in the applicable Order, and thereafter in accordance with Section 11. Operational metadata retained by ContraForce under both Deployment Models. Workspace, tenant, and connector identifiers and configuration; investigation and case records including analyst and agent actions and dispositions; alert and incident identifiers, classifications, timestamps, and outcome records; audit logs of Authorized User activity within the Platform; and service performance and usage records. This metadata may contain identifiers of Authorized Users and of entities named in an investigation. Sub-processor transfers. Nature, subject matter, duration, and purpose as set out above and in Annex 3. Competent Supervisory Authority. Where the EU SCCs apply, the competent Supervisory Authority is determined in accordance with Clause 13 of the EU SCCs: the Supervisory Authority of the EU member state in which the data exporter is established or, where the data exporter is not established in the EU, the Supervisory Authority of the member state in which the data exporter’s Article 27 representative is established or in which the Data Subjects whose Personal Data is transferred are located. Where the UK Addendum applies, the competent authority is the UK Information Commissioner. Where the Swiss FADP applies, the competent authority is the Swiss Federal Data Protection and Information Commissioner. Annex 2 — Technical and Organizational Measures This Annex completes Annex II of the EU SCCs. ContraForce maintains an information security program aligned to recognized industry standards, including ISO/IEC 27001, ISO/IEC 27002, and the NIST Cybersecurity Framework, and maintains a SOC 2 Type II examination covering the Cloud Services. The program includes the following measures. Governance and policy. Documented information security policies reviewed at least annually and approved by management. Assigned ownership of the security program. Risk assessments conducted at least annually. Security awareness training on hire and at least annually thereafter. Background screening of personnel to the extent permitted by applicable law. Documented onboarding and offboarding procedures including timely revocation of access on termination. Access control. Role-based access control applied on the principle of least privilege. Unique named accounts, with shared and generic accounts prohibited for administrative access. Multi-factor authentication required for administrative access to production systems. Privileged access restricted to personnel with a documented need and reviewed at least quarterly. Just-in-time or time-bound elevation for production access where supported. Logging of privileged access. Tenant isolation. Logical separation of each Customer’s and each workspace’s data such that data is accessible only within the authenticating tenant context. Access to Customer environments through federated or delegated access mechanisms governed by the permissions Customer grants and revocable by Customer. Controls designed to prevent access to one Customer’s data from another Customer’s context. Encryption. Encryption of Customer Personal Data in transit using industry-standard transport encryption. Encryption of Customer Personal Data at rest using industry-standard algorithms. Documented key management procedures with restricted access to key material. Pseudonymization and minimization. Collection and Processing limited to what is necessary to provide the Cloud Services. Redaction and masking applied where supported by the Cloud Services. De-identification and aggregation applied before any incorporation into Aggregated Statistics. Operational security. Change management with peer review and approval for production changes. Segregation of development, test, and production environments. Prohibition on the use of production Customer Personal Data in non-production environments except under equivalent controls. Secure software development practices including code review and dependency scanning. Vulnerability management with defined remediation timelines based on severity. Penetration testing conducted at least annually by a qualified independent third party. Endpoint protection and patch management for systems with access to production. Monitoring and logging. Centralized logging of production systems and administrative activity. Monitoring and alerting for anomalous or unauthorized activity. Log retention sufficient to support investigation. Protection of logs from unauthorized modification. Incident response. A documented incident response plan, tested at least annually. Defined severity classification, escalation paths, and roles. Procedures for containment, investigation, eradication, recovery, and post-incident review. Notification procedures consistent with Section 10 of this DPA. Resilience. Documented backup procedures with restoration testing. Documented business continuity and disaster recovery plans with defined recovery objectives, reviewed at least annually. Use of resilient cloud infrastructure with redundancy across availability zones where supported. Supplier management. Security review of Sub-processors before engagement and periodically thereafter. Contractual flow-down of data protection and security obligations. Maintenance of a Sub-processor inventory. Physical security. Production infrastructure is hosted in facilities operated by cloud infrastructure providers that maintain independently audited physical and environmental security controls. ContraForce does not operate its own data centers. Annex 3 — Sub-processors This Annex completes Annex III of the EU SCCs. The Sub-processors engaged by ContraForce, together with the purpose and location of their Processing, are set out in the Sub-processor List maintained at https://trust.contraforce.com/subprocessors. The Sub-processor List as in effect at any time constitutes Annex III of the EU SCCs for the purposes of this DPA. Changes to the Sub-processor List are made in accordance with Sections 7.2 and 7.3. The Sub-processor List may also identify third parties engaged in connection with ContraForce’s Processing of Account Data and Usage Data as a Controller under Section 2.3, including payment processing and service notification providers. Those third parties are identified for transparency, do not Process Customer Personal Data, and are not Sub-processors for the purposes of this DPA or of Annex III of the EU SCCs. On written request, ContraForce will provide Customer with a copy of the Sub-processor List as in effect on a specified date, identifying which entries Process Customer Personal Data. Under the BYOC Model, cloud infrastructure within Customer’s own subscription is operated under Customer’s own agreement with its cloud provider, and that provider is not a ContraForce Sub-processor in respect of that infrastructure. Annex 4 — EU Standard Contractual Clauses The EU SCCs are incorporated into this DPA by reference and are completed as follows. Modules. Module Two applies where Customer is a Controller of the transferred Customer Personal Data. Module Three applies where Customer is a Processor. Parties. The data exporter and data importer are as set out in Annex 1, Part A. Signature and date are satisfied by the parties’ entry into the Agreement, or by an executed signature page where one has been executed. Clause 7 (Docking clause). Applies. Clause 9 (Use of sub-processors). Option 2, general written authorization, applies. The notice period is thirty (30) days as set out in Section 7.2. Clause 11 (Redress). The optional independent dispute resolution language does not apply. Clause 13 (Supervision). The competent Supervisory Authority is as set out in Annex 1, Part B. Clause 17 (Governing law). Option 1 applies. The governing law is the law of Ireland. Clause 18 (Choice of forum and jurisdiction). The courts of Ireland. Annex I.A (List of parties). Annex 1, Part A of this DPA. Annex I.B (Description of transfer). Annex 1, Part B of this DPA. Annex I.C (Competent supervisory authority). Annex 1, Part B of this DPA. Annex II (Technical and organisational measures). Annex 2 of this DPA. Annex III (List of sub-processors). Annex 3 of this DPA. Annex 5 — UK International Data Transfer Addendum Where the UK GDPR applies to a Restricted Transfer, the UK Addendum is incorporated into this DPA and completed as follows. Table 1 — Parties. Start date: the effective date of the Agreement. The parties, their roles, key contacts, and signatures are as set out in Annex 1, Part A and in the Agreement. Table 2 — Selected SCCs, Modules and Selected Clauses. The EU SCCs as incorporated and completed by Annex 4 of this DPA, including the module, clause elections, and appendix information stated there. Table 3 — Appendix Information. Annex I.A: Annex 1, Part A. Annex I.B: Annex 1, Part B. Annex II: Annex 2. Annex III: Annex 3. Table 4 — Ending this Addendum when the Approved Addendum changes. Neither party may end the UK Addendum as set out in Section 19 of the UK Addendum. For the purposes of the UK Addendum, references in the EU SCCs to the GDPR are to the UK GDPR, the competent authority is the UK Information Commissioner, and the governing law and forum under Clauses 17 and 18 are the law of England and Wales and the courts of England and Wales respectively. © 2026 ContraForce Group, Inc. All rights reserved.