Data Processing Agreement
DATA PROCESSING AGREEMENT
By using our website, software and service, you and any company or entity that you are acting for (hereinafter referred to as the “Controller”) acknowledge that your use of the website, software and service may involve transfer of personal data to SeqOps AB (hereinafter referred to as the “Processor” or “SeqOps”) and hence, you agree to enter into this DPA with SeqOps AB and accept that you shall be bound by the contents thereof.
Where the SeqOps Services are procured through an MSP, reseller or other partner and the partner is the controller or processor of the relevant Personal Data, the terms of this DPA shall apply with the modifications set out in Annex IV.
1.DEFINITIONS AND INTERPRETATION
1.1.Definitions
In this DPA:
"Applicable Data Protection Law" means all applicable laws and regulations relating to the protection of Personal Data and privacy applicable to the Processing under the Main Agreement, including, where applicable, Regulation (EU) 2016/679 ("GDPR"), applicable Swedish data protection legislation and legislation concerning international transfers of Personal Data.
"Controller Personal Data" means Personal Data Processed by SeqOps or its Sub-processors on behalf of the Controller in connection with the Services.
"Data Subject", "Personal Data", "Processing", "Processor", "Controller", "Supervisory Authority" and "Personal Data Breach" shall have the meanings given to them under the GDPR, where the GDPR applies.
"Main Agreement" means the agreement under which SeqOps provides the Services to the Controller, including any applicable Terms of Service (Users | Partners), Master Services Agreement, order form or other contractual document governing the Services.
"Services" means the SeqOps software, platform, Monitoring Agent, cloud integrations, vulnerability and misconfiguration monitoring, prioritisation, reporting and remediation-guidance services, together with any AI-assisted or agentic cybersecurity functionality made available by SeqOps, including ACAP (Autonomous Cybersecurity Agent Platform), VaultAI-enabled functionality, security analysis, workflow orchestration, alerts, recommendations and authorised integrations, as provided under the Main Agreement.
"Sub-processor" means any third party appointed by or on behalf of SeqOps to Process Controller Personal Data on behalf of the Controller in connection with the Services.
"Restricted Transfer" means a transfer of Personal Data to a country or recipient that is subject to the international-transfer requirements of Chapter V GDPR or equivalent applicable law.
"SCCs" means the European Commission's Standard Contractual Clauses for international transfers adopted by Commission Implementing Decision (EU) 2021/914, as amended or replaced from time to time.
"TOMs" means the technical and organisational measures set out in Annex II.
1.2.Interpretation
References to legislation include amendments, replacements and successor legislation.
If there is a conflict between this DPA and the Main Agreement concerning the Processing of Personal Data, this DPA shall prevail to the extent of that conflict.
If the SCCs apply to a Restricted Transfer, the SCCs shall prevail over this DPA to the extent of any conflict concerning that Restricted Transfer.
2.ROLE OF THE PARTIES AND SCOPE
2.1.Controller and Processor
The Controller determines the purposes and means of the Processing of Controller Personal Data.
SeqOps shall Process Controller Personal Data only on behalf of and in accordance with the documented instructions of the Controller, except where otherwise expressly provided in this DPA or required by applicable law.
2.2.Subject matter and purpose
The subject matter of the Processing is the provision, operation, maintenance, support and development of the Services, including:
- a.collection and ingestion of data from the Controller's authorised cloud environments, servers, workloads, integrations and Monitoring Agents;
- b.vulnerability and misconfiguration monitoring;
- c.analysis, prioritisation and presentation of security findings;
- d.provision of remediation guidance;
- e.account administration and user access management;
- f.technical support and troubleshooting;
- g.security, availability, logging, monitoring and service administration;
- h.software development, maintenance and testing to the extent such activities require access to Controller Personal Data;
- i.backup and disaster-recovery activities; and
- j.such other Processing as is reasonably necessary to provide the Services and expressly instructed by the Controller.
- k.provision of AI-assisted and agentic cybersecurity functionality through ACAP and associated services, including analysis, workflow orchestration, generation of alerts, findings and recommendations, where enabled by the Controller
- l.processing of user and tenant identifiers, access permissions, authentication status, entitlement information and other technical information required to authenticate, authorise and operate the integration between SeqOps and ACAP
- m.processing of user prompts, requests, instructions, security findings, technical information, tool requests and responses, AI-generated outputs and related audit records, to the extent submitted to, obtained by or generated through ACAP or associated services in providing the Services; and
- n.transmission of relevant lifecycle, entitlement and access-management information between SeqOps and ACAP, including instructions relating to tenant deactivation and deletion of tenant data
SeqOps shall not use Controller Personal Data for purposes incompatible with the Controller's documented instructions.
2.3.Duration
The Processing shall continue for the duration of the Main Agreement and any period reasonably required to complete the return or deletion of Controller Personal Data in accordance with Clause 14.
2.4.Categories of Data Subjects
The categories of Data Subjects may include:
- a.employees and personnel of the Controller;
- b.users and authorised administrators of the Services;
- c.personnel of the Controller's customers, suppliers and service providers, where their information is contained in monitored environments;
- d.individuals whose Personal Data is incidentally present in logs, system records, configuration data, vulnerability data or other information processed through the Services; and
- e.such other Data Subjects whose Personal Data the Controller instructs SeqOps to Process.
2.5.Categories of Personal Data
Depending on the Controller's use of the Services, Controller Personal Data may include:
- a.names and business contact details;
- b.business email addresses and usernames;
- c.account and authentication information;
- d.identifiers associated with servers, cloud accounts, devices, workloads and systems;
- e.IP addresses and network identifiers;
- f.system, application, security and audit logs;
- g.vulnerability, configuration and security finding information;
- h.technical metadata and telemetry;
- i.support communications and correspondence;
- j.information contained in configuration files or system environments that may incidentally constitute Personal Data; and
- k.other Personal Data included in data submitted to or collected by the Services by or on behalf of the Controller.
- l.ACAP-related information, including user identifiers, tenant identifiers, tenant type, user roles, access permissions, ACAP permissions, MFA completion status, entitlement information, signed access-pass information, user prompts and requests, technical instructions, tool requests and responses, alerts, AI-generated outputs, workflow records and audit information, to the extent such information relates to an identified or identifiable individual.
The Controller shall not intentionally submit Special Categories of Personal Data to the Services unless expressly agreed with SeqOps in writing.
3.CONTROLLER'S RESPONSIBILITIES
3.1.Lawfulness
The Controller is responsible for ensuring that:
- a.it has an appropriate legal basis for the Processing of Controller Personal Data;
- b.its instructions to SeqOps comply with Applicable Data Protection Law;
- c.it has provided all necessary privacy notices to Data Subjects;
- d.it has obtained any required permissions, authorisations or consents for the collection and Processing of Controller Personal Data; and
- e.the Controller Personal Data supplied to SeqOps is adequate, relevant and limited to what is necessary for the Services.
3.2.Instructions
The Controller's instructions are principally documented in:
- a.the Main Agreement;
- b.this DPA and its Annexes;
- c.the Controller's configuration and use of the Services; and
- d.subsequent written instructions issued by the Controller and accepted by SeqOps.
SeqOps shall inform the Controller if, in its reasonable opinion, an instruction infringes Applicable Data Protection Law.
4.PROCESSING BY SEQOPS
4.1.Documented instructions
SeqOps shall:
- a.Process Controller Personal Data only on documented instructions from the Controller;
- b.ensure that persons authorised to Process Controller Personal Data are bound by confidentiality obligations;
- c.implement the TOMs set out in Annex II;
- d.assist the Controller as required under this DPA; and
- e.comply with its obligations under Applicable Data Protection Law.
4.2.Legally required Processing
Where SeqOps is required by applicable law to Process Controller Personal Data other than on the Controller's instructions, SeqOps shall, unless prohibited by law:
- a.inform the Controller of the relevant legal requirement before Processing; and
- b.Process only the minimum amount of Personal Data necessary to comply with that requirement.
5.AUTHORISED PERSONNEL AND OPSIO PVT. LTD.
5.1.General personnel requirements
SeqOps shall ensure that persons authorised to Process Controller Personal Data:
- a.have a legitimate business need for access;
- b.are subject to appropriate confidentiality obligations;
- c.receive appropriate data protection and security training; and
- d.are provided only such access as is appropriate to their role and responsibilities.
5.2.Access controls
SeqOps shall maintain appropriate controls over privileged and administrative access, including, where appropriate:
- a.individual user accounts;
- b.multi-factor authentication;
- c.least-privilege principles;
- d.access approval procedures;
- e.logging of privileged access;
- f.periodic access reviews; and
- g.prompt removal of access when it is no longer required.
5.3.Opsio Pvt. Ltd. as Sub-processor
SeqOps engages Opsio AB to provide services in connection with the development, maintenance, technical support, operation and improvement of the Services.
In providing such services, Opsio AB may engage Opsio Pvt. Ltd., an entity incorporated in India, as a downstream Sub-processor to provide development, maintenance, technical support, infrastructure, operational and related technical resources.
Accordingly, the relevant processing chain is:
SeqOps AB → Opsio AB → Opsio Pvt. Ltd.
To the extent Opsio AB or Opsio Pvt. Ltd. Processes or has access to Controller Personal Data, each entity shall be subject to appropriate written data-processing and confidentiality obligations. Opsio AB shall ensure that Opsio Pvt. Ltd. is bound by data protection and security obligations providing at least the level of protection required under this DPA and Applicable Data Protection Law.
Authorised personnel of Opsio AB and Opsio Pvt. Ltd. may access Controller Personal Data and SeqOps systems only to the extent necessary for the provision, development, maintenance, support, security or operation of the Services and in accordance with the documented instructions applicable to the Processing.
Neither entity is authorised to use Controller Personal Data for its own purposes or for purposes incompatible with the Controller's documented instructions.
5.4.Opsio personnel
SeqOps shall require Opsio AB and Opsio Pvt. Ltd., as applicable, to ensure that personnel who may access Controller Personal Data:
- a.are individually identifiable and authorised;
- b.are subject to binding confidentiality obligations;
- c.receive appropriate security and data protection training;
- d.use appropriate authentication controls;
- e.access Controller Personal Data only for authorised service purposes;
- f.are subject to access logging and monitoring where technically appropriate;
- g.have access revoked promptly when their role changes or their services are terminated; and
- h.comply with the applicable security requirements imposed upon Opsio under SeqOps's written sub-processing agreement.
5.5.No independent use by Opsio entities
Neither Opsio AB nor Opsio Pvt. Ltd., nor their respective personnel, shall:
- a.use Controller Personal Data for its own purposes;
- b.sell, disclose or otherwise commercialise Controller Personal Data;
- c.use Controller Personal Data for its own analytics or product development;
- d.use Controller Personal Data to train, fine-tune or develop an artificial intelligence or machine-learning model;
- e.combine Controller Personal Data with data belonging to other customers for its own purposes; or
- f.otherwise Process Controller Personal Data except on documented instructions from SeqOps consistent with the Controller's instructions.
6.SECURITY OF PROCESSING
6.1.Technical and organisational measures
Taking into account the state of the art, costs of implementation and the nature, scope, context and purposes of Processing and the risks to Data Subjects, SeqOps shall implement and maintain the TOMs described in Annex II.
6.2.Changes to security measures
SeqOps may update the TOMs where reasonably necessary to maintain or improve the security of the Services, provided that such changes do not materially reduce the overall level of protection applicable to Controller Personal Data.
6.3.Security documentation
Upon reasonable request, SeqOps shall provide the Controller with appropriate information concerning its security measures, which may include security summaries, certifications or independent assessment reports where available.
SeqOps shall not represent that it holds any certification unless expressly identified in the relevant documentation.
7.SUB-PROCESSING
7.1.General authorisation
The Controller provides SeqOps with general written authorisation to appoint Sub-processors for the Processing of Controller Personal Data, subject to the requirements of this Clause 7.
The Sub-processors authorised as at the Effective Date are listed in Annex III.
7.2.Sub-processor obligations
Before authorising a Sub-processor to Process Controller Personal Data, SeqOps shall:
- a.conduct appropriate due diligence having regard to the nature of the Processing;
- b.enter into a written agreement requiring the Sub-processor to provide an appropriate level of data protection and security;
- c.impose obligations concerning confidentiality, security, Personal Data Breaches, Data Subject rights, assistance, deletion/return and audits; and
- d.where applicable, implement appropriate international-transfer safeguards.
Where a Sub-processor engages a further Sub-processor to Process Controller Personal Data, SeqOps shall ensure that the requirements of this Clause 7 are satisfied throughout the relevant sub-processing chain. SeqOps shall remain responsible, as between SeqOps and the Controller, for the performance of its Sub-processors' obligations to the extent required by Applicable Data Protection Law.
7.3.Responsibility
As between the Controller and SeqOps, SeqOps shall remain responsible for the performance of its Sub-processors' obligations to the extent required by Applicable Data Protection Law.
7.4.New Sub-processors
SeqOps may add or replace a Sub-processor by providing the Controller with prior notice.
The notice shall identify, where reasonably practicable:
- a.the Sub-processor's name;
- b.location;
- c.service/function;
- d.categories of Processing; and
- e.applicable transfer mechanism where Personal Data is transferred outside the EEA.
The current Sub-processor list shall be maintained at:
https://seqops.io/self-service/legal/sub-processors
7.5.Objection
SeqOps shall provide the Controller with at least thirty (30) calendar days' prior written notice before a new or replacement Sub-processor begins Processing Controller Personal Data, except where a shorter period is reasonably necessary due to an urgent security, operational or legal requirement. In such circumstances, SeqOps shall provide as much prior notice as reasonably practicable and explain the reason for the shorter notice period. The Controller may object to the appointment of a new Sub-processor on reasonable data-protection grounds by notifying SeqOps within thirty (30) calendar days after receiving notice. The Controller's thirty (30) calendar day objection period under this Clause shall run from receipt of the notice.
The Parties shall use reasonable efforts to resolve the objection.
If the Parties cannot reasonably resolve the objection, SeqOps may, where commercially and technically feasible, offer an alternative configuration that avoids the affected Processing.
Where no reasonable alternative is available, either Party may terminate the affected Services in accordance with the termination provisions of the Main Agreement.
7.6.Existing Sub-processors
The Controller authorises the Sub-processors identified in Annex III as of the Effective Date, subject to this DPA.
8.DATA SUBJECT RIGHTS
8.1.Assistance
Taking into account the nature of Processing, SeqOps shall provide reasonable assistance to the Controller in responding to requests from Data Subjects exercising their rights under Applicable Data Protection Law.
8.2.Requests received by SeqOps
If SeqOps receives a request from a Data Subject relating to Controller Personal Data, SeqOps shall:
- a.promptly notify the Controller;
- b.not respond substantively except on the Controller's documented instructions or where required by law; and
- c.provide reasonable assistance to the Controller in responding to the request.
8.3.Technical assistance
Where reasonably possible, SeqOps shall provide appropriate functionality enabling the Controller to access, correct, export or delete Controller Personal Data through the Services.
9.PERSONAL DATA BREACH
9.1.Notification
SeqOps shall notify the Controller of a Personal Data Breach affecting Controller Personal Data:
without undue delay and, in any event, no later than forty-eight (48) hours after becoming aware of the breach.
9.2.Information
The notification shall, to the extent information is available at the time, include:
- a.the nature of the breach;
- b.the categories and approximate number of Data Subjects concerned;
- c.the categories and approximate number of Personal Data records concerned;
- d.the likely consequences of the breach;
- e.measures taken or proposed to address the breach and mitigate its effects;
- f.relevant contact information; and
- g.any other information reasonably required by the Controller to meet its obligations under Applicable Data Protection Law.
Where complete information is not initially available, SeqOps may provide information progressively as it becomes available.
9.3.Sub-processor incidents
SeqOps shall require each Sub-processor and any further Sub-processor in the relevant processing chain, including Opsio AB and Opsio Pvt. Ltd., to notify SeqOps without undue delay of any Personal Data Breach affecting Controller Personal Data.
9.4.Cooperation
SeqOps shall reasonably cooperate with the Controller in investigating, containing, mitigating and remediating a Personal Data Breach.
SeqOps shall not notify a Supervisory Authority or Data Subject concerning Controller Personal Data unless:
- a.instructed by the Controller; or
- b.required by applicable law.
10.DATA PROTECTION IMPACT ASSESSMENTS AND REGULATORY ASSISTANCE
SeqOps shall provide reasonable assistance to the Controller, taking into account the nature of Processing and information available to SeqOps, in relation to:
- a.data protection impact assessments;
- b.prior consultations with Supervisory Authorities;
- c.security assessments;
- d.information required under Articles 30–36 GDPR; and
- e.other reasonable regulatory or compliance enquiries relating to the Processing.
11.INTERNATIONAL DATA TRANSFERS
11.1.General principle
SeqOps shall not transfer Controller Personal Data outside the EEA except where a lawful transfer mechanism under Applicable Data Protection Law is available.
11.2.Restricted Transfers
Where a Restricted Transfer is required, SeqOps shall implement an appropriate mechanism under Chapter V GDPR.
Depending on the transfer structure, this may include:
- a.an applicable adequacy decision;
- b.the SCCs; or
- c.another lawful transfer mechanism recognised under Applicable Data Protection Law.
11.3.Opsio Processing Chain - India
Where Opsio AB engages Opsio Pvt. Ltd. in India to Process or access Controller Personal Data in connection with the Services, SeqOps shall ensure that the relevant sub-processing arrangement is documented and that appropriate safeguards are implemented in accordance with Applicable Data Protection Law.
Where Controller Personal Data is transferred or made accessible from the EEA to Opsio Pvt. Ltd. in India, such transfer or access shall be subject to an applicable Chapter V GDPR transfer mechanism.
Where required, the relevant transfer shall be covered by the European Commission's Standard Contractual Clauses, Module 3 (Processor-to-Processor), between the appropriate EEA data exporter and the Indian data importer, together with an appropriate transfer impact assessment and supplementary measures.
The identity of the relevant data exporter and importer, the contractual transfer chain and the applicable transfer documentation shall be accurately reflected in Annex V.
SeqOps shall ensure that Opsio AB is contractually required to impose equivalent data protection, confidentiality and security obligations on Opsio Pvt. Ltd. and to provide SeqOps with appropriate evidence of compliance upon reasonable request.
11.4.Controller-to-Processor transfers
Where the Controller transfers Controller Personal Data to SeqOps outside the EEA and SCCs are required, the applicable SCC module shall be incorporated into or executed alongside this DPA.
11.5.Transfer assessment
Before commencing a new Restricted Transfer, SeqOps shall assess, to the extent required by Applicable Data Protection Law:
- a.the transfer route;
- b.the applicable transfer mechanism;
- c.the law and practice of the destination country relevant to the transfer;
- d.the nature of the Personal Data;
- e.the purposes and context of Processing; and
- f.appropriate supplementary measures.
11.6.Supplementary measures
Where required, supplementary measures may include:
- a.encryption in transit and at rest;
- b.access controls and least-privilege principles;
- c.pseudonymisation or minimisation;
- d.strong authentication;
- e.logging and monitoring;
- f.contractual restrictions on access and disclosure; and
- g.organisational measures concerning government-access requests.
11.7.Government access requests
Where legally permitted, SeqOps and its Sub-processors shall notify the Controller of legally binding requests from public authorities for access to Controller Personal Data.
SeqOps shall, where legally permitted:
- a.assess the legality of the request;
- b.challenge unlawful or disproportionate requests where appropriate;
- c.disclose only the minimum amount legally required; and
- d.document the response.
12.PROCESSING FOR SECURITY, ANALYTICS, PRODUCT IMPROVEMENT AND AI
12.1.Customer Personal Data
SeqOps shall not use identifiable Controller Personal Data for its own independent purposes unless such use is:
- a.expressly authorised by the Controller;
- b.required by law; or
- c.carried out in circumstances where SeqOps is acting as an independent Controller and the applicable requirements for such Processing have been satisfied.
12.2.Aggregated or anonymised information
SeqOps may use information that has been irreversibly anonymised or aggregated so that it no longer constitutes Personal Data for purposes such as:
- a.service analytics;
- b.security analysis;
- c.product improvement;
- d.capacity planning; and
- e.statistical reporting.
Such use shall not permit SeqOps to identify the Controller or individual Data Subjects from the resulting information.
12.3.AI-powered features
SeqOps may make available AI-assisted and agentic cybersecurity functionality as part of the Services, including ACAP (Autonomous Cybersecurity Agent Platform) and functionality provided through or supported by VaultAI.
ACAP is a SeqOps service. In connection with the integration, SeqOps may transmit to ACAP information necessary to authenticate users, identify customer tenants, verify permissions and operate the integration. Such information may include numeric user identifiers, tenant identifiers, tenant type, user roles, ACAP permissions, MFA completion status, entitlement information, signed access passes, user and permission changes and lifecycle instructions.
The integration may also involve the transmission of user requests and instructions submitted through the ACAP interface. Depending on the functionality enabled and the Controller's use of the Services, Controller Personal Data may be processed by ACAP and associated AI or infrastructure providers.
SeqOps shall ensure that any Processing of Controller Personal Data through ACAP, VaultAI or an underlying provider is carried out only for the purposes of providing the Services and in accordance with the Controller's documented instructions, this DPA and Applicable Data Protection Law.
Before permitting an ACAP, VaultAI or other third-party provider to Process Controller Personal Data, SeqOps shall:
- a.identify the legal entity providing the relevant service;
- b.identify the hosting, infrastructure, AI/model and other external providers that Process or may access Controller Personal Data;
- c.determine the locations from which Controller Personal Data is stored, accessed or otherwise Processed, including any disaster-recovery or failover locations;
- d.ensure that the relevant providers are subject to appropriate written data-processing and confidentiality obligations;
- e.obtain the necessary Sub-processor authorisation in accordance with Clause 7 and ensure that the relevant provider is disclosed in Annex III;
- f.implement any applicable international-transfer mechanism and supplementary measures; and
- g.document the relevant Processing activities, retention arrangements and technical and organisational safeguards.
SeqOps shall not permit an unidentified AI/model provider or other external provider to Process Controller Personal Data through ACAP or VaultAI.
Controller Personal Data shall not be used by SeqOps, Opsio AB, Opsio Pvt. Ltd., ACAP, VaultAI or any underlying AI/model provider to train, fine-tune or develop general-purpose or provider-owned AI models, except where expressly authorised by the Controller in writing and permitted by Applicable Data Protection Law.
12.4.AI provider requirements
Where a third-party AI provider Processes Controller Personal Data:
- a.the provider shall be identified in Annex III;
- b.it shall be subject to an appropriate written data-processing agreement;
- c.it shall be subject to appropriate confidentiality and security requirements;
- d.its retention of Controller Personal Data shall be appropriately restricted;
- e.it shall not use Controller Personal Data to train, fine-tune or develop models except where expressly authorised by the Controller and permitted by Applicable Data Protection Law; and
- f.any Restricted Transfer shall be subject to an appropriate Chapter V GDPR transfer mechanism.
Where AI-assisted or agentic functionality is capable of interacting with a Controller's systems, applications, tools, APIs or integrations, SeqOps shall ensure that such functionality operates within the Controller's documented instructions, configured permissions and authorised access rights.
For the initial ACAP pilot, write actions through the ACAP integration shall remain disabled through the applicable platform-wide control and ACAP-side restrictions. Such write functionality shall not be enabled until the relevant technical controls have been implemented and tested and the Controller has provided separate written authorisation.
Any subsequent enablement of write functionality shall be subject to appropriate authentication, role-based permissions, logging and additional confirmation controls proportionate to the nature and risk of the action.
12.5.AI output
Where ACAP or associated functionality is configured to perform actions through a Controller's systems, tools, APIs or integrations, such actions shall be limited to the permissions and instructions expressly authorised by the Controller. SeqOps shall not enable such write or execution functionality for a Controller unless the required technical controls are in place and the Controller has separately authorised the relevant functionality in writing.
The Controller remains responsible for determining which users may access and manage ACAP functionality and for configuring the permissions and authorisations made available to those users.
13.AUDIT AND COMPLIANCE INFORMATION
13.1.Information
SeqOps shall make available information reasonably necessary to demonstrate compliance with this DPA and Article 28 GDPR.
13.2.Audit
The Controller may conduct an audit where:
- a.required by Applicable Data Protection Law;
- b.a Personal Data Breach or material security incident gives reasonable grounds for an audit; or
- c.information otherwise reasonably available to the Controller is insufficient to demonstrate compliance.
13.3.Audit procedure
Audits shall:
- a.be conducted on reasonable prior written notice;
- b.take place during normal business hours;
- c.avoid unreasonable disruption to SeqOps's operations;
- d.comply with reasonable security and confidentiality requirements; and
- e.not provide access to other customers' confidential information.
Where available, SeqOps may satisfy audit requirements by providing relevant independent audit reports, certifications, security questionnaires or equivalent evidence.
13.4.Costs
Each Party shall bear its own costs of ordinary compliance activities. Where an audit is required because of a demonstrated material breach by SeqOps, SeqOps shall bear its reasonable costs.
14.RETURN, EXPORT AND DELETION
14.1.Export period
Upon termination or expiry of the Services, the Controller shall have a period of thirty (30) calendar days to export Controller Personal Data using the functionality made available by SeqOps or otherwise agreed between the Parties.
14.2.Deletion
Following expiry of the export period, SeqOps shall delete Controller Personal Data within a further thirty (30) calendar days, unless:
- a.the Controller requests earlier deletion;
- b.retention is required by applicable law; or
- c.the Parties have agreed otherwise.
14.3.Backups
Controller Personal Data contained in backups shall be overwritten or deleted in accordance with SeqOps's documented backup-retention cycle and, in any event, within one hundred and eighty (180) days after deletion from active systems, unless a longer period is required by applicable law.
During that period, the data shall remain protected and shall not be restored or used except where necessary for disaster recovery, security or legal compliance. Where a backup is restored, Controller Personal Data that was previously subject to a valid deletion request shall be deleted again in accordance with the applicable deletion process.
14.4.Deletion confirmation
Upon reasonable request, SeqOps shall provide written confirmation that Controller Personal Data has been deleted in accordance with this Clause.
14.5.Legal retention
Where applicable law requires retention, SeqOps shall:
- a.inform the Controller unless prohibited by law;
- b.retain only the data required by law;
- c.restrict its use to the legally required purpose; and
- d.delete the retained data when the legal retention period expires.
15.CONFIDENTIALITY
Each Party shall keep confidential all Confidential Information received from the other Party in connection with this DPA.
SeqOps shall ensure that persons authorised to access Controller Personal Data are subject to confidentiality obligations.
Confidentiality obligations concerning security findings, vulnerabilities, credentials, system architecture and security information shall survive termination of the Main Agreement for so long as the information remains confidential.
Opsio and its personnel shall be subject to equivalent confidentiality obligations through the applicable sub-processing agreement.
16.REGULATORY COOPERATION
The Parties shall reasonably cooperate in responding to Supervisory Authorities concerning Processing under this DPA.
Nothing in this DPA shall require either Party to disclose information where prohibited by applicable law.
The Controller remains responsible for its communications with Supervisory Authorities concerning its role as Controller, except where SeqOps is required to communicate directly by law.
17.SECURITY AND REGULATORY REQUIREMENTS
17.1.NIS2 and other customer requirements
Where the Controller is subject to NIS2, the Swedish Cybersecurity Act, DORA or other sector-specific security requirements, the Parties may agree a separate security or regulatory addendum.
The DPA and Annex II establish the baseline Processing and security obligations but do not by themselves constitute a representation that SeqOps or the Services are certified or compliant with any specific regulatory framework.
17.2.Evidence
Where reasonably required for an enterprise customer, SeqOps may provide security documentation, questionnaires, audit reports and other reasonable evidence subject to confidentiality and security restrictions.
18.LIABILITY
18.1.Main Agreement
Unless otherwise required by Applicable Data Protection Law, liability arising under this DPA shall be governed by the liability provisions of the Main Agreement.
18.2.Mandatory liability
Nothing in this DPA shall exclude or limit liability to the extent such exclusion or limitation is prohibited by Applicable Data Protection Law.
18.3.Sub-processors
As between the Controller and SeqOps, SeqOps remains responsible for its Sub-processors as required by Applicable Data Protection Law.
19.TERM AND TERMINATION
This DPA shall commence on the Effective Date and remain in force for so long as SeqOps Processes Controller Personal Data.
Termination of the Main Agreement shall not relieve either Party of obligations that by their nature survive termination, including confidentiality, security, deletion and legally required retention obligations.
20.CHANGES TO THIS DPA
20.1.Changes required by law
SeqOps may amend this DPA where reasonably necessary to:
- a.comply with Applicable Data Protection Law;
- b.reflect changes to the Services or Processing; or
- c.implement guidance or decisions of competent Supervisory Authorities or courts.
20.2.Notice
Where an amendment materially affects the Controller's rights or obligations, SeqOps shall provide reasonable prior notice and publish the updated version in the Legal Centre.
20.3.SCCs
No amendment to this DPA shall modify the mandatory provisions of applicable SCCs.
21.ORDER OF PRECEDENCE
In the event of conflict:
- 1.mandatory provisions of Applicable Data Protection Law;
- 2.applicable SCCs;
- 3.this DPA;
- 4.the Main Agreement; and
- 5.other service documentation,
shall prevail in that order, but only to the extent of the conflict concerning data protection.
22.GOVERNING LAW AND DISPUTE RESOLUTION
This DPA shall be governed by the laws of Sweden.
Any dispute arising out of or in connection with this DPA shall be resolved in accordance with the dispute-resolution mechanism contained in the Main Agreement.
The Parties shall not apply separate or conflicting arbitration and court-jurisdiction provisions to the same dispute.
Nothing in this Clause prevents a Party from seeking urgent interim or protective relief from a competent court where permitted by law.
23.ELECTRONIC ACCEPTANCE
Where the Services are procured through the SeqOps self-service platform, this DPA may be accepted electronically by an authorised representative of the Controller through the applicable sign-up or contracting process.
Electronic acceptance shall constitute execution of this DPA between the Parties.
For enterprise customers, the DPA may instead be executed by authorised representatives of the Parties.
24.SEVERABILITY
If any provision of this DPA is held invalid or unenforceable, the remaining provisions shall remain in full force and effect.
The Parties shall replace the invalid or unenforceable provision with a valid provision that most closely reflects its intended purpose.
ANNEX I
PROCESSING DETAILS
A.Subject matter
Provision and operation of the SeqOps SaaS platform, including vulnerability and misconfiguration monitoring, Monitoring Agent functionality, cloud integrations, security analysis, prioritisation, reporting, remediation guidance, AI-assisted and agentic cybersecurity functionality through ACAP and associated VaultAI-enabled services, account and access management, support, maintenance, software development and related technical services.
B.Duration
For the duration of the Main Agreement and the period required for return/deletion of Controller Personal Data.
C.Nature of Processing
Processing may include:
- collection;
- recording;
- organisation;
- structuring;
- storage;
- retrieval;
- consultation;
- use;
- analysis;
- transmission;
- disclosure to authorised Sub-processors;
- restriction;
- deletion;
- destruction;
- authentication and authorisation of users and tenants;
- transmission and processing of user identifiers, tenant identifiers, access permissions and entitlement information;
- processing of user requests, prompts and instructions submitted through ACAP;
- AI-assisted analysis and generation of alerts, findings and recommendations;
- processing of tool requests, responses, workflow information and audit records, where applicable;
- interaction with authorised integrations and APIs, subject to the Controller’s configured permissions; and
- deletion and lifecycle management of tenant information.
D.Purpose
The purpose is to provide, secure, maintain, support and improve the Services, including AI-assisted and agentic cybersecurity functionality where enabled by the Controller, in accordance with the Controller's documented instructions and this DPA.
E.Categories of Data Subjects
As described in Clause 2.4.
F.Categories of Personal Data
As described in Clause 2.5.
G.Special Categories
The Services are not intended for the Processing of Special Categories of Personal Data.
If Special Categories are to be Processed, the Parties shall document the relevant Processing and safeguards in writing before such Processing begins.
ANNEX II
TECHNICAL AND ORGANISATIONAL MEASURES
SeqOps shall maintain technical and organisational measures appropriate to the risks associated with the Processing.
1.Access control
SeqOps shall maintain:
- role-based access controls;
- least-privilege principles;
- unique user accounts;
- privileged-access controls;
- multi-factor authentication where appropriate;
- periodic access reviews; and
- timely removal of access when personnel change roles or leave.
2.Authentication
SeqOps shall maintain appropriate controls for authentication credentials, including secure password practices and, where applicable, multi-factor authentication.
3.Encryption
Controller Personal Data shall be protected using encryption:
- in transit using appropriate industry-standard encryption; and
- at rest where supported by the relevant infrastructure and appropriate to the risk.
Cloud credentials, API keys, agent secrets and comparable sensitive authentication material shall be appropriately protected.
4.Secrets and credentials
Secrets, API keys and cloud credentials shall not be stored in plaintext where appropriate security controls can reasonably be implemented.
5.Logging and monitoring
SeqOps shall maintain appropriate security logging and monitoring for:
- authentication;
- privileged access;
- relevant administrative activity;
- security events; and
- material changes to production systems.
6.Vulnerability management
SeqOps shall maintain processes for identifying and addressing vulnerabilities affecting systems used to provide the Services.
7.Secure development
SeqOps shall maintain appropriate secure software-development practices, including:
- controlled development environments;
- code review where appropriate;
- dependency management;
- vulnerability assessment;
- separation of development and production environments where appropriate; and
- controlled deployment processes.
8.Production access
Production access shall be restricted to authorised personnel with a legitimate operational requirement.
Where technically feasible, production access shall be logged and monitored.
9.Opsio Pvt. Ltd. access
Because authorised Opsio personnel may have broad technical access to SeqOps systems and Controller Personal Data, SeqOps shall require and maintain appropriate controls designed to ensure that such access is controlled, attributable and auditable.
In particular:
- a.Opsio personnel shall use individually attributable accounts;
- b.shared administrator accounts shall be prohibited except where technically unavoidable and appropriately controlled;
- c.multi-factor authentication shall be used for privileged access where technically available;
- d.access shall be granted based on role and business need;
- e.privileged access shall be logged and monitored where technically feasible;
- f.access rights shall be reviewed periodically;
- g.access shall be revoked promptly when no longer required;
- h.Opsio personnel shall be bound by confidentiality obligations;
- i.Opsio personnel shall receive appropriate security and data protection training; and
- j.Opsio shall not use Controller Personal Data for any purpose other than providing authorised services to SeqOps.
10.Data minimisation
SeqOps shall seek to limit access to Controller Personal Data to the minimum reasonably required for the relevant service.
The existence of technical access capability shall not constitute authorisation to use Controller Personal Data for unrelated purposes.
11.Backup and recovery
SeqOps shall maintain backup and recovery procedures appropriate to the Services and risks, including controls designed to protect backup data against unauthorised access.
12.Business continuity
SeqOps shall maintain reasonable measures designed to support availability and restoration of the Services following technical or security incidents.
13.Incident management
SeqOps shall maintain procedures for identifying, assessing, containing, investigating and responding to security incidents and Personal Data Breaches.
14.Personnel security
Personnel with access to Controller Personal Data shall be subject to appropriate confidentiality obligations and security/data protection training.
15.Physical security
Physical infrastructure used to Process Controller Personal Data shall be protected through the security controls of SeqOps's hosting providers and other relevant service providers.
16.Hosting
The current SeqOps primary hosting environment is Amazon Web Services (AWS), eu-north-1 (Stockholm), Sweden.
Disaster-recovery copies of audit logs are maintained in Amazon Web Services, eu-central-1 (Frankfurt), Germany.
Any additional hosting, disaster-recovery, failover or infrastructure locations used to Process Controller Personal Data shall be appropriately documented and reflected in the applicable Sub-processor disclosures and transfer arrangements.
17.Data segregation
SeqOps shall maintain reasonable logical controls designed to prevent unauthorised access between customers' environments and data.
18.Testing and review
SeqOps shall periodically review and, where appropriate, test the effectiveness of relevant technical and organisational measures.
- 19.ACAP integration and Access Controls
Where ACAP functionality is enabled, SeqOps shall maintain appropriate technical and organisational measures designed to protect Controller Personal Data processed through the ACAP integration.
Such measures shall include, as applicable:
- a.signed access passes with a limited validity period, including the five-minute validity period used for the current integration;
- b.limitation of information transmitted through the SeqOps-to-ACAP integration to information reasonably necessary for user authentication, tenant identification, entitlement verification and operation of the integration;
- c.role-based access restrictions and enforcement of the applicable ACAP permissions;
- d.multi-factor authentication requirements for access to management functionality;
- e.restrictions on API access, including controls preventing write operations through API keys where such operations are not authorised;
- f.signed API requests, IP restrictions and rate limiting for service-to-service communications;
- g.logging and monitoring of relevant access, administrative activity and integration events;
- h.tenant-level segregation and access restrictions designed to prevent unauthorised access to another Controller's information;
- i.protection of signing keys, access passes, API credentials and other authentication material;
- j.controls designed to ensure that lifecycle and tenant-deletion instructions are appropriately processed; and
- k.appropriate controls over any third-party AI/model provider or external service involved in Processing Controller Personal Data.
For the initial ACAP pilot, SeqOps shall maintain a platform-wide technical control that prevents write operations through the ACAP connection, and ACAP-side write functionality shall remain disabled. Such controls shall be implemented and tested before the pilot is made available to customers.
Write functionality shall not be enabled until the Controller has separately authorised it in writing and the applicable technical, authentication, permission and logging controls have been implemented and tested.
Where write functionality is subsequently enabled, SeqOps shall ensure that actions are limited to the permissions and instructions authorised by the Controller and that additional confirmation controls are applied to high-risk actions, where appropriate.
ANNEX III
AUTHORISED SUB-PROCESSORS
The following Sub-processors are authorised as of the Effective Date.
| Sub-processor | Location | Function | Processing | Transfer mechanism |
|---|---|---|---|---|
| Amazon Web Services EMEA SARL, Sverige filial | Sweden / EEA. Primary SeqOps hosting in eu-north-1 (Stockholm), with disaster-recovery copies of audit logs in eu-central-1 (Frankfurt), Germany. | Cloud hosting and infrastructure | Hosting, storage, compute, databases, file storage, application infrastructure, backups, disaster recovery and related services | EEA |
| Functional Software, Inc. d/b/a Sentry | United States; EU-region processing in Germany, as configured. | Application monitoring, error reporting and diagnostic services | Technical logs, diagnostic information, application telemetry and error-reporting data that may contain Controller Personal Data. | Applicable Chapter V GDPR transfer mechanism and supplementary measures, where required. |
| Opsio AB | Sweden/EEA | Provision of services to SeqOps relating to software development, maintenance, technical support, infrastructure, operations and related technical services, including coordination of resources used to provide the Services. | Processing or access to Controller Personal Data to the extent required to provide the relevant services to SeqOps. | EEA. Any onward access or transfer to a non-EEA entity shall be documented separately and subject to the applicable transfer mechanism |
| Opsio Pvt. Ltd. | India | Downstream development, maintenance, technical support, infrastructure, operational and related technical resources provided to Opsio AB in connection with the SeqOps Services. | Access to and processing of Controller Personal Data, technical information, logs, configurations and SeqOps systems to the extent necessary to provide the relevant services. | Applicable SCC Module 3 (Processor-to-Processor) arrangement between the appropriate EEA data exporter and Opsio Pvt. Ltd., together with an appropriate transfer assessment and supplementary measures, where required. |
| GitHub, Inc. | United States | Source-code hosting, development collaboration and deployment-related services | Source code, technical information and deployment-related logs, including Controller Personal Data where such information is included in or accessible through the relevant services. | Applicable Chapter V GDPR transfer mechanism and supplementary measures, where required. |
1.Opsio
Opsio Pvt. Ltd. is expressly authorised as a Sub-processor notwithstanding that its authorised personnel may have broad technical access to SeqOps systems and Controller Personal Data.
Such access shall remain subject to Clause 5 and Annex II.
2.Sub-processor list
SeqOps shall maintain a current customer-facing Sub-processor list containing:
- name;
- location;
- service/function;
- categories of Processing; and
- applicable international-transfer mechanism.
ANNEX IV
MSP / PARTNER PROCESSING MODEL
1.Partner-sourced customers
Where an MSP, reseller or other partner procures or provides the Services to its own customer, the Parties shall document the applicable data-protection roles.
Depending on the actual arrangement:
Partner Controller → SeqOps Processor/Sub-processor → Opsio Sub-processor or:
End Customer Controller → Partner Processor → SeqOps Sub-processor → Opsio Sub-processor
2.Partner instructions
Where SeqOps acts as a Sub-processor to a Partner that acts as Processor for an End Customer, the Partner shall provide SeqOps with documented processing instructions and shall ensure that its agreement with the End Customer permits the relevant Processing and appointment of SeqOps as a Sub-processor.
3.Flow-down obligations
Where SeqOps acts as a Sub-processor to a Partner, SeqOps shall provide the Partner with data-protection obligations corresponding to those applicable to SeqOps as a processor, to the extent required by Applicable Data Protection Law.
4.Opsio
Where Opsio is used in such a Partner processing chain, the relevant structure shall be:
End Customer → Partner → SeqOps AB → Opsio AB → Opsio Pvt. Ltd.
The actual processing roles and contractual relationships shall be determined by the relevant customer and partner arrangement.
Each relevant processing and sub-processing relationship, including any onward transfer or access from outside the EEA, shall be documented and supported by the applicable data-processing agreements and transfer safeguards.
5.Assistance
SeqOps shall provide reasonable assistance to the Partner in accordance with the applicable DPA and Applicable Data Protection Law.
6.End-customer rights
Where the Partner is the Processor and the End Customer is the Controller, SeqOps shall provide reasonable assistance to the Partner in responding to Data Subject requests and regulatory obligations, taking into account the nature of SeqOps's Processing.
ANNEX V
INTERNATIONAL TRANSFER FRAMEWORK
1.Transfer mechanism
Where Controller Personal Data is transferred from the EEA to a recipient outside the EEA and no adequacy decision applies, the Parties shall use an applicable Article 46 transfer mechanism.
2.SCC Module 2
Where the Controller is the data exporter and SeqOps is the data importer, the Parties shall use SCC Module 2 (Controller-to-Processor) where required.
3.SCC Module 3 — Opsio Pvt. Ltd.
Where Controller Personal Data is transferred or made accessible from the EEA to Opsio Pvt. Ltd. in India through the Opsio sub-processing arrangement, the applicable SCC Module 3 (Processor-to-Processor) shall be executed between the appropriate EEA data exporter and Opsio Pvt. Ltd. as data importer, where required by Applicable Data Protection Law.
Where Opsio AB is the relevant EEA exporter and Opsio Pvt. Ltd. is the Indian importer, the applicable transfer documentation shall reflect that relationship.
The SCCs shall be completed with the relevant parties, processing details and technical and organisational measures and shall not be modified except as permitted by the SCCs.
4.Opsio transfer assessment
The relevant transfer or access involving Opsio Pvt. Ltd. in India shall be assessed having regard to:
- the actual contractual and processing chain;
- the categories of Controller Personal Data potentially accessible;
- the technical access available to authorised personnel of Opsio AB and Opsio Pvt. Ltd.
- the purpose and method of access;
- the location of the relevant personnel and systems;
- applicable Indian law and practices relevant to the transfer;
- the technical and organisational measures maintained by the relevant entities;
- encryption and authentication controls;
- access logging and monitoring;
- confidentiality obligations; and
- the availability and effectiveness of supplementary measures.
SeqOps shall maintain evidence of the applicable transfer mechanism, transfer assessment and supplementary measures and shall make relevant information available to the Controller upon reasonable request.
5.Transfer impact assessment
For transfers requiring an assessment, SeqOps shall maintain an appropriate transfer assessment addressing:
a. the nature of the transfer;
b. the data involved;
c. the destination;
d. the applicable transfer mechanism;
e. relevant laws and practices in the destination country;
f. the likelihood and impact of access by public authorities;
g. technical measures;
h. organisational measures; and
i. contractual safeguards.
6.Supplementary measures
Where required, supplementary measures may include:
a. encryption in transit;
b. encryption at rest;
c. strong authentication;
d. individual user accounts;
e. least-privilege access;
f. access logging;
g. privileged-access controls;
h. contractual restrictions on use and disclosure;
i. confidentiality obligations;
j. personnel training;
k. incident response procedures; and
l. procedures concerning government-access requests.
- 7.ACAP and VaultAI transfers
Before Controller Personal Data is made available to ACAP, VaultAI or any underlying hosting, AI/model or external service provider located outside the EEA, SeqOps shall identify the relevant legal entity, destination country, transfer route and applicable transfer mechanism.
Where a Restricted Transfer is involved, SeqOps shall implement the applicable Chapter V GDPR transfer mechanism, including the relevant SCC module where required, together with an appropriate transfer assessment and supplementary measures.
The relevant transfer arrangements and providers shall be reflected in Annex III and the applicable contractual documentation before the relevant Processing begins.
ANNEX VI
DATA RETENTION AND EXIT
1.Active data
Controller Personal Data remains available in the Services for the duration of the subscription, subject to the Main Agreement.
2.Export
Following termination, the Controller shall have thirty (30) calendar days to export its data.
3.Deletion
SeqOps shall delete active Controller Personal Data within the following thirty (30) calendar days, subject to legal retention requirements.
4.Backups
Backup copies of Controller Personal Data shall expire in accordance with SeqOps's documented backup-retention cycle and, in any event, within one hundred and eighty (180) days after deletion from active systems, subject to Clause 14.3 of the DPA.
During the backup-retention period, the data shall remain protected and shall not be restored or used except where necessary for disaster recovery, security or legal compliance.
Where a backup is restored, Controller Personal Data previously subject to a valid deletion request shall be deleted again in accordance with the applicable deletion process.
5.Certification
Upon request, SeqOps shall provide written confirmation of deletion.
ANNEX VII
DOCUMENT CONTROL
Document: Data Processing Agreement Version: 2.1 Effective Date: 03 November 2026 Previous Version: 1.0 / March 2026 Owner: SeqOps AB Next Review: 03 November 2027
By ticking the box below, you confirm that you have read, understood and agreed to the provisions contained in this DPA.