EU Data Sovereignty: What It Means for SaaS Companies
Your application is hosted in the EU. But does that mean all your data stays there?
Not necessarily. The APIs, CDNs, and third-party services your application relies on may process data outside Europe, even when your main infrastructure is based in the EU.
Let's look at what EU data sovereignty means, why it matters for SaaS companies, and what you should check when choosing a provider.
What Is EU Data Sovereignty?
EU data sovereignty is about maintaining control over how data is stored, processed, accessed, and governed, including which countries' laws may apply to it.
This goes beyond server locations. Even when your data is stored in the EU, you still need to know who can access it and which third parties are involved in processing it.
Data sovereignty vs. data residency vs. GDPR
These terms are closely related, but they don't mean the same thing.
| Term | What it means |
|---|---|
| Data sovereignty | Which laws and controls govern your data and who can access it. |
| Data residency | Where your data is physically stored or processed. |
| GDPR compliance | Meeting the GDPR's requirements for collecting, using, storing, protecting, and transferring personal data. |
One common misconception is that the General Data Protection Regulation (GDPR) requires all personal data to remain in the EU or the wider European Economic Area (EEA). It doesn't.
Personal data can be transferred outside the EEA when the applicable GDPR requirements are met. Depending on the circumstances, they may involve an adequacy decision or safeguards such as Standard Contractual Clauses (SCCs), along with additional measures that may be necessary.
The European Commission explains the rules for international data transfers in more detail.
So, EU data residency and GDPR compliance aren't the same thing. A SaaS provider can comply with GDPR without keeping all its data in Europe. Similarly, EU-only hosting doesn't automatically guarantee GDPR compliance.
There’s also an important difference between keeping data in the EU and preventing access to it from outside the EU. A provider might store data in Frankfurt, for example, while allowing its support team in another country to access it remotely. These are separate considerations when evaluating a service.
Why EU Data Sovereignty Matters for SaaS
As SaaS applications rely on more cloud services, external APIs, and AI tools, keeping track of where data goes becomes more complicated.
The EU is paying closer attention to this, too. The European Commission's Data Union Strategy identifies safeguarding EU data sovereignty as one of its priorities, alongside making more data available for AI and simplifying data rules.
For SaaS companies, this isn't just a regulatory discussion. Customers, especially those in regulated industries or large enterprises, may have specific requirements for where their data is processed and who can access it. Even when EU-only processing isn't legally required, it may still be a contractual or security requirement.
To meet those expectations, companies need to understand not only their own infrastructure but also the third-party services their applications depend on.
Your app is hosted in the EU. Is your entire stack in the EU?
Let's say you're building a SaaS application for European customers. Your backend runs in Frankfurt, your database is hosted in the same region, and you've configured your cloud provider to keep your primary infrastructure in the EU. So far, so good.
But your application also uses a few third-party services:
- An analytics platform that collects user events.
- An error monitoring tool that receives application logs.
- A CDN that delivers content to users around the world.
- A feature management platform that controls which features are available to different users.
Now, here's the question: where does the data handled by each of these services actually go?
Your analytics platform might process user events outside Europe. Your monitoring tool might receive logs containing IP addresses or user identifiers. And your CDN might route requests through infrastructure in another region.
None of these automatically creates a GDPR violation. But they're data flows you should understand, especially if your organization has specific EU residency requirements.
It helps to look at three separate things: where data is stored, where it's processed, and who can access it. For example, storing application logs in an EU data center doesn't necessarily prevent a support engineer outside the EU from accessing them.
For each service, check which of these requirements it can meet and which ones need additional control.
Not Every Third-Party Service Needs Your User Data
Here's something that's easy to overlook: two SaaS tools providing similar functionality might handle user data very differently. For example, some services need to receive user attributes to perform their core functions, while others can process that information directly within your application.
The difference matters because every additional data transfer may introduce new security, privacy, or compliance considerations. This is where data minimization comes in. One of the GDPR's key principles is to limit personal data processing to what's necessary for a specific purpose.
For developers, this raises a practical question: does the service really need your end users' data, or could it do its job without receiving that information?
Feature flagging is a good example of how the underlying architecture can make a difference.
What Does EU Data Sovereignty Mean for Feature Flagging?
Feature flags let developers enable or disable functionality without deploying new code. They're commonly used for gradual rollouts, targeted releases, and testing features in production.
Since feature management platforms become part of your application's infrastructure, their architecture matters too. Two things are worth checking: where configurations are delivered from and where targeting rules are evaluated.
1. Where is your feature flag configuration delivered from?
Feature flag SDKs need access to configurations containing flag values and targeting rules.
Many feature management platforms distribute these configurations through CDNs to improve performance and availability.
However, a global CDN may use infrastructure outside the EU, depending on how requests are routed and where configurations are stored.
If your organization has strict regional requirements, check whether your feature management provider supports EU-only configuration delivery.
2. Where are feature flags evaluated?
Some feature management solutions evaluate targeting rules remotely, which may require sending user attributes to an external service. Others evaluate feature flags locally, inside the application.
Let's say you want to enable a new feature only for Premium customers. With remote evaluation, your application may need to send the customer's subscription information to the feature management provider to determine whether the feature should be enabled.
With local evaluation, the SDK can make that decision inside your application, using the subscription information it already has. This means user attributes don't need to be sent to the provider just to evaluate a feature flag.
There's a trade-off to consider, though. With local evaluation, the SDK needs access to the targeting rules. Those rules may contain user identifiers or other information you wouldn't want to expose, especially in a client-side application where the configuration can be inspected. It's therefore worth checking how the platform handles sensitive values in its targeting rules.
How ConfigCat Supports EU Data Sovereignty
ConfigCat is an EU-based feature management company headquartered in Hungary, with its main infrastructure and database hosted in the European Union.
ConfigCat offers an EU-only CDN option for feature flag configuration delivery, while its SDKs evaluate targeting rules locally. Here's what that means in practice.
EU-only CDN
ConfigCat's Data Governance feature lets you choose where feature flag configurations are published and delivered.
You can select between two options:
- Global CDN (default): Configurations are delivered through a globally distributed CDN for low latency and high availability.
- EU Only: Configurations are published to and served from EU CDN nodes.
If you select EU Only, make sure you also set the corresponding Data Governance option in your ConfigCat SDK. Otherwise, requests may need to be redirected to the EU CDN, which can increase response times.
The EU Only setting applies to configuration delivery. It doesn't cover every service or subprocessor ConfigCat uses, so those still need to be reviewed separately if you have broader data residency requirements.
Local feature flag evaluation
ConfigCat SDKs evaluate feature flags locally, inside your application. The SDK downloads and caches the feature flag configuration, then evaluates targeting rules without sending your end users' targeting attributes to ConfigCat. Because the configuration is cached, the SDK doesn't need to make a network request every time it evaluates a flag.
Remember the concern about sensitive targeting values? ConfigCat supports confidential targeting comparators, which let you use hashed comparison values instead of storing them as cleartext in feature flag configurations.
Built with security in mind
In addition to being an EU-based company, ConfigCat is ISO/IEC 27001:2022 certified. Our Trust Center also provides access to security documentation, our Data Processing Agreement, and subprocessor information for vendor security reviews.
What to Check When Choosing a SaaS Provider for EU Data Residency
Before adding a new SaaS service to your application, here are a few questions worth asking:
- Where is data stored and processed? Check the location of databases, backups, APIs, and other supporting infrastructure.
- Can data be accessed from outside the EU? Find out where support and operations teams are located and how access is controlled.
- Which subprocessors are involved? Review the provider's subprocessor list and any international data transfers.
- Does the provider offer EU-only data residency options? Check what these options actually cover, including CDNs and other supporting services.
- Can you control or minimize the data being shared? Look for options such as local processing, regional endpoints, and configurable data collection.
These questions won't replace a formal compliance review, but they can help you identify potential issues before introducing a new service into production.
Final Thoughts
EU data sovereignty isn't just about choosing an EU hosting region. It's about understanding how data moves through your application and which services have access to it.
And as we've seen, even an EU-hosted application can rely on services that process information elsewhere. That's why it's worth looking beyond hosting locations and checking how your entire SaaS stack handles data.
For feature management, ConfigCat combines an EU-based company and EU-hosted core infrastructure with local feature flag evaluation and an EU-only CDN option.
This gives engineering teams more control over configuration delivery while keeping user attributes within their applications during feature flag evaluation.
Want to learn more? Explore ConfigCat's Data Governance options or get started for free.
You can stay up to date with ConfigCat on X, Facebook, LinkedIn, GitHub, and the News & Product Updates page.
