[Playbook] How to architect security into the agentic SDLC
Download now
Product
Platform Overview
Unified AppSec across AI, code, OSS & containers
Agents
Developer Tools
fREE
Integrations
AI Governance
AI Coding Agents
AI Models
MCP & Skills
AI Code
Code Scanning (AI SAST)
Secrets Detection
AI Security Review
Open Source
Dependencies (SCA)
Malicious Package Detection
Patches
Container Scanning
SBOM & Compliance
SUPPLY CHAIN
Package Firewall
CI/CD Security
Artifact Signing
Solutions
CATEGORY
AI Code Security
Software Supply Chain Security
Agentic Remediation
COMPLIANCE
Cyber Resilience Act (CRA)
FedRAMP
ISO 42001
PCI DSS
SOC 2
INDUSTRY
Financial Services
Software & Technology
Research
PROJECTS
Coding Agent Benchmark
OSS Risk Explorer
OWASP Top 10 Risks for OSS
RISK INTELLIGENCE
Vulnerability Reporting
Threat Research
Supply Chain Risk Hub
Research Hub
Latest research into vulnerabilities and software supply chain attacks.
Resources
LEARN
Docs
Blog
Case Studies
Events
Reports
COMPANY
Customers
Partners
Careers
News
About Us
Featured
Agent Security League
Agent Security League
Malware in Open Source Ecosystems
Malware in Open Source Ecosystems
Dependency Management ReportSecure Code Prompt Library
LeanAppSec
Docs
Pricing
Login
Book a Demo
Book Demo
Start Free Trial
Book Demo

Endor Labs Data Processing

Last updated on
September 28, 2026
Title goes here

Endor Labs Data Processing

Last updated on
September 28, 2026
Enter your email to be notified of changes to this list.

This Endor Labs Data Processing Agreement (the “DPA”) is entered into between Endor Labs Inc. (“Endor Labs”) and the customer identified in the Order Form (“Customer”). This DPA forms part of the Endor Labs Master Services Agreement or other written agreement between the parties for the provision of services (the “Agreement”), and is effective as of the effective date of the Agreement. Capitalized terms used but not defined in this DPA have the meanings given in the Agreement.

1. Definitions

1.1 “Account Data” has the meaning given in the Agreement or, if not defined in the Agreement, means Personal Data that relates to Endor Labs’ relationship with Customer, including the names and contact information of individuals authorized by Customer to access Customer’s account, support communications, and billing and administrative information relating to Customer. Account Data does not include Customer Data or Customer Personal Data submitted to or processed through the Services.

1.2 “Aggregated and De-identified Data” has the meaning given in the Agreement or, if not defined in the Agreement, means data derived from Customer Personal Data, Customer Data, or use of the Services that has been aggregated or de-identified such that it does not identify, and could not reasonably be used to identify, Customer or any natural person.

1.3 “Applicable Privacy Law” means any applicable law, regulation, or binding regulatory guidance governing the privacy, protection, or Processing of Personal Data, including the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020 (“CPRA”) (as so amended, the “CCPA”), the EU General Data Protection Regulation (Regulation (EU) 2016/679) (“EU GDPR”), the UK General Data Protection Regulation (“UK GDPR”) and the Data Protection Act 2018, the Swiss Federal Act on Data Protection (“Swiss FADP”), and any US state privacy law described in Annex C (US State Privacy Law Addendum), each as amended, superseded, or replaced from time to time.

1.4 “Controller” means the entity that determines the purposes and means of Processing Personal Data, including any “business” as defined in the CCPA.

1.5 “Customer Personal Data” means the Personal Data within Customer Data (as defined in the Agreement) that Customer or its Users provide, transmit, or make available to Endor Labs in connection with Customer’s use of the Services, as further described in Annex A, Part 1 (Description of Processing Activities). Customer Personal Data does not include Usage Data, Account Data, or Aggregated and De-identified Data.

1.6 “Data Subject” means the identified or identifiable natural person to whom Personal Data relates.

1.7 “Outputs” has the meaning given in the Agreement or, if not defined in the Agreement, means the content and results generated or returned by the Services.

1.8 “Personal Data” means any information that identifies, relates to, describes, or could reasonably be used to identify a natural person, as defined under Applicable Privacy Law.

1.9 “Processing” (and “Process” and “Processes”) means any operation performed on Personal Data, whether or not by automated means, including collection, storage, use, disclosure, combination, erasure, or destruction.

1.10 “Processor” means the entity that Processes Personal Data on behalf of the Controller, including any “service provider” or “contractor” as those terms are defined under the CCPA or other US state privacy laws.

1.11 “SCCs” means the standard contractual clauses approved by the European Commission pursuant to Implementing Decision (EU) 2021/914.

1.12 “Security Incident” 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 Endor Labs or its Sub-processors. Security Incident does not include unsuccessful attempts that do not compromise the security of Customer Personal Data, including unsuccessful log-in attempts, pings, port scans, or denial-of-service attacks.

