Article

When European jurisdiction is not enough

When a European authority, defense organization, or corporation stores data with a technology provider subject to US jurisdiction, it may also become exposed to aspects of US law that are often overlooked during procurement processes.

One of the most important examples is the Clarifying Lawful Overseas Use of Data Act—commonly known as the CLOUD Act—enacted in the United States in 2018. Its implications are increasingly relevant for organizations assessing how sensitive information, communications services, and digital infrastructure should be procured and managed.

What the law actually does

The CLOUD Act clarifies that certain providers subject to US jurisdiction can be required to disclose data within their possession, custody, or control—regardless of where that data is physically stored. As a result, data hosted in an EU facility may still be subject to a lawful US request if the provider falls within the scope of the relevant US legal framework.

The location of the server does not determine the jurisdiction of the data. The provider’s home country does.

The reach of the CLOUD Act extends beyond providers headquartered in the US. It applies to any company with a physical presence in the US and can extend to EU entities whose service provider has a corporate link to the US, such as a US parent company or subsidiary. For European organizations using services with US corporate ties, it is worth understanding whether and how those connections affect the legal framework governing their data.

In practice, information that may be subject to disclosure includes account information, emails, chat messages, and files stored within the service. Requests are typically subject to oversight by a court or independent authority and must relate to the prevention, detection, investigation, or prosecution of serious crime.

Data sovereignty has become an increasingly important consideration in procurement decisions.

The relationship with European law

The General Data Protection Regulation (GDPR) governs how personal data of EU residents must be handled, stored, and transferred—and places strict limits on transfers to third countries without adequate protection. The CLOUD Act operates within a different legal framework. When a US authority requests data from a provider subject to US jurisdiction, the European customer may have limited practical options.

This places globally operating providers in a complex position. A company subject to both European and US legal obligations may face competing requirements when responding to government access requests. The CLOUD Act includes mechanisms that allow providers to challenge requests that may conflict with foreign law, but these are limited in scope. The broader legal questions remain an active topic of debate among European data protection authorities and policymakers. It is one reason why data sovereignty has become an increasingly important consideration in procurement decisions across both the public and private sectors in Europe.

A related instrument, the Foreign Intelligence Surveillance Act, FISA, addresses a different dimension of the same question. Where the CLOUD Act operates through law enforcement with some judicial oversight, FISA operates through intelligence collection, with different procedural conditions. Together, these instruments illustrate why the question of where a provider is headquartered has become relevant alongside the question of where its servers are located.

What this means for procurement

For organizations handling sensitive information, selecting a provider involves more than evaluating functionality, performance, and security controls.

Procurement teams increasingly consider whether the provider itself is subject to legal obligations that could affect how customer data is handled, disclosed, or accessed. A solution may be hosted within Europe and still be connected to legal frameworks outside Europe through ownership structures, corporate relationships, or operational control.

Whether that exposure is acceptable depends on the nature of the information involved, the organization’s risk profile, and its regulatory obligations. For a growing number of organizations, questions of jurisdiction and sovereignty have become part of the security assessment.

The question is not only whether a solution is secure. It is whether the organization operating it is subject to legal obligations that could affect the confidentiality, control, or governance of the data entrusted to it.

Sectra's perspective

  • The platform that underpins Sectra Tiger/E is hosted in geo-redundant facilities located in Sweden. This decision is specific and deliberate: the data that flows through Tiger/E’s secure communications environment stays in Europe and is under European jurisdiction. That is an architectural choice—not an incidental outcome.
  • For many of our customers, this structure matters because it aligns operational control, hosting location, and legal jurisdiction within Europe. For organizations where data sovereignty is a procurement requirement rather than a preference, knowing where data is held and which legal frameworks apply to it is part of how trust is established.
  • For nearly 50 years, Sectra has developed secure communication solutions for organizations where confidentiality, availability, and trust are essential. That experience shapes how we approach sovereignty: not as a compliance requirement, but as a foundational design principle.
  • As European organizations navigate an increasingly complex regulatory and geopolitical landscape, the origin, ownership, and jurisdictional exposure of technology providers are becoming important factors in security and procurement decisions.

Let's talk

Fill in this form below and a Sectra representative will contact you.

We recognize and respect the importance of your privacy. By submitting this form, you agree to our Privacy policy >>

This site is protected by reCAPTCHA.

Related reading

Related products