Understand Loom data residency

Loom data residency integrates with Atlassian's enterprise data residency framework, which enables organizations to control where their Loom data is stored and processed. The configuration of data residency occurs during provisioning of a net-new Loom workspace through the Atlassian Admin Hub.

Supported regions:

• Launched in May 2026: Germany (Frankfurt) and United States (Oregon)

Architecture: Loom uses a hybrid global edge and sharded system. The global edge handles authentication and routing, while regional shards store and process all customer content within their respective regions.

Data storage and processing

Data stored in your region

All user-generated content (UGC) is stored and processed exclusively within your selected region:

• Videos, comments, transcripts, and AI-generated content (summaries, text documents)

• ワークスペースの設定

• All editing artifacts and collaboration features

What remains global

Loom is designed so that your user-generated content (videos, audio, transcripts, comments, and AI-generated documents) is stored and processed within your selected data residency region. However, some limited data processing occurs outside that region to support global reliability, security, and account management:

• User data: User authentication and session management data, user settings, and preference data

• Organization membership: Enables workspace switching across sites

• Audit logs: Only IDs are stored, but no actual user-generated content (UGC)

• Cross-workspace features: Notifications, history, and watch later

セキュリティとコンプライアンス

Encryption and access controls

• In transit: All encrypted data uses TLS/HTTPS protocols

• At rest: Regional shard databases, media files, and storage buckets are encrypted using AWS encryption services

• Logical isolation: Customer data is isolated within designated regional shards with workspace-level authorization

• Access principles: Least privilege access, purpose limitation, and full transparency accessed through Admin Hub

Alignment with Atlassian standards

Loom data residency follows the same security frameworks, encryption standards, and operational procedures used by Atlassian cloud apps data residency. All implementations undergo Atlassian's standard legal, privacy, and responsible tech reviews. Understand data residency

Set up data residency

Data residency is configured during product provisioning through Atlassian Administration Hub:

For new Loom standalone customers:

1. Navigate to Atlassian Administration.

2. Select Apps, then Add app.

3. Scroll to Start with a single app, find Loom, and select Try it now.

4. Select Create a new site, and enter a site name. Select Agree and add.

5. Choose your data region (Germany or United States) from the Select data location dropdown menu. Select Continue.

6. To complete automated provisioning, stay on the loading screen until you are redirected to your new Loom space.

For Teamwork Cloud (TWC) customers:

1. Navigate to Atlassian Administration.

2. Select Apps, then Add app.

3. Under the Teamwork Collection card, select Try it now.

4. Select Create a new site, and enter a site name. Select Agree and add.

5. Choose your data region (Germany or United States) from the Select data location dropdown menu. Select Continue.

6. To complete automated provisioning, stay on the loading screen until you are redirected to your new Loom space.

View Loom’s pinned region

1. Navigation to Atlassian Administration

2. Select Data management, then Data residency.

3. From there, you can view Loom's pinned region.

重要な注意事項

Workspace availability

All core Loom features are fully supported with data residency

• Recording and editing: Pause, restart, delete, speaker notes, trim (waveform and transcript), effects

• AI features: Auto summaries, filler word/silence removal, document/bug report/message generation, multi-language transcription

• Collaboration: Sharing (public link, workspace, email), commenting, timestamp reactions, viewer analytics

• Content organization: Auto titles, Spaces, Folders, workspace management

Capabilities that aren’t supported

• Slack notifications: Slack connections to the EU workspace will enable limited functionality. Slack unfurls (previews) will remain functional.

• Mobile support iOS and Android: Users will not be able to access the European workspace or content until functionality is completed (est. May 11) and the customer is on the latest version.

• User transfer content: Users with workspace memberships between the European and US workspace will not be allowed to transfer content.

• Admin tools: Partial support (Video dives, user memberships, workspace dives) is available for admin tools, and ongoing tooling is being built.