Security statement
How we secure ourselves.
Comply24 itself works to the standards the platform is built for: ISO/IEC 27001 and the requirements that financial institutions place on their service providers under DORA. Below we set out how we do that: where your data is stored, how it is protected and what is in preparation.
Last updated: 16 November 2026
ISO/IEC 27001 as the basis
Our information security management system follows ISO/IEC 27001:2022, with our own policy house of 17 policies and 12 procedures, approved on 10 November 2026. Certification is in preparation.
Hosting in the EU
The application runs in Nuremberg (Germany), monitoring in Helsinki (Finland) and the second copy of the backups is kept in Amsterdam (the Netherlands). For the data in the platform we only use European providers.
A separate environment per customer
Every customer has its own database schema. Permissions apply per resource and per action and are enforced on the server.
External penetration test
An independent party tests the platform every year. The first test is scheduled for the first week of December 2026. Customers and prospects receive the summary under a non-disclosure agreement.
99.5% availability
Our service level agreement sets 99.5% per month, with monitoring and alerting around the clock. Other arrangements are recorded in the order form.
Single sign-on
You log in through OpenID Connect with your own accounts, so your own rules for multi-factor authentication apply. Our engineers reach the servers only with personal keys.
Measures
Seven subjects, the facts per subject.
As at 16 November 2026.
Hosting and infrastructure
- The platform runs on Hetzner Cloud within the EU: three application servers in Nuremberg (Germany) and a separate monitoring server in Helsinki (Finland).
- A second copy of all backups is kept at Scaleway in Amsterdam (the Netherlands), in a fully separate environment.
- The database runs on three servers that replicate synchronously. If one server fails, nothing is lost and another takes over automatically.
- The servers have no public web ports. Web traffic only enters through the load balancer, over a private network, and passes two firewall layers.
- Servers, network and firewall are defined as code, with version control and review. There is no manual server configuration.
Encryption
- In transit: TLS 1.2 and 1.3, with HSTS.
- Backups: encrypted before they leave the server. Database backups with AES-256 and a separate key per location, so one key never opens both copies.
- Secrets: stored encrypted, never in the code. Every change is scanned for leaked keys.
- Key management: keys are replaced every year, and immediately when an employee leaves or a leak is suspected.
Access control
- Access to the production environment is reserved for a limited number of engineers, with the minimum rights their task requires.
- Access to the servers by personal key only. Password login is switched off.
- Access rights are reviewed every quarter. When someone leaves or changes role, we withdraw access within one working day.
- In the platform you manage users, roles and permissions yourself. Every decision is in the audit trail, with name and time. No one approves their own work.
Monitoring and logging
- Monitoring runs on a separate server in another data centre. It therefore keeps working if the cluster fails.
- Servers, database, application and the traffic per customer are tracked, with automatic alerting.
- Retention of monitoring data: metrics 30 days, logs 14 days.
Backup and continuity
- Encrypted backups at two locations with two providers, with recovery to the second.
- Recovery objectives in the service level agreement on loss of the main location: no more than 1 hour of data (RPO) and recovery within 8 hours (RTO).
- Runbooks for every scenario and a fixed exercise schedule: a restore test every month, a failover and a restore from the second location every quarter, a full test every year.
- The full regime and the recovery time per scenario are set out further down this page.
Secure development and vulnerabilities
- The development environment is not publicly reachable and sits behind a VPN. No one changes the main version directly.
- Every change goes through automated tests and scanners, followed by code review, security review and a release gate. Each of these three can block a change.
- Remediation periods for vulnerabilities: critical within 7 days, high within 30 days, medium within 90 days. Security updates of the servers are installed automatically.
- An independent party carries out a penetration test of the application and the API every year. The first test is scheduled for the first week of December 2026.
- Test and production have separate databases and roles.
AI functions
- The platform has AI functions in Signal, Trace and Prove. They prepare the work and make a proposal.
- Every proposal shows its source and stays marked until a person validates it. Without that decision a proposal does not count.
- The functions run on models that Comply24 operates itself, on its own cluster in the Netherlands. Your documents do not go to an external model provider, are not used for training and are not kept after processing.
- We actively monitor every function: how often a proposal is accepted, amended or rejected. A new model version goes live only after it passes a fixed test set.
- One overview in the platform shows, per function, the purpose, the model, the processing location and who validates. Your administrator can switch an optional function off there.
Backup and recovery
Two locations, two providers, two countries.
Everything is kept at Hetzner in Germany and at Scaleway in the Netherlands. The loss of one provider therefore never means the loss of the backups.
- Database: a full backup every week, an incremental one every day and the changes in between continuously, to both locations. Recovery is possible to the second.
- A nightly copy per database: kept for 30 days at Hetzner and 35 days at Scaleway.
- Servers: daily snapshots, seven days back.
- Against deletion or ransomware: the second location keeps 30 days of earlier versions. The key that writes backups cannot manage or delete them.
- Partial recovery: restoring one database or one customer environment without touching the rest.
- Monitoring: a monitor checks that every backup is current at both locations and raises an alarm if it is not.
| Scenario | Maximum data loss | Recovery time |
|---|---|---|
| Failure of one server | None | Automatic |
| Corrupted data or a faulty change | A few seconds | 30 minutes to a few hours |
| One database or customer environment damaged | A few seconds to 24 hours | Minutes to 1 hour |
| Login sessions lost | No more than 1 hour | Minutes: log in again |
| Complete loss of the main location | Seconds to 1 hour | A few hours, from the second location |
Sub-processors
The parties behind the platform.
The current list of sub-processors is an annex to the data processing agreement. We announce a new sub-processor or a change of location 90 days in advance.
| Party | Function | Location |
|---|---|---|
| Hetzner Online GmbH, Hetzner Finland Oy | Hosting of the Comply24 platform and of the monitoring | Germany and Finland |
| Scaleway SAS | Second copy of the backups of the platform | The Netherlands |
| Devly B.V. | Hosting and management of the models for the AI functions of the platform | The Netherlands |
| Microsoft (Microsoft 365) | E-mail, office software and file storage: contact details and correspondence | European Union |
Responsible disclosure
Found a vulnerability? Report it to us.
This statement applies to the platform and to the websites of Comply24. It is also published in security.txt.
Report a vulnerability to security@comply24.nl. We confirm receipt within 3 working days, give an assessment within 10 working days and keep you informed of the fix.
What we ask of you
- Give us reasonable time to investigate and to fix the issue, and keep the report confidential until it is fixed.
- Do not view more data than is needed to demonstrate the vulnerability, and do not change or delete anything.
- Do not use brute force, social engineering or attacks that disrupt the service.
Comply24 takes no legal action against a reporter who acts in good faith and in line with these rules.
Ownership and exit
- All data is yours. Export at any time, without our involvement.
- Escrow of the source code, the installation instructions and the infrastructure definitions: the contract and the first deposit are scheduled for the first week of December 2026. After that the deposit is updated every month.
- When the contract ends, you keep the results. We delete your data from production within 30 days after you have confirmed receipt of the export; backups expire at the latest 65 days after that.
Certification and testing
- ISO/IEC 27001: the policies and procedures have been approved and certification is in preparation.
- An independent party carries out a penetration test of the application and the API every year. The first test is scheduled for the first week of December 2026.
- Hosting provider Hetzner holds an ISO/IEC 27001 certificate and a C5 attestation (type 2). Scaleway holds an ISO/IEC 27001 certificate.
DORA Article 30
What DORA Article 30 requires of the contract, and what we provide.
Article 30(2) of DORA lists what a contract with an ICT service provider must contain. For each element, the table shows what you get from us.
| Article | What DORA requires | What Comply24 provides |
|---|---|---|
| 30(2)(a) | Description of the service and of subcontracting | Service description per module, with the list of sub-processors and a duty to notify changes. |
| 30(2)(b) | Location of processing and storage | Nuremberg (Germany), Helsinki (Finland) and Amsterdam (the Netherlands). Set out in the contract annex, with prior notice of an intended change. |
| 30(2)(c) | Availability, authenticity, integrity and confidentiality | The measures on this page, and the full description in the security file. |
| 30(2)(d) | Access, recovery and return of data | Export at any time, recovery as in the table above, escrow and the arrangements on termination in the contract annex. |
| 30(2)(e) | Service levels | Response times and availability in the contract annex, with the review procedure. |
| 30(2)(f) | Assistance with ICT incidents | Notification chain and contacts. We report a security incident within 24 hours, and a priority 1 incident within 4 hours. |
| 30(2)(g) | Cooperation with supervisors | Audit and inspection rights, and cooperation with your supervisor, in the contract annex. |
| 30(2)(h) | Termination and notice periods | Termination rights and minimum notice periods in the contract annex. |
Regulation (EU) 2022/2554, Article 30(2). Your lawyer can read the annex alongside your own outsourcing policy.
Questions about our security?
The security file for your assessment.
For customers and prospects we make the full security file available under a non-disclosure agreement. We first send the agreement. You then receive the documents. We reply within one working day.
What you receive
- The full description of infrastructure and security
- The planning of the measures that are still being introduced
- Recovery runbooks and the exercise schedule
- Certificates and reports of the hosting providers
- Completed CIS v8 questionnaire
- Information security policies and standards
- List of sub-processors, with location and role
- Data processing agreement and DORA addendum
- Description of the incident process and notification chain
Involving colleagues
Involve your colleagues. Each question has its own page.
You rarely decide on a platform alone. These pages answer the questions of the people you need.
The first step
Try it free for two weeks. Or start with a demo.
Try the platform for two weeks with real legislation, news and alerts. Or see in thirty minutes what it does with a law from your own scope. For either, contact us.
Assurances you can check on this site
