EU & cross-borderUpdated 22 November 20269 min read

EU Data Residency on a Budget: Hosting AI on Hetzner From India

Architecture guidance for Indian teams hosting AI for EU customers on Hetzner's German and Finnish data centres: region choice, encryption, why access from India is still a transfer, DPA and SCCs.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Provider
Hetzner Online GmbH (Germany)
EU locations
Nuremberg, Falkenstein (Germany); Helsinki (Finland)
Non-EU locations
USA and Singapore
Processor contract
Hetzner offers an Art. 28 GDPR DPA
Access from India
Restricted transfer under GDPR Chapter V
Transfer tool
SCCs, Decision (EU) 2021/914, plus TIA

Quick answer

Hosting AI workloads on Hetzner's EU data centres (Nuremberg and Falkenstein in Germany, Helsinki in Finland) keeps EU personal data at rest in the EU, but it does not remove GDPR transfer obligations if engineers in India can access that data. You still need Hetzner's Article 28 DPA, SCCs with your EU customers, a transfer impact assessment and strong encryption and access controls.

  • Hetzner Online GmbH is a German provider with EU data centres in Nuremberg, Falkenstein and Helsinki; it also has US and Singapore locations, which you must avoid for EU-resident data.
  • EU residency reduces transfer risk but does not eliminate it: remote access from India to EU-hosted personal data is a transfer under GDPR Chapter V.
  • Sign Hetzner's Article 28 data processing agreement and list Hetzner as a sub-processor in customer DPAs.
  • Encrypt data at rest and in transit, keep keys under EU-side control where possible, and minimise who in India can see plaintext.
  • Self-managed infrastructure shifts security work onto you; GDPR Article 32 and DPDP section 8(5) both expect it done well.

Who this is for: Indian AI startups selling to EU customers, Platform and DevOps engineers, CTOs choosing EU hosting, Privacy leads preparing DPAs and TIAs, IT services firms hosting EU client workloads

Why Indian teams choose EU hosting for EU customers

EU customers increasingly ask a simple question in procurement: where is our data stored? For an Indian AI SaaS company, answering "in the EU" can shorten security reviews and reduce the scope of transfer analysis.

Hetzner Online GmbH is a German hosting provider with data centres in Nuremberg and Falkenstein (Germany) and Helsinki (Finland). It also operates locations in the USA and Singapore. It offers a data processing agreement under Article 28 GDPR. Many smaller teams look at Hetzner because they can run their own stack — databases, vector stores, self-hosted open-weight models — on EU infrastructure with a European provider.

What EU residency does and does not achieve

It doesIt does not
Keep data at rest in the EUMake remote access from India lawful by itself
Simplify customer questionnaires about storage locationReplace SCCs where Indian staff can access personal data
Reduce the volume of data actually transferredRemove your security obligations under GDPR Article 32
Make government-access analysis easier for stored dataCover data sent to non-EU model APIs from your EU servers

This page covers how to design the architecture so the residency claim is true and the remaining transfers are controlled. It does not compare prices or hardware; check hetzner.com for current products.

Choosing the region and pinning data to it

Pick EU locations only

Use only Hetzner's EU locations — Nuremberg, Falkenstein or Helsinki — for any resource holding EU personal data. Hetzner's US and Singapore locations are outside the EU; placing a replica, backup or snapshot there would defeat the residency claim and create a further transfer.

Germany or Finland?

Both are EU Member States, so GDPR applies identically. Practical factors include latency to your customers, the availability of the specific products you need in each location, and redundancy. A common pattern is primary in one location and backups in another EU location.

Pin everything, not just the database

Residency claims fail on secondary data. Check where each of these lives:

  • primary databases and object storage;
  • vector databases and embeddings;
  • model weights and fine-tuning datasets derived from customer data;
  • backups and snapshots;
  • logs, traces and error reports;
  • CI/CD artefacts that may contain test data;
  • monitoring and alerting services (often third-party SaaS outside the EU).

Watch outbound calls

If your EU-hosted application sends prompts with personal data to a model API hosted outside the EU, that is a transfer from your EU environment. Either self-host models in the EU or use providers with EU processing commitments and the right contracts.

