Skip to content

EU data residency

Every qube CloudQube offers is backed by an EU-incorporated provider hosting in the EU. Not just “EU available”, actually incorporated and headquartered in the EU. Your data stays under EU jurisdiction by default and there is no path to a non-EU subprocessor without you opting in explicitly.

QubeRegionNotes
DomainEURegistry filings handled by an EU-incorporated registrar.
DNSEU anycastDNS records resolved from EU PoPs by an EU-incorporated provider.
EmailEUTransactional sending and the inbox you receive bounces in are both in EU data centres.
DatabaseEUSingle-region by default; region pickable at provisioning time.
ContainerEUMulti-region within EU available; pick at provisioning time.
AnalyticsEU (Germany)Self-hosted CloudQube instance, no third-party analytics vendor.
MonitoringEUProbes run from EU PoPs; alerts emitted from the EU email qube.

The full, named list of subprocessors lives at cloudqube.eu/legal/subprocessors. It is the only place on this site where individual provider names appear, because the law requires us to publish that list. The docs themselves describe everything in terms of generic roles to keep the focus on what you are actually building, not who we have a contract with this quarter.

  • Your project data, files, databases, emails, DNS records: in the EU.
  • Your billing data and invoices: in the EU.
  • Your account login: handled by an EU-incorporated identity stack.
  • Outbound payments to non-EU service providers (when you opt in to one): out of the EU at the moment they leave us, with a clear consent flow before any data is sent.

If your customers ask about GDPR, you can answer with a paper trail. Your processor agreement is with us, ours are with EU subprocessors, and there is no Schrems-II-style transfer to worry about unless you specifically opt one in.