Data residency

Data residency: choose where your organization’s data is stored.

Crewdle runs a complete stack in Canada, the United States and Europe. Your organization is served by one of them, and it stays there.

Start free Ask about your region

Updated October 2026

Crewdle is built to help organizations with data-residency requirements. This page says where your data is stored, what is global, and what other companies process, including AI providers. It does not promise legal compliance, and it does not hide the parts that sit outside your region.

Three regions, each a full stack

  • Canada

    Montréal

    Default

    The default region. Your database, files and back-end services run in Montréal, and so do your agents, AI gateway and knowledge search.

    Who hosts what

    • Database, files and back-end services: Montréal
    • Agents, AI gateway and knowledge search: Montréal

  • United States

    Virginia

    Your database runs in the United States, across several data centres. Your files, back-end services, agents, AI gateway and knowledge search run in Northern Virginia.

    Who hosts what

    • Database: United States, several data centres
    • Files and back-end services: Northern Virginia
    • Agents, AI gateway and knowledge search: Northern Virginia

  • European Union

    Frankfurt

    Your database, files and back-end services run in Frankfurt, and so do your agents, AI gateway and knowledge search.

    Who hosts what

    • Database, files and back-end services: Frankfurt
    • Agents, AI gateway and knowledge search: Frankfurt

Each region is a full Crewdle stack, not a copy: the same code, with its own database, file storage, back-end services, agent runtime and AI gateway. One organization is served by one region only.

How data residency works at Crewdle

  1. You choose the region

    You pick the region when your organization is created. Canada is the default.

  2. The region is permanent

    It cannot be changed later, so your data never moves quietly. To use another region, create a separate organization there.

  3. A full stack, not a copy

    Every region has its own database, files, back-end, agent runtime and AI gateway.

  4. Isolated by design

    Each organization is separated in data and access. Every agent runs in its own container and encrypted workspace.

  5. Plain disclosure

    We say what is stored in your region, what is global, and what other companies process.

What stays in your region, what is global, and what others process

Choosing a region decides where your data is stored. It does not decide where an AI model runs. Here is the full picture.

What stays in your region, what is global, and what others process
Category Where What it includes
Stored in your region Your region (Canada, United States or Europe)
  • Conversations and messages
  • Agents and their memory
  • Agent workspaces and files
  • Tasks
  • Uploads and deliverables
  • Knowledge bases: documents, vectors, and embeddings computed in your region
  • Usage and credit records
  • Organization settings and roles
Global Canada, for every organization
  • Sign-in identity and user profile: name, email, preferences
  • One directory entry per organization: its name and region, used to route requests
Processed by AI providers The provider’s own infrastructure, mostly in the United States
  • The prompt, context and files sent to the model, for the time of the answer
  • Claude (Anthropic), GPT (OpenAI) and Gemini (Google), through their business APIs
  • Other models, through OpenRouter
  • Media, through ElevenLabs and Runway
Processed by platform services Mostly in the United States
  • Billing details and payments: Stripe
  • Email you send or receive through Crewdle: Twilio SendGrid
  • Pseudonymous product analytics: Google Analytics, with no email or names
  • Web search and browsing for agents: Perplexity, Brave and Browserbase (United States)
Tools you connect Wherever that service keeps your account
  • What your agents read or write in your own accounts: email, calendar, CRM and more

The current sub-processor list and our data processing terms are available on request. Contact us to get them.

AI processing cannot stay entirely in your region today. Every region calls the providers’ global endpoints.

Follow one request: where your data goes

  1. Step 1: You ask

    You message your agent in the Crewdle app. The message is saved in your region.

  2. Step 2: The agent works

    Your agent wakes up in its own container, with its memory and files on an encrypted volume. All of this is in your region.

  3. Step 3: It calls a model

    The AI gateway checks budgets and permissions, then sends the needed context to the model provider, mostly in the United States. The agent never holds a provider key, and nothing is sent in the background or in bulk.

  4. Step 4: It uses your tools

    With your connection, and your approval for sensitive actions, it reads or acts in your accounts. That happens wherever the connected service keeps your account.

  5. Step 5: You get the result

    Replies, files and usage records are saved back in your region.

Security and control

Your region is one layer. These controls apply in every region.

  • Encrypted in transit and at rest

    TLS protects data in transit everywhere. At rest, the database and file storage are encrypted, agent volumes are encrypted, and knowledge indexes sit under a dedicated key in each region.

  • Organizations are isolated

    Organizations are separated by access rules on every record. Each agent runs in its own container with its own private workspace.

  • Approvals before sensitive actions

    Agents ask before sensitive actions: publishing, changing memory or skills, and spending beyond budget. Approval cards appear in your conversation.

  • Central sign-in, roles and permissions

    Central single sign-on across the suite, roles and permissions per organization, and sign-out everywhere in one click.

  • Spending caps and cost records

    Spending caps per agent and per organization, with the full cost of each request recorded in your region.

  • Lean logs

    Server logs keep metadata only. Prompts, replies, transcripts and email bodies are not written to them.

Data residency FAQ

Can we change our region later?

No. The region is fixed when the organization is created, so its data does not move. To use another region, create a separate organization there.

Is my data used to train AI models?

No. Your conversations, documents and content are never used to train AI models, ours or anyone else’s. We use the providers’ business APIs, whose terms exclude training on API data by default.

Can AI processing stay in my region?

Not today: model providers run their own infrastructure, mostly in the United States, and every region calls their global endpoints. Storage, agents, the AI gateway and knowledge search do stay in your region.

Where is my existing data?

Every organization created before October 2026 was moved to Canada in October 2026.

Can I get the sub-processor list and data processing terms?

Yes. Contact us and we will share the current list and our data processing terms.

Does this make us compliant with privacy laws?

The regions are built to help organizations with data-residency requirements, but this page makes no promise of legal compliance. What you must do depends on your situation and on the law that applies to you, so ask your legal adviser.

What if nothing may leave my computer?

In the desktop app, a chat or a hired agent pinned to a local model runs on your own computer, and nothing you send to it leaves your machine.

Questions about where your data lives?

Write to us and a person will answer. Or start free and choose your region when you create your organization.

Contact us Start free
Crewdle Crewdle AI