Sovereignty

Sovereign voice AI, hosted in France

Sovereignty is first an architecture question. With Natalia, your call data stays on your network, in France, outside the reach of non-EU extraterritorial laws.

Sovereignty plays out in architecture

A tricolour badge on a product page says nothing about where your data flows. The real question is structural: do your conversations and call metadata leave your network? With Natalia's disconnected on-premise edition, the answer is no.

It comes down to a structural fact: data that never leaves your infrastructure escapes transfers, sub-processors and third-party jurisdictions. Hosting in France comes next, as a complementary guarantee.

This page gathers Natalia's sovereignty positioning: where your data is hosted, how it stays in France, and why a sovereign alternative to a callbot subject to non-EU laws is justified by architecture above all.

What makes the architecture sovereign

Four structural properties, verifiable at the network level.

No outbound network

In disconnected mode, the appliance opens no connection to the outside. Your call data cannot be exfiltrated, because there is no path to do so.

Zero article 28 sub-processor

No transfer means no controller/processor relationship to document. You remain the sole data controller within the meaning of the GDPR.

Hosted in France

Processing stays on your own infrastructure, in your datacenter, on French soil. You keep physical and legal control end to end.

Outside extraterritorial laws

Data that does not leave your network falls outside the scope of non-EU disclosure laws. This protection comes from the system's design.

Three angles on sovereignty

Each page answers a precise question CIOs and CISOs ask.

Hosting

Hosted in France

Where your data is hosted and why the on-premise architecture keeps everything on your network.

Learn More Data residency

Customer data in France

Data residency, no data leaving your network, zero article 28 sub-processor.

Learn More Positioning

Alternative to a US callbot

The architecture argument against extraterritorial laws such as the CLOUD Act and FISA.

Learn More

Go further

The product that implements this sovereignty, and its legal framework.

Discover the On-Premise edition

The VM appliance you deploy in your datacenter, with its three contractual modes.

On-premise GDPR framework

The contractual framework and the DPA associated with each deployment mode.

Frequently asked questions

What is a sovereign voice AI?
A sovereign voice AI processes calls and their metadata without relying on a third-party cloud or on infrastructure subject to extraterritorial laws. With Natalia's disconnected on-premise edition, processing stays on your own infrastructure, in France, under your sole control.

Is sovereignty simply hosting in France?
No. Hosting in France is a useful but secondary guarantee. The decisive structural fact is that in disconnected mode no data leaves your network: there is then no transfer, no sub-processor, and no third-party jurisdiction to consider.

How does architecture protect better than a contractual commitment?
A contractual commitment can be overridden by a foreign disclosure law. Data that never leaves your infrastructure has no path to be transferred. Architecture makes the guarantee verifiable rather than declarative.

Does Natalia also offer a connected mode?
Yes. Three contractual modes exist, from strict disconnected to connected. Maximum sovereignty matches the strict mode, with no outbound network and no DPA to negotiate. The other modes add features at the cost of a proportionate network surface.

Assess the sovereignty of your telephony

On-premise demo on your own environment. We start from your network architecture and your real constraints.

Request a demo