The awkward part of data sovereignty is that the rack has excellent geography and mediocre legal personality. A server can sit in Indre, hum away in a French building, and still be attached to a provider with legal obligations elsewhere. That is the useful lesson in La Nouvelle République’s reporting on Google’s planned data center near Châteauroux: local storage matters, but it is not a magic spell.
A French address is not the compliance test
La Nouvelle République reported that Google’s future data center is planned for Étrechet, near Châteauroux, and that project backers announced between 10,600 and 14,200 construction phase jobs over about 18 months, followed by between 1,800 and 2,600 jobs during operation. Those are large local numbers, and they help explain why the project is discussed in the language of industrial policy. At the presentation on Monday 12 October 2026, Olivier Delcourt, Google’s western Europe data center operations manager, described the French presence as “S’implanter en France est une question de souveraineté.”
That sentence is politically neat. It is not, by itself, a data protection guarantee. A buyer choosing a cloud provider should treat the data center address as one field in the diligence file, alongside the provider’s corporate control, transfer mechanisms, support model, subcontractors, and response process for lawful access requests. If your vendor deck stops at the map pin, your lawyers are not being difficult. They are reading the part after the map.
Why cloud data can still cross a border
La Nouvelle République’s 22 October 2026 report framed the issue plainly: personal information stored nearby may still move across the Atlantic when a U.S. digital company is caught between European data rules and foreign legal obligations. Lauren Bensaid, a lawyer quoted by the newspaper, put the cloud problem in one sentence: “Avec le cloud, les données peuvent circuler sans frontières.” That is the compliance mechanism hiding under the sovereignty slogan.
In practice, the question is not only where disks are located. The harder questions are who can technically access the environment, which legal entity contracts with the customer, whether data or metadata is transferred for support or operations, and what happens when another jurisdiction demands access. None of those questions is answered by saying the data center is in France. France can be the place of storage while the risk analysis still points to a multinational provider structure.
The EU-U.S. framework permits transfers, it does not erase diligence
The European Commission says personal data may flow freely from the EU to U.S. companies that participate in the EU-U.S. Data Privacy Framework. The Commission also says the U.S. national security safeguards behind that framework limit intelligence access to what is necessary and proportionate, and create a redress mechanism for Europeans. It further says those safeguards apply to all GDPR transfers to U.S. companies, regardless of the transfer mechanism used.
That is not the same as saying every U.S. linked cloud deployment is forbidden. It is also not the same as saying every French hosted deployment is sovereign in the procurement sense. The Commission’s position gives buyers a legal route for some transfers, especially where the provider participates in the framework. The practical job is to document the route, not to wave at the word France until the transfer risk goes away.
What buyers should ask before signing
Using La Nouvelle République’s reporting and the European Commission’s transfer guidance as the baseline, the procurement checklist is fairly dry, which is how compliance checklists should be. Ask whether the provider makes a specific data residency commitment for the service you are buying, not for the brand generally. Ask what exceptions apply for support, security, maintenance, backup, telemetry, and subcontractors. Then ask which transfer mechanism covers any movement to a U.S. company, including whether the relevant entity participates in the EU-U.S. Data Privacy Framework.
The contract should also say how the provider handles legally compelled access requests, what notice it gives where permitted, and what audit evidence the customer receives. Those clauses do not make foreign law disappear. They give the customer a record of who may access the data, under what process, and with what safeguards. That record is what a regulator, board, or public sector buyer will ask for when the sovereignty brochure has been recycled.
The next useful disclosure for projects like Étrechet is not another speech about sovereignty. It is a plain account of the provider entity, the transfer path, the access controls, and the contractual promises attached to the service. Builders and buyers in Europe should assume that data localization is a starting condition, not the finish line. The rack may be French. The legal exposure may still need a passport check.