1.13 “Sub-processor” means any third party engaged by Endor Labs to Process Customer Personal Data on Endor Labs’ behalf.

1.14 “Trust Center” means the security, compliance, and legal pages that Endor Labs maintains at trust.endorlabs.com and endorlabs.com/legal, including its Sub-processor list, or any successor locations identified by Endor Labs.

1.15 “UK Addendum” means the International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner’s Office (version B1.0, in force 21 March 2022), as updated.

1.16 “Usage Data” has the meaning given in the Agreement or, if not defined in the Agreement, means technical logs, events, and usage and performance information generated by or collected in connection with the Services, excluding the content of Customer Personal Data.

2. Scope; Roles

2.1 Processor Role and Instructions. With respect to Customer Personal Data, Customer is the Controller and Endor Labs is the Processor. Where Customer acts as a Processor on behalf of another Controller, Customer appoints Endor Labs as a Sub-processor, and Customer represents and warrants that its instructions to Endor Labs are authorized by the relevant Controller. In that case, references in this DPA to Customer’s instructions, obligations, or rights as Controller will be deemed to include Customer acting on behalf of the relevant Controller, as applicable. Endor Labs will Process Customer Personal Data only: (a) in accordance with Customer’s documented instructions as set forth in this DPA and the Agreement; (b) as necessary to provide, maintain, secure, and support the Services; (c) as required by Applicable Privacy Law (in which case Endor Labs will inform Customer of the requirement before Processing unless prohibited by law); and (d) as set forth in Annex A, Part 1. The Agreement, this DPA, the applicable Order Forms, and Customer’s documented configuration and use of the Services constitute Customer’s complete documented instructions as of the effective date of this DPA; any additional instructions require the parties’ written agreement. If Endor Labs reasonably believes that an instruction infringes Applicable Privacy Law or is technically infeasible or outside the scope of the Services, Endor Labs will promptly notify Customer and will not be required to follow it. Endor Labs’ restrictions on using Customer Personal Data to train, develop, or improve artificial intelligence or machine learning models are set forth in Section 10 (AI and Machine Learning Restrictions) of this DPA and the applicable model-training or data-use provisions of the Agreement.

2.2 Independent Controller Activities. Except as set forth below, with respect to Usage Data and Account Data, and any Aggregated and De-identified Data that constitutes Personal Data, Endor Labs is an independent Controller (and not a joint Controller with Customer). To the extent such data constitutes Personal Data, Endor Labs Processes it as an independent Controller solely for purposes related to managing its relationship with Customer (including account administration, billing, and communications, subject to applicable law and opt-out rights), operating, securing, supporting, and improving the Services, preventing fraud and abuse, and complying with law. Endor Labs will not Process such data for advertising, sale, sharing, model training, or unrelated product development except with Customer’s express written authorization. Aggregated and De-identified Data that no longer constitutes Personal Data is not subject to this DPA except as provided in Section 11 (Aggregated and De-identified Data). Endor Labs’ Processing as an independent Controller is governed by Endor Labs’ applicable privacy notices and Applicable Privacy Law and is not subject to the Processor obligations in Sections 3 through 9 of this DPA. To the extent Usage Data constitutes Customer Personal Data and is Processed solely to provide the Services on Customer’s behalf, Endor Labs Processes it as a Processor under this DPA. Subject to the restrictions expressly set forth in this DPA and Applicable Privacy Law, nothing in this DPA limits Endor Labs’ rights with respect to Aggregated and De-identified Data, Usage Data, or Account Data.

2.3 Inability to Comply. Endor Labs will notify Customer promptly if Endor Labs determines that it can no longer meet its obligations under Applicable Privacy Law with respect to Customer Personal Data. In that case, Customer may, as Customer’s sole contractual remedy for such prospective inability to continue the affected Processing, suspend the affected Processing or terminate the affected Order Form. Nothing in this Section limits any rights or remedies that may not be limited under Applicable Privacy Law or the SCCs.

2.4 Customer Affiliates. Customer enters into this DPA for itself and, where required by Applicable Privacy Law, on behalf of its Affiliates that use the Services, thereby establishing a separate DPA between Endor Labs and each such Customer Affiliate. Customer remains responsible for coordinating all instructions and communications with Endor Labs under this DPA and for its Affiliates’ compliance, and any right or claim under this DPA on behalf of a Customer Affiliate must be exercised or brought by Customer and not by the Affiliate directly, except to the extent such a restriction is not permitted under Applicable Privacy Law or the SCCs.

