How Eaglessoft protects the invoices, tax data and business data our customers entrust to us — and how we keep our services secure, compliant and resilient.
Published at eaglessoft.com/information-security-policy (https://eaglessoft.com/information-security-policy/)
Document history
| Version | Date | Change |
|---|---|---|
| 1.0 | 29 October 2026 | First version under this title. Replaces the previous "Information Security Policy" page in full. |
Contents
About this policy
This page is a public summary of the Information Security Policy of Eaglessoft BV ("Eaglessoft", "we", "us"), Excelsiorlaan 31, 1930 Zaventem, Belgium. It is written for our customers, partners and auditors. The full policy, and the policies and procedures that support it, are internal documents. We can share more detail with customers and auditors on request, under confidentiality where needed.
If you would like to request more detail about this policy, contact us at [email protected].
Our commitment
Our customers send us invoices, tax data and business-partner data, including personal data and tax identifiers, so that we can process and deliver them for them. Keeping that information secure, and keeping our services running, is central to their trust in us and to our legal and contractual obligations.
Management responsibility
Our management is responsible for information security. It sets this policy, assigns roles, provides the resources needed, and reviews how well our information security management system (ISMS) works at least once a year. Our management approves and oversees our cybersecurity risk-management measures and follows cybersecurity training.
Scope
This policy applies to the design, development, delivery, operation, support and maintenance of our electronic-invoicing and digital-compliance services:
It also covers the infrastructure, corporate IT and processes that support them.
It applies to everyone who works for us or on our behalf, including employees, contractors, temporary staff and suppliers with access to our information or systems.
Our objectives
We are committed to:
Confidentiality
Information is available only to the people who are authorised to see it.
Integrity & authenticity
Information is accurate, complete and protected against unauthorised change. This matters especially for invoices and other fiscal documents.
Availability
Our services and information are available to authorised users in line with the service levels we commit to.
Privacy
Personal data is processed lawfully and fairly, in line with the EU General Data Protection Regulation (GDPR).
Compliance
We meet applicable legal, regulatory and contractual requirements, including e-invoicing mandates and the requirements of the networks and tax authorities we connect to, such as Peppol.
Continual improvement
We set measurable security objectives, track them, and improve our ISMS over time.
How we protect information
The main principles and measures of our ISMS are:
EU hosting
Customer fiscal data processed by DocNaut, our Peppol Access Point and SMP, and our French e-invoicing service is hosted, processed and stored in the European Union. Traffic to and from our websites, portals and APIs passes through the global network of our network security provider, Cloudflare, and may transit outside the EU/EEA under the Standard Contractual Clauses; Peppol message exchange between Access Points does not.
Other personal data also stays in the EU/EEA, except for a small number of documented and approved cases that are covered by data processing agreements and the transfer safeguards required by the GDPR. Access to customer personal and fiscal data is limited to authorised personnel resident in the EU/EEA and approved suppliers. Access from outside the EU/EEA requires a documented assessment and approval by the Data Protection Officer and the Information Security Manager.
Risk-based approach
We identify and assess information security risks regularly, and treat them in line with a documented method.
Security by design and by default
Security and privacy are built into our services and processes from the start.
Access control
Access is granted on a least-privilege and need-to-know basis, and is reviewed regularly.
Encryption
Data is encrypted in transit and at rest, using recognised algorithms and protected key management.
Supplier management
Suppliers and sub-processors are held to security and data-protection obligations that match the risk they present, under written agreements.
Incident management
Security events and incidents are reported, handled and learned from. Where the law requires, we notify the competent authority and the people affected, for example within 72 hours under the GDPR.
Business continuity
We plan, maintain and test backup, recovery and continuity arrangements so that our services stay resilient.
Secure development and change
Our software is developed, tested and changed under controlled processes, with security checks before release.
Vulnerability management
We monitor for vulnerabilities, scan our software, test it independently, and fix issues within defined timeframes.
Awareness and training
Everyone in scope receives security awareness training, and is responsible for information security within their role.
Roles and responsibilities
Top management
Has overall accountability for information security and approves this policy.
Information Security Manager (CISO)
Runs and improves the ISMS and reports on its performance to top management.
Data Protection Officer (DPO)
Oversees our compliance with the GDPR and other data-protection laws. You can contact our DPO at [email protected].
All personnel and suppliers
Must follow this policy and report security events. Breaches of the policy may lead to disciplinary or contractual measures.
Certifications
Eaglessoft BV holds the following certifications, for software development, data processing, system integration and customer/personal data protection processes:
ISO/IEC 27001:2022
Information security management · issued as TS EN ISO/IEC 27001:2023
- Certificate 1754-01 · valid until 19 November 2028
- Initial certification 20 November 2025
- Issued by BBS Belgelendirme Eğitim ve Gözetim Hizmetleri A.Ş., accredited by TÜRKAK (AB-0021-YS), an IAF MLA signatory for ISO/IEC 27001
ISO/IEC 27701:2019
Privacy information management · issued as TS ISO/IEC 27701:2021
- Certificate 1754-02 · valid until 27 January 2029
- Initial certification 28 January 2026
- Issued by BBS under its TÜRKAK accreditation (AB-0021-YS)
| Standard | Certificate number | Certified scope | Valid |
|---|---|---|---|
| ISO/IEC 27001:2022 (information security management), issued as TS EN ISO/IEC 27001:2023 | 1754-01 | Software Development, Data Processing, System Integration and Customer Data Security Processes | Initial certification 20 November 2025, valid until 19 November 2028 |
| ISO/IEC 27701:2019 (privacy information management), issued as TS ISO/IEC 27701:2021 | 1754-02 | Software development, data processing, system integration and personal data protection processes | Initial certification 28 January 2026, valid until 27 January 2029 |
Both certificates are subject to regular surveillance audits. You can check the validity of these certificates at www.bbsas.com.tr (https://www.bbsas.com.tr) and tbds.turkak.org.tr (https://tbds.turkak.org.tr).
Reporting a security issue
We welcome reports from security researchers, customers and anyone else who finds a vulnerability in our services. This section is our coordinated vulnerability disclosure policy.
Scope
The websites and services that we operate:
Services operated by third parties, such as our network security provider, Microsoft 365, the Peppol central infrastructure and other Peppol service providers, are out of scope; please report issues in them to their owners.
How to report
E-mail [email protected] and please include:
- a description of the vulnerability and the affected service, URL or component;
- the steps to reproduce it, with a proof of concept if you have one;
- its possible impact, as you see it;
- how we can contact you, and whether you want to be credited.
Rules for research
Please act in good faith and in proportion:
- do not access, copy, change or delete data that is not yours, and use only your own accounts or test data. If you encounter personal or customer data, stop, do not keep it, and tell us in your report;
- do only what is needed to demonstrate the vulnerability, and do not install backdoors or keep access;
- do not disrupt our services or other users.
Out of scope
- Denial-of-service attacks and load testing;
- social engineering, including phishing of our staff or customers;
- physical attacks on our offices or data centres;
- spam;
- automated scanning that generates significant traffic.
What we do
Acknowledge
We acknowledge your report within 3 business days.
Assess
We assess it and keep you informed of our progress.
Fix
We tell you when the issue is fixed.
Credit
With your agreement, we credit you once the issue is resolved.
Disclosure
Please do not disclose the vulnerability publicly, or share it with others, for 90 days after your report, unless we agree an earlier or later date with you.
Safe harbour
If you follow this policy in good faith, we will not take legal action against you, or ask an authority to do so, for your research and report. If a third party takes action against you over research that complied with this policy, we will make clear that it was authorised by us.
Our contact details for security reports are also published in machine-readable form at eaglessoft.com/.well-known/security.txt (https://eaglessoft.com/.well-known/security.txt) and docnaut.com/.well-known/security.txt (https://www.docnaut.com/.well-known/security.txt).
Security incidents. If you suspect a security incident affecting your data, for example a lost or misused password or API credential, please e-mail [email protected] without delay.
For questions about personal data, contact [email protected]. For anything else, contact [email protected].
Review of this policy
We review our Information Security Policy at least once a year, and whenever there is a significant change to our organisation, services, technology or legal requirements. We update this summary when the policy changes. Each version has a version number and an effective date, shown at the top of this page.
Questions about our security?
Report a vulnerability, request more detail about this policy, or reach the right team — we treat every message seriously.
For questions about personal data: [email protected]
