Guide
Data residency
Where Logthread keeps your data, which regions exist today and how a workspace's region is chosen.
Regions today#
Logthread runs in one region: Asia Pacific (Mumbai), India. Every workspace is created there, and its data stays there.
| Region | Status |
|---|---|
| Asia Pacific (Mumbai), India | Available. Every workspace is stored here. |
| Europe (Frankfurt) | On the roadmap. |
| US East (Ashburn) | On the roadmap. |
The region a workspace uses is shown in the app's top bar under Data region. It is fixed when the workspace is created and cannot be moved later.
How a workspace gets its region#
Today there is nothing to choose: new workspaces are created in Mumbai. When more regions are available, you will pick the region when you create a workspace, and each region's data will stay in that region. A company that needs data in more than one region will use one workspace per region.
If your organisation needs a region that is not available yet, tell us at sign-up or through support before you send data. Moving an existing workspace's stored data to another region is not offered.
What is stored where#
Everything below is in the Mumbai region (Oracle Cloud ap-mumbai-1 and Logthread's storage in the same region).
| Data | Where it lives | How long |
|---|---|---|
| Logs, traces and metrics you send | Logthread's telemetry storage, in a separate storage organisation for each workspace | Your plan's retention |
| Telemetry in transit | Logthread's ingest gateway and its queue. Large or delayed batches wait in a private bucket until they are stored | Until stored, then deleted |
| Accounts, workspace settings, keys (digests only), dashboards, alert rules, SLOs and the audit log | Logthread's control-plane database | While the workspace exists |
| Database backups | Daily backups of the control-plane database in a private bucket, plus a monthly disk backup | 30 days |
| Downloads (SDKs, agent, collector packs) | Public downloads bucket | Not customer data |
Telemetry is not copied to another region, and backups are kept in the same region. Logthread has no second region for failover today.
What leaves the region#
- Alert notifications go to the destinations you set up (email, Slack, Microsoft Teams, PagerDuty, Opsgenie, webhooks). Alert content is sent only to channels you configure.
- Email (verification, invitations, alert emails) goes through Logthread's email delivery provider. The Subprocessors page lists it.
- Pari, the AI assistant, runs on an AI service in Mumbai. It never receives your logs, traces or metric values. Owners can turn it off. See Pari.
- Exports and SQL results you download leave the region because you download them.
Your services can send telemetry to Logthread from anywhere. Enterprise workloads in Oracle Cloud Mumbai can also send it over a private network path that never crosses the internet; see Private ingest.
Related#
- Team, usage and billing: data protection, encryption and deletion.
- Subprocessors: the providers that process data for Logthread and where.