2.5 Customer-Directed Services. The Services may permit Customer to configure the Services to transmit Customer Data, including Customer Personal Data, to a third-party product or service selected by Customer, including an AI or large language model provider accessed using Customer’s own account, API key, or other credentials (including a model provider that Customer connects through the bring-your-own-key option for the AI Features described in the Agreement) (each, a “Customer-Directed Service”). Customer’s configuration of the Services to route Customer Personal Data to a Customer-Directed Service constitutes Customer’s documented instruction to transmit that data. A Customer-Directed Service is not a Sub-processor, and Sections 5 (Sub-processors) and 10 (AI and Machine Learning Restrictions) do not apply to its Processing of Customer Personal Data. As between the parties, Customer is solely responsible for its selection of, and terms with, each Customer-Directed Service; for the lawfulness of the disclosure, including any required legal basis, notices, consents, and transfer mechanisms; for evaluating the Customer-Directed Service’s security, retention, and data-use practices, including any use of data to train or improve models; and for ensuring that no Restricted Data is transmitted except as permitted under Customer’s agreement with that provider and Applicable Privacy Law. Endor Labs’ obligations under this DPA do not apply to Customer Personal Data once it has been delivered to a Customer-Directed Service, and Endor Labs is not responsible for the acts, omissions, or security of any Customer-Directed Service. Endor Labs will protect credentials Customer submits to configure a Customer-Directed Service as Customer’s Confidential Information and will use them solely to provide the Services as configured by Customer.

2.6 Deployment Models. Endor Labs hosts the Services in the hosting region (United States or European Union) specified in the applicable Order Form, and the Processor obligations in Sections 3 through 9 apply to the Customer Personal Data that Endor Labs Processes there. Where Customer configures cloud scanning, Endor Labs accesses Customer’s source code repositories and Processes the Customer Personal Data they contain for the duration of each scan, retaining scan metadata and results. Where Customer configures hybrid scanning in Customer’s own environment, Endor Labs’ systems do not access Customer’s source code repositories and Endor Labs Processes only the scan metadata and results transmitted to the Services. Customer is responsible for the environment it controls, and Endor Labs’ obligations under this DPA apply to Customer Personal Data only to the extent Endor Labs Processes it. In either case, Endor Labs Processes Account Data and Usage Data as an independent Controller in accordance with Section 2.2.

3. Confidentiality of Processing

Endor Labs will ensure that persons authorized to Process Customer Personal Data are subject to binding confidentiality obligations or professional duties of confidentiality, and access to Customer Personal Data will be limited to Endor Labs personnel and Sub-processors who require access to perform the Services.

4. Security

Endor Labs will implement and maintain technical and organizational measures designed to protect Customer Personal Data against unauthorized or unlawful Processing and against accidental loss, destruction, damage, alteration, or unauthorized disclosure, as further described in Annex A, Part 2 (Technical and Organizational Measures). Endor Labs may update such measures from time to time, provided that the updated measures do not materially reduce the overall level of security provided to Customer Personal Data. Endor Labs’ audit reports and certifications are available as set forth in Section 12 (Audit Rights). Endor Labs’ then-current security controls are described at the Trust Center.

5. Sub-processors

Customer authorizes Endor Labs to engage Sub-processors to Process Customer Personal Data in accordance with this Section 5. Endor Labs maintains its current list of Sub-processors at the Trust Center, and Customer will subscribe there to notifications of changes to the list; publication of a change at the Trust Center and the resulting notification constitute Endor Labs’ notice of the change to Customer. Endor Labs will provide Customer with at least ten (10) days’ advance notice of any material addition, replacement, or removal of a Sub-processor that will Process Customer Personal Data, except where a shorter notice period is reasonably necessary for urgent security or legal reasons. Endor Labs will impose on Sub-processors the same data protection obligations required under Applicable Privacy Law and obligations no less protective than Endor Labs’ obligations under this DPA with respect to Customer Personal Data, in each case to the extent applicable to the services provided by the Sub-processor. Endor Labs remains liable for its compliance with this DPA, including for the acts and omissions of Sub-processors that breach this DPA in connection with their Processing of Customer Personal Data. If Customer objects to a new or replacement Sub-processor on reasonable data protection grounds, Customer must notify Endor Labs in writing within ten (10) days of the applicable notice. The parties will cooperate in good faith to resolve the objection. If the objection relates to a Sub-processor that Endor Labs uses only for the AI Features (as defined in the Agreement), Customer may resolve the objection by disabling the AI Features for its account. If the parties are unable to resolve the objection within a reasonable time, Customer may, as Customer’s sole contractual remedy for such objection, terminate the affected Order Form upon written notice and pay Endor Labs all amounts due and owing under the Agreement as of the date of such termination. Nothing in this Section limits any rights or remedies that may not be limited under Applicable Privacy Law or the SCCs.

6. Data Subject Rights

Taking into account the nature of the Processing and the information available to Endor Labs, Endor Labs will provide Customer with reasonable assistance to fulfill Customer’s obligation to respond to Data Subject rights requests under Applicable Privacy Law. Endor Labs will promptly notify Customer if Endor Labs receives a Data Subject request and will not respond on Customer’s behalf without Customer’s prior written authorization, except as required by Applicable Privacy Law. To the extent assistance under this Section 6 requires work beyond the Services, Customer will compensate Endor Labs at Endor Labs’ then-current professional services rates. Endor Labs’ obligations under this Section are limited to information reasonably available to Endor Labs and do not require Endor Labs to disclose confidential information of other customers, compromise the security of Endor Labs systems, or take actions not required by Applicable Privacy Law.

