# Where your workspace runs

The one region hosted workspaces run in today, which services may process data elsewhere, and how to take your data out.

Source: https://tokentriage.com/docs/build/data-residency

---
import NextSteps from '../../../components/NextSteps.astro';

{/* Sources for every statement below, so a later editor can check rather than guess:

    the region, and that no other region accepts new workspaces: design D5 in
      docs/consolidated-launch/account-model-design/design.md, and the read-only
      placement review recorded under FMT-012 in
      docs/consolidated-launch/foundation-manual-testing/feedback.md;
    the create form's placement sentence: ui/src/features/account/workspaces/Workspaces.tsx,
      which links here;
    export at every lifecycle state, and that deletion takes a request and a confirmation
      (see the export-and-delete page for when it can still be cancelled):
      ui/src/features/account/index/AccountIndex.tsx and docs/build/export-and-delete.mdx;
    the account-services vendors and their locations: src/data/subprocessors.ts.

    Do not add a second region, a date for one, or a certification here until the
    owner has confirmed it (owner action OWN-AM-002). */}

When you create a workspace, the form tells you where it will run:

> This workspace runs in US West (Oregon). Provider processing and account services may use
> other locations.

This page explains both halves of that sentence, and what you can do with your data wherever
it sits.

## One region today: US West (Oregon)

Hosted workspaces run in US West (Oregon), the Amazon Web Services region `us-west-2`. The
service that receives your applications' requests and answers for your workspace runs there.

Other regions aren't offered today. That's why the create form states a location instead of
asking you to pick one. A choice would list regions the service turns down.

A workspace's region is set when the workspace is created, and it stays fixed for the life of
that workspace. You can't move an existing workspace to another region in place.

If your obligations require a workspace to run outside the United States, the hosted service
doesn't offer that today.

## What may be processed somewhere else

Two kinds of processing aren't tied to your workspace's region.

| What | Where it happens |
|---|---|
| Model provider processing | When a request goes to a model provider, that provider processes it wherever it processes requests, under its own terms. Your workspace's region doesn't change where the provider works. |
| Account services | Sign-in, billing records and email may use other locations. The [subprocessors list](/subprocessors) names each company involved, what it handles and where. |

So "runs in US West (Oregon)" describes your workspace. It doesn't describe every system a
request or an account record passes through.

## Taking your data out, and deleting it

You can export your data at any time, including while an account is suspended for non-payment
and after you've asked for a workspace to be deleted.

Deleting a workspace takes a request and a confirmation. [Export your data and delete a
workspace](/docs/build/export-and-delete) covers what a bundle holds, how to check it, when a
deletion can still be cancelled, and what a deletion removes and keeps.

<NextSteps items={[
  { title: 'Export your data and delete a workspace', href: '/docs/build/export-and-delete', description: 'Request a bundle, check its digests, and read what a deletion purged and kept.' },
  { title: 'Who can do what in your company', href: '/docs/build/organizations-and-access', description: 'How organizations, workspaces and teams differ, and what each role can do.' },
  { title: 'Add a saved provider connection', href: '/docs/build/provider-connections', description: 'Connect the model provider your requests go to.' },
]} />