Skip to content

Cookie Settings

We use necessary cookies and Google reCAPTCHA to protect our forms from spam. You can find details in our privacy policy.

Privacy Policy
FragonStudios

By Danijel Balog, Founder, Fragon Studios · Last updated: 2026-11-13

GDPR-compliant hosting for apps and web applications

Updated: By Danijel Balog, founder of Fragon Studios in Linz

What matters when hosting personal data from an Austrian point of view, what a server location in the EU does not solve on its own, and when a large US provider is still the right choice.

A server in the EU alone does not make hosting GDPR-compliant.

In short

  1. Besides the server location, what counts is a data processing agreement under Art. 28 GDPR, a basis for every transfer to a third country, known subprocessors and appropriate technical measures.
  2. The server does not have to be in Austria. Under data protection law, a data centre in Germany or Finland is on a par with one in Vienna.
  3. AWS, Azure and Google Cloud are permitted in principle if the US recipient takes part in the EU-US Data Privacy Framework. We consider the legal situation there less stable.
  4. Fragon Cloud runs on dedicated servers at Hetzner in Germany and Finland, with a DPA and without transfers to third countries.
  5. This page gives a technical overview and is not legal advice.

What makes hosting GDPR-compliant?

Six points decide it, from the server location to access control.

As the operator of the application, you remain responsible. The hosting provider is a processor and must be able to show that it processes the data only on your instructions and with suitable safeguards.

  • Server location

    A data centre in the EU, in the EEA or in a country with an adequacy decision, also for backups and logs.

  • Data processing agreement

    A DPA under Art. 28 GDPR with the hosting provider, in writing or electronically.

  • Third-country transfers

    None, or a clear basis under Art. 44-50 GDPR.

  • Subprocessors

    A list of all other service providers and where they are based.

  • Backups

    Regular, stored separately, restore tested.

  • Access control

    Few people with access, personal accounts, logging.

This is general guidance, not legal advice.

Does the server have to be in Austria?

No. Under data protection law, a data centre in Germany or Finland is on a par with one in Vienna.

The GDPR applies in the same way across the whole EU. Stricter requirements can come from industry rules, customer contracts or tenders.

What matters is who has access to the data and whether it leaves the EU. For transfers, the Austrian Data Protection Authority looks at whether the recipient is based in a third country, not at the address of the data centre.

Do I need a data processing agreement with my hosting provider?

Yes, as soon as the hosting provider processes personal data for you, and practically every host of an app or web application does.

The agreement follows Art. 28 GDPR.

  • processing only on documented instructions
  • confidentiality of everyone with access
  • technical and organisational measures under Art. 32 GDPR
  • rules for further processors
  • support with access and erasure requests from data subjects
  • support with data protection impact assessments and notification duties
  • notification of data breaches without undue delay
  • deletion or return of the data after the contract ends
  • evidence and audits, including inspections

With large providers, the DPA is usually a standard document that you accept in your account. That is normal. You should still read it, especially the list of subprocessors and the rules on how you are told about new ones.

Can I use AWS, Azure or Google Cloud?

In principle yes, if the US recipient takes part in the EU-US Data Privacy Framework.

Since the European Commission's adequacy decision of 10 July 2023, transfers to US companies that take part in the framework have been permitted. The rules for transfers to third countries are set out in Art. 44-50 GDPR.

No further safeguards needed

Adequacy decision, Art. 45

  • for the USA since 10 July 2023, if the recipient takes part in the Data Privacy Framework
Safeguards and assessment

Without a decision, Art. 46

  • appropriate safeguards, usually standard contractual clauses
  • a case-by-case assessment, as the CJEU required in its Schrems II ruling
Only as an exception

Exceptions, Art. 49

  • for occasional transfers in exceptional cases

According to the Austrian Data Protection Authority, you must check before every transfer whether the US recipient is on the Data Privacy Framework List. If it is not, you need a safeguard under Art. 46 or an exception under Art. 49 GDPR. This also applies to services you add on the side, such as email delivery, error tracking, analytics or AI APIs.

