Data residency - Threetone Documentation

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.

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.

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

Map the workflow

List the assets and external integrations involved. Include data copied into your own application, logs, and review exports.

Request specific confirmation

Use the Help Center 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.

Record unresolved requirements

Keep unsupported regions, transfers, and migration needs visible before using affected data. Review privacy settings separately; saved preferences do not prove enforcement.

Does changing my time zone move workspace data?

No. Time-zone preferences control temporal context or presentation, not deployment location.

Can I migrate an existing workspace to another region?

No verified self-service region migration is available. Confirm an explicitly supported process before planning a move.

​Prepare a residency assessment

Prepare a residency assessment