Modum by Nomadengenuity

EUROPEAN DIGITAL SOVEREIGNTY

Safeguarding business knowledge in Europe.

Give agents enough context to do their job while keeping control over your documents, your operating methods and where they can go.

Explore the proposed controls

Why this matters now

52.7%

of EU enterprises in scope used paid cloud services in 2025. Eurostat

20.0%

of EU enterprises with at least 10 employees used AI in 2025, up from 13.5% in 2024. Eurostat

European policy

The Commission's Data Union Strategy connects trusted data flows with competitiveness, security and AI. Its sovereignty consultation examines how to protect sensitive EU data. European Commission

The agent changes the data flow

A supplier invoice may be stored in Europe while its contents travel elsewhere through a prompt, a generated excerpt, an embedding service or a log. For an SME, sovereignty means knowing where each copy is processed, who can access it and what can leave the approved environment. Internal procedures and commercial terms also deserve protection when they contain no personal data.

Modum brings the operating model, approved policies and source evidence into one governed business memory. If an agent asks whether it can draft a supplier invoice, the intended response is the applicable rule and authorized receipt status. The ERP still validates the transaction, and the original document remains in the approved environment.

PLANNED MVP CONTROLS

From residency to verifiable control

EU processing boundary

Keep source copies, the vector index and backups on approved EU infrastructure. Confirm where extraction, embeddings and logs are processed before enabling each provider.

Policy at the point of access

Use scoped, revocable credentials and check company, source permissions and destination at each request. Deny a request when a required permission or approved destination is missing.

Encryption and private tunnels

Use encrypted transport, encryption at rest and managed keys. Private tunnels can connect supported sources to the approved environment. Destination policy still governs what can leave through those connections.

Interoperability and audit

Expose the same controls through MCP and API. Record who requested context, the policy version used and the outcome, with minimal sensitive content in the logs.

What a pilot should demonstrate

  • Map the locations of source copies, derived indexes, backups, model endpoints and logs.
  • Run the same request with an approved identity and a restricted identity. Confirm the latter receives zero excerpts or document metadata.
  • Remove a source permission or revoke a token, then repeat the request and verify the denial.
  • Attempt a request to a destination outside the configured boundary and verify the block and audit event.

These are planned acceptance tests. The public demo illustrates the flow using sample data.

How GDPR applies

EU hosting supports residency. GDPR obligations also depend on the processing activity and who can access personal data. If personal data or excerpts are transferred outside the EEA, Chapter V applies. The EDPS supervises EU institutions and bodies. It provides institutional context for the EU data protection framework.

GDPR on EUR-Lex · Role of the EDPS