7. Data Protection Impact Assessments

To the extent required by Applicable Privacy Law and upon Customer’s reasonable written request, Endor Labs will provide reasonable cooperation and assistance with the conduct of data protection impact assessments and any required prior consultations with supervisory authorities, in each case solely to the extent relating to Endor Labs’ Processing of Customer Personal Data. Customer is responsible for conducting the assessment and reaching any legal determinations required under Applicable Privacy Law. The cost and limitation provisions in Section 6 (Data Subject Rights) apply equally to assistance under this Section 7.

8. Security Incidents

Endor Labs will notify Customer in writing without undue delay, and in any event within seventy-two (72) hours, after Endor Labs becomes aware of a Security Incident. Endor Labs may provide initial notice based on information then available and supplement it as additional information is confirmed. To the extent then known, the notification will include a description of the Security Incident, the likely consequences, and the measures taken or proposed to address it. Endor Labs will cooperate with Customer and take reasonable steps within Endor Labs’ control to investigate, mitigate, and remediate the Security Incident. As between the parties, Customer is solely responsible for fulfilling any third-party notification obligations relating to a Security Incident, except to the extent Applicable Privacy Law requires Endor Labs to provide such notices. Endor Labs’ notification of, or response to, a Security Incident does not constitute an acknowledgment of any fault or liability.

9. Data Return; Deletion

Upon Customer’s written request following termination or expiration of the Agreement (or earlier, to the extent Customer Personal Data is no longer required for the Services), Endor Labs will, at Customer’s election, return Customer Personal Data to Customer in an industry-standard, machine-readable format or securely delete it within ninety (90) days after the request. Absent such a request, Endor Labs may retain Customer Personal Data subject to this DPA and delete it in the ordinary course, and where the SCCs apply Endor Labs will delete or return that data at the end of the provision of the Services as Clause 8.5 of the SCCs requires. Upon Customer’s written request, Endor Labs will provide a written certification confirming such return or deletion. Notwithstanding the foregoing, Endor Labs may retain Customer Personal Data (a) in routine system backups until they are overwritten or expire in the ordinary course of Endor Labs’ backup cycle; (b) to comply with a legal hold or any order or request from a court, regulator, or other governmental authority; and (c) to the extent and for the period required by Applicable Privacy Law. Customer Personal Data so retained remains subject to this DPA. Customer acknowledges that fulfilling a return or deletion request before the end of the term of the Agreement may limit or prevent Endor Labs’ ability to continue providing the affected Services.

10. AI and Machine Learning Restrictions

Endor Labs will not use Customer Personal Data to train, fine-tune, develop, or improve any artificial intelligence or machine learning model (including any such model operated by a Sub-processor or third-party provider engaged by Endor Labs), except: (a) as Aggregated and De-identified Data under Section 11 (Aggregated and De-identified Data); or (b) with Customer’s express written authorization. With respect to AI/ML Sub-processors, Endor Labs will contractually require each such Sub-processor not to use Customer Personal Data to train, fine-tune, develop, or improve its models except as expressly authorized under the Agreement and, where the Sub-processor offers configurable training or retention settings, Endor Labs will use commercially reasonable efforts to configure those settings consistently with this restriction. Endor Labs will also require that each such Sub-processor: (i) Processes Customer Personal Data only as necessary to provide inference or other Services to Endor Labs; (ii) does not retain Customer Personal Data except as necessary to provide, secure, debug, or comply with legal obligations for the applicable service; and (iii) does not permit human review of Customer Personal Data except for abuse, security, support, or legal-compliance purposes and only under confidentiality obligations. Endor Labs’ use of Outputs for model training or improvement is subject to the Agreement. Customer may disable the AI Features (as defined in the Agreement) for its account as described in the Agreement and the Documentation. Nothing in this Section 10 restricts Endor Labs’ Processing of Customer Personal Data as otherwise authorized under this DPA or the Agreement, or as necessary to provide, maintain, secure, or support the Services.

11. Aggregated and De-identified Data

Customer authorizes Endor Labs to aggregate and de-identify Customer Personal Data. To the extent any resulting data no longer constitutes Personal Data under Applicable Privacy Law, such data will be considered outside the scope of this DPA. With respect to any such data that constitutes Aggregated and De-identified Data: (a) Endor Labs will implement and maintain reasonable technical and organizational measures designed to ensure that the data could not reasonably be associated with, or used to re-identify, any Data Subject; (b) Endor Labs will not attempt to re-identify the data except to test the effectiveness of its de-identification processes; (c) Endor Labs will Process the data solely in aggregated or de-identified form (as applicable); and (d) Endor Labs will contractually require any recipients of Aggregated and De-identified Data to maintain the data in aggregated or de-identified form and not to attempt re-identification, in each case to the extent required by Applicable Privacy Law. Endor Labs applies de-identification and aggregation measures intended to align with the standards for deidentified information and aggregate consumer information under California Civil Code Section 1798.140 and comparable de-identification, aggregation, or anonymization requirements under Applicable Privacy Law. Subject to the foregoing, Endor Labs may use Aggregated and De-identified Data for the purposes permitted under the Agreement or, where the Agreement does not address such use, to operate, secure, analyze, improve, benchmark, and develop the Services.