Access from India is still a transfer

This is the point most teams get wrong. Under GDPR, making personal data accessible to a recipient in a third country is treated as a transfer, even if the bytes stay on servers in Germany. India has no EU adequacy decision. So when an engineer in Bengaluru opens a database shell on a Nuremberg server, or views a customer ticket with personal data, Chapter V applies.

What this means in practice

  • Your SCCs with EU customers (usually Module 2, controller to processor) must still cover your Indian entity's access.
  • Your transfer impact assessment should describe who in India can access what, under what controls.
  • If your EU subsidiary contracts with customers and your Indian entity is a sub-processor, Module 3 may apply between them.

Reducing access-driven transfers

  1. Role separation. Most engineers need access to infrastructure, not to customer personal data. Give them metadata and metrics, not rows.
  2. Just-in-time access. Time-bound, ticket-linked elevation for production data, approved and logged.
  3. Masked views. Support tools show tokenised or redacted fields by default.
  4. Bastion and session recording. Route all production access through an audited bastion in the EU.
  5. Break-glass procedures for incidents, with after-the-fact review.

These measures do not eliminate the transfer, but they shrink it and strengthen your TIA. See GDPR adequacy and India.

Encryption and key management

Encryption is your strongest supplementary measure for transfers and your baseline for Article 32 security.

At rest

  • Encrypt disks and volumes; on self-managed servers this is your responsibility to configure.
  • Encrypt database fields holding the most sensitive data at the application layer.
  • Encrypt backups before they leave the server, with separate keys.

In transit

  • TLS everywhere, including internal service-to-service traffic.
  • Private networking between servers where available; VPN or mTLS for administrative access.

Key management

  • Run key management in the EU, ideally under the control of your EU entity or the customer.
  • Separate key administrators from database administrators.
  • Log every key access.

Why key location matters

If personal data is encrypted and keys are only accessible in the EU, a person in India who can reach the storage layer sees ciphertext. That is a meaningful supplementary measure in a transfer impact assessment. It weakens once Indian staff can decrypt — for example, through application access — so combine it with the access controls in the previous section.

DPDP Rule 6(1)(a) lists encryption, obfuscation, masking and virtual tokens as security measures for Indian data; the same toolkit serves both regimes. See encryption and tokenisation for AI pipelines.

Contracts: Hetzner DPA, customer DPA and SCCs

Three contractual layers need to line up.

LayerPartiesPurpose
Hetzner DPA (Art. 28)You ↔ HetznerHetzner as your processor or sub-processor for hosting
Customer DPA (Art. 28) with SCCsEU customer ↔ your contracting entityYour processing for the customer; SCCs for access from India
Intra-group agreementYour EU entity ↔ your Indian entity (if both exist)Sub-processing and SCC Module 3 where applicable

Practical steps

  1. Accept Hetzner's DPA through its account process and keep a copy.
  2. List Hetzner as a sub-processor in customer DPAs, naming the EU locations used.
  3. Name your Indian entity as a sub-processor or importer where it accesses data, and incorporate SCCs.
  4. List all other sub-processors — monitoring, email, model APIs, support tools — with locations.
  5. Prepare a TIA describing EU residency, access from India, encryption and access controls.

If you are an Indian entity contracting directly

Your EU customer exports to you under SCC Module 2. Hetzner, as your sub-processor, is in the EU, which helps; but your Indian staff's access is the transfer the SCCs cover. For the clause-level detail, see DPA and SCCs for Indian vendors.

Operating it securely: your responsibilities

Self-managed hosting means you, not the provider, carry most security work. GDPR Article 32 requires measures appropriate to risk; customers will audit them.

Minimum operational baseline

  • Hardened images and automated patching.
  • Firewalls with default-deny inbound; no public database ports.
  • Identity: SSO and MFA for consoles and bastions; no shared accounts.
  • Monitoring: centralised logs in the EU, alerting on anomalous access.
  • Backups: encrypted, tested restores, in a second EU location.
  • Incident response: runbooks that let you notify customers fast enough for their 72-hour Article 33 deadline.
  • Self-hosted models: isolate inference servers, restrict who can change model weights and prompts, and log inputs and outputs according to your retention policy.

