> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Data residency

> Document regional data-handling requirements and the evidence needed before relying on a residency commitment.

Data residency concerns where data is stored and processed. Review it for each category your workflow uses, including uploaded documents, conversations, recordings, credentials, analysis, and operational logs.

<Warning>
  Threetone does not currently expose a verified workspace region-selection or data-migration workflow. A country, language, or time-zone setting does not enforce where data is stored or processed. Do not treat those values as a residency commitment.
</Warning>

## Prepare a residency assessment

Work with the person responsible for your organization's data requirements and the owners of connected systems.

| Requirement | Information to record |
| - | - |
| Storage | Permitted regions for primary data, replicas, backups, and exports |
| Processing | Where model, speech, document, and tool operations may run |
| Access | Who may access the data and from which locations |
| Transfer | Which connected services receive each data category |
| Lifecycle | Retention, deletion, and any migration requirements |

<Steps>
  <Step title="Map the workflow" id="residency-map-workflow">
    List the [assets](/overview/administration/assets) and external integrations involved. Include data copied into your own application, logs, and review exports.
  </Step>

  <Step title="Request specific confirmation" id="residency-confirmation">
    Use the [Help Center](https://help.threetone.in/en) to confirm supported arrangements for the intended deployment. Ask for the scope of any commitment rather than inferring it from a provider name or endpoint hostname.
  </Step>

  <Step title="Record unresolved requirements" id="residency-unresolved">
    Keep unsupported regions, transfers, and migration needs visible before using affected data. Review [privacy settings](/agents-platform/monitor/privacy/overview) separately; saved preferences do not prove enforcement.
  </Step>
</Steps>

<AccordionGroup>
  <Accordion title="Does changing my time zone move workspace data?" id="residency-faq-timezone">No. Time-zone preferences control temporal context or presentation, not deployment location.</Accordion>
  <Accordion title="Can I migrate an existing workspace to another region?" id="residency-faq-migration">No verified self-service region migration is available. Confirm an explicitly supported process before planning a move.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.