Data Zones

Traceable data zones per model.

A preferred model zone is selected per chat. The available region, retention, and transfer basis depend on the provider, model, and account configuration.

Data zone: Deutschland

German data zone.

Persistent Vantero data is stored in Germany; selected models process requests in the German data zone. Provider terms on retention and transfers must be reviewed before each approval.

Server locations: Germany; specific region identified per model

German data centres
Review provider terms before approval
Approval per model and account
Managed web search only after separate approval

6 available text models

Mistral AI LogoMistral Small 24B
OpenAI LogoGPT-OSS 120B
Alibaba Qwen LogoQwen3 VL 235B
Meta Platforms LogoCodeLlama 13B
Meta Platforms LogoLlama 3.3 70B
Meta Platforms LogoLlama 3.1 405B

1 available image model

Black Forest Labs FLUX LogoFLUX.1 Schnell

Data zone: Global

Mistral models via a global endpoint.

Mistral models currently use a global provider endpoint. A fixed inference region, training exclusion, or zero data retention is stated only when supported by account-specific evidence.

Provider endpoint: Global, no fixed inference region promised

Global provider infrastructure
Review account and provider terms
Native web search included

5 available text models

Mistral AI LogoMistral Small
Mistral AI LogoMistral Medium 3
Mistral AI LogoMistral Large
Mistral AI LogoCodestral
Mistral AI LogoDevstral

Data zone: Europa

Frontier models in European data zones.

Frontier and specialist models may be provided through provider-designated European cloud regions. The actual region, availability and transfer basis must be reviewed per model and account.

Server locations: EU region identified per model

Provider-designated EU regions
Review region and provider terms
Web access included

21 available text models

OpenAI LogoGPT-5.4
OpenAI LogoChatGPT-5
OpenAI LogoChatGPT-5 Mini
OpenAI LogoChatGPT-4.1
OpenAI LogoChatGPT-5 Nano
Google Gemini LogoGemini 2.5 Pro
Google Gemini LogoGemini 2.5 Flash
Google Gemini LogoGemini 2.5 Flash-Lite
Anthropic Claude LogoClaude Opus 4.6
Anthropic Claude LogoClaude Sonnet 4.6
Anthropic Claude LogoClaude Haiku 4.5
Amazon Nova LogoNova Pro
Amazon Nova LogoNova 2 Lite
Amazon Nova LogoNova Lite
Amazon Nova LogoNova Micro
DeepSeek LogoDeepSeek V3.2
MiniMaxMiniMax M2.5
Alibaba Qwen LogoQwen3 Coder 480B
Alibaba Qwen LogoQwen3 VL 235B
Alibaba Qwen LogoQwen3 Next 80B
Moonshot Kimi LogoKimi K2.5

7 available image models

Black Forest Labs FLUX LogoFLUX.2 Pro
Google Gemini LogoImagen 3 Fast
Google Gemini LogoImagen 3
Google Gemini LogoImagen 4 Fast
Google Gemini LogoImagen 4
Google Gemini LogoImagen 4 Ultra
Amazon Nova LogoNova Canvas

Data zone: USA

US cloud with transfer controls.

Perplexity models provide real-time web access on US infrastructure. The transfer basis, provider terms and required safeguards must be reviewed before use.

Server location: USA

US infrastructure (Perplexity)
SCC/TIA review
Real-time web search
Deep Research

4 available text models

Perplexity AI LogoSonar
Perplexity AI LogoSonar Reasoning Pro
Perplexity AI LogoSonar Deep Research
Perplexity AI LogoSonar Pro

1 available image model

OpenAI LogoGPT Image 2
Background

Data residency is only one review factor.

The provider, technical endpoint, access controls, retention and legal basis for possible transfers must be assessed alongside the storage location.

CLOUD Act

Where processing has a third-country connection, possible government access, the transfer basis and supplementary safeguards must be assessed.

Keep transfer mechanisms current

Adequacy decisions, Standard Contractual Clauses and transfer assessments must match the specific provider and current legal position.

Check the DPA for each plan

Where a service processes personal data on a controller's behalf, Art. 28 GDPR requires a binding DPA. Whether a consumer plan is suitable depends on its contractual and privacy terms.

Check training controls

Training and feedback use varies by provider, product, plan and account configuration and must be documented before approval.

Assess DPIA risk

A DPIA is required under Art. 35 GDPR where the specific processing is likely to result in a high risk; the use of AI alone does not trigger it in every case.

Classify AI Act duties

Information, literacy, labelling and potential high-risk duties must be assessed for the specific feature and intended use.

Compliance

Documents and review paths for data protection.

The DPA and TOMs are available. Provider information and customer-specific reviews and approvals must be kept current for the intended use.

DPA available

Electronically incorporable data processing agreement with a transparent sub-processor list.

TOMs documented

Technical and organisational measures according to Art. 32 GDPR available for review.

Review training and retention

Vantero uses inputs for response generation and not to train its own models. Third-party terms must be reviewed per model and account before approval.

Storage and processing context

Persistent platform data in Frankfurt; request processing follows the identified model and feature context.

Checklist for the data protection officer

Incorporate the DPA for the intended use
Review TOMs under Art. 32 GDPR
Compare storage and processing locations
Review provider terms for training and retention
Review sub-processors and transfers

Frequently asked questions about data zones

Can different data zones be used within the same team?+
Yes. Each chat can have its own data zone. Within a team workspace, different members can use different zones.
What happens to data when the zone is changed?+
Persistent chat and document data remains in Frankfurt. Content required for a request is processed according to the selected model, tool or integration and its identified processing context.
How is managed web search approved for data protection?+
Managed Linkup web search is enabled only after the DPA and applicable retention terms have been documented and internally approved. Relevant search queries and explicitly requested URLs may be sent to the provider.
How does data sovereignty differ from data residency?+
Data residency describes the technical storage or processing location. A broader risk review also considers provider structure, access rights, sub-processors, retention and potential third-country transfers.
Where is user data stored?+
Persistent account, chat, document, workspace and assistant data is stored on self-operated systems within IONOS Cloud infrastructure in Frankfurt. Request content may be sent to the identified processing context depending on the model, tool or integration.

Ready for traceable AI use?

Set up Early Alpha access after approval; available features depend on the applicable test configuration.