Sub-processors: retain the right to know who intervenes
Your European host relies on US cloud, global CDN, offshore support — without a solid sub-processor clause, you do not know who touches your data.
Browse our Compliance posts on European hosting.
No results for this search
Your European host relies on US cloud, global CDN, offshore support — without a solid sub-processor clause, you do not know who touches your data.
Server logs, analytics, WAF, CDN — IP addresses are personal data. Without clear retention policy, you accumulate invisible GDPR risk.
Keeping everything indefinitely "just in case" violates GDPR; erasing at 7 days prevents post-incident investigation — policy must calibrate by log type and risk.
A well-configured KMS turns encryption into auditable proof. Misconfigured, it becomes a black box where host and customer pass the buck.
OVHcloud displays ISO 27001 across its cloud range, but the certificate never covers the entire catalogue at once. Here is how to read the scope before choosing Public Cloud, Hosted Private Cloud, or shared hosting.
In Belgium, the APD expects a readable sub-processing chain: beyond the host's DPA, list its sub-processors and those it engages for your project.
Checking "encryption enabled" on a quote says nothing about who can read your data during an incident or legal request. Here is how to tell decorative encryption from real control.
SecNumCloud commits operational sovereignty, but leaving qualified cloud without lock-in requires contractual formats, delays, and assistance — negotiate before signing.
Hetzner's DPA frames GDPR processing, but read it line by line before hosting customer data — sub-processors, German location, and IaaS responsibilities included.
SecNumCloud is not RFP decoration. Cloud Temple offers it on precise scopes — useful for sensitive State data and critical operators, out of scope for a classic town hall brochure site.
Production data in France, backups in Ireland or on third-party tape — sovereignty also depends on copies, often missing from the sales deck.
SecNumCloud is not GDPR-plus or generalized HDS — it is a strict ANSSI qualification whose product scope determines whether your workload is actually covered.
Hosting in the EU is not enough if CDN, edge logs, and WAF collect IP and URL elsewhere. Map the distribution layer before promising strict residency.
Cutting overly broad admin rights shrinks attack surface — but poorly tuned least privilege paralyzes support and on-call. How to find operational balance.
"Keep everything ten years" or "delete at 30 days" without business frame exposes you to GDPR and courts. The right duration is one you can apply and justify.
ISO 27001 on the sales slide often covers only headquarters and internal IT — not the shared datacenter where your VPS runs. The certificate is read in the appendix.
Signed SCCs and EU region no longer close the file: TIA, supplementary measures, and subprocessor chain — the host must prove, not assert.
Deleting a database row is not enough — backups, CDN, logs, and subprocessors often keep copies; erasure rights require mapping them all.
A generic DPA appendix is not enough — documented instructions, sub-processor list, 72-hour breach notice and TIA support are what a hosting contract must guarantee.
Under HDS, an attestation that excludes backups or restoration leaves a gaping hole. How to verify production, copies and DR procedures are audited.
Two identical ISO 27001 logos can hide opposite scopes. How to align product, region and backups before comparing OVHcloud, Hetzner or Infomaniak.
Type II SOC 2 reassures a US client — but the report is under NDA, scope often excludes your shared offer, and criteria do not replace GDPR.
A datacenter in Roubaix does not guarantee zero transfer: US CDN, India support, replicated backup — the flow map is missing on nine contracts out of ten.
ISO on the slide, SOC2 "on request," generic DPA — useful audit starts with dated, scoped, understandable documents — not a marketing checklist.