Data Processing Agreement
Last updated: 1 February 2026
This Data Processing Agreement ("DPA") forms part of the agreement between Maecos BV ("Processor") and the customer ("Controller") for the use of the Maecos platform (the "Agreement"). By using the Maecos platform, the Controller accepts the terms of this DPA.
Processor: Maecos BV, Kerkstraat 127, 2060 Antwerpen, Belgium (BE 0769.475.264).
Controller: The entity identified in the Agreement.
1. Definitions
In this DPA, unless the context requires otherwise:
- "Personal Data" means any information relating to an identified or identifiable natural person that is processed by the Processor on behalf of the Controller through the Maecos platform.
- "Processing" means any operation performed on Personal Data, including collection, storage, retrieval, use, disclosure, and erasure.
- "Data Protection Laws" means Regulation (EU) 2016/679 (GDPR) and any applicable national implementing legislation.
- "Sub-processor" means any third party engaged by the Processor to process Personal Data on behalf of the Controller.
- "Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to Personal Data.
2. Scope and Purpose of Processing
The Processor processes Personal Data solely to provide the Maecos connected operator platform and related services as described in the Agreement. The details of the processing are as follows:
| Subject matter | Provision of the Maecos platform for manufacturing operations management, including data capture, workflow execution, quality management, and reporting. |
| Duration | The term of the Agreement, plus any retention period described in Section 10. |
| Nature and purpose | Automated and manual processing of Personal Data to operate the platform, execute workflows, generate reports, and provide technical support. |
| Categories of data subjects | Employees and operators of the Controller, contractors and temporary workers, and other individuals whose data the Controller enters into the platform. |
| Types of Personal Data | Names, email addresses, job titles, login credentials (hashed), activity logs and timestamps, data entered into forms, checklists, and documents, and uploaded files that may contain Personal Data. |
| Special categories | The Processor does not intentionally process special category data. If the Controller enters such data into the platform, the Controller is responsible for ensuring a lawful basis exists. |
3. Obligations of the Processor
The Processor shall:
- Process Personal Data only on documented instructions from the Controller, unless required by EU or Member State law. In such case, the Processor shall inform the Controller before processing, unless prohibited by law.
- Ensure that persons authorised to process Personal Data have committed to confidentiality or are under an appropriate statutory obligation of confidentiality.
- Implement and maintain the technical and organisational security measures described in Section 6.
- Respect the conditions for engaging Sub-processors as set out in Section 5.
- Assist the Controller, taking into account the nature of the processing, with appropriate technical and organisational measures for fulfilling data subject requests under Chapter III of the GDPR.
- Assist the Controller in ensuring compliance with Articles 32 to 36 of the GDPR, taking into account the nature of processing and the information available to the Processor.
- At the choice of the Controller, delete or return all Personal Data after the end of the provision of services, as described in Section 10.
- Make available to the Controller all information necessary to demonstrate compliance with this DPA and allow for and contribute to audits as described in Section 9.
4. Obligations of the Controller
The Controller shall:
- Ensure that any instructions given to the Processor regarding the processing of Personal Data comply with Data Protection Laws.
- Ensure a lawful basis exists for the processing of Personal Data by the Processor.
- Be solely responsible for the accuracy, quality, and legality of Personal Data provided to the Processor.
- Inform the Processor without undue delay if the Controller becomes aware of any data protection issues that may affect the processing.
5. Sub-processors
5.1 General authorisation
The Controller provides general authorisation for the Processor to engage Sub-processors. The current list of Sub-processors is available at maecos.com/legal/subprocessors.
5.2 Notification of changes
The Processor shall notify the Controller at least 30 days before adding or replacing a Sub-processor, giving the Controller the opportunity to object. The notification will include the identity of the Sub-processor, the processing it will perform, and its location.
5.3 Right to object
If the Controller has reasonable grounds to object to a new Sub-processor, the Controller shall notify the Processor in writing within 14 days of receiving the notification. The Parties shall discuss the objection in good faith. If no resolution is reached, the Controller may terminate the affected services without penalty.
5.4 Sub-processor obligations
The Processor shall impose on each Sub-processor, by way of a written contract, data protection obligations no less protective than those set out in this DPA. The Processor remains fully liable to the Controller for the performance of each Sub-processor.
6. Security Measures
The Processor shall implement and maintain technical and organisational measures appropriate to the risk, including:
- Encryption: All data encrypted in transit (TLS 1.2+) and at rest (AES-256).
- Access control: Role-based access, multi-factor authentication for administrative access, principle of least privilege.
- Tenant isolation: Each customer environment is fully isolated with separate compute containers, storage, and database schemas.
- Network security: Private networking, firewalls, intrusion detection, and regular vulnerability scanning.
- Monitoring: Continuous infrastructure and application monitoring with automated alerting.
- Backup: Automated daily and monthly backups stored in a geographically separate location within the EU.
- Personnel: Background checks, mandatory security training, and confidentiality agreements for all staff with access to customer data.
Full details of the security program are described at maecos.com/security.
7. Data Breach Notification
7.1 Notification to Controller
The Processor shall notify the Controller without undue delay, and in any event within 72 hours, after becoming aware of a Data Breach affecting the Controller's Personal Data.
7.2 Content of notification
The notification shall include, to the extent available:
- A description of the nature of the breach, including the categories and approximate number of data subjects and records concerned.
- The name and contact details of the Processor's contact point for further information.
- A description of the likely consequences of the breach.
- A description of the measures taken or proposed to address the breach and mitigate its effects.
7.3 Ongoing cooperation
The Processor shall cooperate with the Controller and provide additional information as it becomes available. The Processor shall not notify any supervisory authority or data subject on behalf of the Controller unless explicitly instructed to do so.
8. International Data Transfers
The Processor stores and processes all customer data within the European Economic Area (EEA). The primary data centre is located in the EU (AWS eu-west-1, Ireland).
If a Sub-processor processes Personal Data outside the EEA, the Processor shall ensure that an adequate transfer mechanism is in place, such as:
- An adequacy decision by the European Commission.
- Standard Contractual Clauses (SCCs) as adopted by the European Commission.
- Binding Corporate Rules approved by the relevant supervisory authority.
The Sub-processor list at maecos.com/legal/subprocessors indicates the location of each Sub-processor.
9. Audits and Inspections
The Processor shall make available to the Controller all information reasonably necessary to demonstrate compliance with this DPA.
The Controller (or a mandated third-party auditor bound by confidentiality) may conduct an audit of the Processor's processing activities, subject to the following conditions:
- The Controller provides at least 30 days' written notice.
- Audits are conducted during normal business hours and no more than once per year, unless required by a supervisory authority or following a Data Breach.
- The Controller bears its own costs. If the audit requires material effort from the Processor beyond making information available, the Parties shall agree on reasonable compensation.
- The auditor shall not access data belonging to other customers of the Processor.
10. Data Retention and Deletion
10.1 During the Agreement
The Processor retains Personal Data for as long as necessary to provide the services under the Agreement and as instructed by the Controller.
10.2 After termination
Upon termination or expiry of the Agreement, the Processor shall:
- Data export: Make the Controller's data available for export in a standard machine-readable format for a period of 30 days. Data export is available as a paid service.
- Deletion: After the 30-day export window, or upon written request from the Controller, delete all Personal Data from production systems within 30 days. Copies in backups will be overwritten in accordance with the regular backup rotation cycle.
10.3 Certification
Upon request, the Processor shall provide written confirmation that deletion has been completed.
11. Data Subject Requests
If the Processor receives a request from a data subject to exercise their rights under the GDPR (access, rectification, erasure, restriction, portability, or objection), the Processor shall:
- Promptly notify the Controller of the request.
- Not respond to the request directly unless authorised by the Controller.
- Assist the Controller with fulfilling the request, taking into account the nature of the processing.
The Controller can fulfil most data subject requests directly through the platform's administrative interface.
12. Liability
Each Party's liability under this DPA is subject to the limitations of liability set out in the Agreement. Nothing in this DPA limits either Party's liability for breaches of Data Protection Laws to the extent such limitation is not permitted by applicable law.
13. Term and Termination
This DPA takes effect on the date the Agreement is executed and remains in force for as long as the Processor processes Personal Data on behalf of the Controller. Sections that by their nature should survive termination (including Sections 7, 10, and 12) shall survive.
14. Amendments
This DPA may be amended by the Processor to reflect changes in Data Protection Laws or supervisory authority guidance. Material changes will be communicated to the Controller at least 30 days before they take effect. Continued use of the services after the effective date constitutes acceptance of the updated DPA.
15. Governing Law
This DPA is governed by the laws of Belgium. Any disputes arising from this DPA shall be submitted to the courts of Antwerpen, Belgium, unless mandatory provisions of Data Protection Laws require otherwise.
16. Contact
Questions about this DPA or data processing? Contact us at privacy@maecos.com.