Avid can host supported customer data and reporting in the United States, Canada, or Australia. This article explains where each region is hosted, what stays in-region, what broader security controls still apply, and current benchmark limits.
Use this article when
- You need to understand where Avid stores and processes data for your organization.
- You are evaluating Avid for a team with in-region data requirements.
- You are confirming what customer data stays in-region versus what uses broader platform resources.
- You want to know how benchmarks behave for regionalized organizations.
What regional data residency means
Data residency is the region where Avid creates and keeps supported customer data resources and reporting data for your organization. When your account is set to a region, Avid configures supported storage and reporting for that region.
Avid’s security controls apply in every region. Regional hosting does not replace encryption, access controls, or third-party audits.
Residency covers supported customer data and reporting. Some platform resources that are not customer data may still run as global or short-lived services outside your selected region.
Supported regions
| Region | Hosting location | Notes |
|---|---|---|
| United States | United States | Default region for most organizations. |
| Canada | Toronto, Ontario, Canada | Hosted in Ontario, which has the strictest provincial data rules in Canada. Choosing Canada covers organizations across Canadian jurisdictions. |
| Australia | Sydney, New South Wales, Australia | Same residency model as Canada, with hosting in Sydney. |
Avid may add regions later. Contact Avid during evaluation or onboarding if you need a region that is not listed here.
What customer data is handled in-region
When your organization uses a regional residency setting, Avid handles supported customer data and reporting in that region, including:
- Reporting and data storage: Datasets used for reporting and data processing are created in the selected region.
- Data sync infrastructure: Avid configures data sync destinations so integrated data flows to the in-region environment.
- Regionalized file storage: Regionalized file storage buckets use a region-based suffix tied to the account setting.
What is not covered by the residency selection
Residency applies to supported customer data and reporting. A few supporting assets and temporary files are not region-bound today. These are usually not donor records or other sensitive fundraising data:
- Image uploads: User profile images, organization logos, and photos are stored globally in Avid.
- Pathway result downloads: Temporary files created for Pathway status updates are not region-bound.
- AI organization context (sometimes called vector storage): Metadata about your organization, brand guidelines, and other AI instructions are not region-bound. Your donor data and other sensitive details stay in your selected region.
If your organization needs a complete country-only data boundary, tell Avid during evaluation so we can review your requirements.
SOC 2 and security documentation
Avid’s security controls apply across all regions:
- Data is encrypted in transit and at rest.
- Access controls restrict who can view or manage data.
- Avid holds third-party audits and accreditations, including SOC 2 Type II.
For the latest compliance documentation and the full Trust Center, visit trust.avidai.com.
Benchmark limitations
Regionalized organizations can still view the US-hosted benchmarks. Avid does not currently include regionalized-organization data in those benchmark pools.
Why: Avid needs enough in-region organizations to keep benchmark results anonymous. Until that threshold is met, contribution from Canada-hosted and Australia-hosted organizations stays disabled.
- You can still open and use the available US-hosted benchmark views.
- Your organization’s data is not added to the shared benchmark pool today.
- Avid may introduce separate regional benchmarks when enough organizations are hosted in each region.
Set this before data is loaded
Changing data residency after data has been uploaded or after non-file integrations are connected is constrained by Avid’s migration limits. Set residency during account setup, before any data is loaded.
To request or confirm a region, contact Avid during onboarding or account configuration. Avid can review your requirements and confirm whether your environment can use the selected region.
When to contact LockStep Support
Contact LockStep Support or your Avid rep when you need to confirm or change residency, or when a compliance review needs written confirmation of hosting location.
Include:
- Your organization name in Avid
- The region you need (United States, Canada, or Australia)
- Whether data or non-file integrations are already loaded
- Any compliance deadline or questionnaire you need Avid to complete