Skip to content

GDPR-native infrastructure

EU data residency — hosting, databases and analytics in Europe

Every HostStack app, database, and backup lives in Helsinki, Finland — run by a Danish company, with no US CLOUD Act exposure. Here is what EU data residency actually requires, and why an EU region from a US provider is not the same thing.

EU data residency means your data is stored and processed on servers inside the European Union. On HostStack that is Helsinki (Finland) today, on Hetzner infrastructure, with additional EU regions in Germany (Nuremberg, Falkenstein) on the roadmap. But residency alone does not make you GDPR-safe. The harder question — the one a procurement reviewer actually asks — is who can be legally compelled to hand the data over. That depends on where the provider is incorporated, not just where the servers are. For the general definition, and how residency differs from sovereignty and localization, read what is data residency.

Location is not the same as sovereignty

Data location (necessary)

The physical region your data sits in. Most US providers now offer an EU region — AWS Frankfurt, Render EU, Heroku Dublin — which fixes latency and storage location. It is necessary, but on its own it is not sufficient for a clean GDPR answer.

Legal incorporation (decisive)

The jurisdiction the company itself answers to. A US-incorporated company is reachable by the US CLOUD Act anywhere on earth, EU region included. An EU-incorporated company is not. This is the factor Schrems II actually turns on.

The US CLOUD Act and Schrems II

The US CLOUD Act (2018) lets US authorities compel any US-incorporated company to disclose data it controls — even when that data is held on servers outside the United States. The Schrems II ruling (CJEU, 2020) found that this exposure means an EU data subject's personal data is at risk when it is controlled by a US company, regardless of storage location. For a European controller, that is the core problem: with a US provider, the honest answer to “can a foreign government compel access to our customers' data?” is we cannot guarantee that it cannot. With an EU-incorporated provider, there is no US legal pathway to reach.

Who is actually an EU company?

Most platforms have an EU region. Far fewer are EU companies. The CLOUD Act turns on the second column, not the third.

  • HostStackEU company

    Incorporated in Denmark · EU region: FI (DE soon)

  • ScalewayEU company

    Incorporated in France · EU region: FR, NL, PL

  • OVHcloudEU company

    Incorporated in France · EU region: FR, DE, IT, PL

  • Clever CloudEU company

    Incorporated in France · EU region: FR, PL

  • AivenEU company

    Incorporated in Finland · EU region: Many EU

  • RenderNot EU

    Incorporated in United States · EU region: Frankfurt

  • RailwayNot EU

    Incorporated in United States · EU region: EU (limited)

  • Incorporated in United States · EU region: Amsterdam, Frankfurt

  • Fly.ioNot EU

    Incorporated in United States · EU region: Region-pinned

  • VercelNot EU

    Incorporated in United States · EU region: Edge / region

  • Incorporated in United States · EU region: Dublin

  • SupabaseNot EU

    Incorporated in United States · EU region: EU regions

  • NeonNot EU

    Incorporated in United States · EU region: EU regions

  • AWS RDSNot EU

    Incorporated in United States · EU region: Frankfurt etc.

Incorporation reflects public corporate records; EU-region availability is from each provider's documentation. Verify current details against the provider before a compliance sign-off.

Hosting data in Europe: everything that has to stay

Moving the app to an EU region is the start, not the finish. Personal data leaves the EU through the tools around the app far more often than through the app itself. For a residency claim to hold, every layer below needs an EU answer:

Application and database

The obvious part: where the app runs and where the primary database sits.

Backups and replicas

Often forgotten. A backup copied to a US bucket is a transfer, even if production never leaves Frankfurt.

Logs and error tracking

Request logs and stack traces carry IP addresses, emails and ids. Shipping them to a US log or APM vendor moves personal data out of the EU.

Web analytics

The tag runs in every visitor’s browser and sends their IP, user agent and the URL they are on to the analytics vendor — before your own server sees anything.

Email and support tools

Transactional email providers and help desks hold names, addresses and message content.

On HostStack the first four layers run on the same EU platform: services, managed databases and backups in Helsinki, and error tracking, uptime checks and site analytics on the same EU-hosted control plane. For email and support tools, check each vendor the same way.

Data residency for web analytics in Europe

Analytics is where EU data residency most often breaks without anyone noticing. The app can sit in an EU data centre while the analytics tag on every page sends each visitor's IP address, browser and current URL to a US company. In 2022 the Austrian, French and Italian data protection authorities each found a website's use of Google Analytics unlawful for exactly that reason. The EU–US Data Privacy Framework (2023) makes transfers to certified US companies lawful again for now, but it is the third such arrangement after Safe Harbor and Privacy Shield were both struck down, and it does not change who can compel access to the data.

Five questions settle whether an analytics setup is actually EU-resident:

  1. Where are the raw events stored, and where is the vendor incorporated? The CLOUD Act point above applies to analytics vendors exactly as it does to hosting.
  2. Is the visitor’s IP address stored, or only used and dropped?
  3. Does the tag set a cookie or write to localStorage? If it does, ePrivacy rules require consent first — which means a banner.
  4. Do your URLs carry ids (/customers/123)? Then the path itself is personal data, and the tag should report the route template instead.
  5. How long are raw events kept, and can you shorten it?

EU-resident analytics on HostStack