Indian legal overlay

  • For EU customers' data processed by your Indian entity under contract, DPDP section 17(1)(d) disapplies most DPDP duties, but section 8(5) reasonable security safeguards still apply.
  • CERT-In's April 2022 directions on incident reporting apply to your Indian systems; consider them in incident planning.
  • Indian users' data should not be mixed into EU environments without considering DPDP notice and transfer duties from 13 May 2027.

Common mistakes

  • Snapshots copied to a non-EU location.
  • Third-party monitoring tools receiving personal data in logs.
  • Every engineer in India holding production database credentials.
  • Claiming "EU-only" while calling a non-EU model API with customer data.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Use EU locations only

    Place all resources holding EU personal data in Nuremberg, Falkenstein or Helsinki.

    GDPR Ch. V

  2. Pin secondary data

    Confirm backups, snapshots, logs, embeddings and CI artefacts stay in EU locations.

    GDPR Art. 32

  3. Accept Hetzner's DPA

    Execute the Article 28 data processing agreement and record it.

    GDPR Art. 28

  4. Update customer DPAs

    List Hetzner and your Indian entity as sub-processors with locations.

    GDPR Art. 28(2)

  5. Cover access from India with SCCs

    Incorporate SCC Module 2 or 3 and describe access in the TIA.

    Decision (EU) 2021/914

  6. Encrypt with EU-held keys

    Encrypt at rest and in transit and keep key management under EU-side control.

    GDPR Art. 32

  7. Restrict and log production access

    Use just-in-time access, masked views and an audited EU bastion.

    GDPR Art. 32

  8. Check outbound model calls

    Prevent personal data flowing from EU servers to non-EU model APIs without a lawful basis.

    GDPR Ch. V

  9. Apply DPDP security for Indian entity

    Meet section 8(5) safeguards for EU client data processed by the Indian entity.

    DPDP s.17(1)(d), s.8(5)

Answers

Frequently asked questions

Does hosting on Hetzner Germany make my Indian company GDPR compliant?

No, not by itself. EU hosting keeps data at rest in the EU, which helps, but GDPR compliance also needs a lawful basis, processor contracts, security, breach handling and transfer safeguards. If staff in India can access the data, SCCs and a transfer impact assessment are still needed.

Is accessing EU servers from India a data transfer?

Yes. Making EU personal data accessible to people in India is treated as a transfer to a third country, even if the data stays on EU servers. India has no adequacy decision, so you need a Chapter V mechanism such as SCCs and appropriate supplementary measures.

Which Hetzner locations are in the EU?

Hetzner's data centres in Nuremberg and Falkenstein in Germany and Helsinki in Finland are in the EU. Hetzner also has locations in the USA and Singapore, which are outside the EU and should not hold EU-resident personal data if you are making an EU residency commitment.

Does Hetzner offer a GDPR data processing agreement?

Yes. Hetzner offers a data processing agreement under Article 28 GDPR. Accept it for your account, keep a record, and list Hetzner as a sub-processor in the DPAs you sign with your own EU customers.

Can I run open-source LLMs on Hetzner for EU customers?

Yes, self-hosting open-weight models in an EU location keeps prompts and outputs in the EU and avoids transfers to third-party model APIs. You remain responsible for security, access control and logging, and the AI Act may apply to the system you provide.

What encryption should I use for EU data accessed from India?

Encrypt data at rest and in transit, encrypt backups, and keep key management in the EU under restricted control. Encryption is strongest as a supplementary measure when people in India cannot decrypt personal data, so pair it with role separation and masked views.

Legal references and sources

  • GDPR, Regulation (EU) 2016/679 — Articles 28, 32 and Chapter V (official text)
  • Commission Implementing Decision (EU) 2021/914 — Standard Contractual Clauses (official text)
  • Digital Personal Data Protection Act, 2023 — Section 17(1)(d), section 8(5) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.