Data residency: EU only and Flexible

Every workspace runs in one of two processing packages, and the package applies to every step that processes your data. Every workspace starts on EU-only processing.

EU only (default)

Everything in CORA stays in the EU. With EU-only processing, every processing step stays inside the EU or does not happen. There is never a fallback to a processor outside the EU. Your database, files, search index, and stored background work data are in the EU too.

What this means in practice:

• AI requests use approved EU routes and fail closed if that route is unavailable, rather than quietly running elsewhere.
• Background processing such as memory extraction, search indexing, document reading, and editor assistance uses EU routes.
• Public web search uses an EU-hosted search provider.
• Meetings in the browser, the chat microphone and Discord voice recordings are transcribed in the EU.
• Images are generated in the EU, with an image model that runs in Sweden.
• Advanced model choices that process outside the EU are not offered.
• Managed mailboxes and Agent email run on Mailgun's EU region.
• A feature without an approved EU route is unavailable instead of being routed outside the EU.
• How you pay is separate: a workspace on EU only or EU Strict may pay by card or by invoice. Card payments go through Stripe, which handles CORA's own billing records and never your workspace content.

Flexible processing (on request)

With Flexible processing, your stored data stays in the EU, and CORA can also use models and services that run outside the EU, through approved processors under data processing agreements and Standard Contractual Clauses. It offers the broadest choice of advanced models, and the newest image model.

CORA turns on Flexible processing when the workspace owner asks in writing. Until then, the owner cannot pick it in Settings -> Data residency.

EU Strict

EU Strict is EU-only processing locked by a contract with CORA, for company workspaces. While the lock is set:

• Nobody in the workspace can switch to Flexible processing. The setting shows as read-only with the reason.
• Both data sharing settings are off and cannot be turned on.
• No one at CORA can read the workspace's conversations.
• MCP servers of other services cannot be connected.
• CORA sends no marketing email to the workspace's members.

Contact CORA to change the contract.

Who can switch

Open Settings -> Data residency. Every member can see the active package. Only the workspace owner can change it. The owner can switch to EU only at any time, and to Flexible processing while CORA has turned it on for the workspace. Personal workspaces also start on EU-only processing; EU Strict is for company workspaces only.

Stored data does not move when you switch, because it is already in the EU.

Data residency cannot be changed by asking CORA in chat. It stays in its dedicated settings page.

Sub-processors

The providers used in each package are listed on the public sub-processor page at /subprocessors.