Trust Center

Data Residency

The Magif platform runs in the European Union: customer conversations, agent inference, knowledge bases, file storage, the primary database and application hosting all run on EU infrastructure.

Last updated: 4 October 2026

Whose data flows where

Two kinds of data move through the platform. Your clients' data comes first: their conversations and agent memory run and stay on infrastructure in the European Union. Your own data as a coach, knowledge bases, configuration and billing, follows the same map. Every component below is marked with whose data it handles.

End user

Your clients: the people who chat with your agent.

Coach

You, the creator: the coach who builds and operates agents.

EU data residency for AI agents

EU data residency for AI agents covers where replies are generated and where conversations, files and knowledge are stored. On Magif, agent inference runs on Scaleway Generative APIs in Paris. Conversations and memory are stored in MongoDB Atlas in Frankfurt, the knowledge-base index in Qdrant Cloud in Frankfurt, and files in AWS S3 in Paris.

Planning a coaching programme for a team? GDPR-compliant AI leadership coaching for teams in the EU

AI chat and UK data residency

AI chat on Magif is processed and stored in the EU, not the UK. Transactional email is the one UK-based component: AWS SES in London sends sign-in verification codes and account notifications under the UK adequacy decision. These emails contain no conversations, uploaded files or platform content.

Current inference architecture

Core agent inference runs on open-source models hosted on Scaleway in the European Union. The legacy LLM_ANONYMISER component is no longer part of the current architecture. See the Scaleway entry in the vendor register.

How data flows

End users and creators interact with the magif.ai application. The application routes each request to the components below, grouped by the region where processing takes place.

End users

Chat with a creator's agent

End user

Creators

Build and operate agents

Coach

magif.ai application

Routes every request to the components below

European Union

Processing and storage inside the EU

Agent inference

Scaleway Generative APIs

Paris, France

Creator assistant inference

AWS Bedrock

Paris, eu-west-3

Primary database

MongoDB Atlas, hosted on AWS

Frankfurt, Germany, AWS eu-central-1

Vector storage (RAG)

Qdrant Cloud

Frankfurt, europe-west3

Real-time messaging

Redis Cloud

Paris, eu-west-3

File storage

AWS S3

Paris, eu-west-3

Transactional email

AWS SES

London *

Product analytics

PostHog Cloud EU

Logging and monitoring

Datadog (EU site)

* Transactional email (sign-in verification codes and account notifications) is still sent through AWS SES in the London region while its migration to the EU (Paris) completes. These emails carry no customer conversations, uploaded files or platform content.

Component by component

Each platform component, with its provider, region and the data it handles. Legal entities and transfer bases live in the subprocessor register. The badges on each card show whether the component touches your clients' data, your coach data, or both.

Agent inference

European Union (Paris, France)
End userCoach

Client conversations, plus the coach knowledge passages the agent draws on.

Provider
Scaleway Generative APIs
Data
Conversation messages, agent instructions, retrieved knowledge passages

Coaching agent conversations run on open-source models hosted by Scaleway (EU), including vision, served from Scaleway Generative APIs in the European Union. Zero data retention: prompts and outputs are not retained by the provider after processing.

Creator assistant inference

European Union (Paris, eu-west-3)
Coach

Coach data only: creator assistant conversations, configuration context and media.

Provider
AWS Bedrock
Data
Creator workspace conversations, agent configuration context, media submitted for analysis

The MAX creator assistant, including its media analysis tools, runs on foundation models served through the AWS Bedrock regional endpoint in Paris (eu-west-3). Inference requests are processed inside the EU region. Zero data retention: prompts and outputs are not retained by the provider after processing.

Primary database

European Union (Frankfurt, Germany, AWS eu-central-1)
End userCoach

Client conversations, memory and accounts; coach configuration, offers and billing.

Provider
MongoDB Atlas, hosted on AWS
Data
Accounts, agent configurations, conversations, billing records, platform data

Accounts, agents, conversations and platform records are stored in a managed MongoDB Atlas cluster hosted on AWS in Frankfurt, Germany (eu-central-1). Data is encrypted in transit (TLS) and at rest, and the cluster is backed up on a managed schedule.

Vector storage (RAG)

European Union (Frankfurt, europe-west3)
Coach

Coach data only: the knowledge-base index. Client conversations are not stored here.

Provider
Qdrant Cloud
Data
Embedded knowledge-base passages uploaded by creators

Knowledge-base embeddings are stored in a Qdrant Cloud cluster in the EU. Embeddings are computed by open-source models hosted by Scaleway (EU). All vector operations are proxied through the Magif agents API; client applications never talk to the vector store directly.

Real-time messaging

European Union (Paris, eu-west-3)
End userCoach

Live chat delivery for client and creator conversations; transient only.

Provider
Redis Cloud
Data
Transient message routing data

Live chat delivery uses a Redis Cloud instance in the Paris region for message routing between application nodes.

File storage

European Union (Paris, eu-west-3)
End userCoach

Files clients share in chat; coach knowledge documents and page media.

Provider
AWS S3
Data
Uploaded documents, media files, generated images

Uploaded files and generated media are stored in AWS S3 in the Paris region (eu-west-3).

Transactional email

United Kingdom (London, eu-west-2)
End userCoach

Verification and transactional email for clients and coaches.

Provider
AWS SES
Data
Email addresses, verification codes

Sign-in verification codes and account notifications. Transactional email (sign-in verification codes and account notifications) is still sent through AWS SES in the London region while its migration to the EU (Paris) completes. These emails carry no customer conversations, uploaded files or platform content.

Product analytics

European Union
End userCoach

Usage signals for chat and dashboard surfaces; not message content.

Provider
PostHog Cloud EU
Data
Usage events, session analytics

Product analytics run on PostHog EU Cloud. Events are collected through a first-party proxy on the magif.ai domain.

Logging and monitoring

European Union
End userCoach

Technical logs and traces across the platform.

Provider
Datadog (EU site)
Data
Application logs, performance traces

Application logs, traces and monitoring use the Datadog EU site.

Legal entities, contracting details and transfer bases for each provider are in the Subprocessor Register.

Optional / auxiliary processing

Some features such as web search, image generation, payments and transactional email use additional providers. These services do not form part of the core coaching-model inference path and are invoked only when the relevant feature is used. Full vendor details are in the Subprocessor Register.

Transfer status

Where processing happens for each group of components, and the legal basis where a transfer applies.

European Union

Agent inference, Creator assistant inference, Primary database, Vector storage (RAG), Real-time messaging, File storage, Product analytics, Logging and monitoring: processing for these components takes place inside the European Union. No transfer mechanism is required.

Transactional email (sign-in verification codes and account notifications) is still sent through AWS SES in the London region while its migration to the EU (Paris) completes. These emails carry no customer conversations, uploaded files or platform content. Transfer basis until then: UK adequacy decision.

Auxiliary vendor processing is listed in the subprocessor register, with the purpose, region and transfer basis for each vendor.