Imagine you arrive at the plant in the morning, want to open the process data from last night’s shift, and nothing works. Not because of a server failure, but because an external provider has blocked access. Many IT and quality managers in manufacturing only ask themselves this question when it is too late. Data sovereignty is the answer, and it starts long before an emergency.
In April 2024, the German state of Schleswig Holstein became the first federal state to decide by cabinet resolution to move its state administration to a digitally sovereign IT workplace: from Microsoft Office to LibreOffice, from Windows to Linux and from Exchange to open source alternatives. What applies to a state administration applies just as much to an automotive supplier: anyone who does not control their quality data themselves may end up handing over the ability of their entire operation to act.

This article explains what data sovereignty means for manufacturing companies, why the server location is the wrong metric and how to secure control over your data across its entire lifecycle. It is written for IT management, compliance and quality managers in discrete manufacturing.
- Data sovereignty means deciding at all times where data is stored, who can access it and how long it remains available.
- The server location does not determine control over access. What matters is the provider’s jurisdiction: a US company remains subject to the US CLOUD Act even with an EU data center.
- For manufacturers, data sovereignty is especially critical for quality and production data that must remain provable for many years.
- Real sovereignty rests on three levers: sole control over access, an open vendor neutral data format and a documented cloud exit strategy.
Jurisdiction counts
Not the server location but the provider’s jurisdiction decides who can access the data.
43 % without plan B
Only 57 % of the companies surveyed have an exit strategy (Lünendonk 2026).
Archive openly
An open archive format preserves evidence, even after the source system is shut down.
01 · Definition
What does data sovereignty mean for manufacturers?
Data sovereignty describes a company’s ability to control its data, access and digital processes independently and in compliance with the law. For a manufacturing company, this is not an abstract IT question but an operational requirement. Anyone handling a complaint, passing an audit or defending a product liability case needs reliable access to the related process and quality data at all times.
The difference from data protection is important. Data protection governs how personal data may be processed. Data sovereignty goes further and asks who actually controls access. A system can be fully GDPR compliant and still not sovereign if a third party could block access technically or legally.
83 %
of the companies surveyed consider it realistic that a cloud provider could restrict or shut off access unilaterally
Source: Lünendonk study Digital Sovereignty, 2026
43 %
of the companies surveyed have no exit strategy for switching providers
Source: Lünendonk study Digital Sovereignty, 2026
10 years
after a product is placed on the market, product liability claims expire in Germany
Source: Section 13 ProdHaftG
2018
the year the US CLOUD Act came into force
Source: US Congress
| Term | Key question | Governs | Example in manufacturing |
|---|---|---|---|
| Data sovereignty | Who controls access? | Control over storage location, access and availability | Evidence remains accessible even under sanctions |
| Data protection | How may data be processed? | Handling of personal data (GDPR) | Storing worker IDs in inspection logs lawfully |
| Data security | How is data protected technically? | Protection against loss, manipulation and third party access | Encryption and access control in the archive |
The three sub questions, where is the data stored, who can access it and how long does it remain available, are the practical core. They can be answered for each system individually. If one of the answers is unclear, sovereignty is not given at that point.
02 · Server location
Why does the server location not determine control over access?
The most common misconception is: if the servers are in Germany or the EU, the data is sovereign. That is not true. On paper, everything looks solid: redundant data centers in the EU, modern firewalls, a security operations center around the clock. What matters, however, is not the physical location but the jurisdiction the provider is subject to.
The US CLOUD Act obliges US providers to hand over data on the order of US authorities, regardless of whether the servers are in Frankfurt, Paris or Amsterdam. As long as the provider is a US company, such as Microsoft, Amazon or Google, US law applies. A data center in the EU does not change that. The law does not require the affected company to be notified.
The EU counters with the EU Data Act, which has applied since September 2025. Among other things, it requires cloud providers to take appropriate measures against unlawful access by third countries. However, there is no legal act that overrides the US CLOUD Act. The core message therefore stands: a server location in the EU does not automatically protect against US access. What counts is the jurisdiction the provider is subject to.
Common mistake
A supplier moves its quality database to a cloud, arguing that the data center is in Germany. The provider is a US corporation.
In an emergency, it is not the location in Germany but the provider’s jurisdiction that decides on access. The supposed security gain does not exist.
| Model | Server location | Provider jurisdiction | Control over access |
|---|---|---|---|
| US cloud, US data center | USA | USA | Low |
| US cloud, EU data center | EU | USA | Low |
| EU cloud, EU provider | EU | EU | Medium |
| On premises | Own plant | Own company | High |
Control over access means sole control over who can view and hand over the data. The provider’s jurisdiction weighs more heavily than the server location.
This is exactly the logic that first public authorities are acting on. Schleswig Holstein is gradually moving its state administration to open source to fundamentally reduce its dependence on US providers. For a manufacturer, the answer does not have to be a complete software switch. The decisive step is to keep evidence relevant data out of the reach of a foreign legal system, above all through a sound cloud exit strategy.
03 · Levels
What are the three levels of data sovereignty in production?
Data sovereignty can be broken down into three levels that must each be met independently. If one is missing, control has gaps, even if the other two are implemented perfectly.
Level 1
Control over access
Control over who accesses the data must lie with the company, not with a provider subject to a foreign legal system.
Sovereign if
The provider is subject exclusively to European law or the data is stored on premises, no third country can force disclosure and access is logged.
At risk if
A US provider is involved, even with an EU data center, or access is possible without notification.
Key question: Can a third party force or block access against my will?
Level 2
Control over format
Data in a proprietary format ties the company to a provider. Open formats keep data readable for decades, independently of the source system.
Sovereign if
Archiving uses an open, documented format, data remains readable after the source system is replaced and no license agreement limits access to your own historical data.
At risk if
The data can only be read with the provider’s software or a format change forces an expensive migration.
Key question: Will I still be able to read my data in ten years without today’s provider?
Level 3
Control over switching
Without a documented exit option, a switch in a crisis takes months rather than days. Since September 2025, the EU Data Act has required cloud providers to make switching technically possible.
Sovereign if
A documented cloud exit strategy exists, data portability is secured contractually and technically and a path back on premises is defined.
At risk if
No exit plan is documented or a switch would only be possible with great effort.
Key question: How long would it take me to get away from this provider completely?
Control over access, format and switching together form the practical definition of data sovereignty. A company that can answer all three questions remains able to act, even if the political or economic situation changes.
Keep your production data under your own control
The CHRONOS white paper shows how to meet retention obligations without keeping legacy systems running and how to keep access, format and retention of your data in your own hands.
04 · Crisis
What happens when access is lost in a crisis?
The most effective test of sovereignty is playing through a crisis. Not how well everything runs in normal operation, but what happens when access is lost. According to Lünendonk, 83 percent of the companies surveyed consider such a scenario realistic.
| Scenario | Without sovereignty | With sovereignty | Measure |
|---|---|---|---|
| Provider blocks access because of sanctions | Quality data is stored with a US cloud provider. Complaints and audit evidence come to a halt because the evidence is unreachable. | Evidence is archived on premises with integrity protection. Complaints and audits continue without interruption. | Bring evidence relevant data under your own control before an emergency occurs. |
| Source system is shut down | Data can only be read in the legacy system. A product liability case years later can no longer be proven. | Data was archived openly before the shutdown. The database content remains structured and searchable. | Transfer data into an open archive format before every system replacement. |
Key message
“Sovereignty is not a state you reach. It is a decision you make again with every architecture.”
Amadeus Lederle, Chief Technology Executive, CSP Intelligence GmbH
The decisive factor is timing. Anyone who only acts in a crisis acts too late. A complete switch of provider requires planning, migration and testing, and that time is not available in an emergency. Sovereignty must therefore be built into the architecture, not retrofitted as an emergency measure.
05 · Cloud exit
What does a cloud exit strategy look like?
A cloud exit strategy is a documented plan for how a company moves its data and applications from one provider to another or back on premises. It is the practical expression of control over switching. According to Lünendonk, almost every second company surveyed has no such strategy, and that becomes a risk in an emergency.
Inventory data stocks (1 to 2 weeks)
Record all systems that hold production and quality data. For each system, clarify where the data is stored and who has access. Assign evidence obligations and retention periods.
Result: a complete overview of how critical each data set is for sovereignty.
Assess dependencies and jurisdiction (2 to 4 weeks)
Check the jurisdiction of each provider, not just the server location. Identify proprietary formats that make switching harder. Request data portability under the EU Data Act.
Result: a prioritized list of the systems with the highest sovereignty risk.
Define and test the way back (ongoing)
Define a documented path back on premises for critical data. Transfer evidence relevant data into an open archive format. Test the recovery path in practice at least once.
Result: reliable ability to act that also works under time pressure.
Since September 2025, the EU Data Act has given European companies a right to data portability and has required cloud providers to make switching technically possible. This reduces the risk of vendor dependency but does not replace the company’s own decision on whether and when a switch makes sense. The strategy remains the company’s responsibility.
06 · Lifecycle
How does sovereignty last across the entire data lifecycle?
Sovereignty does not end with the choice of a provider. It must remain in place across the entire data lifecycle, from capture in production through active use to long term archiving. The last phase in particular is often overlooked, even though it is the longest.
| Phase | What happens | Sovereignty question | Typical risk |
|---|---|---|---|
| 1 Capture | Process and quality data is created at machines and inspection stations. | Is the data captured in a controlled system from the start? | Isolated solutions without central control |
| 2 Use | Data flows into analysis, complaints and process improvement. | Does access remain independent of external providers? | Dependence on a proprietary analysis platform |
| 3 Archiving | Evidence must remain readable for many years. | Is the data stored in an open format under your own control? | Loss of readability after a system replacement |
For manufacturers, the archiving phase is the most critical point. A complaint or product liability case can arise many years after production. If the related process history can no longer be read because the source system was shut down and the format was proprietary, the evidence is lost. Reliable archiving does not secure the file system, but the relevant database content in a structured, application aware way.
Rule of thumb
Backup and archiving are not the same. A backup serves short term recovery. Archiving serves long term, structured retention with integrity protection. For data sovereignty over decades, archiving is what counts. More on this in the article Backup vs. Archiving.
07 · Solution
How does the CSP Manufacturing OS secure data sovereignty?
Data sovereignty is not a product feature you buy but a property of the architecture. CSP therefore relies on an architecture in which customers keep control over their own data, from capture to long term archiving with integrity protection.
The CSP Manufacturing OS captures, uses and archives quality and production data on a common basis. With CHRONOS, evidence is stored in line with OAIS in an open format, installed locally and under the sole control of the company. The data thus remains readable and protected even after legacy systems have been replaced.
Open format
Archiving with integrity protection in an open, vendor neutral format.
Over 70 % smaller
Reduction in database size by offloading inactive data.
Over 40 % savings
Lower IT operating costs through reduced system load.
Installed locally
The data never leaves the company, control over access stays in house.
Retire legacy systems
Legacy systems can be shut down without losing access to historical data as evidence.
The approach is deliberately conservative: the focus is not on the convenience of a third party platform, but on the customer’s lasting control over their own data. Vendor independence is therefore not a convenience topic but a requirement.
Check your data sovereignty before an emergency
Talk to us about your legacy systems and evidence obligations, or learn more about data archiving with CHRONOS.
FAQ
Frequently asked questions
What does data sovereignty mean for a manufacturing company?+
Data sovereignty means that a company decides at all times where its data is stored, who can access it and how long it remains available. For manufacturers, this mainly concerns quality and production data that must remain provable for many years. Sovereignty is achieved when access still works even if an external provider or a political decision would restrict it.
Why is a server location in the EU not enough for data sovereignty?+
The server location alone does not determine who controls access. What matters is which jurisdiction the provider is subject to. A US company such as Microsoft, Amazon or Google remains subject to the US CLOUD Act even with a data center in Frankfurt and can be obliged to hand over data regardless of the physical storage location. There is no EU legal act that overrides the CLOUD Act. Real data sovereignty therefore requires that the provider is subject exclusively to European law or that the data is stored on premises under the sole control of the company.
What is the difference between data sovereignty and data protection?+
Data protection governs how personal data may be processed. Data sovereignty is broader and concerns who actually controls access. A system can be GDPR compliant and still not sovereign if a third party could block access technically or legally. Sovereignty is therefore the prerequisite for enforcing data protection under pressure.
What role does the US CLOUD Act play for German manufacturers?+
The US CLOUD Act of 2018 obliges US providers to hand over data on the order of US authorities, regardless of where it is stored. For German manufacturers, this is a compliance risk as soon as quality or production data is stored with a US provider. The law does not require the affected company to be notified, so access can take place without the customer’s knowledge.
What is a cloud exit strategy and why does it matter?+
A cloud exit strategy is a documented plan for how a company moves its data and applications from one cloud provider to another or back on premises. According to the Lünendonk study “Digital Sovereignty: From Risk to Resilience” (2026), only 57 percent of the companies surveyed have an exit strategy for switching providers. Since September 2025, the EU Data Act has required cloud providers to make switching technically possible. The strategic decision, however, remains with the company.
How do manufacturers secure long term control over quality data?+
Quality and production data often has to remain provable for many years, for example because of customer requirements under IATF 16949 or for product liability cases. Under Section 13 of the German Product Liability Act, claims only expire ten years after the product was placed on the market. Control over this period comes from archiving with integrity protection in an open, vendor neutral format that remains readable after the source system is replaced and stays under the company’s control.
What happens to archived data when the source system is shut down?+
With proper archiving, the relevant business data remains fully available and searchable after the source system is shut down. This requires that not just the file system is backed up, but that the relational database content is archived in a structured, application aware way. Legacy applications can then be retired without losing access to historical production data as evidence.
Is archiving on premises still up to date, or should you move to the cloud?+
Both models have their place. What matters is not cloud versus own data center, but who retains control over access. Archiving operated locally offers maximum data sovereignty because the data never leaves the company. Anyone using the cloud should look for a provider under European law, an open data format and a documented exit strategy.