#Record of changes
26/10/2026 – Creation and publication of the first version of the data protection annex for the services of the soc.luxgap.com platform.
#Introduction
This Data Protection Annex (hereinafter the “Agreement” or “DPA”) governs the processing of personal data carried out by Luxgap Sàrl (“Luxgap”) in the context of the provision of the services of the soc.luxgap.com platform. It supplements the Contract and/or Terms of Use entered into between Luxgap and the Client and forms an integral part thereof.
Where Luxgap processes personal data on behalf of the Client in the context of the provision of the platform, Luxgap acts as Processor and the Client as Controller. This Agreement sets out Luxgap’s commitments in accordance with Article 28 of the GDPR.
In the event of any conflict between this Agreement and the Terms of Use on matters relating to the protection of personal data, this Agreement shall prevail. Luxgap may update this Agreement in order to reflect legal, regulatory or technical developments; the applicable version and its effective date are shown at the top of the document and in the record of changes.
This Agreement is drawn up in French. In the event of any discrepancy between the French version and a translation, the French version shall prevail.
#Article 1. Definitions
For the purposes of this Agreement, the following terms are defined as follows:
“Data Protection Legislation”: The General Data Protection Regulation ((EU) 2016/679, “GDPR”), (ii) the Luxembourg Law of 1 August 2018 implementing the GDPR into national law, and (iii) any applicable national legislation, including secondary regulations and legislation;
“Data of a personal nature” or “Personal data”: Any information relating to an identified or identifiable natural person; an “identifiable natural person” is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
“Contract”: The main contract under which personal data will be exchanged and processed and to which this Agreement may be annexed;
“Data subject”: The natural person whose data are processed;
“Controller”: The entity which, alone or jointly with others, determines the purposes and means of the processing;
“Processor”: The entity which processes personal data on behalf of the Controller and in accordance with its instructions;
“Sub-processor”: Any processor engaged by the Processor to carry out specific processing activities on behalf of the Controller, in accordance with the conditions of Article 4.6 of this Agreement;
“Processing”: Any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction;
“Data protection impact assessment”: An assessment carried out prior to the processing of personal data where it is likely to result in a high risk to the rights and freedoms of data subjects;
“Personal data breach”: A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed;
“Third country”: Any country outside the scope of the data protection legislation of the European Economic Area (“EEA”).
#Article 2. Purpose and Scope
The purpose of this Agreement is to define the respective rights and obligations of the Parties concerning the processing of personal data carried out by the Processor on behalf of the Controller under the Contract.
This Agreement applies to all processing of personal data carried out by the Processor on behalf of the Controller in the performance of the Contract, as described in Appendix 1. It is binding on the Processor and on any person acting under its authority who has access to the personal data.
#Article 3. Term
This Agreement enters into force on the date of entry into force of the Contract and/or Terms of Use and remains valid for the entire term of said Contract. It shall remain applicable for as long as the Processor processes personal data on behalf of the Controller, as specified in Appendix 1.
#Article 4. Obligations of the Parties
#4.1. Description of the processing
- (a)The details of the processing operations, in particular the categories of personal data and the purposes of the processing for which the personal data are processed on behalf of the Controller, are specified in Appendix 1.
- (b)Where the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (“sensitive data”), the Processor shall apply specific restrictions and/or additional safeguards.
#4.2. Instructions
- (a)The Processor shall process personal data only on documented instructions from the Controller, unless required to do so by Union or Member State law to which the Processor is subject. In such a case, the Processor shall inform the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest. Subsequent instructions may also be given by the Controller throughout the duration of the processing of personal data. Such instructions shall always be documented.
- (b)The Processor shall immediately inform the Controller if, in its opinion, instructions given by the latter infringe the data protection legislation.
#4.3. Purpose limitation
The Processor shall process the personal data only for the specific purposes defined in Appendix 1, unless it receives further instructions from the Controller.
#4.4. Security of processing and confidentiality
- (a)The Processor shall implement, as a minimum, the technical and organisational measures specified in Appendix 2 to ensure the security of the personal data. This includes protecting the data against a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of the processing and the risks involved for the data subjects.
- (b)The Processor shall grant access to the personal data undergoing processing only to members of its staff authorised for the implementation, management or monitoring of the contract. The Processor shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
#4.5. Documentation and compliance
- (a)The Processor shall make available to the Controller, on request, all information necessary to demonstrate compliance with the obligations laid down in this Agreement.
- (b)If the Controller has reason to believe that the processing of personal data by the Processor or by a sub-processor does not comply with the provisions of this Agreement, it reserves the right to verify, directly or through an independent external auditor of its choice, the Processor’s compliance with its obligations.
- (c)Audits may also include inspections at the premises or physical facilities of the Processor and shall, where appropriate, be carried out with reasonable notice.
- (d)The Parties shall make the information referred to in this clause, including the results of any audits, available to the competent supervisory authority on request.
#4.6. Use of sub-processors
- (a)The Processor has the Controller’s general authorisation for the engagement of sub-processors. The list of sub-processors engaged is set out in Appendix 3.
- (b)The Processor shall inform the Controller in writing of any intended changes to that list through the addition or replacement of a sub-processor at least thirty (30) days in advance of implementation. This allows the Controller to object to such changes prior to the engagement of the sub-processor(s) concerned. Any objection must be justified and proportionate to the interests of the parties.
- (c)Where the Processor engages a sub-processor for carrying out specific processing activities (on behalf of the Controller), it shall do so by way of a written contract which imposes on the sub-processor, in substance, the same data protection obligations as those imposed on the Processor under this Agreement.
- (d)At the Controller’s request, the Processor shall provide a copy of the contract entered into with the sub-processors and of any subsequent amendments. To the extent necessary to protect business secrets or other confidential information, including personal data, the Processor may redact parts of the contract prior to sharing a copy.
- (e)The Processor shall remain fully responsible to the Controller for the performance of the sub-processor’s obligations under its contract with the latter.
#4.7. International transfers
- (a)Any transfer of data to a third country or an international organisation by the Processor may only be carried out on the basis of an agreement or documented instructions from the Controller, or in order to fulfil a specific requirement under the data protection legislation to which the Processor is subject. Such transfer shall be carried out in compliance with Chapter V of the GDPR.
- (b)The Controller agrees that where the Processor engages a sub-processor for carrying out specific processing activities which involve a transfer of personal data within the meaning of Chapter V of the GDPR, the Processor and the sub-processor can ensure compliance with that Chapter by using standard contractual clauses adopted by the Commission in accordance with Article 46(2) of the GDPR, provided the conditions for the use of those clauses are met. The list of sub-processors, including, where applicable, transfers outside the European Union to third countries, is set out in Appendix 3 of this Agreement. Such transfers are deemed accepted by the Controller.
#Article 5. Assistance to the Controller
- (a)The Processor shall notify the Controller without delay, and in any event within a maximum of five (5) working days, of any request it has received from a data subject. It shall not respond to the request itself, unless expressly authorised to do so by the Controller.
- (b)The Processor shall assist the Controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing.
- (c)The Processor shall also assist the Controller in ensuring compliance with the following obligations, taking into account the nature of the processing and the information available to it:
- 1)The obligation to carry out a data protection impact assessment where the type of processing envisaged is likely to result in a high risk to the rights and freedoms of natural persons;
- 2)The obligation to consult the competent supervisory authority prior to processing where the impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the Controller to mitigate the risk;
- 3)The obligation to ensure that personal data are accurate and up to date, by informing the Controller without delay if the Processor becomes aware that the data it is processing are inaccurate or have become outdated.
#Article 6. Notification of personal data breaches
(a) The Processor shall cooperate with and assist the Controller for the purpose of complying with its obligations under Articles 33 and 34 of the GDPR, whichever is applicable, taking into account the nature of the processing and the information available to the Processor.
(b) In the event of a personal data breach concerning data processed by the Controller, the Processor shall assist the controller:
- 1)in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the Controller has become aware of it, where relevant (unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);
- 2)in obtaining the following information which, pursuant to the data protection legislation, shall be stated in the Controller’s notification, and must at least include:
- the nature of the personal data, including where possible the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
- the likely consequences of the personal data breach;
- the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
(c) In the event of a personal data breach concerning data processed by the Processor, the latter shall notify the Controller without undue delay and at the latest forty-eight (48) hours after having become aware of it. Such notification shall contain at least:
- 1)a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);
- 2)the details of a contact point where more information concerning the personal data breach can be obtained;
- 3)its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.
- (d)Where, and insofar as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
#Article 7. Fate of personal data
- (a)Processing by the Processor shall only take place for the duration specified in Appendix 1. After the end of the provision of the processing services, the Processor shall, at the choice of the Controller, delete all personal data processed on behalf of the latter and certify to it that it has done so, or return all the personal data processed on its behalf and delete existing copies.
- (b)Where the law applicable to the Processor prohibits the return or deletion of the personal data, the Processor shall ensure that the personal data are processed only to the extent and for as long as required under that law.
#Article 8. Data Protection Officer
The Processor shall communicate to the Controller the name and contact details of its Data Protection Officer in Appendix 1, if it has designated one in accordance with Article 37 of the GDPR.
#Article 9. Non-compliance with the clauses and termination
- (a)Without prejudice to any provisions of the GDPR, in the event that the Processor is in breach of its obligations under these clauses, the Controller may instruct it to suspend the processing of personal data until it complies with these clauses, or terminate the contract. The Processor shall promptly inform the Controller in case it is unable to comply with these clauses, for whatever reason.
- (b)The Controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these clauses if:
- 1)the processing of personal data has been suspended by the Controller pursuant to point (a) and compliance with these clauses is not restored within a reasonable time and in any event within one month following suspension;
- 2)the Processor is in substantial or persistent breach of these clauses or its obligations under the data protection legislation;
- 3)the Processor fails to comply with a binding decision of a competent court or the competent supervisory authority regarding its obligations under these clauses or under the applicable data protection legislation.
- (c)The Processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these clauses where, after having informed the Controller that its instructions infringe applicable legal requirements in accordance with Clause 4.2, the Controller insists on compliance with the instructions.
#Article 10. Miscellaneous
- (a)If any provision of this Agreement is held to be unlawful, invalid or unenforceable, in whole or in part, that provision shall be deemed not to form part of the Agreement, without affecting the lawfulness, validity or enforceability of the other provisions of this Agreement.
- (b)In such case or in the event of a missing provision, the Controller undertakes to notify the Processor immediately and in good faith so that the latter can put in place a new valid provision replacing the inapplicable or missing provision of the DPA.
- (c)The Agreement is governed by and construed in accordance with the applicable Luxembourg law. Any dispute arising out of or in connection with the Agreement shall be submitted to the exclusive jurisdiction of the courts of Luxembourg if it could not first be settled amicably.
#Appendix 1 Description of the processing
| Purposes of the processing | Provision, operation and maintenance of the soc.luxgap.com security monitoring platform, including the management of accounts and access, the collection and analysis of security logs and events from the sources connected by the Client, the detection and qualification of alerts, incident management and, where the contract so provides, the performance of response actions, the monitoring of security posture, exposure and compliance, reporting, the sending of notifications, support, as well as security and abuse prevention. The processing is limited to the documented instructions of the Controller. |
|---|---|
| Means and nature of the processing | Automated processing via the platform, hosted by OVHcloud, in France, and intervention by Luxgap analysts. The artificial intelligence features rely on models operated by Luxgap and, for certain features, on the third-party model provider listed in Appendix 3. Where the Client provides its own access key to a model provider, that provider does not act as a sub-processor of Luxgap. Luxgap does not use client content to train, improve or enrich AI models. |
| Categories of personal data processed | Users’ identification and account data (name, business e-mail address, role, language, authentication data); Security logs and events from the connected sources, including in particular account identifiers, IP addresses, workstation and device names, timestamps and activity information; Data relating to alerts, incidents, investigations and response actions, including the accounts and resources concerned; Data relating to the Client’s exposure, in particular identifiers and e-mail addresses found in data leaks or publicly available sources; Content entered or uploaded by the Client (registers, contacts, documents, reports), which may contain personal data relating to the Client or to third parties; Technical data (audit logs, timestamps, IP addresses, technical identifiers). The platform is not intended for the processing of special categories of data (sensitive within the meaning of Article 9 of the GDPR); where applicable, their presence falls under the responsibility and instructions of the Client. |
| Categories of data subjects | Authorised users of the Client, staff of the Client and other users of the monitored information systems, contacts of the Client and of its suppliers recorded in the platform, persons whose identifiers linked to the Client appear in data leaks and, where applicable, any natural person whose data appear in the Client’s content or logs. |
| Place(s) of processing of personal data | European Union. Hosting of the application, the database and the collected logs in France (OVHcloud). Other places of processing are listed in Appendix 3. |
| Duration of the processing | Term of the Contract. The collected logs are retained for the period agreed with the Client; backups are retained according to a limited retention cycle. Thereafter, the data are deleted or returned in accordance with Article 7; backup copies are erased at the end of their retention cycle. |
| Legal basis for the processing | Processing by the Processor is based on the Contract and the documented instructions of the Controller (Article 28 of the GDPR). Determining the legal basis for the processing with regard to the data subjects is the responsibility of the Controller. |
| Contact point of each Party | Main contact point Processor: Luxgap Sàrl, 2 rue de l’École, L-8376 Kahler - contact@luxgap.com - +352 621 583 116. Data Protection Officer (DPO) Luxgap: dpo@luxgap.com. |
| Persons designated as authorised to carry out the processing activities | Members of Luxgap’s staff authorised for the implementation, management or monitoring of the Contract and subject to a duty of confidentiality. |
| Third countries to which personal data are transferred (if applicable) | United States, for the artificial intelligence features using the third-party model provider listed in Appendix 3. Residual access from a third country by a sub-processor may only take place if it is subject to appropriate safeguards within the meaning of Chapter V of the GDPR. |
| ADEQUACY Decision (if applicable) | Not applicable: no adequacy decision is relied upon. Transfers to the United States are governed by the standard contractual clauses adopted by the Commission (Implementing Decision (EU) 2021/914), incorporated into the data processing agreement of the provider concerned. |
#Appendix 2 Technical and organisational measures to ensure the security of the data
The Processor implements and maintains the following technical and organisational measures in order to ensure a level of security appropriate to the risk. These measures are regularly reassessed in the light of the state of the art, the nature of the processing and the risks to the data subjects.
#Security governance
Documented cybersecurity policy reviewed at least annually, risk analysis performed annually and upon any significant change.
#Hosting and physical security
Hosting by OVHcloud, in France. The physical security of the site is the responsibility of OVHcloud and relies on the certifications it publishes for its data centres.
#Network isolation
Database with no external exposure, single public entry point and administration through a VPN.
#Encryption
Communications encrypted using HTTPS. Application-level encryption of the most sensitive data, in particular secrets for access to the connected sources, password hashing and encryption of backups.
#Access management
Segregation of data between clients, role-based access rights, two-factor authentication, protection against repeated login attempts and time-limited sessions.
#Application security
Protection against common web attacks and containerised execution environment. The artificial intelligence features rely on models operated by Luxgap and, for certain features, on the third-party model provider listed in Appendix 3; certain data sources are never transmitted to an artificial intelligence model.
#Logging and detection
Traceability of sensitive actions, in particular logins, account management, exports and access by Luxgap staff to a user account, monitored by LuxGap Safety. Audit logs do not contain passwords.
#Backup and continuity
Daily encrypted backup of the database, with an off-site copy, retained according to a limited retention cycle.
#Secure development
Automated checks before any release to production, continuous updating of dependencies and storage of secrets outside the code.
#Awareness and training
Mandatory annual staff training in information security.
#Incident management
Documented procedures for the detection of, response to and notification of security incidents, with post-incident analysis.
#Appendix 3 List of sub-processors
| Name of the entity | Address | Name, position and contact details of the contact person | Nature of the service |
|---|---|---|---|
| OVH SAS (OVHcloud) | 2 rue Kellermann, 59100 Roubaix, France | Data Protection Officer - dpo@ovhcloud.com | Hosting of the application, the database, the collected logs and the backups on a server located in France. |
| Microsoft Ireland Operations Ltd | One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland | Microsoft Data Protection Officer - via the Microsoft privacy portal | Storage of an encrypted off-site backup copy in OneDrive (Microsoft 365), within the EU Data Boundary. |
| Anthropic Ireland, Limited | 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland | Data Protection Officer - dpo@anthropic.com | Provision of artificial intelligence models for certain features of the platform. Processing may take place in the United States. |