12. Audit Rights

Endor Labs’ most recent independent security audit report or assessment (such as a SOC 2 audit report), where Endor Labs maintains one, together with Endor Labs’ security documentation at the Trust Center, serves as the primary means of demonstrating compliance with this DPA. Where Endor Labs maintains such a report or assessment, Endor Labs will, upon reasonable request, make its then-current report or equivalent documentation available to Customer, subject to reasonable confidentiality obligations. If additional information is reasonably required, Endor Labs will respond to reasonable written security questionnaires. If compliance still could not reasonably be demonstrated, Customer may, no more than once annually and upon at least sixty (60) days’ prior notice, engage an independent third-party auditor subject to confidentiality obligations to conduct an audit at Customer’s expense during normal business hours and in a manner that minimizes disruption to Endor Labs. Endor Labs may reasonably object to any auditor that is a competitor, lacks independence, or is otherwise unsuitable. No audit or inspection will provide Customer or its auditor with access to other customers’ data, Endor Labs’ source code, information that would compromise the security of Endor Labs’ systems or other customers, or facilities where access would pose a security risk, and Endor Labs may require Customer and its auditor to agree to reasonable confidentiality protections in connection with any audit or inspection.

13. Government Access Requests

To the extent legally permitted and reasonably practicable, Endor Labs will use commercially reasonable efforts to notify Customer of any legally binding governmental request for Customer Personal Data prior to disclosure. Endor Labs may challenge or seek to narrow any request that Endor Labs reasonably believes is overbroad, unlawful, or otherwise inappropriate and will disclose only the Customer Personal Data required by law.

14. International Data Transfers

To the extent Endor Labs Processes or transfers Customer Personal Data to a jurisdiction for which Applicable Privacy Law requires a lawful transfer mechanism, Endor Labs will comply using a recognized mechanism, including the SCCs, the UK Addendum, the Swiss modifications to the SCCs, or any other lawful transfer mechanism recognized under Applicable Privacy Law. The terms set forth in Annex B (International Data Transfer Addendum) are incorporated by reference into this DPA and apply to the extent Customer Personal Data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country that the applicable supervisory authority has not recognized as providing an adequate level of protection.

15. Customer Obligations

15.1 Restricted Data. Customer represents and warrants that Customer will not submit, and will not permit any User to submit, the following categories of data to the Services without the parties’ express prior written agreement (including an executed business associate agreement, which constitutes such agreement with respect to Protected Health Information) (collectively, “Restricted Data”): (a) social security numbers or other government-issued identification numbers; (b) protected health information subject to HIPAA, or other information regarding an individual’s medical history, mental or physical condition, or medical treatment or diagnosis; (c) health insurance information; (d) biometric or genetic information; (e) passwords or credentials for third-party online accounts (other than credentials created for and used solely to access the Services or submitted to configure a Customer-Directed Service); (f) credentials for any financial accounts; (g) tax return data; (h) payment card information subject to PCI DSS; (i) Personal Data of children under sixteen (16) years of age; (j) precise geolocation data; or (k) any other information that falls within any special categories of Personal Data as defined under Applicable Privacy Law. Restricted Data also includes API keys, private keys, access tokens, passwords, secrets, and production credentials, in each case unless the parties specifically agree otherwise in writing, and in each case excluding (i) credentials that Customer submits to configure the Services, including to connect Customer’s source code repositories, CI/CD pipelines, and other integrations or a Customer-Directed Service (as defined in Section 2.5), and (ii) secrets, credentials, and other Restricted Data that are present in Customer’s source code, repositories, container images, or other Customer Data submitted to the Services for scanning and analysis, which Endor Labs Processes only as necessary to detect and report them to Customer and to provide the Services. If Customer Personal Data submitted to the Services incidentally contains Restricted Data, Customer remains solely responsible for ensuring such submission complies with Applicable Privacy Law, and Endor Labs’ obligations under this DPA apply to such data as Customer Personal Data.

