MitDesk docs
Governing it

Sovereign routing

6 min read Odoo 20.0

Sovereign routing decides where the data of a chat turn may be processed. It looks at two things: what kind of data the turn carries, and where the AI model runs.

Who this is for: administrators and security owners who control where data may go.

You need: Edition: Business. It needs the module minddesk_sovereign, which also needs minddesk_workforce. See Editions. The hosting class of a model or endpoint (on-premises, EU cloud, non-EU cloud) is part of Basic.

Data classes: Financial, HR / employee, Internal, Personal data and Public, and where each may go

Where a model runs: the hosting class

Every AI model and endpoint has a hosting class. You see it as Where it sends data (on the endpoint) and as the provider class (on the model).

The AI Models list with the provider class of each model

You choose which provider or address a model uses. You cannot choose its class. MitDesk works it out:

  • Ollama always counts as On-premises. Point it only at a machine you control.
  • Anthropic, OpenAI and Gemini count as Non-EU cloud.
  • Mistral counts as EU cloud.
  • A named endpoint or the OpenAI-compatible provider is judged by its address:
    • A loopback address, a private address, localhost, or a name ending in .local, .internal, .lan, .localdomain or .home.arpa is On-premises.
    • A short list of EU hosts, built into MitDesk, is EU cloud.
    • Everything else, and anything MitDesk cannot read, is Non-EU cloud.

MitDesk reads the address as text. It does not look it up in DNS. New EU hosts are added in a MitDesk release, not in a setting.

MitDesk works out the class again at every check. It does not trust the stored value. A changed record cannot make a cloud provider look local.

Data classes

A data class says what kind of data it is and how far it may travel. Open Governance ▸ Sovereign ▸ Data Classes.

MitDesk ships five classes:

Class Starting setting
Public May go to any provider.
Internal Local or EU-hosted cloud.
Personal data Local or EU-hosted cloud.
Financial Stays on-premises.
HR / employee Stays on-premises.

This is a starting point. Review it. An upgrade never resets a change you made.

For each class you set Where it may go:

  • Stays on-premises,
  • Local or EU-hosted cloud,
  • Any provider, including non-EU.

The switch A dated exception may go further says whether a routing allowance can take the class past this limit. If it is off, the limit is a hard boundary.

The shipped classes are for the whole database. You can add your own classes for one company, for example "Patient records".

For your own class:

  • You must choose at least one Allowed agent. Other agents may not process this data.
  • If the class may reach a cloud provider, you must confirm the cloud warning and write down the decision.

Classified data: which Odoo model carries which data class

How a turn gets a class

A turn gets its data classes in two ways.

  1. Classified data. An administrator says that a model, or one field of it, carries a class. On a data class, use the Classified button, or the tab Classified data. For example, Journal Entry is Financial and Contact is Personal data. If you leave the field empty, the line covers the whole model.
  2. Detection. MitDesk also scans the content for IBANs, BICs, email addresses, phone numbers, tax IDs, addresses and labelled names. Wide patterns, such as names and addresses, count only when a field label gives them meaning.

The models that attachments were read from count too. A pinned record is not a way around the rule.

In the settings, Unclassified data can name a default class. Without it, only the models you classified are restricted.

What happens to a sensitive turn

When a turn carries classified data, MitDesk chooses the model before anything leaves.

  1. If the model you asked for is local or EU-hosted and routing allows it, MitDesk keeps it.
  2. Otherwise MitDesk looks for another local or EU-hosted model, local first. It skips models that Sovereign Mode excludes, that cannot do a web search the turn needs, that are not set up, or that routing refuses. A switch is written to the audit log.
  3. Otherwise MitDesk looks for a routing allowance that covers every class in the turn.
  4. Otherwise it stops. Nothing is sent.

When it stops, the message names the kinds of data it found (for example "an IBAN"), never the values. It names the model you asked for and where it runs. It lists up to five local or EU models and why each was not used. An administrator is told how to fix it. Other users are told whom to ask.

A refused turn writes an audit row on its own, so the attempt stays in the record. The row holds a marker, not the content.

Fail closed

A class with no routing decision may not leave. An unknown hosting class counts as non-EU. If a caller names a different class than the model really has, MitDesk uses the real one and logs the mismatch.

Routing allowances

An allowance is a narrow exception with an end date. Open Governance ▸ Sovereign ▸ Routing Allowances.

Routing allowances: company, data class, scope, provider, model, expiry and days left

An allowance:

  • names one data class,
  • covers One model or All models from one provider,
  • needs a written Reason (the business and legal justification),
  • records who approved it and when,
  • exists only once for each class and target.

Also accept non-EU hosting is the informed risk acceptance. It needs an expiry date. MitDesk does not accept one without it. An expired allowance never allows anything. MitDesk creates an Odoo activity for the approver before it ends. The default notice is 7 days. The system parameter minddesk.routing_allowance_warning_days changes it.

An allowance only lifts a block. It does not redirect traffic. A local or EU model still wins when one is available. It does not turn off masking.

Sovereign Mode and masking

Sovereign Mode is one switch in the MitDesk settings (block Sovereign Mode). It limits every AI turn to local models. If you turn on Also allow EU-hosted cloud, EU models are allowed too. The switch works for chat, agents, automations, digital employees on a schedule, server actions and external AI tools. Check configuration lists the active models that the current mode would refuse. It does not call any provider.

Sovereign Mode limits AI turns only. Knowledge-search embeddings, outbound MCP tools and webhooks send data on their own. The data classes and the cloud deny list reach them, but the switch does not. Keep the embedding model local and classify the models those tools read. See Knowledge and sources.

Before a turn goes to a non-local model, MitDesk replaces structured personal and financial values with placeholders. In chat, the answer is shown with the real values restored. The setting for each of Personal data to cloud and Financial data to cloud is:

  • Mask before cloud egress (the default),
  • Block cloud egress,
  • Allow raw values to EU cloud. This is an explicit decision, and MitDesk only honors it for an EU-hosted provider.

Files and images are not masked.

After an answer, the chat shows the hosting of the last request, for example Local — nothing left your server or Non-EU cloud — data left your server, with the region.

An on-premises analyst explains which data classes may leave the EU

If it does not work

If a request is refused by Sovereign Mode, see "A sovereign refusal" in Troubleshooting.