How to control data residency on Claude
Data residency on Claude is controlled through workspace settings where you can specify geographic regions for data processing and storage. Enterprise customers have additional options to configure data retention policies and regional compliance settings.
Prerequisites
- Claude Pro or Team subscription
- Admin access to your Claude workspace
- Understanding of data privacy regulations
- Knowledge of your organization's compliance requirements
Step-by-Step Instructions
Access workspace settings
Configure data processing region
US-East, EU-West, or Asia-Pacific. Click Save Changes to apply the new region.Set data storage location
Configure cross-border data transfer restrictions
transfer-policy to strict or flexible based on your needs.Set up data retention policies
retention-period value. Choose from options like 30-days, 90-days, or custom. Enable Automatic Deletion to ensure compliance with data minimization principles.Enable audit logging for data residency
1-year or 7-years.Review and apply enterprise controls
Verify data residency configuration
data-residency-test tool.Common Issues & Troubleshooting
Data residency settings are grayed out or unavailable
Verify you have a Claude Pro, Team, or Enterprise subscription as data residency controls require a paid plan. Check that you have admin permissions in your workspace settings under User Management.
Regional processing options don't include your required location
Contact Claude support to request additional regions or check if your region is covered under a broader geographic designation. Some locations may be available through government-cloud or special compliance tiers.
Cross-border transfer restrictions are causing feature limitations
Adjust the transfer-policy setting from strict to flexible in Transfer Controls, or whitelist specific regions for limited cross-border processing while maintaining compliance.
Audit logs are not capturing data residency events
Ensure Data Residency Logging is enabled in Audit & Compliance settings and that your log retention period is properly configured. Check that the audit-scope includes data movement events.