A data centre in Frankfurt or Vienna does not turn a US corporation into a European provider. That is why we consider the legal situation with US providers less stable than with a provider without US ties. This is our assessment as developers, not legal advice.

The adequacy decision is being challenged in court and applies until there is a ruling.

The General Court of the EU dismissed an action against it on 3 September 2025 (case T-553/23), and an appeal against that judgment has been lodged with the CJEU (C-703/25 P). The decision applies until there is a ruling.

What technical measures are part of secure hosting?

Art. 32 GDPR requires measures that are appropriate to the risk.

In practice that means encryption, separate backups with tested restores and strict access control.

  • encryption in transit and on the storage media
  • daily backups at a separate location
  • restores tried out regularly instead of just assumed to work
  • access only for named people, with personal accounts
  • updates for the operating system and dependencies on a fixed schedule
  • logs that are kept only as long as necessary

A backup that has never been restored is a hope. Ask your hosting provider how long a restore takes and when it was last tested. If your application is already running and you are unsure where it stands on security and data protection, a software audit will tell you.

What does Fragon Cloud offer for GDPR-compliant hosting?

Fragon Cloud runs on dedicated servers at Hetzner in Germany and Finland, with a DPA under Art. 28 GDPR and without transfers to third countries.

The data centres in Nuremberg, Falkenstein and Helsinki are run by Hetzner Online GmbH, a German company.

  • 14 daysis how long the daily backups are kept, on geographically separate storage.
  • 30 daysnotice period, with no automatic twelve-month renewal.
From the published information on Fragon Cloud.
ItemFragon Cloud
LocationsHetzner in Germany and Finland (Nuremberg, Falkenstein, Helsinki)
SubprocessorHetzner Online GmbH, Germany (data centres)
HardwareAMD EPYC and Ryzen Pro, dedicated cores
StorageNVMe SSD with RAID, encrypted locally
Backupsdaily, kept for 14 days, geographically separate storage
Restoreon request within a few hours
ContractDPA under Art. 28 GDPR, 30-day notice period
We take care of deployment, SSL, monitoring and backups, and you talk directly to the engineer who runs the server.

On the Fragon Cloud page we describe how we run the software we build for our customers. We take care of deployment, SSL, monitoring and backups.

The difference from a large provider is less the technology than the contact. You talk directly to the engineer in Austria who runs the server and usually built your application too.

When is a large US cloud provider still the better fit?

For most applications of small and medium-sized businesses (SMEs), infrastructure like Fragon Cloud is enough. For the rest, AWS, Azure or Google Cloud is the more honest recommendation.

  • users on several continents who need data centres outside Europe
  • heavily fluctuating load that has to scale up automatically many times over
  • special managed services that only exist there
  • existing group contracts or requirements from your own IT department

In these cases we advise on AWS, Azure and GCP and make sure that region, DPA and subprocessors fit your data. We do not build projects with GDPR-sensitive data on US providers ourselves. The application stays portable, the stack is standard, and a later move is not a rebuild.

Not legal advice

This page gives a technical overview. Whether your specific processing is GDPR-compliant is for your data protection officer or a data protection lawyer to clarify.

Frequently asked questions

Is a server in the EU enough for the GDPR?

No. The location is an important point, but not the only one.

You also need a DPA under Art. 28 GDPR, a basis for every transfer to a third country, known subprocessors and appropriate technical measures.

Where are the Fragon Cloud servers?

At Hetzner in Germany and Finland.

In the data centres in Nuremberg, Falkenstein and Helsinki. Fragon Cloud itself does not transfer any data to third countries.

How long are backups kept at Fragon Cloud?

14 days by default.

Backups run daily to geographically separate storage. Longer retention is available at extra cost, and a restore takes a few hours on request.

Can I move my application to another hosting provider later?

Yes. Fragon Cloud has a 30-day notice period.

There is no automatic twelve-month renewal, and we help with the migration, wherever it goes.

Further reading

Want an assessment of hosting for your application?

Describe your application and the data it processes. We reply within one business day with an assessment of hardware, location and price.