15.2 Lawful Basis, Security, and Assessment. Customer represents and warrants that: (a) Customer has established and will maintain a valid legal basis under Applicable Privacy Law (including, where applicable, Articles 6, 9, and 10 of the EU GDPR or the equivalent provisions of the UK GDPR) for Endor Labs’ Processing of Customer Personal Data as contemplated by the Agreement and this DPA; and (b) Customer has provided all required notices and obtained all required consents (including, where applicable, under Articles 12 through 14 of the EU GDPR or the equivalent provisions of the UK GDPR). Customer is solely responsible for making appropriate use of the Services to ensure a level of security appropriate to the risk in respect of Customer Personal Data, for securing the account credentials, systems, and devices Customer uses to access the Services, and for backing up Customer Personal Data as applicable. Customer acknowledges that it has had the opportunity to evaluate the Services, the technical and organizational measures described in Annex A, Part 2, and Endor Labs’ commitments under this DPA in determining whether the Services are appropriate for Customer’s intended use.

16. Liability

Each party’s liability under or in connection with this DPA is subject to the limitations and exclusions of liability set forth in the Agreement, which are incorporated herein by reference. Nothing in this Section 16 limits the rights of Data Subjects or supervisory authorities under Applicable Privacy Law, or limits either party’s liability to such persons or authorities (or to Data Subjects under the third-party beneficiary provisions of the SCCs) to the extent such liability may not be limited by contract under Applicable Privacy Law.

17. Term; Survival

This DPA is effective as of the effective date of the Agreement and will remain in force for the duration of the Agreement and for as long as Endor Labs Processes Customer Personal Data. Upon termination or expiration of the Agreement, this DPA will continue in effect until all Customer Personal Data has been returned or deleted in accordance with Section 9 (Data Return; Deletion). Any provision that, by its nature, is intended to survive will survive termination or expiration of this DPA and the Agreement.

18. Miscellaneous

This DPA supplements the Agreement; in any conflict between the Agreement and this DPA with respect to the Processing of Customer Personal Data, this DPA controls, unless amended by Special Terms that expressly reference the provision amended, except that any business associate agreement between the parties controls with respect to Protected Health Information and compliance with HIPAA, and in all other respects the Agreement governs. This DPA, together with the Agreement, the Annexes hereto, and any applicable Order Forms, constitutes the entire agreement between the parties with respect to the Processing of Customer Personal Data. Except as expressly set forth in this DPA, this DPA may be amended or modified only by a written instrument signed by authorized representatives of both parties. Endor Labs may, however, modify this DPA (including replacing the SCCs, UK Addendum, or Swiss modifications to the SCCs with any successor or replacement transfer mechanism) on written notice to Customer solely to the extent necessary to maintain compliance with Applicable Privacy Law, so long as any such modification does not materially reduce the protections afforded to Customer Personal Data or materially increase Customer’s obligations under this DPA. If any provision is held unenforceable, it will be modified to the minimum extent necessary to make it enforceable and the remaining provisions will remain in full force and effect. This DPA will be governed by, and the parties submit to, the governing law and jurisdiction specified in the Agreement. Notices under this DPA will be given in accordance with the notice provisions of the Agreement; Security Incident notices may also be sent by email to Customer’s designated notice or security contact.

Annex A: Processing Details

Part 1: Description of Processing Activities

A.1 Parties. Data Exporter: Customer, acting as Controller or Processor, as applicable. Data Importer: Endor Labs, acting as Processor or Sub-processor, as applicable. The parties’ details are as set forth in the Agreement or applicable Order Form.

A.2 Data Subjects and Personal Data. Customer Personal Data may relate to (a) Customer’s employees, contractors, and other Users who access or use the Services or who contribute to the source code repositories that Customer connects to the Services; (b) individuals whose Personal Data is contained in Customer’s source code, repositories, container images, software bills of materials, or other Customer Data; and (c) any other individuals identified in the applicable Order Form, and may include repository and commit metadata attributing code changes to individuals (author names, email addresses, and commit messages), professional data (job title and employer) where contained in Customer Data, code snippets and file locations retained to report findings, any Personal Data contained in Customer’s source code or other Customer Data, and any other categories specified in the applicable Order Form. Account Data and Usage Data, including, where applicable, User names, email addresses, employee identifiers, authentication identifiers and account-access metadata (excluding passwords, access tokens, private keys, and other authentication secrets), log records, session data, feature usage statistics, device identifiers, and IP addresses generated by use of the Services, are Processed by Endor Labs as an independent Controller in accordance with Section 2.2 (Independent Controller Activities) of this DPA, except to the extent Section 2.2 provides that Endor Labs Processes such data as a Processor.

A.3 Special Categories of Personal Data. Endor Labs does not intentionally collect or Process special categories of Personal Data or other Restricted Data, and Customer must not submit them to the Services unless the parties have specifically agreed in writing in the applicable Order Form or other written agreement (including, with respect to Protected Health Information, an executed business associate agreement).

A.4 Nature, Purpose, Frequency, and Duration of Processing. Endor Labs will Process Customer Personal Data as necessary to scan and analyze Customer’s source code, dependencies, container images, CI/CD pipelines, coding-agent activity, and related artifacts for security and compliance findings; to report findings and remediation guidance to Customer; to provide the AI Features where enabled; to provide, maintain, secure, and support the Services; to fulfill its obligations under this DPA; and to comply with Applicable Privacy Law. Processing is continuous for the duration of the Agreement (as initiated by Customer through its use of the Services) and for such additional period as is necessary to return or delete Customer Personal Data in accordance with Section 9 (Data Return; Deletion).

