EU-first: you know where your data is

Five checkable commitments and Staffbite's own dependency map: where the data is, whose law applies to it and how you can get out if you need to.

EU-first means that we build systems so that the data is in the EU by default, and the location, jurisdiction and exit path of every dependency are known.

More and more European companies see technology dependencies as a business risk (Bitkom 2026, Gartner 2025). In Finland, interviews by the Digipool of the National Emergency Supply Organisation show that the risk is recognised, but concrete plans are often missing. The sources are below.

We do not promise 100 % EU. We promise that you know where your data is, whose law applies to it and how to get out if you need to.

Full technological independence is not a realistic goal, as Finland's Digipool also notes. Conscious decisions about dependencies are possible.

Request a dependency mapping

Updated

Five commitments

Every project of ours follows these, and each one can be checked.

  1. Data in the EU by default. Hosting, database and backups are in the EU. Exceptions are recorded.
  2. Jurisdiction is disclosed. For every service we state the location and the company's home country. For example, Gemini in Vertex AI's EU multi-region: processing takes place in EU member states, but the provider, Google, is a US company.
  3. An exit plan for every critical dependency: how the service is replaced, how long it takes and what it costs.
  4. The model can be changed. The architecture is not tied to one language model. Gemini, Mistral or open weights on your own or a European provider's infrastructure are a configuration question, not a rewrite.
  5. Privacy by design: no third-party tracking scripts, no tracking cookies and no unnecessary personal data. The only analytics is self-hosted, cookieless Umami. On 8 October 2026 the Finnish Data Protection Ombudsman imposed an administrative fine of €33,000 on a company offering therapy appointment booking, because the tracking tools on its website passed health-related data to Google, Meta and Microsoft. The decision is not yet final (tietosuoja.fi, in Finnish).

Our own dependency map

The same structure we make for clients. The map also includes our own US dependencies.

Service Used for Location Company's home country Exit path Status
UpCloud site hosting and PostgreSQL database Helsinki data centre (Location and data) Finland the application is a single Go program in a container and the data is in standard PostgreSQL, so both can be moved to another provider in use
Google Workspace email karo@staffbite.fi, including notifications of contact requests Google's data centres United States the domain's MX records are switched to another email service and the messages are migrated in use
GitHub source code and automated tests code on GitHub's servers; no visitor or client data United States the code is a git repository that can be moved to any git service in use
Fonts and scripts the site's appearance and functionality the site's own server; the only exception is the self-hosted Umami (below), no requests to other companies' services (Privacy) no external supplier no external dependency in use
Gemini, Vertex AI (EU multi-region) the AI architect on this site, solution sketches and internal summaries of contact requests processing in EU member states United States the model is changed through configuration, for example to Mistral or to open weights on EU infrastructure in use
Lettermint notifications to Staffbite of messages sent with the contact form and the AI architect's contact card EU (Netherlands and Germany) Netherlands sending email is a separate part of the application that can be switched to another service in use
Umami, self-hosted cookieless visitor analytics Hetzner's data centre in the EU Germany the software and the data are under our own control, so they can be moved to another server in use

UpCloud also has data centres in the United States, so we say it precisely: the data is in UpCloud's Helsinki data centre, and UpCloud is a Finnish company.

Gemini's EU multi-region keeps the model's processing in EU member states, but it does not guarantee that nothing is retained. Google does not use customer data to train models without permission, but caching is on by default, and Google may log prompts to detect abuse (Google Cloud: Vertex AI data governance). We do not use grounding with Google Search, because it stores search logs for 3 days and cannot be turned off. How the AI architect handles data is described in the privacy policy.

Location does not decide jurisdiction

Data location tells where the data sits on disk and where it is processed. Jurisdiction tells which country's authorities can compel the provider.

The US CLOUD Act (18 U.S.C. § 2713 (Figure and source)) requires a US provider to disclose data in its possession, custody or control under a valid order, regardless of where the data is located (Cornell LII).

At a hearing of the French Senate on 10 June 2025, the director of legal affairs of Microsoft France could not guarantee under oath that French public-sector data would not be handed over to US authorities without France's consent (French Senate).

Finland's Digipool puts it the same way: “technical sovereignty is not solved by the location of the data alone” (our translation from Finnish).

Processing in the EU removes much of the transfer risk. On its own, it does not settle which country's law the provider is subject to.

Dependencies are a business risk

