Annex 1: Data Processing Agreement
Version 1.0, effective 2026-11-01. Also published at https://www.docnaut.com/legal/data-processing-agreement.
1. Parties, scope and order of precedence
1.1 This Data Processing Agreement ("DPA") is entered into between Eaglessoft BV, Excelsiorlaan 31, 1930 Zaventem, Belgium — enterprise number 1025.494.094, RLE Brussels (Dutch-speaking enterprise court) ("Eaglessoft"), and the Customer that has accepted the DocNaut Terms of Service (the "Terms"). It forms Annex 1 of the Terms and is accepted together with them. Capitalised terms not defined in this DPA have the meaning given in the Terms or in the GDPR.
1.2 This DPA applies to Personal Data that Eaglessoft processes on behalf of the Customer when providing the Services ("Customer Personal Data"). It meets the requirements of Article 28(3) of Regulation (EU) 2016/679 (the "GDPR").
1.3 If there is a conflict between this DPA and the Terms on the processing of Customer Personal Data, this DPA prevails. A data processing agreement signed between Eaglessoft and the Customer, for example as part of a signed Customer Addendum, prevails over this DPA on the processing of personal data. For liability, governing law and courts, the Terms apply unless that agreement expressly provides otherwise.
1.4 Where an End Customer obtains the Services through a Partner under a contract with that Partner only, the Partner is Eaglessoft's counterparty for this DPA, as set out in the DocNaut Partner Terms (https://www.docnaut.com/legal/partner-terms). In that case Eaglessoft acts as the Partner's sub-processor, the End Customer being the controller, or, where the Partner is itself the controller of that data, as the Partner's processor, and references in this DPA to the Customer are references to the Partner.
2. Roles of the parties
2.1 Eaglessoft as processor. For the content of the Documents the Customer sends and receives through the Services, and the Personal Data in them, the Customer is the controller and Eaglessoft is the processor. Where the Customer itself acts as a processor for its own clients (for example an accounting firm), Eaglessoft acts as the Customer's sub-processor, and the Customer is responsible for obtaining any authorisation its controller requires.
2.2 Eaglessoft as controller. Eaglessoft is an independent controller, and this DPA does not apply, for the Personal Data it processes for its own purposes. These are: user accounts and authentication, customer and partner verification (KYB/KYC), support, contracts and billing, security and access logs, registration of the Customer on the Peppol network, and the Peppol activity logs that Eaglessoft must keep and disclose under the Peppol rules. That processing is described in the Eaglessoft Privacy Policy at https://eaglessoft.com/privacy-policy/. The technical metadata of each transmission is therefore processed in two roles: as processor, to deliver the Documents, and as controller, only to keep and disclose the logs that the Peppol rules require.
2.3 The Customer is responsible for the lawfulness of the processing it instructs, including having a legal basis for it and for sending Documents to their recipients, and for informing the data subjects concerned.
3. Details of the processing
The subject matter, duration, nature and purpose of the processing, the types of Personal Data and the categories of data subjects are described in Appendix A.
4. Instructions
4.1 Eaglessoft processes Customer Personal Data only on the Customer's documented instructions, including with regard to transfers outside the EU/EEA, unless EU or Member State law requires otherwise. In that case Eaglessoft informs the Customer of that legal requirement before processing, unless that law prohibits it on important grounds of public interest.
4.2 The Customer's documented instructions are: the Terms and this DPA; the Customer's configuration and use of the Services, including the Documents it submits, the recipients and networks it selects and its API calls; and any further written instructions agreed between the parties. Additional instructions outside the scope of the Services require Eaglessoft's agreement and may be charged at Eaglessoft's rates then in force.
4.3 Eaglessoft informs the Customer without delay if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection law. Eaglessoft may suspend the execution of that instruction until the Customer confirms or changes it.
5. Confidentiality
Eaglessoft ensures that persons authorised to process Customer Personal Data are bound by a contractual or statutory duty of confidentiality, receive appropriate data protection training, and access Customer Personal Data only where needed to provide the Services, support the Customer or meet a legal obligation. Access to Customer Personal Data is restricted to authorised personnel resident in the EU/EEA. Access by personnel outside the EU/EEA is permitted only where it has been individually assessed and approved by Eaglessoft's Data Protection Officer and Information Security Manager and recorded under its information security management system, and is protected by encrypted connections, multi-factor authentication and access logging.
6. Security of processing
6.1 Eaglessoft implements and maintains appropriate technical and organisational measures to protect Customer Personal Data, in line with Article 32 GDPR. The measures are described in Appendix B.
6.2 DocNaut is operated under Eaglessoft BV's information security management system, certified to ISO/IEC 27001:2022 (certificate 1754-01) and ISO/IEC 27701 (certificate 1754-02). The certificates can be verified on IAF CertSearch (https://www.iafcertsearch.org/certified-entity/DWlWwwEVFfw5Qdpjz27L9cib), and Eaglessoft provides copies on request.
6.3 Eaglessoft may update its measures as technology and risks change, provided the overall level of protection is not reduced. Eaglessoft reviews the measures at least once a year.
6.4 The Customer is responsible for the security of its own systems, integrations and credentials, for the configuration of its users and access rights, and for not sending special categories of Personal Data (Article 9 GDPR) or data relating to criminal convictions (Article 10 GDPR) through the Services, except where a Document lawfully requires it.
7. Sub-processors
7.1 General authorisation. The Customer gives Eaglessoft a general authorisation to engage sub-processors. The sub-processors in use on the date of acceptance are listed in Annex 2 of the Terms and at https://www.docnaut.com/legal/sub-processors. Eaglessoft provides, on request, information on the sub-processors used by its sub-processors.
7.2 Obligations. Eaglessoft imposes on each sub-processor, by written contract, the same data protection obligations as set out in this DPA, in substance, in particular sufficient guarantees of appropriate technical and organisational measures. Eaglessoft remains fully liable to the Customer for the performance of its sub-processors' obligations.
7.3 Notice of changes. Eaglessoft informs the Customer of any intended addition or replacement of a sub-processor at least 30 days before the change, by e-mail to the Customer's account administrators or by a notice in the portal, and updates the published list. Other persons, such as the Customer's data protection officer, can receive the same notices by e-mailing [email protected] with the subject "Sub-processor updates".
7.4 Right to object. The Customer may object to the change in writing, on reasonable grounds relating to data protection, within those 30 days. The parties then discuss the objection in good faith. Eaglessoft may propose a reasonable alternative, such as not using the new sub-processor for the Customer's data. If no solution is agreed within a reasonable time, the Customer may terminate the affected Services by written notice with effect from the date the change takes effect, and Eaglessoft refunds any prepaid fees for the period after termination. No other compensation is due.
7.5 Urgent replacement. Where a sub-processor must be replaced urgently for reasons outside Eaglessoft's control (for example the sub-processor's insolvency or a security reason), Eaglessoft may make the change immediately and informs the Customer, where feasible before the new sub-processor processes Customer Personal Data, and otherwise as soon as possible. The right to object in clause 7.4 then applies from that notice.
8. International transfers
8.1 Eaglessoft stores and processes Customer Personal Data in the European Union or the European Economic Area (EU/EEA).
8.2 There are two exceptions, both listed in Annex 2:
Network security provider. All requests to and responses from the DocNaut website, portal and APIs, including their content and any Documents uploaded or downloaded through them, pass through the global network of Cloudflare, Inc., Eaglessoft's network security and content delivery provider, and may be processed in transit outside the EU/EEA. Cloudflare does not store Documents. This transfer is covered by the Standard Contractual Clauses incorporated in Cloudflare's Data Processing Addendum and by Cloudflare's certification under the EU–US Data Privacy Framework. Peppol message exchange between Access Points does not pass through that network.
E-mail and collaboration. Customer Personal Data that the Customer sends to Eaglessoft by e-mail, for example in a support request, is processed in Microsoft 365 within the Microsoft EU Data Boundary. Limited residual transfers outside the EU/EEA are covered by the Microsoft Products and Services Data Protection Addendum and the Standard Contractual Clauses it incorporates.
8.3 Eaglessoft does not transfer Customer Personal Data outside the EU/EEA otherwise, unless the Customer instructs it (for example by sending a Document to a recipient outside the EU/EEA), under clause 7, or through remote access by authorised personnel approved under clause 5. Any transfer by Eaglessoft or a sub-processor to a country without an adequacy decision of the European Commission is covered by the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, or another valid transfer mechanism under Chapter V GDPR.
9. Assistance to the Customer
9.1 Data-subject requests. Taking into account the nature of the processing, Eaglessoft assists the Customer by appropriate technical and organisational measures in responding to requests from data subjects to exercise their rights under Chapter III GDPR. If Eaglessoft receives such a request directly, it forwards it to the Customer without undue delay and does not respond itself, except to confirm that it has forwarded the request.
9.2 Other assistance. Eaglessoft assists the Customer, taking into account the nature of the processing and the information available to it, with its obligations under Articles 32 to 36 GDPR, including security, breach notification, data protection impact assessments (DPIAs) and prior consultation of a supervisory authority.
9.3 Assistance is free of charge where it is limited to information and tools that Eaglessoft already makes available. Eaglessoft may charge reasonable costs, agreed in advance, for assistance beyond that, unless the assistance is needed because of a breach of this DPA by Eaglessoft.
10. Personal data breaches
10.1 Eaglessoft notifies the Customer without undue delay, and in any event within 36 hours, after becoming aware of a personal data breach affecting Customer Personal Data, and provides the information the Customer needs for its own notification in phases as it becomes available.
10.2 The notification describes, as far as then known: the nature of the breach, including the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed to address the breach and mitigate its effects; and a contact point for more information. Where information is not yet available, Eaglessoft provides it in phases as it becomes available.
10.3 Eaglessoft takes the measures needed to contain the breach and mitigate its effects, and cooperates with the Customer so that the Customer can meet its own obligations to notify the supervisory authority and the data subjects. Notification of a breach is not an acknowledgement of fault or liability.
10.4 Notifications are sent to the Customer's account administrators and to any security or privacy contact the Customer has registered in the portal. The Customer keeps those contacts up to date.
11. Deletion or return at the end of the Services
11.1 During the Terms, the Customer can export its Documents and related data through the portal or the APIs while they are kept in the Services (Appendix A).
11.2 When the Terms end, the Customer may export its data during the retrieval period of at least 30 days set out in section 18 of the Terms. After that period Eaglessoft deletes the Customer Personal Data from its active systems, except data it must keep by law and Documents that the Customer has instructed it to keep under an optional archiving service, and from backups as they expire in the normal backup rotation, within 30 days after the end of that period. Until deletion, backups remain protected under this DPA and are not used for any other purpose.
11.3 Eaglessoft may keep Customer Personal Data after that period only where EU or Member State law requires it, and only for as long as that law requires. In that case this DPA continues to apply to that data, and Eaglessoft processes it only for the purpose of that legal requirement.
11.4 Eaglessoft confirms the deletion in writing.
12. Information and audits
12.1 Eaglessoft makes available to the Customer all information necessary to demonstrate compliance with Article 28 GDPR and this DPA. This includes its current ISO/IEC 27001 and ISO/IEC 27701 certificates, a summary of its most recent certification or surveillance audit, and its answers to reasonable security questionnaires.
12.2 If that information is not sufficient to demonstrate compliance, or a supervisory authority requires it, the Customer may carry out an audit, including an inspection, itself or through an independent auditor bound by confidentiality who is not a competitor of Eaglessoft. The Customer gives at least 30 days' prior written notice and a proposed audit plan. Audits take place during business hours, no more than once a year unless a supervisory authority requires it or a personal data breach affecting the Customer has occurred, and in a way that does not disrupt Eaglessoft's operations or compromise the security or confidentiality of other customers' data.
12.3 Each party bears its own costs of an audit.
12.4 Eaglessoft cooperates with the supervisory authorities in the performance of their tasks.
13. Liability
Each party's liability arising out of or in connection with this DPA is subject to the limitations and exclusions of liability in the Terms. Nothing in this DPA limits either party's liability towards data subjects under Article 82 GDPR, or any liability that cannot be limited under applicable law.
14. Term
This DPA applies for as long as Eaglessoft processes Customer Personal Data on behalf of the Customer, including after the end of the Terms until the data has been deleted or returned under clause 11.
15. Governing law and courts
This DPA is governed by Belgian law. The courts of Brussels have exclusive jurisdiction over any dispute arising out of or in connection with it, without prejudice to the powers of the supervisory authorities.
Appendix A: Details of the processing
| Item | Description |
|---|---|
| Subject matter | Provision of the DocNaut Services: the exchange of the Customer's electronic business documents over the Peppol network and other e-invoicing networks and platforms, and the related validation, transformation, routing, delivery and storage. |
| Duration | The term of the Terms, plus the period until deletion or return under clause 11. |
| Nature of the processing | Receiving, storing, validating, transforming, enriching with technical metadata, routing, transmitting and delivering Documents; making them available in the portal and through the APIs; logging transmissions; backing up; deleting. |
| Purpose | To provide the Services to the Customer under the Terms, and to provide support at the Customer's request. |
| Types of Personal Data | Personal Data contained in Documents and their attachments, such as: names, job titles and business contact details (e-mail, telephone, postal address) of contact persons; names, addresses and identifiers (such as VAT, enterprise or Peppol identifiers) of trading partners that are natural persons, such as sole traders; bank account details (IBAN, BIC) and payment references; order, delivery and invoice references; product and service descriptions; and the technical metadata of each transmission (sender and receiver identifiers, document type, message identifiers, time stamps and status). |
| Categories of data subjects | The Customer's employees, representatives and contact persons named in Documents; the Customer's customers, suppliers and other trading partners that are natural persons, and their employees and contact persons; any other natural person named in a Document. |
| Special categories of data | None intended. The Customer does not send special categories of Personal Data or data relating to criminal convictions, except where a Document lawfully requires it. |
| Frequency | Continuous, for as long as the Customer uses the Services. |
| Retention | Documents are kept for 3 months after their final status has been made available to the Customer and are then deleted, unless the Customer has ordered the optional archiving service; at the end of the Services, as set out in clause 11. The Services are not a statutory archive; the Customer keeps its own copies of Documents for the periods required by law. |
| Sub-processors | As listed in Annex 2 of the Terms and at https://www.docnaut.com/legal/sub-processors. |
| Location | EU/EEA, with the exceptions described in clause 8.2. |
Appendix B: Technical and organisational security measures
DocNaut is operated under Eaglessoft BV's information security management system, certified to ISO/IEC 27001:2022 (certificate 1754-01) and ISO/IEC 27701 (certificate 1754-02). The measures are defined in that system. In summary:
| Area | Measures |
|---|---|
| Governance | Information security and data protection policies approved by management and reviewed at least annually; a designated Information Security Manager (CISO) and Data Protection Officer; risk assessment and treatment; records of processing activities; DPIAs for high-risk processing; internal audits and external certification audits. |
| People | Confidentiality obligations for all staff and contractors; background screening where permitted; security and privacy awareness training; access to Customer Personal Data restricted to authorised staff resident in the EU/EEA, with access from outside the EU/EEA only where individually approved and recorded (clause 5). |
| Access control | Role-based access on a need-to-know and least-privilege basis; individual accounts; strong authentication, including two-factor authentication; prompt removal of access on role change or departure; periodic access reviews; customer-side access managed through the portal and client-credential API access; access to Customer Personal Data and access to the logs recording that access are held by different persons. |
| Encryption | Encryption in transit (TLS) for the portal, APIs and network connections; encryption at rest for databases, storage volumes and backups; managed custody of cryptographic keys and secrets. |
| Separation | Logical separation of each customer's data; separate production and non-production environments; no real personal or fiscal data in development or testing (masked or synthetic data only). |
| Logging and monitoring | Central logging of security-relevant events; monitoring and alerting through a security information and event management (SIEM) system; protection of logs against tampering; security event logs kept for 90 days in active storage, then up to 1 year in a secured archive, and then deleted; application logs and API gateway access logs kept for 7 days; longer only where the law requires it; Peppol activity logs kept for as long as the law and the Peppol rules require, and at least 3 months. |
| Network security | Firewalling and network segmentation; web application firewall, rate limiting and DDoS protection for public endpoints; hardened system and cluster configurations. |
| Vulnerability management | Patch management; dependency and container image scanning; components with unresolved critical or high vulnerabilities are not released; coordinated vulnerability disclosure policy. |
| Secure development | Secure development lifecycle with code review and security testing before release; privacy by design and by default; change management. |
| Availability and resilience | Database backups at least every 24 hours, with a near-real-time streaming replica; an encrypted, immutable (write-once) offsite copy in the EU/EEA, kept separate from the primary hosting environment; operational backups retained for 30 days; tested restore procedures; business continuity and disaster recovery plan, with a full disaster recovery exercise performed annually and recorded. |
| Incident management | Documented incident management procedure with 24/7 on-call response; assessment of personal data breaches by the Data Protection Officer; notification to customers under clause 10 and to authorities where required by law; incidents that may affect other Peppol service providers are notified to the Peppol Coordinating Authority and the Peppol participants involved within 4 hours of detection, as required by the Peppol Service Level Requirements. |
| Suppliers | Assessment of suppliers before engagement; written data processing terms with each sub-processor; EU/EEA data location, except as listed in Annex 2; monitoring and exit procedures, including data return and secure deletion. |
| Physical security | Hosting in professionally operated data centres in the EU/EEA with access control, surveillance and environmental protection, under the providers' own certified controls. |
| Deletion | Documented retention schedules and secure deletion at the end of the retention period and at the end of the Services (clause 11). |