Events are stored on HostStack’s own control plane in Helsinki, Finland, under a Danish company — no US analytics vendor in the path.
Cookieless by default: the tag writes nothing to the visitor’s device, so it needs no consent banner.
IP addresses are used for a country lookup at ingest and never stored.
Record ids are scrubbed from paths, and apps behind a login can report route templates instead of URLs.
Raw events are kept for 35 days by default (up to 365 if you choose); longer ranges come from daily rollups.
It works for any site you own, hosted on HostStack or not, with one script tag of about 4 KB.

Setup and the exact data model are in the site analytics docs.

How HostStack keeps your data in the EU

Operated by MICCI, incorporated in Denmark (CVR 45587452) — an EU company, not a US one. No US CLOUD Act pathway.
All compute, managed databases, and backups run on Hetzner infrastructure in Finland (Helsinki) today — an EU member state — with additional EU regions in Germany (Nuremberg, Falkenstein) on the roadmap.
A Data Processing Agreement is available to every customer at signup, on every plan — not gated behind an Enterprise contract.
Sub-processors are limited to EEA-based providers (Hetzner — a German company running your workloads in its Finland region — for compute and storage, Stripe IE for billing, EU registrars and ACME for TLS) and listed in the DPA.
Environment variables and off-site backups are encrypted at rest with AES-256-GCM, and off-site backups stay within the EU. Persistent volumes created on or after 26 October 2026 are encrypted at rest too (LUKS2); older volumes are not.
No data is transferred to US infrastructure as part of normal operation, so there is no Standard Contractual Clauses / transfer-impact-assessment burden to carry.

More detail lives in our Data Processing Agreement, sub-processor list, and Trust Center.

Further reading

Frequently asked questions

What does EU data residency mean?

EU data residency means your data is physically stored and processed on servers located inside the European Union. On HostStack, every service, database, and backup lives in Finland (Helsinki) on Hetzner infrastructure today, with additional EU regions in Germany (Nuremberg, Falkenstein) on the roadmap. Data residency on its own, however, is not the same as data sovereignty — a US-owned provider can store data in the EU and still be compelled to hand it over under the US CLOUD Act. Full protection requires both EU location and EU legal incorporation.

Is hosting data in an EU region enough for GDPR compliance?

Not by itself. The Schrems II ruling found that data held by a US-incorporated company is at risk of US government access regardless of where the servers sit, because the US CLOUD Act reaches any US company globally. An EU region from a US provider (AWS Frankfurt, Render EU, Vercel) reduces latency and addresses storage location, but the controller still cannot guarantee that US authorities cannot compel access. The cleanest GDPR posture is a provider that is itself incorporated in the EU.

What is the US CLOUD Act and why does it matter for European companies?

The US CLOUD Act (2018) lets US authorities compel any US-incorporated company to disclose data it controls, even when that data is stored on servers outside the United States. For a European company, this means using a US cloud provider — even in an EU region — leaves a legal pathway for US access to personal data, which can conflict with GDPR Articles 44–50 on international transfers. Choosing an EU-incorporated provider removes that pathway.

Which PaaS and database providers are actually incorporated in the EU?

A minority of them. Among managed application and database platforms, HostStack (Denmark), Scaleway, OVHcloud and Clever Cloud (France), and Aiven (Finland) are EU-incorporated. Render, Railway, Fly.io, Vercel, Heroku, Supabase, Neon, and AWS RDS are all US-incorporated and offer an EU region but remain subject to the US CLOUD Act.

Which hosting providers and PaaS platforms help with EU data residency?

Look for three things together: servers in an EU member state, a company incorporated in the EU, and a Data Processing Agreement you can sign without an Enterprise contract. HostStack, Scaleway, OVHcloud, Clever Cloud and Aiven meet the first two; the US platforms (AWS, Render, Vercel, Heroku, Fly.io, Railway, Supabase, Neon) meet only the first. HostStack also publishes its DPA and sub-processor list and offers the DPA on every plan at signup.

Does Google Analytics meet EU data residency requirements?

Not on its own terms. Google Analytics is run by a US company, so the CLOUD Act reaches its data wherever it is stored, and its tag sends every visitor’s IP address and URL to Google. In 2022 the Austrian, French and Italian data protection authorities each found a website’s use of it unlawful. The EU–US Data Privacy Framework (2023) currently makes those transfers lawful for certified US companies, but it is the third such framework after Safe Harbor and Privacy Shield were struck down, and it does not make the data EU-resident.

Is there a web analytics tool that keeps data in Europe?

Yes. HostStack’s site analytics stores events on its own control plane in Helsinki, Finland, under a Danish company. It is cookieless by default, so it needs no consent banner, uses IP addresses only for a country lookup at ingest and never stores them, and works for any site you own, hosted on HostStack or not. Other EU-based options exist too; whichever you choose, check where the raw events are stored and where the vendor is incorporated.

Where is HostStack data stored, and who is the legal entity?

HostStack is operated by MICCI, a company registered in Denmark (CVR 45587452). All compute, databases, and backups are hosted on Hetzner infrastructure in Helsinki, Finland today — an EU member state — with additional EU regions in Germany on the roadmap. A Data Processing Agreement is available to every customer at signup, and the full sub-processor list is published in the DPA.

Does HostStack provide a DPA (Data Processing Agreement)?

Yes — to every customer, on every plan, at signup, not just on Enterprise contracts. The DPA names the controller-to-processor relationship, the EEA sub-processors (Hetzner DE/FI for compute and storage, Stripe IE for billing, plus EU registrars and ACME for TLS), and the incident-notification path. That makes a Schrems II / GDPR procurement review short.

Deploy on EU soil, under an EU company

Start for free — no card. Your data never leaves the EU.