Sovereignty
GDPR voicebot: your data stays in France
Data residency, no transfer, zero sub-processor to document. With Natalia in disconnected mode, your customers' data never leaves your network.
Data residency: beyond documentary compliance
The GDPR compliance of a voicebot is demonstrated on documents, while data residency depends on the architecture. It is that architecture that makes compliance genuinely verifiable.
Data residency answers a simple question: where is your customers' data physically located, and who can access it? A cloud voicebot spreads that data across the vendor's infrastructure and its sub-processors. An on-premise voicebot keeps it with you.
This page treats data residency as a positioning choice. The associated contractual framework, DPA and deployment modes, is detailed separately on the on-premise GDPR framework page.
No data leaves your network
This is the heart of the positioning. In disconnected mode, the appliance has no exit channel.
Your customers' data, numbers, timestamps, call metadata, is processed locally and stored locally. No copy is sent to an external service, because no outbound connection is opened.
This property is verifiable at the network level: there is no flow to inspect, because there is no outbound flow. Data residency becomes an observable fact at the network level.
Encrypted local storage
Data stays on the appliance, encrypted at rest.
Pseudonymization by default
Numbers are masked by default, revealed only to an authorized, audited role.
No outbound network
In disconnected mode, no exfiltration channel is possible.
Zero article 28 sub-processor in disconnected mode
Without a data transfer, there is no controller/processor relationship to document within the meaning of article 28 of the GDPR.
A cloud voicebot almost always involves a chain of sub-processors: host, processing engine, ancillary services. Each must be covered by a DPA and listed in your record of processing activities.
In disconnected mode, that chain disappears. You remain the sole data controller. There is no sub-processor to audit, no article 28 DPA to negotiate, which shortens procurement cycles overseen by a CISO or a DPO.
Concrete effect
Fewer sub-processors to cover means fewer documents to produce, to sign and to keep up to date in your record of processing.
What it changes for your DPO
Disconnected mode simplifies the impact assessment and the record, because it removes actors from the equation.
Lighter record
No external sub-processor to reference in disconnected mode.
Controlled access
Internal roles, immutable exportable audit log.
Article 17 erasure
Selective erasure per employee extension, audited and certified.
The contractual framework that formalizes these guarantees, mode by mode, is described on the dedicated on-premise GDPR framework page.
Frequently asked questions
Can a voicebot be GDPR-compliant without sending data outside?
Where does the customer data processed by Natalia reside?
What is the difference between this page and the on-premise GDPR framework?
Keep your customers' data on your network
On-premise demo on your own environment. We check the absence of outbound flow together.
Request a demo