Part 2: Technical and Organizational Measures

Endor Labs implements and maintains an industry-standard information security program designed to protect the confidentiality, integrity, and availability of Customer Personal Data, evidenced by Endor Labs’ then-current independent audit reports and certifications, which as of the effective date of this DPA include a SOC 2 Type II audit report, available to Customer in accordance with Section 12 (Audit Rights). Endor Labs’ measures include, as applicable to the Services and the nature of the Processing, role-based access controls and least-privilege principles, multi-factor authentication for privileged access, periodic access reviews, industry-standard encryption in transit and at rest, a security incident response plan, logging and monitoring to detect and alert on anomalous activity, physical and environmental security for facilities used to host Customer Personal Data, including those of Endor Labs’ cloud infrastructure providers (badge access, surveillance, fire suppression, power redundancy, climate control), backup and business continuity / disaster recovery procedures with periodic recoverability testing, vulnerability scanning, periodic penetration testing or equivalent technical security assessments, risk-based patch management, appropriate due diligence of Sub-processors consistent with applicable law and contractual security obligations, security awareness training for personnel who Process Customer Personal Data, and appropriate background screening to the extent permitted by applicable law. Endor Labs also maintains logical access controls and, where applicable, tenant isolation or equivalent logical segregation controls designed to limit access to Customer Personal Data to authorized users and systems. Endor Labs also maintains written information security policies and procedures governing access control, change management, vulnerability management, secure development practices, and incident response.

Part 3: Sub-processors

Customer authorizes Endor Labs to engage the Sub-processors identified at the Trust Center, in accordance with Section 5 (Sub-processors). The current Sub-processor list at the Trust Center constitutes the then-current list of authorized Sub-processors. Endor Labs’ Sub-processors may include providers of cloud infrastructure, hosting, database, and content delivery services, artificial intelligence and machine learning model inference and API services, customer support, ticketing, and knowledge-base tooling, customer relationship management, notification, and communications tooling, product analytics services, and workflow automation services. Endor Labs will notify Customer of changes to the Sub-processor list in accordance with Section 5 (Sub-processors).

Annex B: International Data Transfer Addendum

This Annex B applies only to the extent Customer Personal Data is transferred from the European Economic Area, the United Kingdom, or Switzerland to a country not recognized as providing an adequate level of data protection by the applicable supervisory authority. If no such transfers occur under the Agreement, this Annex B does not apply.

B.1 EU SCCs. Where Customer Personal Data is transferred from the EEA to a country not the subject of an EU adequacy decision, the parties agree to be bound by the SCCs, incorporated by reference into this DPA. Module Two (Controller to Processor) applies where Customer is a Controller, and Module Three (Processor to Sub-processor) applies where Customer is itself a Processor on behalf of another person. In any conflict between the SCCs and any other provision of this DPA or the Agreement, the SCCs prevail with respect to transfers governed by them. The following elections apply: Clause 7 (Docking) is not used; Clause 9(a) (Sub-processors) Option 2 applies, with notice period as in Section 5 (Sub-processors); Clause 11 (Redress) optional language is not used; Clause 13 (Supervision) the competent supervisory authority will be determined in accordance with Clause 13 of the SCCs and identified in Annex I.C to the extent required; Clause 17 (Governing Law) Option 1, governed by the law of Ireland; Clause 18 (Forum) the courts of Ireland. Annexes I, II, and III to the SCCs are populated by Annex A, Part 1, Annex A, Part 2, and Annex A, Part 3 of this DPA, respectively.

B.2 UK Addendum. Where Customer Personal Data is transferred from the United Kingdom to a country not subject to UK adequacy regulations, the parties agree to be bound by the UK Addendum, incorporated by reference. Table 1 (parties) is as identified in Annex A, Part 1 and the start date is the effective date of the Agreement; Table 2 incorporates the SCCs in Section B.1; Table 3 (Appendix Information) is as set forth in Annex A, Part 1, Annex A, Part 2, and Annex A, Part 3 of this DPA; and either party may end the UK Addendum under Section 19 of the UK Addendum.

B.3 Swiss Modifications to the SCCs. Where Customer Personal Data is transferred from Switzerland and the Swiss FADP applies, the SCCs in Section B.1 apply with the following modifications: references to the GDPR mean the Swiss FADP and applicable Swiss data protection provisions; references to a “Member State” will not be interpreted to exclude Data Subjects in Switzerland from exercising rights in their place of habitual residence; the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; and the governing law and courts are those of Switzerland, together with any further modifications required under the Swiss FADP or guidance of the Swiss Federal Data Protection and Information Commissioner.

