Hostinger
Hosting PaaS · hostinger.com · last read 2026-11-09
At a glance
- Is Hostinger GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Hostinger itself publishes, each answer linked to its source and the date we read it.
- Does Hostinger have a data processing agreement (DPA)?
- Yes. Hostinger publishes a data processing agreement at hostinger.com. It describes how a new subprocessor is announced but states no notice period. It promises breach notification "without undue delay", with no number of hours. Source and date
- Is Hostinger ISO 27001 certified?
- Hostinger states ISO/IEC 27001 certification (2022 edition, as Hostinger names it), and says the certificate or audit report is available on request. In Hostinger's words: “Hostinger is an ISO/IEC 27001:2022 certified hosting provider.” We read this on 2026-11-09. Source and date
- How does Hostinger transfer personal data out of the EU?
- Hostinger's agreement relies on the EU standard contractual clauses and the UK transfer addendum. Source and date
- Who are Hostinger's subprocessors?
- Hostinger lists 8 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-11-09. Source and date
- How do you report a security vulnerability to Hostinger?
- Hostinger publishes a security.txt at www.hostinger.com naming https://hackerone.com/hostinger. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Hostinger International Ltd. |
|---|---|
| HQ | CY |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | hostinger.com · 2026-11-09 |
Data location
No data-location observation recorded yet.
The same question for every vendor: where SaaS vendors store EU data.
Subprocessor chain
8 third parties · 0 with a country outside the EEA · all read 2026-11-09
| Subprocessor | Country | Purpose |
|---|---|---|
| AMAZON WEB SERVICES EMEA SARL | — | — |
| Anthropic Ireland, Limited | — | — |
| Cloudflare, Inc. | — | — |
| Google Cloud EMEA Limited | — | — |
| MailChannels Corporation | — | — |
| Proofpoint, Inc. | — | — |
| spectra tech, UAB | — | — |
| Vonage B.V. | — | — |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-11-09 · hostinger.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | SCC module 2 |
| Transfer mechanism | SCC module 3 |
| Transfer mechanism | UK Addendum |
| Notice of new subprocessors | New sub-processors added to Appendix 3; no notice period stated |
| If you object to one | Customer may terminate the affected Covered Services without penalty by written notice, with reasons, within 10 days of receiving notice; termination applies to the whole bundle if bundled |
| Breach notification | without undue delay |
| Audit | Customer may confirm compliance by specific written request at reasonable intervals; may terminate if Hostinger declines a properly scoped audit instruction |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
We found no version number or date in the agreement as we read it.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Is Hostinger ISO 27001 certified?
Hostinger states ISO/IEC 27001 certification (2022 edition, as Hostinger names it), and says the certificate or audit report is available on request. We read this on 2026-11-09.
- Available on request “Hostinger is an ISO/IEC 27001:2022 certified hosting provider.”
Source: trust.hostinger.com, 2026-11-09
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| GDPR | Claimed | — | trust.hostinger.com | 2026-11-09 |
| ISO/IEC 27001:2022 · ISO27001 | Available on request | — | trust.hostinger.com | 2026-11-09 |
| PCI DSS v4.0.1 · PCIDSS | Available on request | — | trust.hostinger.com | 2026-11-09 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
- FedRAMP Marketplace (US): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-09, no entry under Hostinger; Hostinger International Ltd.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
Support window
Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.
Vulnerability reporting: hackerone.com (security.txt, expires 2027-01-21; read 2026-11-09)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-11-09 |
| dpa | Public | full | 200 | 2026-11-09 |
| subprocessors | Public | full | 200 | 2026-11-09 |
History
Nothing has moved since we started watching this vendor on 2026-11-09. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.