Trust · Sub-processors

Sub-processors, on the record

A sub-processor is an external service that processes data on our behalf when you use Nexa Agora. This is the complete list — who they are, what they do, where the processing happens, and what you can switch off. It is the same register our DPA points to, kept public the way the product keeps everything: dated and inspectable.

Sub-processorService / purposeProcessing regionTransfer safeguardCan a workspace disable it?
Microsoft Azure — AI model servingAI reasoning, embeddings, document OCR for your agentsSweden Central (EU Data Zone)No third-country transfer — EU-resident processingYes — workspaces can run exclusively on self-hosted/sovereign models or bring their own
Microsoft Azure — data platformPrimary database, document storage, platform infrastructureNorth Europe (Ireland)No third-country transfer — EU-resident processingNo — core platform infrastructure
Microsoft Azure — voice & image servicesSpeech-to-text, text-to-speech, image generationEast US 2 (United States)Microsoft DPA + EU SCCs; Microsoft is EU-US DPF-certifiedYes — voice and image features can be switched off (or capped to zero) per workspace
Microsoft 365 (Graph)Delivery of invitation and account emailsEuropean Union (Microsoft 365 tenant provisioned in an EU region)Microsoft DPA + EU SCCs / DPFNo — required for account lifecycle emails (content is limited to the invitation itself)
Stripe, Inc.Payment processing and subscription billing (card data is collected and held by Stripe, PCI-DSS)United StatesStripe DPA + EU SCCs; Stripe is EU-US DPF-certifiedApplies only when purchasing a paid plan; free workspaces send nothing to Stripe
GitHub, Inc.Optional read-only access to your code repositories for agentsUnited StatesGitHub DPA + EU SCCs / DPFYes — per-project opt-in; off by default
Web search providers (optional)Live web search for agentsSelf-hosted by default (EU); external providers only if enabledn/a on the default pathYes — the default search is self-hosted; external providers are opt-in

EU-resident by default

Chat reasoning, embeddings, OCR, the database and document storage all run in EU regions. The platform ships with an EU-only switch that hides and blocks any non-EU model — it never silently falls back.

The sovereign option

Workspaces can route AI entirely through self-hosted models — our sovereign pool or your own infrastructure. In that mode, no chat content reaches any model sub-processor in the table above.

What is not on this list

The vector store, PDF rendering, search, observability and the control plane are operated by NexaEthos on its own infrastructure. Self-hosted components are not third-party sub-processors, so they do not appear here.

How this register changes

New sub-processors are added to this register at least 14 days before activation, and workspace owners can object through support within that window (Art. 28(2) GDPR). A new external provider lands here in the same change that enables it — never after the fact.

Residency and transfers are also answered in plain language in the FAQ (chapter III, Security & data protection), and what this site itself collects is on the privacy page.

Last updated 20 July 2026. If this register changes, the date changes with it — and the change is announced first.