In the companies of Finland's National Emergency Supply Organisation, as much as 75 % of applications (Figure and source) run on international cloud services. The risk is recognised, but according to the report “concrete plans or measures have not been widely made” (Digipooli and Technology Industries of Finland, 02/2026; interviews with 20 business decision-makers; our translation from Finnish).

On 24 March 2026 the Finnish Ministry of Justice cancelled its decision to build a new election information system on AWS, because “the international political situation has changed” (our translation). The 2027 Finnish parliamentary elections will be run with the current system, whose servers are in Finland (Finnish Government, 24 March 2026, in Finnish).

Sovereignty also has a price. In the ministry's comparison, the cloud would have cost about €1.6 million over ten years and a traditional data centre about €6 million (Yle, 6 November 2025, in Finnish). That is why dependencies should be chosen consciously, not all avoided.

In Germany, 85 % of companies (Figure and source) consider the country too dependent on US cloud providers. In the same survey, 43 % said there are no European alternatives that meet their requirements (Bitkom Cloud Report 2026, n = 603, 09/2026).

What the law says now

Data Act

The cloud-switching rules of the EU Data Act have applied since 12 September 2025. A customer can initiate a switch with at most two months' notice, and the transition period is at most 30 days. From 12 January 2027, no separate switching charges may be made (Bundesnetzagentur).

The act eases the contract terms, but it does not remove technical lock-in. That is why the exit is designed into the architecture.

AI Act

The prohibited practices and Article 4 on AI literacy have applied since 2 February 2025, the obligations for general-purpose AI models since 2 August 2025 and the transparency obligations since 2 August 2026. The Digital Omnibus, which entered into force in July 2026, moved the obligations for the high-risk systems of Annex III to 2 December 2027 and those for systems embedded in products to 2 August 2028 (European Commission, 19 October 2026).

Data Privacy Framework and GDPR

The EU–US Data Privacy Framework (DPF) is in force, but its basis has again been called into question. On 31 July 2026 the European Data Protection Board asked the Commission to assess how durable it is (EDPB).

The GDPR does not require EU hosting. However, transfers outside the EU without adequate safeguards have led to the largest GDPR fines: Meta €1.2 billion (2023), TikTok €530 million (2 May 2025) and Yango €100 million (8 May 2026), a case in which the Finnish Data Protection Ombudsman took part (tietosuoja.fi, in Finnish).

Dependency mapping

A dependency mapping is a short, scoped review of your company's own technology and AI dependencies. You get:

  • A dependency map with the same structure as above: service, purpose, location, the company's home country, exit path and status.
  • Exit priorities: which dependencies are critical and where to start.

The mapping is not legal advice. The same content is also the EU module of the AI Mindset workshop.

Tell us where you are starting from, and we will tell you how the mapping would work for you.

Frequently asked questions

Is data safe if it is in the EU but the provider is a US company?

Location settles part of it, not all of it. Processing in the EU reduces transfers outside the EU, but the US CLOUD Act applies to a US provider regardless of where the data is. That is why we state both the location and the company's home country for every service, and plan an exit path.

Does the GDPR require data to be in the EU?

No. The GDPR allows transfers outside the EU with appropriate safeguards. However, the largest GDPR fines have come precisely from deficient transfers, so processing in the EU removes much of the risk.

What does the Data Act mean for switching cloud providers?

A cloud service can be switched with at most two months' notice and a 30-day transition, and from 12 January 2027 no separate switching charges may be made. The act does not solve technical lock-in, so the exit is designed into the architecture.

What does the AI Act require from us now?

The prohibited practices and Article 4 on AI literacy apply. The Digital Omnibus eased Article 4 in July 2026: it requires measures to support AI literacy. The obligations for high-risk systems start on 2 December 2027. We do not give legal advice.

Does Staffbite use US services itself?

Yes. Email runs through Google Workspace, the source code is on GitHub, and the AI architect uses Google's Gemini model in Vertex AI's EU multi-region. We list them in our dependency map with their locations and exit paths.

What does a dependency mapping include?

A short, scoped review of your company's technology and AI dependencies. The result is a dependency map showing each service's purpose, location, the company's home country and exit path, together with exit priorities: which dependencies are critical and where to start.

Get in touch

Start planning now

Tell the AI architect what you are planning. It answers right away and can put together a solution sketch from the conversation that you can share with your team.

Ask the AI architect

Send a message with the form

Staffbite is based in Helsinki (Location and data). Read about EU-first