B.4 New Transfer Mechanism. Endor Labs may, on notice to Customer, modify this DPA and replace the SCCs, UK Addendum, or Swiss modifications to the SCCs with any new or successor transfer instrument, or with another valid transfer mechanism, in each case to the extent necessary to maintain compliance with Applicable Privacy Law and provided that the replacement does not materially decrease the overall protection of Customer Personal Data.

B.5 Operational Clarifications. For Clause 8.3 of the SCCs, Customer will protect Endor Labs’ and its licensors’ trade secrets, business secrets, and confidential information when complying with transparency obligations. For Clause 8.8, any approval by Customer of a Sub-processor under Section 5 (Sub-processors) constitutes Customer’s documented instructions to effect onward transfers to that Sub-processor. Audits under Clauses 8.9(c) and 8.9(d) are governed by Section 12 (Audit Rights). Certification of deletion under Clauses 8.5 and 16(d) will be provided only upon Customer’s written request.

Annex C: US State Privacy Law Addendum

C.1 General and Generic Terms. This Annex C applies to the extent Endor Labs Processes Personal Data of residents of US states that have enacted applicable privacy laws, including the CCPA and the other state laws described in Section C.3 (Applicability). In any conflict between this Annex C and the main body of this DPA with respect to US state privacy law compliance, this Annex C controls. The terms “business,” “controller,” “processor,” “commercial purpose,” “sell,” “share,” “service provider,” and “contractor” have the respective meanings given in the applicable US state privacy laws, and “personal information” means Customer Personal Data to the extent it constitutes “personal information,” “personal data,” or a similar term governed by those laws. The parties intend that, with respect to any personal information, Endor Labs acts as a service provider, contractor, or processor under the US state privacy laws.

C.2 Service Provider Commitments. Endor Labs will not: (a) sell or share Customer Personal Data; (b) engage in cross-context behavioral advertising using Customer Personal Data; (c) retain, use, or disclose Customer Personal Data for any purpose other than performing the Services for Customer under the Agreement, or as otherwise permitted by the applicable US state privacy laws; (d) retain, use, or disclose Customer Personal Data outside the direct business relationship between Endor Labs and Customer; or (e) combine Customer Personal Data with personal information received from or on behalf of another person or entity, or collected from Endor Labs’ own interactions with consumers, except as permitted under the applicable US state privacy laws. Endor Labs will provide the same level of privacy protection as required of businesses or controllers under the applicable US state privacy laws. Endor Labs will cooperate with Customer to assist with consumer privacy rights requests by providing technical means to access and delete Customer Personal Data within the Services, as technically feasible; unless required by law, Endor Labs will refer such requests to Customer. To the extent Endor Labs Processes Sensitive Personal Information (as defined by Applicable Privacy Law) on behalf of Customer, Endor Labs will Process it only for the purposes set forth in this DPA and the Agreement and will not use or disclose it to infer characteristics about individuals except as permitted by law. Customer may take reasonable and appropriate steps to help ensure Endor Labs’ use of Customer Personal Data is consistent with Customer’s obligations under applicable US state privacy laws. Endor Labs will notify Customer if it determines that it can no longer meet its obligations under this Annex C and will cooperate to stop and remediate any unauthorized Processing. Endor Labs certifies that it understands the restrictions in this Section C.2 and will comply with them.

C.3 Applicability. This Annex C applies to the CCPA (as amended by the CPRA) and to any other comprehensive US state privacy law applicable to Endor Labs’ Processing of Customer Personal Data, in each case to the extent the applicable thresholds are met and as amended or superseded from time to time.

Gradient
Login
Endor Labs
Company
HomePricingContact UsAboutCareers
LEARN
BlogDocumentationeBook / ReportsEventsLeanAppSecSolution BriefVideo
Tools
Risk Explorer
Why Us?
vs Snykvs Semgrepvs Socketvs Traditional SCAvs Runtime SCA
Products
Use Cases
AI Apps
AI Code Governance
AI Static Application Security Testing (SAST)
Artifact Signing
Bazel Monorepos
CI/CD Discovery
Code Scanning
Compliance & SBOM
Container Scanning
Cyber Resilience Act
Digital Operational Resilience Act (DORA)
FedRAMP
GitHub Actions
ISO 42001
Malicious Package Detection
PCI DSS
RSPM
SBOM Ingestion
SCA with Reachability
Secrets Detection
SOC 2
Upgrades & Remediation
Integrations
Bazel
Bitbucket
C/C++
CircleCI
Claude Code
Cursor
Endor Labs with GitHub Advanced Security
Gemini
GitHub
GitHub Copilot
GitLab
Go
Grok Build
IDE
Java
JavaScript
Jenkins
Jira
Kotlin
Microsoft Defender for Cloud
.NET (C#)
PHP
Python
Ruby
Rust
Scala
Slack
Swift
TypeScript
Vanta
© 2026 Endor Labs. All rights reserved.
Legal and PrivacyTrust and Security

All names, logos, and brands of third parties listed on our site are trademarks of their respective owners. Endor Labs and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.