Security at DPP Host
Last reviewed 30 September 2026
DPP Host is run by Qubites ApS in Denmark. This page says what we do to keep passports and customer data safe, and where we stand on each control of ISO/IEC 27002:2022.
Where we stand
DPP Host is not certified to ISO/IEC 27001.
We assessed our own controls against the 93 controls of ISO/IEC 27002:2022 and reviewed the result on 30 September 2026. No auditor has checked it. Every control and its status is listed below.
- 28 In place Runs today, and we can show it.
- 53 Partly Part of it runs. The rest is named and has an owner.
- 7 Planned Has an owner and a trigger. Nothing runs yet.
- 5 Not applicable Does not apply to DPP Host. The reason is recorded.
What we do
Where your data is
The database, the sign-in service and the server functions run in Frankfurt (EU). Published passports, images and supplier files are stored in Cloudflare R2 under EU jurisdiction. Some data is processed outside the EU. For example, Cloudflare delivers pages from the data centre nearest the visitor, Resend keeps copies of the emails we send for 30 days in the United States, and AI app connections are stored in Cloudflare Workers KV, which is not limited to the EU.
Who can see what
Every database table has row-level access rules. Members of one organisation cannot read another's data. The public key the website uses cannot read or write any table. Owner-services data is kept apart from passports and never reaches the public copies.
No publishing without a person
An AI assistant or an integration can prepare a passport. A person in your organisation approves it after signing in again. Only an API key that an admin has granted the publish right can publish on its own.
Keys
API keys are shown once and stored only as keyed hashes. They expire, can be rotated with an overlap, and stop working when their creator leaves.
In transit and at rest
All connections use TLS with HSTS. The site, the dashboard and the passport pages send a Content Security Policy. Data at rest is encrypted by our providers.
Backups and continuity
Published passports are served from a static copy that stays up when the dashboard or the database is down. Every published passport is copied nightly into a separate EU storage bucket. Our target is to restore published passports within 8 hours, with at most 24 hours of loss. Published passports stay online for 10 to 15 years from publication, and a written wind-down plan sets out how they stay online if DPP Host stops.
Integrity
Each published version has a content hash that is independently timestamped. Anyone can check that it has not been changed.
Incidents
We have a written incident and breach process. It covers the 72-hour notice duty under the GDPR and the notice-and-action process under the Digital Services Act.
The 93 controls
ISO/IEC 27002:2022 lists 93 controls in four groups. Each row gives the control's number, its title in the standard and our status on 30 September 2026. What we do for each control, and where, stays internal; it is available under NDA.
5 Organisational controls
37 controls: 14 in place, 21 partly, 2 planned, 0 not applicable.
| No. | Control | Status |
|---|---|---|
| 5.1 | Policies for information security | Partly |
| 5.2 | Roles and responsibilities | In place |
| 5.3 | Segregation of duties | Partly |
| 5.4 | Management responsibilities | In place |
| 5.5 | Contact with authorities | Partly |
| 5.6 | Contact with special interest groups | Partly |
| 5.7 | Threat intelligence | Partly |
| 5.8 | Information security in project management | In place |
| 5.9 | Inventory of information and other associated assets | In place |
| 5.10 | Acceptable use of information and other associated assets | In place |
| 5.11 | Return of assets | Planned |
| 5.12 | Classification of information | In place |
| 5.13 | Labelling of information | Partly |
| 5.14 | Information transfer | In place |
| 5.15 | Access control | In place |
| 5.16 | Identity management | In place |
| 5.17 | Authentication information | Partly |
| 5.18 | Access rights | Partly |
| 5.19 | Information security in supplier relationships | Partly |
| 5.20 | Addressing information security within supplier agreements | Partly |
| 5.21 | Managing information security in the ICT supply chain | Partly |
| 5.22 | Monitoring, review and change management of supplier services | Partly |
| 5.23 | Information security for use of cloud services | In place |
| 5.24 | Incident management planning and preparation | Partly |
| 5.25 | Assessment and decision on information security events | In place |
| 5.26 | Response to information security incidents | Partly |
| 5.27 | Learning from incidents | In place |
| 5.28 | Collection of evidence | Partly |
| 5.29 | Information security during disruption | Partly |
| 5.30 | ICT readiness for business continuity | Partly |
| 5.31 | Legal, statutory, regulatory and contractual requirements | Partly |
| 5.32 | Intellectual property rights | In place |
| 5.33 | Protection of records | Partly |
| 5.34 | Privacy and protection of PII | Partly |
| 5.35 | Independent review of information security | Planned |
| 5.36 | Compliance with policies, rules and standards | Partly |
| 5.37 | Documented operating procedures | In place |
6 People controls
8 controls: 0 in place, 3 partly, 5 planned, 0 not applicable.
| No. | Control | Status |
|---|---|---|
| 6.1 | Screening | Planned |
| 6.2 | Terms and conditions of employment | Planned |
| 6.3 | Information security awareness, education and training | Partly |
| 6.4 | Disciplinary process | Planned |
| 6.5 | Responsibilities after termination or change of employment | Planned |
| 6.6 | Confidentiality or non-disclosure agreements | Planned |
| 6.7 | Remote working | Partly |
| 6.8 | Information security event reporting | Partly |
7 Physical controls
14 controls: 0 in place, 10 partly, 0 planned, 4 not applicable.
| No. | Control | Status |
|---|---|---|
| 7.1 | Physical security perimeters | Partly |
| 7.2 | Physical entry | Partly |
| 7.3 | Securing offices, rooms and facilities | Partly |
| 7.4 | Physical security monitoring | Not applicable |
| 7.5 | Protecting against physical and environmental threats | Partly |
| 7.6 | Working in secure areas | Not applicable |
| 7.7 | Clear desk and clear screen | Partly |
| 7.8 | Equipment siting and protection | Partly |
| 7.9 | Security of assets off-premises | Partly |
| 7.10 | Storage media | Partly |
| 7.11 | Supporting utilities | Not applicable |
| 7.12 | Cabling security | Not applicable |
| 7.13 | Equipment maintenance | Partly |
| 7.14 | Secure disposal or re-use of equipment | Partly |
8 Technological controls
34 controls: 14 in place, 19 partly, 0 planned, 1 not applicable.
| No. | Control | Status |
|---|---|---|
| 8.1 | User endpoint devices | Partly |
| 8.2 | Privileged access rights | Partly |
| 8.3 | Information access restriction | In place |
| 8.4 | Access to source code | Partly |
| 8.5 | Secure authentication | Partly |
| 8.6 | Capacity management | Partly |
| 8.7 | Protection against malware | Partly |
| 8.8 | Management of technical vulnerabilities | Partly |
| 8.9 | Configuration management | In place |
| 8.10 | Information deletion | Partly |
| 8.11 | Data masking | In place |
| 8.12 | Data leakage prevention | Partly |
| 8.13 | Information backup | Partly |
| 8.14 | Redundancy of information processing facilities | Partly |
| 8.15 | Logging | Partly |
| 8.16 | Monitoring activities | Partly |
| 8.17 | Clock synchronization | In place |
| 8.18 | Use of privileged utility programs | Partly |
| 8.19 | Installation of software on operational systems | In place |
| 8.20 | Networks security | Partly |
| 8.21 | Security of network services | Partly |
| 8.22 | Segregation of networks | In place |
| 8.23 | Web filtering | Not applicable |
| 8.24 | Use of cryptography | Partly |
| 8.25 | Secure development life cycle | In place |
| 8.26 | Application security requirements | In place |
| 8.27 | Secure system architecture and engineering principles | In place |
| 8.28 | Secure coding | In place |
| 8.29 | Security testing in development and acceptance | In place |
| 8.30 | Outsourced development | Partly |
| 8.31 | Separation of development, test and production environments | Partly |
| 8.32 | Change management | In place |
| 8.33 | Test information | In place |
| 8.34 | Protection of information systems during audit testing | In place |
Suppliers
DPP Host runs on these suppliers. The certifications are the ones each supplier states on its own security page, checked on 30 September 2026 and checked again once a year. They cover the supplier, not DPP Host: our own status is above.
| Supplier | What it does for DPP Host | Certifications the supplier states |
|---|---|---|
| Cloudflare | Edge network, Workers, R2 storage, DNS, email routing | ISO/IEC 27001, 27701 and 27018; SOC 2 Type II; PCI DSS |
| Supabase | Database, sign-in service and server functions in Frankfurt | ISO/IEC 27001; SOC 2 Type 2; HIPAA |
| GitHub | Source code and CI | ISO/IEC 27001; SOC 1 and SOC 2 Type 2 |
| Resend | Email delivery | SOC 2 Type II |
| Scaleway | Off-site copies: built, switched off for now | ISO/IEC 27001; HDS |
Documents and certification
The full Statement of Applicability and our policies are available on request under NDA: hello@dpphost.eu.
Certification: when a customer or the EU rules for DPP service providers require it.
Security reports: hello@dpphost.eu. Privacy: privacy@dpphost.eu. We publish no uptime guarantee.
Statuses as reviewed on 30 September 2026. This page changes when the Statement of Applicability changes.