Sovereign AI: what it actually means for a smaller company

“Sovereign”: four questions, not one

The word covers four requirements that are routinely conflated.

Location. Where is the data stored and processed? A geographic answer, verifiable, the easiest to obtain — and the least decisive on its own.

Law. Which jurisdiction does the provider answer to? A matter of head office and shareholding, not of data centre. A server in Frankfurt run by the subsidiary of an American group still sits within the reach of US law.

The model. Are you using a service whose versions and timetable you do not know, or a model you hold a copy of and update when you choose?

The exit. How long would it take to retrieve your data and your configurations, and start again elsewhere?

Ask the four separately. A supplier who answers “yes, we are sovereign” has answered none of them.

Is hosting in Europe enough?

No, not on its own. The US CLOUD Act, passed in 2018, allows American authorities to require a provider subject to their jurisdiction to hand over data it holds or controls — regardless of the country where it is stored.

Two qualifications, because the subject is often caricatured. It takes a US legal process, in a criminal investigation: this is not self-service access. And the provider can try to have the demand set aside — but that route is narrow: it assumes an agreement between the United States and the country whose law would be broken, and the EU has signed none.

As early as 2019, the European Data Protection Board and the European Data Protection Supervisor flagged the sticking point: such an order can place the provider in conflict with the GDPR.

The risk is real, but targeted. Weigh it against what your data contains, not as a matter of principle.

Can we still use an American service?

Yes, as things stand. The EU-US Data Privacy Framework adequacy decision, adopted on 10 July 2023, has not been annulled. It permits personal data to be transferred to an American company listed as certified under the framework. Failing that, the usual safeguards apply: standard contractual clauses and a transfer assessment.

The framework is contested. The EU General Court dismissed a first challenge on 3 September 2025; an appeal is pending before the Court of Justice. And on 31 July 2026, the European Data Protection Board asked the Commission to assess the consequences of a US Supreme Court ruling of 29 June 2026 for the independence of the authority tasked with enforcing those commitments.

The practical conclusion: it is lawful today. Build nothing that would become unmanageable if that changed.

SecNumCloud: does it concern us?

Probably not, and that is fine.

SecNumCloud is a qualification awarded by France’s ANSSI, the national cybersecurity agency. It attests to a high level of security and, above all, to sought-after protection against extraterritorial laws: head office in the Union, non-European shareholders in the minority, and data, administration and technical logs located in the Union.

It is voluntary. No general rule imposes it on a smaller company. It bites in practice through certain public contracts, certain sectors, or a client who writes it into your agreement.

Its real cost is not its price: it is the catalogue. The qualified offering is narrower, and managed AI services are fewer there than elsewhere.

The sensible reflex: check whether your sector or one of your clients requires it. If not, do not impose it on yourself as a precaution.

Open models or an online service?

An “open” model — one whose parameters are published and downloadable — settles one question: you can run it on infrastructure you choose. Run it on your own, and your documents and your questions never leave.

It settles nothing else. You need suitable hardware, someone to look after it, monitoring, updates. Open means neither free nor simple.

An online service offers the reverse: nothing to run, access to the most advanced models, usage-based billing — and data passing through a third party whose versions and timetable you do not control.

The middle route often fits: an open model, hosted by a European provider, operated on your behalf. You keep control of the applicable law without taking on the operations.

Could you actually change provider?

This is the most useful question, and the least often asked.

The EU Data Act, applicable since 12 September 2025, governs switching cloud provider: a notice period capped at two months, then a transition of no more than thirty days — extendable once at your request, and longer where the provider shows the deadline is technically unfeasible. Switching charges disappear on 12 January 2027; standard service fees and early-termination penalties remain payable.

The law opens the door. It does not make your system portable. What holds you back is your integrations, your indexes, your instructions tuned for one particular model, and your teams’ habits.

Two cheap reflexes at the outset: keep a usable copy of your data and your configurations, and avoid a proprietary feature where a standard equivalent exists.

Test the exit once. A reversibility never attempted does not exist.

When sovereignty is not the right fight

Often, honestly.

Internal meeting notes, a draft sales email, rewording a piece of text: the debate has no place. Use the simplest tool, with clear rules about what does not go into it.

It becomes the right fight as soon as one of three situations is yours. Your data falls under its own regime — health, a regulated sector, sensitive public contracts. You have given clients confidentiality undertakings that bind you, whatever your supplier says. Or the leak of a body of documents would cost you a real advantage: methods, pricing, contracts.

The test fits in one sentence. Look at what goes into the tool, not at the tool. The same service can be acceptable for your training material and out of the question for your client files.